Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

>"what's the coolest project you've worked on?"

This is the first question I ask followed by, "What's the worst project you've worked on?" The answers are pretty insightful.



That's a pretty good one. Tells you what their idea of a bad project is and how much professionalism they can maintain while describing it.

"They made developers write unit tests!!!" vs "There were some personality clashes which unfortunately impacted on the team's ability to collaborate effectively".


A huge amount of information can be uncover with “tell me about the highest performing team you’ve been on? Lowest performing?”


“Ok, so the schema control tool we were using generated XML that SVN had a hard time merging correctly. We ended up with so many broken commits that we invented the Lock Rock. It was a rock that I picked up in the parking lot and you were only allowed to commit schema changes if you were in possession of the rock.”


I'm trying to install a webhook in TeamCity to send a notification to Slack whenever anyone across 16 time zones commits to specific paths in a Perforce depot.

I'll happily trade for your rock.


My new product idea: ~LockRock~ Mutex As A Service! Only $3/month/user subscription!


100% yes. The reaction to that question will tell you a ton about a candidate.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: