World Wide Technology Developer interview questions

I received an email inviting me to submit a resume, and shortly thereafter got offered a phone interview. A few days later I was invited to come to Asynchrony's Springfield office for an in-person interview. The interview lasted about three hours, and consisted of two main parts. In the first, I was interviewed by two of the more senior developers, who asked me a variety of questions about my experience and software development in general, as well as giving me a detailed explanation of how development works at Asynchrony. The second part consisted of a paired-programming session, which involved solving a rather simple but interesting puzzle, presumably to see how I did in pairing and to verify I wasn't just blowing smoke. Think code golf without the golf. I also got a feel during this time for what sort of coding style they prefer to work with, etc.

I was first contacted by an Asynchrony recruiter and given a quick phone screening. We discussed my background and the culture of the company and what I was looking for in a company - standard questions, nothing really technical. The next step was filling out a technical skills sheet and you may be asked to submit some sample code. I didn't have to submit sample code but a couple of my colleagues did. After a week or so I was invited to an onsite interview and given a tour of the building. The first part of the interview will typically be a discussion with peers of similar background and skill sets. There were some technical questions, but it's more of an interview to find out if you're a good fit. As for the technical questions, if it's on your resume be prepared to talk about it. You won't be quizzed on everything and it won't be technical trivia questions but more focused on finding out if you know about what you claim to know and can communicate that effectively (open-ended questions like "What have you done in Angular?", "How have you used JavaScript?"). After an hour or so I was paired with another developer for a pair-programming exercise geared towards your technical background. This will take approximately an hour. You may or may not finish the exercise. My impression was that they were looking for someone who would be a good fit for pair programming because that's how software is developed here. Don't sweat it if you stumble a bit here and there. You mostly need to be able to communicate effectively and demonstrate that you can work with your partner and share your thoughts on how to approach solving the task at hand. The tasks are not that difficult and mostly designed to let you show how you tackle things. Yeah, if you say you can do ASP.NET MVC and don't know how to use a controller class then you'll have problems, but be confident in your abilities and have fun. It should be an enjoyable experience. After it's all done you should get feedback within a week if not sooner as to whether you'll get an offer or not.