Hiring Go engineers when nobody in-house can interview in Go
A product company rewriting a Java system in Go needed to hire into a stack its own team could not assess yet. Two engineers hired through our interviews, and the work continues on further roles.
Client: Product company with its own engineering team
The team was rewriting a Java system in Go. Hiring Go engineers was the obvious move, and the obvious problem: nobody on the team was calibrated to interview for Go yet.
A strong Java engineer can tell whether a Go candidate writes working code. What they cannot reliably tell is whether the candidate thinks in the language, or has rehearsed it for the interview.
Before the first candidate, we built the interview plan and agreed it with the client's tech lead. They could cut or add anything.
The tech lead removed the algorithms section and replaced live coding with a review of a small Go service, because that is what the job actually is. The interview was built around the work, not around a generic test.
Our engineers ran the interviews. The client received a recording and a structured report on every candidate, so any conclusion could be checked against the moment it came from.
Two engineers hired through our interviews.
The client keeps bringing us further roles, and interviews for them are ongoing.
Hiring into a stack your team can't assess yet?
operations@stepup.services