We run a fairly conventional hiring process. The part that predicts success is not the part most candidates prepare for.
We care how you behave when you are stuck
Every technical exercise we run has a point where the candidate does not know the answer. That moment is the actual assessment. The engineers who work out well say what they do not know, describe how they would find out, and reason out loud. The ones who do not, bluff.
Client work is full of unfamiliar situations. Bluffing in front of a client costs us the relationship.
We care that you can explain things to non-engineers
Most of our work involves explaining a technical trade-off to someone who will make a commercial decision from it. If you cannot explain why a migration will take four months rather than two, in language a finance director can act on, the technical judgement behind it never gets used.
What we do not screen on
Not on a specific framework — those change. Not on years of experience as a number. Not on whether you have used our exact stack; if you have operated something comparable, the transfer is usually a few weeks.
What the work is
Real client estates with real constraints. You will see systems built under time pressure by people who had less information than you do. Improving them without contempt for the people who built them is most of the craft.