Commit 1545a8b7 authored by Jonah's avatar Jonah

Initial draft of revised recruitment structure

parent 4ab51f9c
......@@ -12,12 +12,7 @@ We aim to let every person go through the same recruitment process in order to t
1. Company introduction
1. Outline the recruitment process to the candidate and a timeline
1. Check the candidates motivation and check if there is a good fit for the company. Make sure the candidate is not an asshole (https://en.wikipedia.org/wiki/The_No_Asshole_Rule)
1. Prepare technical phone interview, creating a checklist of things to check with the candidate, this should include:
1. Relative skill level
1. Technologies that they are familiar with
1. Technologies that they are not familiar with
1. Basic 'nix knowledge,
1. Figure out what assessments would be good (scoping of assessment)
1. Scope a possible next technical assessment: What kind of engineer are they and what is their skill level?
1. Prepare the technical assessment
1. Decide on what assignments the get (more than 1, they don’t have to finish them all)
1. Create a personalized git repo by copying the contents of a few of our assessment repos into a special one for them
......@@ -28,7 +23,13 @@ We aim to let every person go through the same recruitment process in order to t
1. Go through it together with the candidate and also tell them what checks they pass and which ones they didn’t
1. Announce in-channel #hr that there is a new git repo available for evaluation
1. At least 2 different people will need to be assigned to the repo and evaluate the results.
1. Depending on the results of the assessment the candidate might go to the final step
1. Prepare technical phone interview, creating a checklist of things to check with the candidate, this should include:
1. Relative skill level
1. Technologies that they are familiar with
1. Technologies that they are not familiar with
1. Basic 'nix knowledge,
1. Do the technical phone interview
1. Depending on the results of the interview the candidate might go to the final step
1. Negotiation and offer
1. Onboarding!
......@@ -36,20 +37,6 @@ We aim to let every person go through the same recruitment process in order to t
The first interview is nothing too technical, we just have a nice chat about who you are and what you are looking for. We explain what we do and which role we are looking to fill exactly. This call is mainly to assess if there's a good initial connection and check things like English language proficiency, cultural fit, etc. We usually also ask for a potential starting date and the kind of salary you would like to make so we can make sure we're at least in the same ballpark if we reach the negotiation phase at the end of the process.
## Technical exploration call
Next up is a technical call. In this call we will form an opinion and ask some questions related to your previous positions, your technical experience and your opinions on the current and future IT trends. This call is mainly to see if you have broad experience and if you can hold a good technical conversation. It also serves to see if your experience fits with the position you're interviewing for.
In the technical interview we can start by getting a picture of your skills and preferences. We try to figure out:
- the general nix knowledge
- General understanding of technology
- Where on the ops vs dev spectrum you are
- Whether or not you are a generalist or a specialist
- your overall skill level
We will ask extremely broad questions and ask for as much detail as possible, questions like:
[This is stored in a private repo to not give everything away](someurl.com)
## Technical practical session
The following call is a technical hands-on assessment. This takes around roughly half a day and we expect you to be online with a browser, an ssh and a git client at the least. At the start of this session you'll get one or more challenges, you are then expected to implement that and use your imagination when doing so. After the session we'll have a skype (or hangouts, whatever works) call where you get a chance to present the solutions you have created and the choices you've made.
......@@ -73,20 +60,35 @@ These challenges will be sent to you via a git repo in our company gitlab contai
Since this repository will be kept for archival purposes, please take care not to commit _any_ credentials to this repo.
### Transparency
In the past the technical process has not always been as transparent as it should’ve been. Sometimes the assessment the candidate did was not available for evaluation after a while. After careful consideration the new process will be:
In the past the technical process has not always been as transparent as it should’ve been. Sometimes the assessment the candidate did was not available for evaluation after a while. After careful consideration the new process will be:
- Create a namespace/group in gitlab hosting all the prepared assignments,
- When a candidate gets to do one- or more of these assignments, these are forked to a separate repo in our gitlab.
- When a candidate gets to do one- or more of these assignments, these are forked to a separate repo in our gitlab.
- The candidate can then clone this repo and push the results bash to his own assignment repo
This repo should by default be available to all employees of OlinData and stay there forever, also for archiving purposes.
This repo should by default be available to all employees of OlinData and stay there forever, also for archiving purposes.
This way, as much people as are interested can evaluate an assessment at their own leisure
## Technical exploration call
Next up is a technical call. In this call we will form an opinion and ask some questions related to your previous positions, your technical experience and your opinions on the current and future IT trends. This call is mainly to see if you have broad experience and if you can hold a good technical conversation. It also serves to see if your experience fits with the position you're interviewing for.
In the technical interview we can start by getting a picture of your skills and preferences. We try to figure out:
- the general nix knowledge
- General understanding of technology
- Where on the ops vs dev spectrum you are
- Whether or not you are a generalist or a specialist
- your overall skill level
We will ask extremely broad questions and ask for as much detail as possible, questions like:
[This is stored in a private repo to not give everything away](someurl.com)
Additionally we can decide to drill down into the result of your technical assessment, asking you all kinds of questions about it:
- Why did you choose this specific solution path
- If you would run into issue X again, how would you go about solving this?
## 2nd opinion technical interview
If you finished the previous round at a satisfactory level we'll have you have an interview with one of our engineers to see if they also think you have what it takes. This is usually a more heavy technical interview, but it depends on each individual and the information we have gathered up to that point.
## CEO approval call
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment