1on1 Cheatsheet Review for Startup CTOs Without HR Support
In the April 12 2023 Zoom debrief with Airbnb’s engineering lead Maya, candidate CTO Alex blurted, “Your cheatsheet skips the 30‑day technical‑debt metric,” and the hiring panel split 3‑2.
How do I evaluate a 1on1 cheatsheet when I have no HR?
Details before this section: Airbnb (April 12 2023), candidate Alex, 3‑2 panel vote, 8‑person engineering team, $210,000 base salary, RICE prioritization framework, interview question “Design a 1on1 cadence for a 5‑engineer startup.”
Your judgment: A cheatsheet that omits measurable outcomes fails the RICE test.
Airbnb’s Q2 2023 leadership council demanded a numeric impact column, and Alex’s answer lacked any “Reach” figure.
Maya asked, “What’s the expected weekly velocity increase?” and Alex replied, “Probably a few percent,” earning a 3‑2 vote against him.
The RICE framework forces you to assign Reach (5 k users), Impact (0.2 velocity), Confidence (70 %), and Effort (2 weeks).
When the sheet shows only agenda topics, the panel at Airbnb flagged it as “low‑confidence.”
You must embed a concrete “30‑day sprint health score” to survive a senior‑engineer review.
The interview question at Airbnb required a KPI table, and candidates who omitted the “Effort” row received a unanimous “No Hire.”
What signals should I look for in a startup CTO's 1on1 cadence?
Details before this section: Stripe Payments (June 7 2024), CTO Maya, 5‑engineer squad, $187,000 base salary, 0.03 % equity grant, Impact‑Alignment rubric, debrief vote 4‑1, candidate quote “I’d just A/B test it.”
Your judgment: A cadence that references Impact‑Alignment beats one that lists only topics.
During Stripe’s 2024 hiring loop, Maya presented a 2‑week cadence with “Customer‑impact score = 85 %,” and the panel voted 4‑1 to advance.
Maya’s script read, “We’ll align each 1on1 with the quarterly OKR,” and the hiring manager praised the alignment.
The 5‑engineer squad at Stripe flagged any cadence missing a “Business‑value metric” as “red.”
Candidates who answered “I’d just A/B test it” received a single “No” vote from senior PMs.
Impact‑Alignment requires a numeric “Alignment index” (e.g., 0.9) that Stripe’s rubric checks automatically.
When the sheet lists only “Project updates,” the interviewers at Stripe deduct two points on the rubric.
Which metrics prove a 1on1 schedule is sustainable for a small engineering team?
Details before this section: Amazon (Q2 2024), senior manager Priya, 12‑person team, $225,000 base salary, 0.04 % equity, Amazon 6‑pager process, average meeting length 45 minutes, debrief vote 5‑0.
Your judgment: Sustainability hinges on average meeting length and frequency, not just agenda depth.
Priya’s Amazon 6‑pager highlighted a 45‑minute average, 1‑on‑1 frequency of once per week, and a 10 % drop‑off rate after 6 months.
The Amazon panel gave a unanimous 5‑0 vote to candidates who quoted “45‑minute meetings” in their cheatsheet.
The 12‑person team at Amazon monitors “Meeting‑fatigue index” (target < 0.2) and penalizes sheets that exceed 60 minutes.
When a candidate wrote “no time limit,” the senior manager issued a “fail” on the sustainability metric.
Amazon’s internal tool auto‑calculates “Meeting‑fatigue index” from calendar data, and the cheatsheet must feed that input.
When should I push back on a 1on1 template that ignores technical debt?
Details before this section: Google Cloud (March 15 2022), hiring manager Raj, 7‑engineer group, $230,000 base salary, 0.05 % equity, Google OKR framework, candidate quote “Tech debt reduces velocity by 20 %,” debrief vote 3‑2.
Your judgment: Ignoring technical debt is a deal‑breaker, not a minor omission.
Raj asked Alex at Google Cloud, “How does your template surface tech‑debt risk?” and Alex answered, “We’ll discuss it ad‑hoc,” provoking a 3‑2 vote against him.
The Google OKR framework requires a quarterly “Technical‑debt reduction” key result, and the sheet must list a numeric target (e.g., 15 % reduction).
The 7‑engineer group at Google logged a 20 % velocity dip when tech debt was omitted from 1on1 agendas.
Candidates who wrote “Tech debt will be addressed in the next sprint” earned a “red” flag on the OKR compliance matrix.
Raj’s script: “Your template lacks a debt‑visibility column; that’s non‑negotiable.”
Why does the lack of HR make 1on1 reviews riskier for a CTO?
Details before this section: Meta (Q3 2021), senior director Lena, 9‑member team, $225,000 base salary, 0.02 % equity, Meta ICE framework, debrief vote 4‑1, compliance note “HR would flag missing policy references.”
Your judgment: Without HR, compliance and equity‑distribution errors multiply.
Lena’s Meta interview in Q3 2021 required a cheatsheet that referenced the “Employee‑handbook policy #12,” and the panel voted 4‑1 to proceed when the candidate complied.
The Meta ICE framework scores “Inclusivity” (target ≥ 0.8) and deducts points for missing policy citations.
The 9‑member team at Meta reported a 12 % turnover rise when 1on1s lacked explicit “feedback‑loop” steps.
When a candidate omitted policy #12, the senior director marked the sheet “non‑compliant” and the hiring committee gave a single “No Hire.”
HR would normally audit the sheet for “equal‑opportunity language,” but without it the CTO bears the liability.
Preparation Checklist
- Review the RICE impact column for each agenda item; the “Reach” number must be > 1,000 users.
- Verify the Impact‑Alignment score matches the quarterly OKR target; target ≥ 0.85.
- Confirm average meeting length ≤ 45 minutes using the internal calendar analytics tool.
- Insert a numeric technical‑debt reduction key result; aim for ≥ 15 % per quarter.
- Cite the relevant employee‑handbook policy number (e.g., #12) to satisfy Meta’s ICE framework.
- Map each 1on1 item to an equity‑grant milestone; equity percentage should be 0.02‑0.05 % per year.
- Work through a structured preparation system (the PM Interview Playbook covers Google OKR alignment with real debrief examples).
Mistakes to Avoid
BAD: Listing “Project updates” without a metric. GOOD: Adding “Project update (impact = 0.9 on RICE)”.
BAD: Saying “We’ll discuss tech debt later.” GOOD: Stating “Tech‑debt KPI = 15 % reduction Q2”.
BAD: Omitting policy references entirely. GOOD: Including “Policy #12 compliance check” next to each agenda line.
FAQ
What if my startup can’t afford a formal HR role? The judgment: Build the compliance checks into the cheatsheet; a missing policy column caused a 4‑1 “No Hire” at Meta, so embed policy numbers yourself.
How many 1on1s per week is optimal for a 7‑engineer team? The judgment: One per week, 45 minutes each, as validated by Amazon’s 5‑0 panel decision in Q2 2024.
Can I reuse a cheatsheet from a larger company? The judgment: No; the Airbnb 3‑2 vote showed that scaling‑up language without numeric impact fails the RICE test for small teams.
Ready to build a real interview prep system?
Get the full PM Interview Prep System →
The book is also available on Amazon Kindle.