|
|
|
|
|
by cmh89
1056 days ago
|
|
> If you can describe the day-to-day of what we do without much prompting that's a very strong signal you're a good fit Why not just ask that then? "Tell me about yourself" is just a bad open-ended question. I've been in enough interviews to anticipate generic bad questions like that or "what's your biggest weakness" style questions, but not everyone has. Hiring managers frequently can't differentiate between people who are knowledgeable and people who are just good at interviewing. I've coached many of my peers and done lots of coaching with success because at the end of the day, interviews are about taking advantage of the information asymmetry between your actual experience and what the hiring manager can actually know. |
|
Because that's not all I want to know. I want to see the first things that surface in their mind and what they enjoy talking about. It's not a trick question and the only wrong answers are very clearly wrong sometimes even to those who don't work in software.
> Hiring managers frequently can't differentiate between people who are knowledgeable and people who are just good at interviewing.
I don't agree with this at all. We don't have "hiring managers". That's the problem right there. What the hell are they going to know about the position if they're not in it?
The developers have always done the interviewing of candidates at every place I've worked. We know exactly what to ask and what technical answers actually indicate they can get the job done. It's not hard to know what to ask when you actually do the job you're interviewing someone about.