📎 Webclip
On Hiring Developers and the Technical Interview Process
The post argues that technical hiring should actively reduce unconscious bias, starting with blind CVs, bias training, clear job requirements, and avoiding degree requirements unless they are truly necessary. It also treats the candidate as someone who is interviewing the company as well.
Reading notes#
- Blind CVs should remove personally identifiable information before a resume reaches an engineer.
- Unconscious bias training is presented as a way to reduce bias in hiring.
- Job ads should use clear and concise requirements to widen the pool of applicants.
- Degree requirements should not be listed unless a bachelor’s degree is definitely required.
- The phone interview should be short and focus on cultural fit, with only basic technical discussion.
- The phone interview should also help the candidate learn about the company and engineering organisation.
- Feedback after the phone interview should go to a hiring guild, using a standard structure and neutral language.
- A hiring guild is described as a group of engineers who improve the technical hiring process and support a diverse team.
- Technical interviews should avoid brainteasers and other bias-heavy formats.
- A technical task should be relevant to the role, limited in scope, and not cause undue anxiety.
- At Condé Nast, candidates get a two-hour take-home task and a later face-to-face discussion about their solution.
- The technical task is described as input for discussion, not as a gate.
- Face-to-face interviews should be short, structured, and limited to a small panel.
- Teleconference should be offered to increase flexibility and reduce pressure.
- The interviewer panel should be diverse, and time should be left for the candidate’s questions.
- The conclusion says fair hiring benefits both the team and the business, including better representation and retention.
