4 ms·
I wonder how many trillions of dollars of lost productivity we've incurred by trying to improve our interview skills for brogrammer jobs.
by neilv 4y ago
I wonder how many trillions of dollars of lost productivity we've incurred by trying to improve our interview skills for brogrammer jobs.
- iamnafets 4y agoSimilar in magnitude to the lost productivity of people optimizing for appearances rather than results at work. All prep is basically an arbitrage between the hard work of actually becoming better and the often easier work of preparation. The ideal system would minimize this arbitrage, both for the sake of employers and candidates alike.
- AlotOfReading 4y agoI'm not sure it's a given that prep is an alternative to the hard work of becoming better. Imagine a hypothetical office job with bench press round. Improving your job skills wouldn't be the way to pass it, going to the gym would. That's obviously an extreme hypothetical to illustrate the point, but it's along the same lines as common criticisms of e.g. leetcode and c-suite interview processes.
- iamnafets 4y agoDefinitely. Much of it _isn't_. But the parent comment was referring to the waste of the process, which is necessarily the part that isn't directly useful in the job.
- xboxnolifes 4y agoI think about this a lot. It makes sense, on an individual level, to optimize your ability to interview, so that you can maximize your own results. However, it's crazy to me how frequently companies urge potential applicants to improve their own ability to interview. If a company is aware that they are missing out on good applicants due to how they conduct interviews, they should improve their interview process. I don't see how wanting the applicant pool to improve interview skills is beneficial for anyone involved. It just leads toward reducing the signal to noise ratio of the interviewing process, leading to increased time wasted sifting through the noise.
- majormajor 4y agoI agree races to the bottom aren't always helpful - see also college admissions and how so many kids are loaded to the gills with "extracurriculars" to "stand out" - but ... > If a company is aware that they are missing out on good applicants due to how they conduct interviews, they should improve their interview process. if only it were that easy! I've never worked at a company that hasn't wanted to improve their interview process. Even that "tell people roughly what to expect" thing is a result of trying to improve the process - you can more easily tell the difference between "even with hints, they weren't able to hack it" and "they were able to figure it out, though we're not sure how much the hints had to do with it." That's a step better then "they passed the test" and "they didn't pass the test, regardless of if it's because it caught them by surprise or just that they aren't able to." It's not perfect, but most of the common things I've seen pitched here to "just" make it a better process, like trial periods and take-home "real work sample" tasks, seem wildly impractical as at-scale replacements. EDIT: my personal favorite is when the candidate has a system they've worked on in the past that they can explain in detail and describe challenges and solutions for... but... the pool of people who can do that has been even smaller than the pool of people who can at-least-pseudocode their way through some mild live problem solving and design questions.
- xboxnolifes 4y ago> I've never worked at a company that hasn't wanted to improve their interview process. My point isn't that fixing the process is easy. It's clearly not. And I absolutely sympathize with the issues of hiring. My point is that improving peoples' interview skills doesn't make them better employees, or make qualified candidates easier to find, since it's not a skill that is unique to only people who are actually qualified for the position. Just as qualified people will seem better, so will unqualified people learn how to seem qualified. It's applying a fix that does nothing but: (1) reduce signal to noise, and/or (2) satisfy the "gut feelings" of interviewers on what a good candidate look like. If companies are goading applicants to improve interview skills, all else being equal, assuming this actually leads to increased job offers for the candidates, it means companies are filtering too hard for unimportant "interview skills". ----- EDIT > EDIT: my personal favorite is when the candidate has a system they've worked on in the past that they can explain in detail and describe challenges and solutions for... but... the pool of people who can do that has been even smaller than the pool of people who can at-least-pseudocode their way through some mild live problem solving and design questions. This lightly touches on part of what I mean. Companies frequently test for things outside of what they intend to. Its not possible to completely avoid, but, based on my own interviewing experience, it's doesn't seem like much work goes into adjusting for it. Just breaking down this example, I'll explain what I think you are looking for, and what you end up asking for. Intentionally testing for: - experience working with a complex system - able to identify issues in a complex system - able to figure out solutions to said problem - able to identify tradeoffs to said problem - able to communicate the problem, solution, and tradeoffs Unintentionally testing for: - ability to recall, on short notice, details of a complex system from (likely) months ago, including it's tradeoffs and outcomes, without resources on hand. - the ability to recall challenges and learnings from (likely) months after they've been experienced and absorbed. (This is a big one for me, personally) - knowing how complex is complex enough. An applicant may think bringing up a system they do not consider to be particularly complex may hinder their chances by not meeting expectations. Every point from the unintentional section is something that could completely prevent someone from coming across as a good candidate, but have no bearing on how well they can actually do their work.
- azangru 4y agoFirst, what's a brogrammer job? Second, how is productivity being lost? If, as you say, the loss happens _while_ trying to improve interview skills, then, presumably, the person working on the improvement is looking for a job, and either is not currently employed (and thus can't be losing anyone money in lost productivity), or wishes to quit his current job (and thus is probably not super committed to the tasks at hand).
- xboxnolifes 4y ago> (and thus can't be losing anyone money in lost productivity) What? No, no, no. Being unemployed when you want to be employed is 0% productivity. That is lost productively compared to having a job for that period of time. That extra time spent interviewing is money lost for you compared to working. Having everyone spend more time learning skills that are only used between jobs is productivity that is lost relative to learning skills that improve your ability to do your job, or just doing the job itself.
- lisasays 4y agoFirst, what's a brogrammer job? Pretty much most industry work these days. I agree the term is vague (as used here), but what I think the commenter means is "same old, same old". In the interview process, every company talks about how picky they are about hiring, and how special everyone is who works there. And then you get in there and it's the same sloth and pretentiousness (and not too infrequently, just plain bad interpersonal behavior) as everywhere else. And the same productivity-killing open plan office, too.