I applied through a recruiter. The process took 1 day. I interviewed at Quantitative Risk Management (Chicago, IL) in Mar 2011
Interview
Very well-structured in-person interview process. First was code review of my solution to a problem they had given me. The reviewer drilled into areas of the code where he felt exposed an incomplete grasp of the technical details; very nit-picky things. This was to see how I handle negative feedback, and also how well I could learn new information.
Second interview was with the company owners. They weren't told really who I was or what I was interviewing for, but were there just to give their blessing on any new hires. I had a prepared question on the topic, and that got them bouncing ideas back & forth.
Third interview was with two developers who would be my peers, just to see how I got along with them.
Fourth interview was with two project managers who wanted me to present my design at a high level to see if I could get out of the weeds and talk at a business level.
Fifth interview was with the architect, and was the mirror image of the code review. Rather than go into what I didn't know well, he asked me what my best language was, and we dove deep on that language, even though that wasn't the language I would be expected to know in the position.
I was very positive leaving the interview, but was not offered the position, because I have & communicated aspirations above the position I was interviewing for.
Advice to interviewees: They are not interested in helping you grow professionally. They want to hire you for a job and have you stay in that job as long as possible. If you're interviewing for receptionist, tell them answering phones is what you live for and you can't think of anything more fulfilling.
Interview questions [1]
Question 1
Write one line of C++ which will output the reverse of a string input.
I applied through a recruiter. The process took 1 week. I interviewed at Quantitative Risk Management (Chicago, IL) in Feb 2014
Interview
Had a phone interview with team lead and a developer. Reasonable questions, overall positive. Next step was a Java programming test. Completed the test and was informed that it did not meet expectations. Tried to get some comments on what they didn't like, but no answer to my email.
I applied through a recruiter. I interviewed at Quantitative Risk Management (Fort Wayne, IN) in Feb 2013
Interview
It was a standard interview. Normal question answer sessions with pairs of interviewers. It was not unlike other typical industry interviews. There was a programming test. Just make sure you know your OOP and the microsoft stack and you'll do fine.
Interview questions [1]
Question 1
They asked about design patterns. Nothing out of the ordinary.
I applied through college or university. The process took 1 day. I interviewed at Quantitative Risk Management in Apr 2011
Interview
It was an average interview, with the interviewer asking some general questions about my background, why I am interested in the position and how my skills fit in. I was asked a few questions on object oriented programming. The interview lasted around 35 minutes. QRM employees do not seem to be very cheerful.
Interview questions [1]
Question 1
What are some of the advantages of OOP, in your experience?