3 ms·
Over reasoning? Because I ask a developer what they want to work on during an interview? Guess what, turnover is high when your developers are unhappy with the
by tinco 4y ago
Over reasoning? Because I ask a developer what they want to work on during an interview? Guess what, turnover is high when your developers are unhappy with the work they're doing. I've had developers do work that they didn't like to do, and they quit, so now I make sure they're gonna be happy where I want them.
I'm not second guessing anything, in fact my comment says the exact opposite. If a developer reworks their LinkedIn to highlight some expertise they're interested in working on, then I fully trust them on that and will gladly hire them.
I'm not sure where your whole angle of not trusting developers to know their own happiness comes from. But let me be clear, if you're a generalist with relevant experience I will definitely ask you to come over for an interview. I'm not throwing valuable resumes in the trash. But during the interview I will be frank about what the job entails, and I'll gauge your response to figure out if you'll be content. Whether I'm effective or not I don't know, but I'm going to have to at least try to get the right person at the right position.
edit: BTW I'm not just saying this as a CTO at a small startup, I'm also saying this as a generalist with highly valuable frontend skills and I pray to god I don't have to get into another frontend job (either directly, or by being lured into it after applying as a generalist).
- b112 4y agoWell, rereading your original comment again, I see the second paragraph could be taken in the way you mean in your reply. I think paragraph 1 and 3, sandwiched around 2, created an effect of negation. So thanks for the clarification, and thanks for returning my goat.
- tinco 4y agoMy pleasure brother. Hope no one will be throwing either of our resumes in the trash.