Jerks come in all sizes.
I started with a SQL question. He said "that's a dumb question."
31–40 of 67 posts
Re: I started with a SQL question. He said "that's a dumb question."
#32Asking dumb questions has become one of my moves in interviews. This is to expose LLM users, as LLMs are extremely unlikely to answer a "how do I do X" question with "you shouldn't do X", or "how would you replace Y" with "you should keep using Y". I guess now I have an additional reason to ask, so that I can screen out the assholes that will say it's a dumb question...
Last time I said "you shouldn't do X" in an in person interview, I failed and the feedback was "candidate was not cooperative with the interviewer". So even if the candidate is not using an LLM, the interview process is so messed up now that people willingly go along otherwise they may be rejected for, you know, actually stating what their experience was like. Funnily enough, that was a YC funded company that I was i…
I wonder if the pushback is more of a common reaction from more junior interviewers or once that aren't very empowered and just need to go down a script and worry about getting in trouble if they deviate.
Re: I started with a SQL question. He said "that's a dumb question."
#33Honestly if I was interviewing, even if you told me the future and this was the outcome of hiring the guy, I still wouldn't hire him. It's clear he's brilliant, and experienced, and seems like he's just refusing to "play the game". Speaking truth to power works if you know when to also NOT do it, or how to do it in a way that gets people to listen. It doesn't really matter how brilliant a guy is; if he's not capable…
Re: I started with a SQL question. He said "that's a dumb question."
#34I'm surprised they didn't follow up with "why it that a dumb question?" It would likely lead to an interesting answer on its own, in the context of the interview.
Re: I started with a SQL question. He said "that's a dumb question."
#35Maybe I’m not reading the post right but the dude sounds like a dick? What am I missing here?
For example, say I was the interviewee and actually said of the SQL question: "Well, to be frank, that question isn't so good for understanding my SQL abilities." I don't think that would be rude or evidence of "being an asshole". A retelling of that story may simply be condensing it down to how that statement was interpreted: as a nice way to say, "that's a stupid question".
We shouldn't get too far into parsing what's in the story as a verbatim telling of what happened. We have the author's impressions of those events and their interpretations of the outcomes to drive home a larger point the author wants to make. That's it.
Re: I started with a SQL question. He said "that's a dumb question."
#36Honestly if I was interviewing, even if you told me the future and this was the outcome of hiring the guy, I still wouldn't hire him. It's clear he's brilliant, and experienced, and seems like he's just refusing to "play the game". Speaking truth to power works if you know when to also NOT do it, or how to do it in a way that gets people to listen. It doesn't really matter how brilliant a guy is; if he's not capable…
Being kind and knowing how to deliver disagreement in a constructive way is important. Human beings aren’t perfect logical subjects immune from emotion (thankfully). Hopefully a good manager can take steps to address this or help mediate conversations where such a person might struggle. But places where “playing the game” (like withholding valid concerns with a decision) is a criteria for success are not long for thi…
Re: I started with a SQL question. He said "that's a dumb question."
#37Calling someone a "disagreeable asshole" just for saying that something is a dumb question is a bit strong. So he went out for challenging management on an internal document and he was 100% correct according to that tweet. Seems to me that the actual assholes are still employed in that company. Perhaps he was just hired to fix the mess. Once the job was done, he was no longer needed.
Being an “asshole” relates to inter-personal relationships, it has nothing to do with facts or correctness.
Re: I started with a SQL question. He said "that's a dumb question."
#38They loved his attitude when it challenged broken systems, but the second he aimed that same energy at management's BS, he was out. Makes you wonder... is "culture fit" just code for "won't call out your boss"?
Re: I started with a SQL question. He said "that's a dumb question."
#39Asking dumb questions has become one of my moves in interviews. This is to expose LLM users, as LLMs are extremely unlikely to answer a "how do I do X" question with "you shouldn't do X", or "how would you replace Y" with "you should keep using Y". I guess now I have an additional reason to ask, so that I can screen out the assholes that will say it's a dumb question...
Last time I said "you shouldn't do X" in an in person interview, I failed and the feedback was "candidate was not cooperative with the interviewer". So even if the candidate is not using an LLM, the interview process is so messed up now that people willingly go along otherwise they may be rejected for, you know, actually stating what their experience was like. Funnily enough, that was a YC funded company that I was i…
Re: I started with a SQL question. He said "that's a dumb question."
#40If I were on the board / an investor of the company, I’d let the managers go and hire back that engineer. The goal of a company is to serve its customers and make a profit, not stroke managements egos. And it sounds more like this guy pointed out what was wrong and maybe embarrassed people, but that doesn’t make him an asshole. It’s one thing to be mean or call people names, that’s an asshole. But this guy was an “as…
It’s never a good idea to make someone feel extra embarrassed for an error. That’s how you get them to loathe you and to make them hide future mistakes from you.