3 ms·

On the other hand, next time I'm on a 30 minute screening and end up getting left with 10 minutes to show them I can write a functional program they will be too

On the other hand, next time I'm on a 30 minute screening and end up getting left with 10 minutes to show them I can write a functional program they will be too worn out to ding me for silly stuff like concatenating Strings instead of properly using StringBuilder. "You really should have used the enhanced for loop for that .." or "You really should have used a Lambda there" etc. After years of tech screens like this over the course of my coding career I can't say Im not enjoying a little schadenfreude over this.

ImaCake 4y ago
I get the feeling from this comment that tech interviewers would be very upset with how I write scripts in research. Part of the reason I will never shift to developer as a job is that the interview process is ridiculous. In universities, the uni hiring process is so imposing on the researcher's time that they just hire people they meet through informal processes outside the formal system. The informal system is usually a single interview, send your resume through, and the researcher checks your references to make sure you aren't lying scum.
- strken 4y ago
  This is frequently how it works in smaller tech companies as well, although it's usually just getting sent straight through to the same final interview as everyone else.
- ThePadawan 4y ago
  > and the researcher checks your references to make sure you aren't lying scum. That sounds way more professional than any interviewing process I've gone through in the industry /hj.
  - ImaCake 4y ago
    Interesting! Maybe the stereotype of a tech interview is not the common experience of most developers? This would make more sense and leads me to think that HR is just justifying it's own existence with baroque processes that then make it even less relevant and useful.
    - ThePadawan 4y ago
      FYI I went through a large phase in 2020-2021 where I responded to around 75 job offers and overall had 1-5 calls with ~35 companies each. My cover letter contains a standard phrase about "references available on request". No one requested them.
      - SavageBeast 4y ago
        Every so often I come across a useful and hard to find data point - this is one of those times. Thanks for sharing this.

ImaCake 4y ago

I get the feeling from this comment that tech interviewers would be very upset with how I write scripts in research. Part of the reason I will never shift to developer as a job is that the interview process is ridiculous. In universities, the uni hiring process is so imposing on the researcher's time that they just hire people they meet through informal processes outside the formal system. The informal system is usually a single interview, send your resume through, and the researcher checks your references to make sure you aren't lying scum.

strken 4y ago
This is frequently how it works in smaller tech companies as well, although it's usually just getting sent straight through to the same final interview as everyone else.
ThePadawan 4y ago
> and the researcher checks your references to make sure you aren't lying scum. That sounds way more professional than any interviewing process I've gone through in the industry /hj.
- ImaCake 4y ago
  Interesting! Maybe the stereotype of a tech interview is not the common experience of most developers? This would make more sense and leads me to think that HR is just justifying it's own existence with baroque processes that then make it even less relevant and useful.
  - ThePadawan 4y ago
    FYI I went through a large phase in 2020-2021 where I responded to around 75 job offers and overall had 1-5 calls with ~35 companies each. My cover letter contains a standard phrase about "references available on request". No one requested them.
    - SavageBeast 4y ago
      Every so often I come across a useful and hard to find data point - this is one of those times. Thanks for sharing this.