The recommendation format

A candidate brief you can question.

See how a recommendation can connect the role, the evidence and the next assessment. The company, candidate and assessment below are fictional.

Illustrative example. Fictional candidate and company. No real person, client search or hiring outcome is represented.

Illustrative candidate recommendation

Head of Engineering

Company context
Fictional Series A software company
Role mandate
Hands-on engineering leadership
Recommendation
Advance conditionally

Why this person

The fictional role needs a leader who can stay close to product and architecture while giving a small engineering team clearer direction. This candidate’s account describes that combination in an early-stage environment.

Evidence observed

In the fictional assessment, the candidate traced a production issue from customer symptoms to a diagnosis, explained the decision to simplify an integration and identified which implementation work they completed personally. They also described an architectural choice they would now change.

What they owned

The account attributes technical planning, architecture decisions and direct product implementation to the candidate. Their description of hiring and people management is self-reported and still needs independent validation.

Relevant pattern

They appear comfortable moving between technical detail and the product problem. Their reasoning favours a small solution that can be tested, with explicit attention to what the team can maintain.

Why this company

In this fictional conversation, the candidate connects the customer problem with work they want to own. This is stated interest. Ask them to explain the actual constraints, work they would do themselves and conditions for joining. Keep their motives separate from observed assessment evidence.

Risks

The exercise does not establish that they can develop other engineering leaders or operate across multiple locations. Their approach may depend on direct founder access, which this role may not always provide.

Still to validate

Use a technical conversation to examine an unfamiliar integration problem. Ask a former founder or manager to distinguish personal contribution from team output. Seek a direct report’s account of how the candidate set expectations and handled disagreement.

Recommendation and next step

Advance to a focused technical conversation and structured references if the company confirms that hands-on leadership is the immediate mandate. Keep the recommendation conditional on evidence of developing others and on agreement about the founder’s decision-making role.

Which evidence would make your hiring decision clearer?

Bring the role and what it needs to change. We can discuss how the search and assessment should work.

Book a 20-minute founders call See how we calibrate a search