Interview apprenticeship
Engineers work together to learn from each others. Interviews should be no different. Photo by NESA by Makers on Unsplash

Interview apprenticeship

Software engineers are well-positioned to evaluate a candidate’s technical ability, but conducting an interviews is much more than evaluating code. Non-technical skills like the ones I’ve been writing about, and even interview-specific technical skills, are crucial.

Unfortunately, many software engineers are thrust into interviewing candidates without proper training. Just like engineers need mentorship for their technical skills, new interviewers need hand-holding and feedback. When done right, pairing interviewers of different levels plays a huge role in up-leveling junior interviewers.

The apprenticeship model

The apprenticeship model transitions an engineer from a junior interviewer to an experienced one:

  1. First, an engineer is considered an apprentice interviewer. Every interview is scheduled with an experienced interviewer and up to one apprentice. At no point does an apprentice interview on their own.
  2. After a sufficient number of interviews, the apprentice is designated as an experienced interviewer. At this point, they can interview a candidate on their own, or even with a new apprentice.

However, any process is only as good as the culture that applies it.

Applying apprenticeship effectively

Companies need to focus on using the apprenticeship program as an opportunity to teach, not as a gate-keeping mechanism. To that end:

  • Interviewers need to apprentice for different interview areas individually. For example, if the company has an algorithm section and a system design section, both require different skills. One interviewer can be experienced in one area and an apprentice in another. However, general interview skills carry over, so the second apprenticeship can be shorter.
  • Similarly, an apprentice should be paired with different experienced interviews over time. The way I’ve seen this done is each interview is scheduled with a different pair (though sometimes people cross paths multiple times). This way, the apprentice can observe multiple interview styles.
  • Train experienced interviewers to mentor apprentices. It’s not enough for an experienced interviewer to conduct the interview while the apprentice watches. Instead, the two interviewers should prepare together before the interview and de-brief after.
  • On the note of mentorship, apprentice should ask questions after the interview. “Why did you ask that follow-up?” “What went well, and what could have gone better?” An apprentice is present to learn, not just to fill a requirement.
  • The apprentice can start by observing, but over time, they should spend more time driving the interview. Before graduating from their apprenticeship, they should be driving the entire interview like an experienced interviewer.

If this feels like a lot of work for an hour-long interview, realize that interviewing affects people’s lives. It’s important to take the job seriously.


Pairing an inexperienced interviewer with an experienced one allows engineers to slowly learn how to interview effectively. Best of all, this is done without the candidates being negatively affected, as the experienced interviewer is always present to take the reins.

This article was originally published on the Hiring For Tech website. If you want to read more content from me, please subscribe either by email or on LinkedIn. If you have any thoughts about my content, comment below. And don't forget to follow me for more content!

Srivas Melkote Kainkaryam

Service Management Consulting, Account Delivery, Service Integration & Management, IT Project Management

4 年

Well Said. Indeed, this is one good way to develop interviewing skills. I would like to contribute some points. Am not sure, though, if you have covered this elsewhere or earlier. This being the first feed from your stream that I managed to read completely. These are some thoughts about who can, should be allowed to conduct interviews and what some criteria for selection ought to be: 1. There should be a dedicated training program for people who would like to conduct interviews. Note that this is as much a "will" issue as it is a "skill" issue. Some one without the "skill" can be taught to acquire it whereas, someone without the "will" will NOT acquire it, as they simply do not want to do that activity, and we should let them be. 2. An interviewer's first requirement should be "people skills", THEN, technical/functional skills, not the other way around. 3. Ideally, we need to be able to identify "people" who are capable of "acquiring skills rather than "perfectly ready" candidates, unless it is a short term, contracting position. 4. Selecting a candidate and then interviewing him/her means trying to understand what drives that person and how he/she can be assisted to perform better and improve (off course, the interviewer may NOT be the one doing all the latter activities for the candidate, post joining) 5. Also, to be taken note off, is that a good interviewer NEED NOT be the best person on the job, a well balanced person who knows that job well and has spent some time carrying out tasks involved in the job with good people skill can be an excellent interviewer. 6. Interviewers MUST ensure they are well versed with the candidate prior to the interview, based on the data available to them. Eg: Candidate resume should have been shared with the interviewer well before the interview slot, maybe a day or 2 in advance 7. Recruiter and Interviewer should have a well rounded discussion, in advance, regarding the actual requirement and also the expected grade/designation/pay scale etc. related job details for the position that he/she is conducting an interview for. Some thoughts for now.! Thanks for the good article! #workmusings

要查看或添加评论,请登录

Avik Das的更多文章

  • Acing the system design interview

    Acing the system design interview

    It’s been a while since I last wrote, but in the last year, I’ve done a lot of system design interviews. I really like…

    4 条评论
  • "It's not peaches and cream either for men"

    "It's not peaches and cream either for men"

    I spend a lot of time talking about men’s mental health because it’s what I, as a man, know about. And like with…

    1 条评论
  • It's okay to not be okay

    It's okay to not be okay

    What I’m about to say applies to everybody, but with Movember and my own experience as a man in mind, I hope my words…

    2 条评论
  • What's still wrong with tech hiring

    What's still wrong with tech hiring

    Last year, I set out with a head full of disconnected thoughts about hiring and a vision to share those thoughts with a…

    15 条评论
  • One size does not fit all

    One size does not fit all

    I’ve talked about what seem to be two conflicting topics: standardizing your interviews and accommodating different…

    5 条评论
  • Formal interview training

    Formal interview training

    A running theme in this newsletter is the idea that good software engineers don’t automatically make good interviewers.…

    1 条评论
  • Interviewing and pattern matching

    Interviewing and pattern matching

    For candidates, a full day of interviews is grueling, but in the context of demonstrating your technical skills and how…

    3 条评论
  • Technical skills every software engineer interviewer should have

    Technical skills every software engineer interviewer should have

    There’s a lot of discussion about technical skills candidates need to have, like algorithms, systems design, technical…

  • Prepare your story

    Prepare your story

    If you’re planning on starting or continuing your job hunt this year, the beginning of the year is a good time to…

    3 条评论
  • My optimism for tech hiring in 2021

    My optimism for tech hiring in 2021

    Last week, I talked about what I’ve learned about tech hiring in 2020. Again, because I expect lower than usual…

    6 条评论

社区洞察

其他会员也浏览了