I applied online. The process took 3 days. I interviewed at Upsight (Toronto, ON) in Oct 2011
Interview
Day 1. Talk to recruiter for an hour on the phone.
Day 2. Talk to director for an hour.
Day 3. Do a 2-3 hour coding project pre-screen.
Day 4. Spent approximately 9am-3pm at the office, directly or video-interviewing with various stakeholders. Some kind of personality quiz. A second part to the coding project. Eat lunch and socialize with the office.
Interview questions [1]
Question 1
Lots of soft skill questions, questions as to how I feel about the business practises alongside the more standard technical ones. Nothing with a definite answer as far as I can tell, but gauging whether I am more than just a code-hand.
I applied online. The process took 2 weeks. I interviewed at Upsight
Interview
After applying got contacted by the HR person and she did a preliminary interview. After that she game me an assignment question to do which was a spreadsheet evaluator. Later I did another interview with a technical guy which was pretty straight forward with classic easy questions (I think it was palindrome). And another interview later by the hiring manager I guess (I don't remember the guy's title!)...
Interview questions [1]
Question 1
Nothing crazy really! Just normal textbook questions!
I applied through university. The process took 3 months. I interviewed at Upsight
Interview
I was contacted after my university's career fair.
Initial phone screen with recruiter, then two technical phone interviews with a third party company. These were pretty standard questions: OOD, inheritance & polymorphism, factory & singleton patterns, binary search, hash table basics.
Subsequent on-site interviews lasted one full day: Introduction to the product and architecture, 3 technical 1-on-1 interviews and 1 non-technical 1-on-1 interview. My experience with all of the recruiters, interviewers and the entire team was very pleasant.
Technical interview questions included: Design a bounded queue, sort an array in place, and a lot of architectural/design questions tied to prior projects, along with a discussion of performance and process tradeoffs among design choices.
After the interviews, there was a 2 hour coding project: write a program that reads a configuration of chainable filters from a spec file and applies it to a large amount of text. Interview questions and even the coding project were language-agnostic, which is nice and shows that this company is asking the right type of questions (ie, cultural+conceptual rather than encyclopedia questions about language-specific feature xyz). In the end of the day, we got to sit down with and talk to Jeff, Kontagent's CEO and founder, which was great.
Interview questions [1]
Question 1
"If you had $10m/unlimited resources, how would you scale your past project <xyz> to handle a huge amount of users" – this questions was unexpected more so than difficult, and led to an interesting discussion about design decisions.