When should I hire my first operations or 'chief of staff' person, and what should they own?
The short answer
Hire ops the moment you (the founder) become the bottleneck for things that are not product or sales, usually around 8 to 15 people. Give them the boring load-bearing work: vendor payments, compliance calendar, tooling, onboarding, and meeting hygiene. Do not make it a vanity 'chief of staff' title with no P&L; make it a real owner of 'how the company runs day to day' so you get your calendar back.
Go deeper, your way
3 hand-picked resources, 3 link-checked. Pick how you want to dig in.
📄 Article
✓ Link checkedFreeBeginner
Why we picked it
Written by PostHog's operations lead, this is the sharpest piece on hiring for judgment over resume. Its core claim, attributes far outweigh technical expertise, maps exactly to our answer: your first ops person will hold admin access to your banking, passwords, and infra, so trust, unflappability, and extreme optimism matter more than a shiny CV. It even hands you interview questions and antipatterns for each trait.
Ops is a purely defensive role early on: up to roughly 50 people you are putting out fires, not building systems for hyperscale, so hire someone who stays calm when blamed.
This hire gets top-level access to banking, passwords, and infrastructure, so if you would not trust them with that, keep looking.
Screen for optimism and dependability with real questions, not for pedigree; a great generalist beats a specialist who cannot roll up their sleeves.
Why we picked it
The canonical piece for avoiding exactly the vanity-title trap you warn against. It caps the role at about 20% admin work (so it is not a glorified PA), levels the scope by company size (executive support at 20+, leadership-team support at 75+, stealth-COO at 150+), and hands you a real hiring scorecard via its Mission-Outcomes-Competencies framework so you interview against defined competencies (super organizer, reliable closer, trusted operator) instead of vibes.
Cap admin work at roughly 20%; the role owns systems, operating cadence, and cross-team execution, not the founder's calendar alone
Scope the role by headcount: direct thought partner at ~20 people, leadership-team leverage at ~75, org design at ~150
Interview against a written scorecard (Mission, Outcomes, Competencies) and treat it as a 2 to 3 year post with a planned exit into functional leadership
Why we picked it
This is the concrete, copy-paste artifact the other two essays lack: a real JD skeleton (summary, Who You Are, nine responsibilities, qualifications) plus ten interview questions you can lift straight into a scorecard. It explicitly leaves 10 to 20% of the mandate undefined for the hire to shape, and shows how to swap in your gap areas (finance, HR, sales ops) so a 10 to 20 person startup can spec the exact boring load-bearing surface, vendor payments, onboarding, tooling, that you are trying to offload.