How to hire first rockstar employee

Picture this: it’s 7 p.m., the cleaners are vacuuming the hallway of our shared office space, and I’m still fiddling with a broken CI pipeline. At that moment it hit me—whoever I hire first will be stuck in this room with me, breathing warm server-heat air, for longer stretches than most married couples spend together. That person needs grit, curiosity, and a sense of humor about flaky Wi-Fi. Anything less and we’ll both go insane.

Two quick reality checks before we even draft the job post:

1. Skip the “guru / ninja / rockstar” lingo. Every time I see it, I picture a mid-2000s PowerPoint with flames. Serious candidates bail (I know I would).
2. If you expect your first hire to match your output and decision weight, what you’re really hunting for is a co-founder. That means equity, shared risk, the whole package—otherwise the math just won’t add up for them.

Start by writing down the actual work. Not the aspirational stuff—the Jira tickets you’ll assign next Tuesday. Languages, tools, meetings cadence, on-call duties, coffee runs (kidding, mostly). I iterate on that doc until it stops sounding like marketing copy and starts sounding like Tuesday at 11 a.m. (I’ve thrown out at least five fluffy drafts before landing on something usable.)

If you’re in the “need-a-technical-co-founder” camp, I already wrote a separate guide. Different beast, different playbook.

Now gut-check your culture. Are we talking remote-first with async stand-ups, or pair-programming until midnight? Do we have six months of runway or twelve? And—important since 2020—how do you keep people sane? Candidates have started asking about mental-health budgets and whether the calendar makes space for a lunchtime run. I used to shrug this off; after my own burnout episode in 2019 I no longer do.

A polished site and crisp LinkedIn banner help, but don’t hide behind them. Job ads are notorious for burying the real work. Offer an open Q&A with the team, maybe a half-day paid trial. Let candidates poke at the codebase (within reason) and meet the actual humans. Transparency does more than any hero video on a landing page.

Some engineers care less about ping-pong tables and more about impact. Be candid: joining a seed-stage startup isn’t the only route to meaningful work—academia and NGOs often ship life-changing tech with fewer 2 a.m. deploys. I mention this upfront. Oddly, honesty makes people lean in, not out.

When someone considers jumping aboard, fear takes the driver’s seat. They’re about to swap the comfort of predictable paychecks for a rocket that might explode on the pad. I keep a small FAQ handy and update it after every interview. Yours will differ, but mine usually starts here:

• What does your runway look like? Do you have enough money?
• What is our company’s story?
• What does your target market look like? What size it is?
• How many competitors do you have?

I’ve also begun adding “How will you support my physical and mental health?” Because people ask, and fair enough. Concrete answers help: stipends for a gym membership, no Slack on weekends, mandatory vacation tracking (yes, you can enforce taking days off—it works).

One trick that eased nerves for a recent hire: we started him at 60 % capacity for two months. Salary pro-rated, equity full. Gave both sides breathing room. He could bail gracefully; we could too. Turned out great, but even if it hadn’t, nobody would have mortgaged their future on a bad fit. (I’m not entirely sure this scales beyond the first couple of employees, but it’s handy early on.) However, there were still challenges in ensuring the workload was balanced and that expectations were managed effectively.

It’s tempting to think the first hire is special and everything after will be routine. Truth is, the questions stay the same—your credibility just compounds. With each successful sprint, candidates see proof rather than promises, and those late-night “are we doomed?” conversations get shorter.

📚 More Q&A here