What we look for when hiring engineers
Not leetcode. We care about how you reason about trade-offs, communicate uncertainty and handle being wrong.
Our interview process is deliberately short: a conversation about your experience, a practical pairing session on a realistic problem, and a discussion about trade-offs.
What we are listening for
- Can you explain a decision you would now make differently?
- Do you ask clarifying questions before writing code?
- How do you communicate uncertainty to a non-technical stakeholder?
We do not ask anyone to invert a binary tree on a whiteboard. We do ask you to review a pull request and say what you would change.
Related articles
The case against a microservices-first architecture
For most teams under fifty engineers, a well-structured monolith ships faster and costs less. Here is where we draw the line.
Read articleSecuring file uploads in a CMS
CVs, artwork and documents are the most commonly exploited part of any content-managed site. A practical checklist.
Read articleLegacy modernisation without a big-bang rewrite
Strangler-fig patterns let you replace a legacy system incrementally, with value delivered every few weeks.
Read article