If you haven't heard about the site, glassdoor [ Link to glassdoor for SOE ] is a great place to get relative information about a company and even some interview questions.
So it's been a really long time since I've interviewed for anything, let alone an adult job (I've been a system admin / software developer in the same place for 7 years), but I recently graduated with a BS in CS and have started half heartedly applying to a few places. I got an email yesterday from Sony Online Entertainment asking to setup a phone interview with me this week to work on Everquest Next.
Anyone have advice / tips / experiences with SOE (or general) phone interview process?
Never wear pants when on a phone interview. It's very liberating.
Practice phone interviews with other people or even just by yourself. I hate phone interviews but it's important to be good at it.
I recently interviewed and accepted an offer for a 'Software Engineering' position for one of the top 10 paying tech companies mentioned at http://www.bizjournals.com/dayton/bl...y-company.html. So it was pretty competitive... The interview process consisted of a 1hr phone interview and then 9 45min in person interviews. Luckily they paid for me to stay in town for a few more days to recoup and enjoy myself =)
To help prepare for software development interviews in general, I highly recommend http://www.amazon.com/Programming-In...dp_ob_title_bk I've had job offers from multiple tech companies that are in that top 10 list and every one had questions that had some ties to that book. I think it must be required reading for many =) Glassdoor is also a great resource to get a feel for what to expect.
For the phone interview, my guess is it will partially be them explaining the position and is a great chance for you to be asking questions to show interest if you have any. Some basic language/os trivia like questions would be expected. How does a memory leak occur? Why would you use a virtual function? type questions. Some short answer questions like explain the most challenging project you have worked on. Explain a time when....
For more challenging questions that come up for regular interviews, I would say there is a balance between checking your competency and also getting you to your breaking point and seeing how you deal with challenge. Getting the right answer is a small part of being successful. The key is explaining your approach and your thought process when you do get stuck on something. When it comes down to it, you are going to face a problem at work you don't know how to solve immediately, but do you have the mindset to seek a solution? Then you have the behavioral type questions, how do you deal with an argument,stress etc.
For regular interviews, I'd say don't be afraid to "fail" either, obviously TRY to succeed, but if the problems above your head, don't just flail around.
Well normally I can jump through all the silly hoops, I've been hired on twice after working on the problem for an hour and just telling the interviewer "I've reached the limit of what I can do without consulting someone else or doing additional research", knowing when to ask for help is typically seen as a positive trait. ymmv.
Since you've already gotten lots of great advice, I want to add that if you get this job I will hold you personally responsible when EQ Next inevitably turns out shitty.
Thanks for all the responses. Hopefully it goes well, but after going through the glassdoor site and reading what a lot of people have to say about working for SOE, I'm not quite as enthusiastic as I might have been. Sounds oh so lovely of an atmosphere there /eyeroll
One thing to keep in mind is that there are only 3 software engineer reviews there, so its hard to get a good perspective. Different job roles are going to have a different experience. And even the same role but on a different team will have a different experience.
My advice is to not be a programmer at SoE
Bnet - istrtedajoke#1960
steam- old gregg
You may have already checked it out, but EA has a new grad SE position open in SLC if that's where you still are. The master's program at the UofU for game design is also well respected if you want to do that after getting some experience. I know people that have gone through the program and they work with EA as part of their program and really enjoyed working there. Have you done much game development already? Playable games? I'm not sure where you graduated from, I know the UofU undergrad program has courses that have you work on a team to make a game. I was part of some group interviews for a game company I worked for for a year or so and for me it was important to see the candidate was a programmer that enjoyed gaming, or someone that enjoyed game programming.
Now I'm hiring for a QA Engineer position for a .NET environment in the SLC area. Another area that takes a particular mentality to excel that not all developers have. With your experience, maybe you already know where you fit in. If you are applying to a job that doesn't match your current role, I think its important to point out in a cover letter/interview that you are interested in the transition and why. I'm more likely to toss a resume if their history doesn't match the position even if it looks like they have good skills in the past because I feel like they just spammed a bunch of sites with their resume and might not be likely to stick around.
I'll look at the EA thing.
Not sure if you've already interviewed, but I went through a LOT of interviews last year.
Come up with several work/school related stories, the more recent the better, about things that can cover a few topics. Like, have a story about teamwork and how it went well/bad. Use that as your go to story for any similar questions if you can. I had a similar amount of experience as you (8 years), and so it was good to have some things prepped in my head. And even better, for phone interviews, you can write out reminders for your stories.
Also come up with some questions about the company. Remember it's also an interview for you to see if the company is somewhere you'd like to be. Everyone says to ask them because it shows that you care, but I think it's more important to get a feel of their environment or the type of work. You don't want to get stuck somewhere that's a terrible fit because you didn't ask any questions.
Last edited by Elurin; 06-20-2013 at 03:51 AM.
There are currently 1 users browsing this thread. (0 members and 1 guests)