Hiring engineers when you cannot assess the work yourself is genuinely hard, and the first two hires shape everything that follows — they set the standards, the architecture and, in practice, who the next ten will be.
Hire for judgement over knowledge
Framework familiarity is learnable in weeks; judgement about what to build, what to skip and when to say a plan is wrong takes years. In an early team the second is what protects you, because there is nobody senior to catch a bad architectural decision before it becomes expensive.
Frameworks are learnable. Knowing what not to build is not.
Test with work resembling the job
Puzzle interviews measure puzzle skill. A small, paid, realistic task — extend an existing codebase, review a pull request, debug a failing test — tells you about code quality, communication and how they handle ambiguity. Keep it under four hours and pay for their time.
Get help you trust for the technical read
If you cannot evaluate the work, borrow someone who can: an advisor, a fractional CTO, a technical friend who owes you a favour. One hour of an experienced engineer reviewing a candidate's submission is the cheapest insurance available against a hire that sets the codebase off in the wrong direction.
Ask them to explain a decision
Have a candidate explain a technical tradeoff to you, the non-technical founder. Someone who can make you genuinely understand why they chose one approach over another will be able to do the same for investors, customers and the next hire. Someone who retreats into jargon under that request will be difficult to work with.
Beware the person who agrees with everything
An engineer who never pushes back on scope, timeline or approach is either inexperienced or has decided not to argue. Both are dangerous when you cannot evaluate the technical direction yourself. Some friction in the interview is a positive signal.
Consider a team before an individual
One first engineer carries a large concentration risk — no review, no second opinion, and a single point of departure. An agency or a small partner team can hold the work while you hire deliberately rather than urgently, and the difference between an urgent hire and a deliberate one is usually the difference between a good one and a costly one.
