7 ms·

> This assumes that was the job? What if the job never talks or sits in a room with anyone? That's perfectly fine. Some coding jobs also don't require deep kno

> This assumes that was the job? What if the job never talks or sits in a room with anyone? That's perfectly fine. Some coding jobs also don't require deep knowledge on data structures. Each company and project has its own requirements. This does not reject the value of soft skills and being able to interact with other people. You can also frame this from another perspective. How far should a hiring manager go to accommodate antisocial and straight out toxic people? Does an eggregious backstabber have the right to advance in hiring processes just because others found him unpleasant to work with?

fzeroracer 2y ago
Sitting in a conference room under pressure after potentially flying out possibly hundreds of miles doesn't test your soft skills in actual day to day work. I've known many excellent engineers that buckle under that conditional.
- motorest 2y ago
  > Sitting in a conference room under pressure after potentially flying out possibly hundreds of miles doesn't test your soft skills in actual day to day work. I've known many excellent engineers that buckle under that conditional. You're complaining about the hypothetical effectiveness of concrete hiring practices. You are not rejecting the value and importance of soft skills. Also, the ability to work under pressure is valuable skill. If you have a candidate that fails to perform when being in a room with someone else, I doubt you can argue that that's your hiring decision when other candidates are able to perform in similar circumstances.
  - sarchertech 2y ago
    Literally no other industry except for the performing arts interviews like this. No one else expects senior people to perform “work samples” under pressure, they just talk to them and dig into past work. All of the really damaging hires, I’ve seen in the last couple decades have been engineers with high negative productivity who were great at passing high pressure technical interviews. Also in a couple decades working everywhere from startups to big tech companies in staff+ roles, I have never experienced anything even remotely similar to a performative technical interview. Even when everything is on fire, it’s not even close to the same thing.
    - ryandrake 2y ago
      I’ve always wondered: is there a LeetCode equivalent for doctors? When a hospital interviews a surgeon, do they roll out a cadaver and ask them to remove the gall bladder in 15 minutes while the interviewer scrutinizes how they hold the scalpel?
      - Apocryphon 2y ago
        It’s because medicine, with its residencies and HN-mocked credentialism, is closer to traditional craftsmanship and the progression of apprentice-journeyman-master than the “every hacker for themselves” world of modern tech.
        re-thc 2y ago
        > is closer to traditional craftsmanship and the progression of apprentice-journeyman-master than the “every hacker for themselves”. Let's fix the real problem then? Why can't tech be like this?
        motorest 2y ago
        > Let's fix the real problem then? Why can't tech be like this? Why should it? What problems would they solve? Are you so afraid of competing with those who might not get a certiciation?
        Apocryphon 2y ago
        Well, it'd be nice if they reintroduced proper training of new tech workers, rather than outsourcing it to universities ("not supposed to be trade schools") or relying on internships/co-ops which these days are often nearly as competitive to be hired for as actual jobs. Formalized apprenticeships could help with that, as well as impart a proper culture of craftsmanship. And as far as certs go, just having a simple one for algorithms/data structures can seriously fix the issue of having to go through the Leetcode gauntlet at every single place one interviews at. A certificate for that class of questions would go a long way towards smoothing the existing interview process. DRY, anyone?
  - fzeroracer 2y ago
    > Also, the ability to work under pressure is valuable skill. If you have a candidate that fails to perform when being in a room with someone else, I doubt you can argue that that's your hiring decision when other candidates are able to perform in similar circumstances. I'm curious, as a software engineer when was the last time you've seriously worked under pressure? Like, 'do this thing now or you're fired/the company goes under' and so forth? The kind of snap pressure that interviews can push on you. I haven't been under significant pressure in the past 10 or so years of software engineering. Not when on live ops diagnosing why our server is failing to work in prod, not when identifying critical client crashes.
    - motorest 2y ago
      > I'm curious, as a software engineer when was the last time you've seriously worked under pressure? Jetbrain's 2023 Developers’ Lifestyles survey states that around 29% of all developers work on weekends for work. Having to work weekends is the last resort when working under pressure. Nearly 1/3 of all developers claim they are at that stage. No other profession has the concept of "crunch time". https://www.jetbrains.com/lp/devecosystem-2023/lifestyle/ https://www.jetbrains.com/lp/devecosystem-2023/lifestyle/
      - fzeroracer 2y ago
        I asked you, specifically. I'll bite anyways, but I'll expect an actual answer from you. > Having to work weekends is the last resort when working under pressure No, it's not. I've had to work weekends before. We had a live ops rotation that would occur roughly once every eight weeks or so for me. The times I've had to work on the weekend were due to needing to solve some prod bug that was causing relatively minor headaches but they wanted some triage and solutions in earlier as possible. This was not a 'you are fired if you fail to solve the bug issue' or a thing where management is breathing down my neck to fix it because they're all busy sleeping on the weekend while I'm tanking the call. It's often the result of either shitty management or people that cannot log off. > No other profession has the concept of "crunch time". Crunch time is a vastly different kind of pressure. I would know, I've worked in professional game development. And again, it's often the result of shitty management. If a game is going to fail and management is forcing you to work long hours in order to fix it then it's time to walk away.

fzeroracer 2y ago

Sitting in a conference room under pressure after potentially flying out possibly hundreds of miles doesn't test your soft skills in actual day to day work. I've known many excellent engineers that buckle under that conditional.

motorest 2y ago
> Sitting in a conference room under pressure after potentially flying out possibly hundreds of miles doesn't test your soft skills in actual day to day work. I've known many excellent engineers that buckle under that conditional. You're complaining about the hypothetical effectiveness of concrete hiring practices. You are not rejecting the value and importance of soft skills. Also, the ability to work under pressure is valuable skill. If you have a candidate that fails to perform when being in a room with someone else, I doubt you can argue that that's your hiring decision when other candidates are able to perform in similar circumstances.
- sarchertech 2y ago
  Literally no other industry except for the performing arts interviews like this. No one else expects senior people to perform “work samples” under pressure, they just talk to them and dig into past work. All of the really damaging hires, I’ve seen in the last couple decades have been engineers with high negative productivity who were great at passing high pressure technical interviews. Also in a couple decades working everywhere from startups to big tech companies in staff+ roles, I have never experienced anything even remotely similar to a performative technical interview. Even when everything is on fire, it’s not even close to the same thing.
  - ryandrake 2y ago
    I’ve always wondered: is there a LeetCode equivalent for doctors? When a hospital interviews a surgeon, do they roll out a cadaver and ask them to remove the gall bladder in 15 minutes while the interviewer scrutinizes how they hold the scalpel?
    - Apocryphon 2y ago
      It’s because medicine, with its residencies and HN-mocked credentialism, is closer to traditional craftsmanship and the progression of apprentice-journeyman-master than the “every hacker for themselves” world of modern tech.
      - re-thc 2y ago
        > is closer to traditional craftsmanship and the progression of apprentice-journeyman-master than the “every hacker for themselves”. Let's fix the real problem then? Why can't tech be like this?
        motorest 2y ago
        > Let's fix the real problem then? Why can't tech be like this? Why should it? What problems would they solve? Are you so afraid of competing with those who might not get a certiciation?
        Apocryphon 2y ago
        Well, it'd be nice if they reintroduced proper training of new tech workers, rather than outsourcing it to universities ("not supposed to be trade schools") or relying on internships/co-ops which these days are often nearly as competitive to be hired for as actual jobs. Formalized apprenticeships could help with that, as well as impart a proper culture of craftsmanship. And as far as certs go, just having a simple one for algorithms/data structures can seriously fix the issue of having to go through the Leetcode gauntlet at every single place one interviews at. A certificate for that class of questions would go a long way towards smoothing the existing interview process. DRY, anyone?
- fzeroracer 2y ago
  > Also, the ability to work under pressure is valuable skill. If you have a candidate that fails to perform when being in a room with someone else, I doubt you can argue that that's your hiring decision when other candidates are able to perform in similar circumstances. I'm curious, as a software engineer when was the last time you've seriously worked under pressure? Like, 'do this thing now or you're fired/the company goes under' and so forth? The kind of snap pressure that interviews can push on you. I haven't been under significant pressure in the past 10 or so years of software engineering. Not when on live ops diagnosing why our server is failing to work in prod, not when identifying critical client crashes.
  - motorest 2y ago
    > I'm curious, as a software engineer when was the last time you've seriously worked under pressure? Jetbrain's 2023 Developers’ Lifestyles survey states that around 29% of all developers work on weekends for work. Having to work weekends is the last resort when working under pressure. Nearly 1/3 of all developers claim they are at that stage. No other profession has the concept of "crunch time". https://www.jetbrains.com/lp/devecosystem-2023/lifestyle/ https://www.jetbrains.com/lp/devecosystem-2023/lifestyle/
    - fzeroracer 2y ago
      I asked you, specifically. I'll bite anyways, but I'll expect an actual answer from you. > Having to work weekends is the last resort when working under pressure No, it's not. I've had to work weekends before. We had a live ops rotation that would occur roughly once every eight weeks or so for me. The times I've had to work on the weekend were due to needing to solve some prod bug that was causing relatively minor headaches but they wanted some triage and solutions in earlier as possible. This was not a 'you are fired if you fail to solve the bug issue' or a thing where management is breathing down my neck to fix it because they're all busy sleeping on the weekend while I'm tanking the call. It's often the result of either shitty management or people that cannot log off. > No other profession has the concept of "crunch time". Crunch time is a vastly different kind of pressure. I would know, I've worked in professional game development. And again, it's often the result of shitty management. If a game is going to fail and management is forcing you to work long hours in order to fix it then it's time to walk away.