> Try to get a real sample of work (which we already do for developers by working on GitLab issues) Avoid puzzles or weird algorithm testing questions. Probing for data structures is fine as long as it is relevant to the job the person is going to do.
> Be mindful of the background of the candidate, someone who knows 10 languages already (and some languages in particular, Perl for ex), may pickup ruby in a second given the right chance. Don't assume that someone with a Java background will not be capable of moving to a different stack.
> Consider including non technical people performing soft skills questions. Because technical people should be capable of talking to non-technical just fine, we should assess it.
Kudos to GitLab for these sentences. I think this is far better approach than the usual technical interviews.
Thanks, credit for this goes to our infrastructure lead Pablo if I'm not mistaken. He joined us from Amazon so it might be inspired by their process of which he speaks highly.
I don't know... less than a year ago I didn't even get an interview because they were (legitimately) concerned with my lack of experience with Haml and Rails.
I mean, kudos to them if they changed their view on this. I just wanted to let you know about my experience on the topic at hand.
I think we had the same view a year back but the bar is higher when your experience is less relevant. Of course we make judgment errors too, feel free to reapply.
I promise that your open solicitation to GitHub http://octohire.me/ was not held against you :)
> Technical interviews
> Try to get a real sample of work (which we already do for developers by working on GitLab issues) Avoid puzzles or weird algorithm testing questions. Probing for data structures is fine as long as it is relevant to the job the person is going to do.
> Be mindful of the background of the candidate, someone who knows 10 languages already (and some languages in particular, Perl for ex), may pickup ruby in a second given the right chance. Don't assume that someone with a Java background will not be capable of moving to a different stack.
> Consider including non technical people performing soft skills questions. Because technical people should be capable of talking to non-technical just fine, we should assess it.
Kudos to GitLab for these sentences. I think this is far better approach than the usual technical interviews.
1 : https://about.gitlab.com/handbook/hiring/#technical-intervie...