As GitLab grows, the Technical Writing team expands, and team members participate in the interviews. A defined interview process is important for a consistent hiring process.
Technical Writers (TWs) follow the Engineering hiring process.
The following people interview the candidate for a Technical Writing role:
The goal is to evaluate the candidate’s technical skills and knowledge, such as:
The candidate must be able to onboard quickly and keep up the pace of GitLab development, as well as align with the company values.
If you are a Technical Writer at GitLab and you wish to be part of the hiring process, complete the interview training.
In the last steps of the training, you will:
Although you must shadow only two interviews and be shadowed in one interview, you can request to shadow or be shadowed in more interviews until you feel ready to start interviewing yourself.
For every interview:
When you shadow a Technical Writer, observe how they conduct the interview.
When you are being shadowed by your coach, and during any following interviews:
At the end of the interview, do not give them false expectations. You don't know how well they will do in other interviews, so don't say anything about how you think they will do in the process. Be kind. Thank them for their time and interest.
Fill out the candidate’s scorecard in Greenhouse.
Notes for the next interviewer:
For anything unclear to you, or needs a follow-up, or needs further investigation, add in a note for the next interviewer.
Full notes and results: