A list of things to keep in mind on the next interview.
- Ask to see a portfolio, if not available online
- Ask to see some of the code of the best/lead developer, this will be the best expectation
- Ask to see the version control log and unit test log, dont fall for ‘yes, we have/do that’
- Ask that the best/lead developer be present at the interview
- Make sure the best/lead developer is better than you, else you will be doing his job
- Ask to see some run of the mill code, any random snippet
- Ask them to be very precise on the responsibilities of the applied position, make them contractual
- Ask to look at their DB structures
- Ask to see architectural and design documentation
Once done with the above list, and you are happy, proceed with a normal interview, else say “thanks, but not interested”.
Here’s a nice link about those pimps!
A good thread on StackOverflow about warning signs
The Manager FAQ (good read for managers, and those being managed)
Have you ever participated in such kind of interviews? I think you should be very brave to ask all these questions.
By: Djuffin on October 22, 2008
at 9:58 pm
No, that’s why I am making a list
I always forget.
I do agree it is brave to ask such questions, but IMO you have the right to do so. If they refuse without a valid excuse, alarm bells should sound.
By: leppie on October 23, 2008
at 8:30 am
Sounds like a great way to be on the dole queue for a while.
By: Jack on October 23, 2008
at 11:40 am
Maybe, but I’ll rather be unemployed than have to work at some place that gave you a false impression. Actually, if it’s really bad, I guess you would have some legal grounds to dismiss any contractual obligations.
By: leppie on October 23, 2008
at 12:13 pm
[...] posted this great interview checklist. I’m mirroring it here so that I will always have a [...]
By: A programming interview checklist | Wisdom and Wonder on October 24, 2008
at 8:29 pm