Team, Co-founders & Legal

When should I hire my first operations or 'chief of staff' person, and what should they own?

A starting point

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

Hand-picked from around the web, each with a note on why it earns your time.

3 resources 3 link-checked Read Use

Read

📄 Article
✓ Link checked Free Beginner

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.

Making your first startup ops hire: what founders should look for

From PostHog by Charles Cook 10 min read

  • 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.
Open posthog.com →
📄 Article
✓ Link checked Free Intermediate

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.

How to Hire a Chief of Staff

From a16z by Andreessen Horowitz (a16z) 15 min read

  • 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
Open a16z.com →

Use

📋 Template
✓ Link checked Free Intermediate

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.

Chief of Staff Job Description, Duties & Interview Questions

From vChief by vChief 12 min read

  • Ships a fillable JD plus interview-question set you can drop into a hiring scorecard the same day
  • Deliberately leaves 10 to 20% of the role undefined so the first hire shapes the messy edges you cannot pre-spec
  • Prompts you to name your own gap areas (finance, HR, ops), which is exactly how you decide what stays with the founder versus what they own
Open vchiefs.com →

People also ask

How do I build company culture intentionally from day one? Culture is what you do repeatedly and reward, not a poster of values, so your own behaviour and your first hires set it whether you're deliberate o... Intermediate 3 resources → Should my startup be remote, hybrid, or in-office? Remote works and widens your talent pool massively, 37signals has run a calm, remote-first company for two decades, but it demands strong async wri... Intermediate 2 resources → How do I run a remote team without endless meetings and burnout? Default to async: write things down, replace status meetings with written updates, and protect long stretches of uninterrupted focus, real work hap... Intermediate 3 resources → What operating cadence and rituals should an early team have? Keep it lean: a short weekly written update, clear owners for every project, and one focused planning rhythm (weekly or bi-weekly) is enough at fir... Beginner 3 resources → How do I avoid burning out my small team while still moving fast? Reject the 'crazy at work' hustle myth, sustained output comes from calm, focus, and reasonable hours, not heroics and permanent crunch. Protect pe... Intermediate 3 resources → How do we preserve culture and values as we grow past the first team? Codify your values into concrete hiring, feedback, and promotion decisions, culture scales through who you reward and who you let go, not through s... Advanced 3 resources →