Developer hiring and the market for lemons http://danluu.com/hiring-lemons/
-
-
What data/evidence do you use to differentiate between "doesn't currently have the skill mix to be sufficiently productive" and "we sucked at helping the person ramp up"? The onboarding status quo is very, very bad almost everywhere.
-
In interviews, I ask about hires that don't work out. Common answer: "They would sit at their desk, not ask for help, and produce almost no working code. They weren't a culture fit because they obviously weren't trying."
- 9 more replies
New conversation -
-
-
The worst I've ever been at my job was at a company where I aced the very technical interview, but it turned out that the skills they actually needed were the ability to navigate a large anarchic team and juggle a dozen projects at once because the cycle time on each was so long.
-
...but I'm really not sure how you interview for either of those skills without letting people know that they should run a mile.
- 2 more replies
New conversation -
-
-
How did you end up on such bad teams? Bad luck? Misleading pre-job communication? Other considerations made the teams actually good, and the bad qualities you mentioned are just part of the story?
-
Maybe I just have unlucky friends, but when I compare notes with friends, I don't seem to have had unusually bad luck. No VCS sounds off, but it was an FPGA team and I've heard of similar from other FPGA teams. 75% turnover is a lot, but it's not uncommon to hear about 50%, etc.
- 2 more replies
New conversation -
-
-
Define simple. I've been given programming tests that have:
- 1 more reply
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.