4 ms·

As a hiring manager or company owner (I wore both hats) I developed a routine during the interview that basically leads to a breaking point. I want to either d

by zeroq 2y ago

As a hiring manager or company owner (I wore both hats) I developed a routine during the interview that basically leads to a breaking point. I want to either drill down your bullet points to find out if you're actually an expert in XYZ as the resume claims, or work with you on a coding problem that's simple to understand yet more complex than leetcode challenges. I don't expect you to ace, but I want to check if you're honest and willing to admit your limitations - my philosophy is that I hire humans, not compilers, no one knows how everything, and I'd rather have someone who's fast finding correct answers on the internet than someone who had memorized a book. That's how I like to do it. Its been so long that I don't even remember when I myself was treated this way during an interview.

ericjmorey 2y ago
You're not filtering on honesty, but desperation. The desperate will lie because of the higher stakes for themselves.
- nusl 2y ago
  I dunno. If your immediate response is to lie rather than admit that you don't know something, it increases the probability that this is the person's default response when in such a situation. You don't want that person working for you if you depend on them for critical stuff, like many development or similar positions. If you've ever worked with someone like this, you'd know that it's frustrating and unpleasant mid-to-long-term. Someone breaks prod and refuses to admit it unless given a commit as evidence and a confrontation rather than owning up and fixing/helping fix it? Pretends to know everything then produces terrible work that sucks more hours out of other devs? Nah. Admitting fault and lack of knowledge is important, and it's different to ignorance. If you're desparate, actually know your stuff, and still lie, that's on you IMO. If you don't know your stuff and you lie, you probably wouldn't have made it anyway.
- nh23423fefe 2y ago
  That presumes I can't catch people lying to me?

by zeroq 2y ago

ericjmorey 2y ago

You're not filtering on honesty, but desperation. The desperate will lie because of the higher stakes for themselves.

nusl 2y ago
I dunno. If your immediate response is to lie rather than admit that you don't know something, it increases the probability that this is the person's default response when in such a situation. You don't want that person working for you if you depend on them for critical stuff, like many development or similar positions. If you've ever worked with someone like this, you'd know that it's frustrating and unpleasant mid-to-long-term. Someone breaks prod and refuses to admit it unless given a commit as evidence and a confrontation rather than owning up and fixing/helping fix it? Pretends to know everything then produces terrible work that sucks more hours out of other devs? Nah. Admitting fault and lack of knowledge is important, and it's different to ignorance. If you're desparate, actually know your stuff, and still lie, that's on you IMO. If you don't know your stuff and you lie, you probably wouldn't have made it anyway.
nh23423fefe 2y ago
That presumes I can't catch people lying to me?