They create three role-specific variations. Software Engineer emphasizes low-latency systems and ML infrastructure. Research Scientist highlights publication opportunities and novel mathematical frameworks. Business Operations focuses on scaling challenges and equity compensation.
Alex compiles the drafts into an email to Maddy.
Subject: Job description review - need feedback by EOD
Maddy,
Jian and I drafted company descriptions for our open roles. Attached: three versions (general, technical, business) plus role-specific variations.
Key points we're emphasizing:
• 98% reduction in risky LLM outputs
• Post-processing alignment (no retraining needed)
• Mathematical approach, not heuristic filtering
• 3→15 person growth phase
• Backed by tier-one investors
Review for tone and accuracy. Specifically: does the sales angle in the general description work? We're positioning you as enterprise sales background, which is true but might need your framing.
Need to post by tomorrow to start generating pipeline.
Alex
The conference room in the new Oakland office smells like fresh paint and ambition. Floor-to-ceiling windows look out over a parking lot and, beyond that, the Bay glinting in the afternoon sun. Alex leans back in his chair, which is still the same IKEA model from his grad school apartment because some habits die hard, and surveys the space.
"We actually did it," he says. "Fifteen people. Three months late and double the budget, but we did it."
Jian doesn't look up from his laptop. "The job boards were a disaster."