[qubax]

> The practice interview point strikes me as odd. In large, because I have never done one. Do folks really typically do that many practice interviews?

I only did practice interviews for my college internships and my first job because my resume was so light and my experience in the industry was nonexistent. When you have so little to talk about, it's smart to come prepared with a handful of questions.

Once you have 5 years or so of experience, other than light prep, practice interviews are not necessary. You know what to expect in interviews and you have tons of work experience to talk about and industry experience to ask pertinent questions to the interviewer.

But that's just my own personal experience. Also, after my 1st job, I've never had to take "technical or IQ tests" either. The interview process was more center around my projects and work experience rather than technical know-how.

[pmiller2]

Just out of curiosity, what kind of places have you been interviewing? I'm at about 5 years, and I'm still getting mostly the same old "write down the solution to these leetcode problems" type interviews. I would say 75% is leetcode bullshit, maybe 25% more applied type interviews.

[mattkrause]

Literally anywhere that doesn’t think of itself as a “tech compan.” or the job as a “tech” job.

I’m on the line between neuroscience and machine learning. Interviews for “neuro jobs”, even ones where my major responsibility would be coding, usually involve talking about things I’ve done and how I would tackle new problems. Put a similar position in an org that thinks of itself as “tech” and suddenly I’m traversing graphs and drawing trees.