Live data from Hacker News

Worst interview questions for software developers

fibery.io

11–20 of 253 posts

Re: Worst interview questions for software developers

#11
post #7

>4. Why do you change jobs so often (so rarely)? Am I wrong to think this seems at least somewhat reasonable? Like obviously it's annoying to explain yourself, but it takes time to on-board someone and for them to become productive and it seems reasonable to want someone to stay on long enough for that at least. This naturally applies less to those super engineers you barely need to train and have obvious experienced…

A short job or two, fine, but at a certain point it’s a pattern that needs a reason. If the reason is “my spouse was in the military and we moved around a lot for that, but we longer do”, that’s fair enough. If the answer is that you weren’t happy enough at your last jobs to stay for more than 12 months, then why should I think you’ll be any different at your next job?

My wife had really bad luck with her first three jobs: the offices would just up and close a year or so after she started (this included a Nokia office because of the Microsoft merger). But she would still have to frame her answer in a way that didn’t give vibes that she was cursed.

Re: Worst interview questions for software developers

#12
I'll mention one which I've had which I considered bad. Worse than most on the linked list IMO.

The question was "What is the worst challenge you've faced, and how did you deal with it or overcome it?" and on me asking if it should be work related, "it doesn't have to be work related".

I can't remember whether the wording was exactly "hardest challenge" or "worst problem" or "most difficult challenge", but it used an absolute term (worst/hardest/most, not "a difficult challenge" or "a time in which you faced..."), and it was certainly very close to one of those.

I think that most people's hardest challenges in life are things like "my parents passed away" or "I came out as trans, and my parents disowned me, and I've had to come to terms with that" or "I had a divorce".. basically, interpersonal relationship experiences which really aren't very work relevant.

The use of "hardest" also makes it feel like you're lying if you go for something less serious, but work related.

I brought up a non-work-related rough time in my life from years ago, which still easily stood out as the most challenging time in my life, and then specifically asked again "this doesn't seem work relevant, should I choose a less serious work-related challenge?" and the interviewer asked me to continue with my non-work relevant one (i.e. asked me to relive some trauma).

It soured the experience massively for me, I had to try and disassociate some to avoid crying, and all in all it was the least comfortable I've ever felt in an interview. I can't imagine what signal that gave them.

That somehow also didn't disqualify me since I still got an offer, though I of course declined it.

Anyway, the company was osohq. I hope they don't ask this question anymore, but I guess prepare a story just in case if you do interview there.

Re: Worst interview questions for software developers

#13

>4. Why do you change jobs so often (so rarely)? Am I wrong to think this seems at least somewhat reasonable? Like obviously it's annoying to explain yourself, but it takes time to on-board someone and for them to become productive and it seems reasonable to want someone to stay on long enough for that at least. This naturally applies less to those super engineers you barely need to train and have obvious experienced…

No, you're not wrong, and are even downplaying how seriously disruptive a serial job hopper is to a company. I have without regrets red-flagged numerous well-qualified candidates who were an obvious flight risk at the companies I have worked at, which were always smallish. Now that big tech is contracting its ranks somewhat, this behavior is going to be even more suspect, because they will not have that refuge so easily, and I think it's for the best that we have more pressure to curtail it industry wide.

I don't begrudge people for having good reasons to justify their job switches (e.g., wanted a manager role, and was told none would be forthcoming in the future), but e.g. "I got bored doing React and I wanted try Vue on the MEAN stack" does not bode well for the projects left in the lurch when he gets bored at my workplace.

Re: Worst interview questions for software developers

#14
post #7

>4. Why do you change jobs so often (so rarely)? Am I wrong to think this seems at least somewhat reasonable? Like obviously it's annoying to explain yourself, but it takes time to on-board someone and for them to become productive and it seems reasonable to want someone to stay on long enough for that at least. This naturally applies less to those super engineers you barely need to train and have obvious experienced…

A short job or two, fine, but at a certain point it’s a pattern that needs a reason. If the reason is “my spouse was in the military and we moved around a lot for that, but we longer do”, that’s fair enough. If the answer is that you weren’t happy enough at your last jobs to stay for more than 12 months, then why should I think you’ll be any different at your next job?

You'll never hear the real reason. So if you have an issue with this fact, don't invite the candidate to an interview. If you don't have an issue with it, then why ask? They'll never say "because I'm constantly looking for better opportunities and will jump ship when I can".

This is what most of those questions on the list have in common: both sides of the table know that the answer will be contrived BS. They are a waste of everyone's time.

Re: Worst interview questions for software developers

#15
post #7

Earlier quoted context omitted.

A short job or two, fine, but at a certain point it’s a pattern that needs a reason. If the reason is “my spouse was in the military and we moved around a lot for that, but we longer do”, that’s fair enough. If the answer is that you weren’t happy enough at your last jobs to stay for more than 12 months, then why should I think you’ll be any different at your next job?

My wife had really bad luck with her first three jobs: the offices would just up and close a year or so after she started (this included a Nokia office because of the Microsoft merger). But she would still have to frame her answer in a way that didn’t give vibes that she was cursed.

No one would blame her for the closing of the whole branch. That's kind of the best possible answer.

Re: Worst interview questions for software developers

#16
post #7

Earlier quoted context omitted.

A short job or two, fine, but at a certain point it’s a pattern that needs a reason. If the reason is “my spouse was in the military and we moved around a lot for that, but we longer do”, that’s fair enough. If the answer is that you weren’t happy enough at your last jobs to stay for more than 12 months, then why should I think you’ll be any different at your next job?

My wife had really bad luck with her first three jobs: the offices would just up and close a year or so after she started (this included a Nokia office because of the Microsoft merger). But she would still have to frame her answer in a way that didn’t give vibes that she was cursed.

I've seen some resumes/linkedins that put reasons for why they left the job in similar situations. Acknowledging stuff like that is a good way to get ahead of questions.

Re: Worst interview questions for software developers

#17

Depending on where you are, questions 1 and 3 are just straight up illegal. No interviewer in the US would dare ask about vices or your family situation unless they don’t mind shelling out lawsuit settlements to everyone they interview and decline to hire.

I have sat across from recruiters at a previous job, in California of all places, that would quite frequently ask these very questions. The question is, how would you prove you were asked these questions if you were being interviewed in a state that has 2 party consent laws for recording?

Re: Worst interview questions for software developers

#18

>4. Why do you change jobs so often (so rarely)? Am I wrong to think this seems at least somewhat reasonable? Like obviously it's annoying to explain yourself, but it takes time to on-board someone and for them to become productive and it seems reasonable to want someone to stay on long enough for that at least. This naturally applies less to those super engineers you barely need to train and have obvious experienced…

No, you're not wrong, and are even downplaying how seriously disruptive a serial job hopper is to a company. I have without regrets red-flagged numerous well-qualified candidates who were an obvious flight risk at the companies I have worked at, which were always smallish. Now that big tech is contracting its ranks somewhat, this behavior is going to be even more suspect, because they will not have that refuge so eas…

How short is short in your opinion?

Re: Worst interview questions for software developers

#19
post #7

Earlier quoted context omitted.

A short job or two, fine, but at a certain point it’s a pattern that needs a reason. If the reason is “my spouse was in the military and we moved around a lot for that, but we longer do”, that’s fair enough. If the answer is that you weren’t happy enough at your last jobs to stay for more than 12 months, then why should I think you’ll be any different at your next job?

You'll never hear the real reason. So if you have an issue with this fact, don't invite the candidate to an interview. If you don't have an issue with it, then why ask? They'll never say "because I'm constantly looking for better opportunities and will jump ship when I can". This is what most of those questions on the list have in common: both sides of the table know that the answer will be contrived BS. They are a w…

Not everyone is a serial liar, don't assume people can't give real reasons for deficiencies in their resume.
Post reply on HN