Yeah. I attended attended a talk. The Salesforce employee, her name is Kate Gentry. I believe she's a director now on the release management team. She had given a fabulous talk about release management, and drones were involved. There were a bunch of really great metaphors, that was good for me as an undergrad student, not understanding, first, what Salesforce was, second, what tech was, and third, what release management was. So, having her ... Going to her talk at Grace Hopper gave me a lot of insight into what the role was, what Salesforce was, and then what kind of people worked at Salesforce.
She was super kind, and then when I met her at the booth later for an informal interview, again, I was just like super kind. I knew that not only was it going to be a place I would be interning, it's a place where I would be mentored.
Half of my time was spent on doing that. Release management, that's making sure that code is in a good state to be released to production, and then after you release it to production, it remains healthy. If things hit the fan, then you're the one that gets called, and you need to be able to lead people out of that mess. That's what I was being trained on, my entire internship by a phenomenal team. I was running a weekly patch release of the entire Salesforce application that goes out to hundreds of thousands of customers and I was able to stamp my name on that.
That was a really cool big part of my internship that I'm proud of. Another side project I was doing on the internship, when I wasn't doing release management, was working on a software engineering project. I am a computer science major, even though that's not what I do now, that is something that I wanted to keep my feet wet with as an intern. That project, it started by picking something off of the backlog of the tools team, but after I'd been there a couple of weeks, I did not want to work on that. I'm super stubborn, and I think all my managers up to this point are familiar with it, but if I don't want to work on something, I'm going to find something that I can add value by working on it.
Yeah, there's so many things. I'll try and keep it short. I think, first, the career fair. Interview slots generally fill up by day one, so make sure either you go and talk to the companies you want to talk to immediately, or you have done it before Grace Hopper. The second thing is figuring out a schedule. You can pick the talks you want to go to, but two things to be wary of is location. Where ... Are you going to be running across the convention center and be late to talks and not get seats? Then the second one is: Are there going to be seats open? A lot of times, especially as Grace Hopper grows, the more popular talks will be at capacity even before the talk starts. So having a backup plan of two or three other talks you want to go to is really gonna help maximize your trip.
Then finally, networking. It's really tempting, especially if you go with a friend to grab lunch with them. But I challenge everyone to: Don't go get lunch with your friends. Sit down at a random table, introduce yourself. I ended up sitting next to, I think, a VP at Yahoo when I was a sophomore, and ended up getting her business card and an opportunity there. You never know who you're going to meet. The question I always asked, how did you get where you are today? Where I was at Grace Hopper, I had no tech background. I wasn't sure if I was going to declare a CS major, but I would hear so many stories from women who hadn't been coding since they were 12. They made a career change after they had kids or something crazy, and that's really what gave me the motivation to pursue tech, those tiny conversations.