> Emily’s school has an informal, undergraduate computer science club in which they are collectively reading technical interviewing guides and trying to figure out what tech companies want from them. She has a couple interviews lined up, but all of which are for jobs she’s desperate to get. They trade tips after interviews but ultimately have a shaky understanding of they did right and wrong in the absence of post-interview feedback from companies.
This pains me every.single.time.
Being part of a specialized recruiting agency, I want to double down on how much preparation and insight before the actual interview matters.
Devs spend most of their time developing, not sitting in interviews, so every recruiter should spend at least a few minutes with every candidate giving them some heads-up.
Not like "for question 1, the answer is b", but like how to carry themselves through the interviews and generally what to expect.