Timeline for Good interview programming projects
Current License: CC BY-SA 3.0
13 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 15, 2016 at 15:51 | history | edited | RDL | CC BY-SA 3.0 | Addition describing new hiring process |
| Oct 29, 2014 at 21:46 | comment | added | RDL | @ChuckCottrill It doesn't b/c they are not brought to the board room until 15 minutes before the interview is to start. We have also shortened the questions down to 3. If they can't some up with something for each in the 15 minutes then they likely aren't a good fit for us. | |
| Oct 29, 2014 at 0:32 | comment | added | ChuckCottrill | Some job search sites suggest that you arrive no more than 15 minutes early, suggesting that early arrival interrupts the interviewer. Your pre-interview quiz rewards people who did not follow that courtesy suggestion... | |
| Mar 18, 2011 at 18:03 | comment | added | RDL | @pdr, touche! I definitely agree there! ;) | |
| Mar 18, 2011 at 18:00 | comment | added | pdr | @RDL, Most of our interview process is designed to be kinda fun to the kind of developer we're looking for and hell for the rest. You know how good devs can't resist a challenge. | |
| Mar 18, 2011 at 17:50 | comment | added | RDL | @pdr, wow, a 4-stage interview process for people right out of college? I have only ever been in two stage ones myself. How do you find it works for you? For the record, I have also done 'small projects' in the past for potential employers. They are a good way to weed people as long as the interviewer knows what they are talking about to be able to spot the posers. Good luck in your search. | |
| Mar 18, 2011 at 17:43 | comment | added | pdr | @RDL, I take your point, and if it was the only part of the interview process, I might agree. But we're pretty vigourous with an easy online test, a tough phone interview and a much tougher face-to-face interview before we ever get to that stage. The guy you're talking about isn't getting to our final interview. | |
| Mar 18, 2011 at 17:34 | comment | added | RDL | @pdr, agreed, but someone could explain the code to them so they know what they are talking about that. In that case it would be needed to provide another example for them to look at discuss during the interview. I once worked with a guy who taught programming at the college level but asked me one day 'Can an if statement be inside the else part of another if statement'! No joke! | |
| Mar 18, 2011 at 17:32 | comment | added | RDL | @John. Agreed, it can't be "oh, you forgot a comma there". As I mentioned it is to get an understanding on how the approach things and if they understand the language. If they know their stuff definitely move on to the bigger things. | |
| Mar 18, 2011 at 15:50 | comment | added | pdr | "Allowing someone to do a practical project on their own time doesn't necessarily mean it is them who does it" - True, but I've not yet come across someone brave enough to come into an interview and be questioned on code they haven't written. Should it happen, they're not going to get through the interview and their probation, but I may reconsider my approach. | |
| Mar 18, 2011 at 15:49 | comment | added | John Nicholas | although i have been in many interviews that turn into trivia. Be careful not to get bogged down on this particular bit of sysntax and get onto their large scale understanding. Especially if they are alleged to have a bit of talent or interest. the result was i didnt want to work for them, and im sure it was mutual. | |
| Mar 18, 2011 at 15:41 | comment | added | davidhaskins | This is sort of brilliant. I like it! | |
| Mar 18, 2011 at 15:01 | history | answered | RDL | CC BY-SA 2.5 |