July 14th, 2024

Letting Candidates Know They're Not Moving Forward

The blog post discusses the issue of "ghosting" candidates in software engineering, emphasizing the importance of providing feedback to applicants, respectful hiring processes, and transparent communication for a positive candidate experience.

Read original articleLink Icon
Letting Candidates Know They're Not Moving Forward

In the blog post "Letting Candidates Know They're Not Moving Forward," the author discusses the common practice of "ghosting" candidates in the software engineering industry, where applicants are not informed about their application status. Reasons for this include a lack of downside for companies, fear of confrontation, and the need for time to assess candidates for other positions. The author shares their personal experience of committing to providing feedback to all applicants and the positive impact it had. Additionally, the post highlights the importance of respectful and communicative hiring processes to attract and retain top talent. The author also mentions their participation in Hacker News' "Who is Hiring" thread and reflects on the significance of interview processes in identifying great engineers. Overall, the post emphasizes the value of transparency and communication in the hiring process to create a positive experience for candidates.

Link Icon 2 comments
By @austin-cheney - 4 months
I really love feedback like:

Candidate failed to demonstrate necessary experience when asked about (something specific here).

That lets me know that either I was weak in this primary area of interest for that employer or that I simply failed to sell my potential/performance. Precise no bullshit feedback is amazing.

Most of time I, as a former JS developer, get the impression the employer has absolutely no idea what they want in an engineer and are instead just trying to find some average guy to populate their team of unimpressive averages.

I have since developed my own criteria to evaluate for this. Does the future employer measure things, heavily invest in rapid test automation, optimize for automation speed contrary to what’s popular. If I get the impression the employer just dicks around with tools and only looks at popularity as their measuring stick I have a general idea of what’s coming. If they don’t take their own output seriously I know I am probably not going to get the job, and even if I did I wouldn’t like it. This was so common in JS land that I moved onto the first something else that found me.