Mandate audit
Pressure-test the search before you spend on it
The mandate audit is a working conversation, not a download. There is no form and no gate. It looks at four things that decide whether a search succeeds.
01
Role scope
What will the person own after onboarding, and what sits outside the mandate? Which layer of the system is it: consensus, ledger, serving path, platform, commercial?
02
Sequencing
Which milestone is the hire meant to affect, and does the start date allow it? Should an executive hire come before or after the engineering leader beneath them?
03
Assessment criteria
What evidence will you accept: systems operated, incidents handled, scale reached? How does the Distributed Systems Filter map to the specific system the person will work on?
04
Decision ownership
Who decides, who is consulted and how fast? Searches move at the speed of decisions. TTR's reported 14–21 days to offer is a benchmark, not a promise for every mandate.
05
What to pressure-test
Confirm the audit scope and any follow-up deliverables with Emily during the intro call.
- Whether the role scope matches the business need
- The sequence of engineering and operational hires
- The evidence needed to assess candidates
- Decision ownership and the search process
FAQ
Direct answers
- Is the audit a download?
No. It is a conversation with Emily Landon. There is no form, gate or file.
- Do I need a job description?
No. Many audits begin before a description exists.
- Does booking an intro call commit us to a search?
The intro call is for discussing the mandate. Any search scope, deliverables and engagement terms are confirmed separately with Emily.
- How long does it take?
The intro call is the first step. Bring the role, the timeline and the open questions.
Next step
Pressure-test the search with Emily
Bring the role, even if the scope is unsettled. The intro call is where we pressure-test it and confirm guarantee terms.