3 ms·
Hopefully someday I'll be such a sought-after resource that I could grill a company in the way this post suggests. As it is, I choose my interview battles care
by loteck 9y ago
Hopefully someday I'll be such a sought-after resource that I could grill a company in the way this post suggests.
As it is, I choose my interview battles carefully. One of my favorite questions I ask is whether my position is new (rare for my situation) or if I am replacing someone who left.
This very naturally opens up a conversation about expectations from both sides. If someone separated, why do the interviewers think it didn't work out? If this is a new position, how do they imagine the first year?
Suddenly you're talking about culture, performance and policies without having asked directly about any of those topics.
- dogruck 9y agoThat's truly a brilliant variant of "What will it take to succeed in this role?" Fantastic!
- arielm 9y agoI (founder) actually love hearing these types of questions because they convey actual interest. However, by no means am I saying ask for the sake of asking because I’ll read through that and will probably try to turn it into a conversation you’d be expected to participate in ;)
- AdamJacobMuller 9y agoSame here. Very often it's the questions the interviewee asks in the interview that make my mind up on a hire/pass decision.
- malyk 9y agoThis one is a killer. When I talk to candidates in an interview we do a 30ish minute problem and then you get 30 minutes time to ask anything you can think of with your potential boss. So many people have no questions. You really don't care if we don't use source control, do waterfall development, make people work 14 hour days, or code in pascal? (None of that is true, but if you never ask...)