Home โ€บ Blog โ€บ The Maestro, Season 2 ยท Part 2
The Maestro, Season 2 ยท Part 2 ยท Phase 5 ยท ๐Ÿ‘ฅ CEO hat

Building the Team

With $60M in the bank, the constraint is no longer money: it is people. Gopala has to grow a company of three into a company of about forty in a year, without losing the habits that made Season 1 work: arithmetic before decisions, evidence before claims, and a gate nobody can bypass. This part covers the shape of the organisation, the order of the first 36 hires and why the safety lead is hire number five, how roles are designed, the hiring loop and what research says actually predicts performance, pay and equity, AI agents as teammates, and the hardest part: what Gopala stops doing.

FL
FrontierAGI Team
๐Ÿ’ผ CEO๐Ÿ‘ฅ Recruiter๐Ÿง‘โ€๐Ÿซ Manager๐Ÿ”ฌ Researcher
โš ๏ธ How to read this (as of 2 Nov 2026) hiring_plan.py and hat_hours.py were run (real output below). Salaries, hire dates, hours and every person are the story's scenario; salary bands are not market data. Research on hiring methods is cited. Gopala and his company are a teaching story. Disclosure: Claude, made by Anthropic, helps write this site.

1. Mission log: months 22โ€“26

Week 92 ยท The org chart
  • Draws the target organisation for month 34 before posting a single job; agrees it with the board.
Week 93 ยท First two leads
  • Research lead and head of infrastructure start (both from his Season 1 network).
Week 96 ยท The safety lead
  • Hires the safety and evaluation lead before any new training work starts; hands over the gate's day-to-day running.
Week 104 ยท Twenty-one people
  • Headcount 21 at month 26; the first all-hands where Gopala does not know every detail of every project.

2. The organisation at month 34

Who owns what at month 34 (scenario)

๐Ÿ”ฌ Research ยท 10 peoplemodel, data, the loop, environments
๐Ÿ–ฅ๏ธ Infrastructure ยท 6cluster, training and serving platforms
๐Ÿค– Product ยท 8agents, integrations, the harness
๐Ÿ›ก๏ธ Safety & evaluation ยท 4the gate, evaluations, red team, security
๐Ÿ“ฃ Go-to-market ยท 6sales, solutions, customer success
๐Ÿงพ Operations ยท 2finance, people, legal and compliance
๐Ÿ’ผ CEO + 2 Season 1 hiresstrategy, the board, the gate rule

From hiring_plan.py: 36 planned hires plus the three people from Season 1.

3. The order of the first 36 hires

hiring_plan.py ยท Python 3, no dependencies; scenario dates and salaries
"""hiring_plan.py โ€” the first 36 hires after the Series A, in order.

Fully loaded cost = salary + equity value is NOT included; this is cash:
salary, benefits, payroll tax, laptop and tools (our assumption: 1.3 x base).
Base salaries are SCENARIO bands for a remote-first company hiring globally,
not market data. Each row: month the person starts, team, role, base $k/yr.
"""
LOAD = 1.3
PLAN = [
    (22, "research", "research lead (post-training & RL)", 330), (22, "infra", "head of infrastructure", 300),
    (23, "product", "head of product engineering", 280), (23, "gtm", "founding account executive", 190),
    (23, "safety", "safety & evaluation lead", 280), (24, "research", "research engineer: environments", 250),
    (24, "research", "research engineer: data", 250), (24, "infra", "ML infrastructure engineer", 240),
    (24, "product", "product engineer: agents", 220), (24, "ops", "finance & people operations", 170),
    (25, "research", "research scientist: RSI levels", 300), (25, "product", "product designer", 190),
    (25, "gtm", "solutions engineer", 200), (25, "safety", "red-team engineer", 240),
    (26, "infra", "site reliability engineer", 220), (26, "research", "research engineer: evals", 240),
    (26, "product", "product engineer: integrations", 210), (26, "gtm", "customer success lead", 170),
    (27, "research", "research scientist: pre-training", 310), (27, "infra", "kernel & performance engineer", 280),
    (27, "product", "product manager: platform", 220), (28, "gtm", "account executive", 180),
    (28, "research", "research engineer: synthetic data", 240), (28, "safety", "security engineer", 240),
    (29, "infra", "ML infrastructure engineer", 240), (29, "product", "product engineer: harness", 220),
    (30, "research", "research engineer: training", 250), (30, "gtm", "solutions engineer", 200),
    (30, "ops", "legal & compliance counsel", 260), (31, "research", "research scientist: agents", 300),
    (31, "product", "product engineer: enterprise", 210), (32, "infra", "site reliability engineer", 220),
    (32, "gtm", "head of sales", 260), (33, "research", "research engineer: RL", 250),
    (33, "safety", "evaluation engineer", 230), (34, "product", "developer relations", 190),
]

def main():
    teams = sorted({p[1] for p in PLAN})
    print("month  headcount  people $M/month  " + "  ".join(f"{t:>8}" for t in teams))
    for m in (22, 24, 26, 28, 30, 32, 34):
        on = [p for p in PLAN if p[0] <= m]
        cost = sum(p[3] for p in on) * LOAD / 12 / 1000 + 0.025   # + Gopala and the two Season 1 hires (scenario)
        print(f"{m:5}  {len(on) + 3:9}  {cost:15.2f}  " + "  ".join(f"{sum(1 for p in on if p[1] == t):8}" for t in teams))
    first5 = [p[2] for p in PLAN[:5]]
    print("first five:", "; ".join(first5))
    print(f"research share of hires: {sum(1 for p in PLAN if p[1] == 'research') / len(PLAN):.0%}")

if __name__ == "__main__":
    main()
$ python3 hiring_plan.py # scenario plan; cash cost = 1.3 x base month headcount people $M/month gtm infra ops product research safety 22 5 0.09 0 1 0 0 1 0 24 13 0.30 1 2 1 2 3 1 26 21 0.49 3 3 1 4 5 2 28 27 0.65 4 4 1 5 7 3 30 32 0.77 5 5 2 6 8 3 32 36 0.88 6 6 2 7 9 3 34 39 0.95 6 6 2 8 10 4 first five: research lead (post-training & RL); head of infrastructure; head of product engineering; founding account executive; safety & evaluation lead research share of hires: 28%

Headcount and monthly people cost (scenario)

Month 225 people ยท $0.09M/month
Month 2621 ยท $0.49M
Month 3032 ยท $0.77M
Month 3439 ยท $0.95M

Real output of hiring_plan.py. People cost is cash only; equity is on top.

4. Designing roles before posting them

5. The hiring loop, and what predicts performance

The hiring loop

๐Ÿ“จSourcenetwork, referrals, posts
๐Ÿ“žScreen30 min with the lead
๐ŸงชWork samplepaid, ~4 hours, real problem
๐Ÿ—ฃ๏ธStructured interviewsscored before discussion
๐Ÿ“‡Referencesspecific examples
โœ…Decideany interviewer can block

Structured, scored independently, and built around the real work.

6. What Gopala stops doing

hat_hours.py ยท Python 3, no dependencies; scenario hours
"""hat_hours.py โ€” where Gopala's 60-hour week goes, before and after hiring.

Hours are the story's SCENARIO estimates from his own calendar review.
The rule he follows: keep what defines the company (strategy, the gate,
research direction, hiring the leads), hand off what someone else can do better.
"""
WEEK = 60
BEFORE = {"coding & infra": 14, "on-call & ops": 8, "customer support": 7, "sales calls": 8, "research": 9,
          "the gate (reviews)": 5, "fundraising": 4, "hiring": 3, "admin & finance": 2}
HANDOFF = {"coding & infra": ("head of infrastructure", 12), "on-call & ops": ("SRE rota", 8),
           "customer support": ("customer success lead", 6), "sales calls": ("account executive", 5),
           "admin & finance": ("finance & people ops", 2)}
NEW = {"hiring": 9, "strategy & board": 6, "1:1s with leads": 5, "fundraising": 2}

def main():
    after = dict(BEFORE)
    for k, (who, h) in HANDOFF.items():
        after[k] -= h
    for k, h in NEW.items():
        after[k] = after.get(k, 0) + h - (BEFORE.get(k, 0) if k == "fundraising" else 0)
    print(f"{'activity':22} {'month 18':>8} {'month 26':>8}")
    for k in sorted(set(BEFORE) | set(after), key=lambda k: -after.get(k, 0)):
        print(f"{k:22} {BEFORE.get(k, 0):8} {after.get(k, 0):8}")
    print(f"{'total':22} {sum(BEFORE.values()):8} {sum(after.values()):8}")
    keep = after["research"] + after["the gate (reviews)"] + after["strategy & board"] + after["hiring"]
    print(f"share on what only he should do: {(BEFORE['research'] + BEFORE['the gate (reviews)'] + BEFORE['hiring']) / WEEK:.0%} -> {keep / WEEK:.0%}")

if __name__ == "__main__":
    main()
$ python3 hat_hours.py # scenario hours from his calendar review activity month 18 month 26 hiring 3 12 research 9 9 strategy & board 0 6 the gate (reviews) 5 5 1:1s with leads 0 5 sales calls 8 3 fundraising 4 2 coding & infra 14 2 customer support 7 1 on-call & ops 8 0 admin & finance 2 0 total 60 45 share on what only he should do: 28% -> 53%

Gopala's week, before and after (scenario hours)

Coding & infra: before14 h
Coding & infra: after2 h
Hiring: before3 h
Hiring: after12 h
On-call & ops: before8 h
On-call & ops: after0 h
Strategy & board: after6 h

Real output of hat_hours.py. Share of time on CEO-only work: 28% โ†’ 53%.

7. Try it: hand off a hat

Gopala's week (our model, same numbers as hat_hours.py)

8. Pay and equity

The pool and the ladder (scenario)

12%option pool after Series A
4 yrvesting, 1-year cliff
~6%granted by month 34
~6%kept for later hires

Pool from series_a.py; the split is the story's plan.

9. AI agents as teammates

10. The first 90 days of the research lead (scenario)

Scenario
  • In week six the research lead proposes merging the gate review into the research team's weekly meeting to save time. Gopala says no, and asks the safety lead to explain why in writing to the whole team.

11. Writing down the culture

12. Remote-first, across time zones

13. Why the safety lead is hire number five, not twenty-five

14. The first two weeks of every hire

15. Levels and two career tracks

The two tracks (scenario)

L5 ยท Principalshapes company direction in a field
L4 ยท Staffowns a system or research area across teams
L3 ยท Seniorowns projects end to end
L2 ยท Engineerowns tasks, grows into projects
L1 ยท Juniorlearns with close support (few in year one)
M1โ€“M3 ยท Lead โ†’ head โ†’ executivemanager track, paid in the same bands as L3โ€“L5

The ladder is the story's; the two-track structure is common practice in engineering organisations.

16. Keeping people

17. Eight team-building mistakes

18. Delegation box

๐Ÿ™‹ Gopala himself
  • Hiring the leads and every early hire
  • The org design and the culture principles
  • The gate's rules (the safety lead runs it day to day)
๐Ÿค– AI agents
  • Sourcing lists and interview logistics
  • Draft role briefs and work samples, checked by the leads
  • Running hiring_plan.py scenarios for the board
๐Ÿค Bought, rented or borrowed
  • A recruiting partner for go-to-market roles
  • Employment counsel for remote contracts in several countries
  • A payroll and benefits provider

19. Budget and risk tracker

ItemStatus after Part 2Note
Headcount21 at month 26 โ†’ 39 planned at month 34From hiring_plan.py
People cost$0.49M/month at month 26 (scenario)$0.95M planned at month 34
Gopala's CEO-only time28% โ†’ 53%From hat_hours.py
Hiring riskWatchOne mis-hire in the first ten
Gate riskLowerTwo-approval rule enforced in tooling
Culture riskWatchHalf the company joined in six months

20. The series

The Maestro, Season 2: 23 parts in five phases (Season 1: 18 parts)

VerdictThe team is the product of Season 2's first year. Gopala hires the leads first, puts the safety lead fifth so the gate has an owner before research doubles, tests real work instead of reputations, and gives away the hats that someone else can wear better. What he keeps is what defines the company. Next: where the company plays, and where it does not.

21. Reading the numbers

Primary / standard
Schmidt and Hunter (1998) and Sackett et al. (2022) on selection methods; role families from the Who Runs the AI Factory series.
Secondary โš ๏ธ
None in this part.
Our assumptions
All people, dates, salaries, hours, grants and the 1.3ร— loading are the story's scenario.