>But brain teaser questions and asking gotcha questions about obscure python syntax or something like that isn't a good correlative indicator.
Agreed, but that's not how we interview.
>Did you hire a candidate who say... didn't know what MRO was, but created a stellar result for a take home project?
Do you have me confused with the other guy?
>What I'm saying is that the market is flooded with these false negatives.
Understood. The market is also flooded with incompetent devs, capable of talking at length about Python syntax (and sometimes even the computational model, e.g. MRO, etc.), but who aren't actually able to put that knowledge to use in engineering systems. These are systematically catastrophic hires, by which I mean, the engineering team is significantly better off hiring no-one, than hiring them.
May I ask, why does this seem to matter so much to you? If you are a bootcamp graduate yourself, that doesn't preclude you from being a good engineer. I am more than happy to believe you are the one-in-a-thousand counter-example.
>May I ask, why does this seem to matter so much to you? If you are a bootcamp graduate yourself, that doesn't preclude you from being a good engineer. I am more than happy to believe you are the one-in-a-thousand counter-example.
I'm not a bootcamp graduate engineer. I'm actually quite good at what I do, interviewing (from both sides) and engineering. This topic matters to me because I like to argue online and I have strong opinions.
It's common for people to manipulate their perception of reality to justify their own situation, I assure you I am not doing that here, however I think you are doing this.
>>What I'm saying is that the market is flooded with these false negatives.
>Understood.
A false negative is someone who is GOOD, but appears bad. He is a negative but that assignment is false. I am saying the market is flooded with capable engineers that are good but appear bad due to interview processes and biases. Hence the term false negative.
>Do you have me confused with the other guy?
Nope you guys touched on similar points. You never mentioned syntax, but you're likely testing on algorithms so it's the same result. You get a ton of false negatives. You pay a premium for the guy who does better at the interview when you can get someone who's just as capable at a much lower cost.
The point is someone will hire those false negatives at a cheaper price and that effects the whole market. Companies hire the best they can get.
>Agreed, but that's not how we interview.
That's why a certain segment of the market looks like there's a dearth of people. It's because the interview clouds your perception. You interview the wrong way, you agree. The contradiction here is that although most people like you agree, you still reject people based off the SAME results as the WRONG interview AND you think the rejection is accurate.
That's how the psychology works. Everyone I talk to agrees interviewing is wrong overall but when they use it to judge on individual candidates they think it's accurate.
The contradiction exists even in your own reply. You agree the interview process you use is screwed yet you're really confident about your judgement of the market even though your measurement methodology is SELF admitted to be wrong. It renders your entire argument into question.
Agreed, but that's not how we interview.
>Did you hire a candidate who say... didn't know what MRO was, but created a stellar result for a take home project?
Do you have me confused with the other guy?
>What I'm saying is that the market is flooded with these false negatives.
Understood. The market is also flooded with incompetent devs, capable of talking at length about Python syntax (and sometimes even the computational model, e.g. MRO, etc.), but who aren't actually able to put that knowledge to use in engineering systems. These are systematically catastrophic hires, by which I mean, the engineering team is significantly better off hiring no-one, than hiring them.
May I ask, why does this seem to matter so much to you? If you are a bootcamp graduate yourself, that doesn't preclude you from being a good engineer. I am more than happy to believe you are the one-in-a-thousand counter-example.