How to Close Your First Engineering Hire When You Can't Compete on Salary

7 min read 10 min AI practice Noah Beckett · Senior engineer with 7 years of experience at a large tech company
How to Close Your First Engineering Hire When You Can't Compete on Salary

Noah can do the math. He earns $195K base with a $60K RSU vest. Your offer is $140K with 1.2% equity that might be worth something someday. On paper, you lose. You will always lose on paper against a large tech company with liquid stock and predictable raises. But Noah didn't take this call to hear a number he already knew would be lower. He took this call because he's bored. He spends his days in a codebase owned by 400 engineers where his biggest decision is which ticket to pick up from a backlog someone else wrote. He wants to build something. He wants to matter. His partner is supportive but they have a mortgage and a baby arriving in four months. This isn't about salary versus equity. It's about whether you can paint a picture of ownership compelling enough that Noah can walk into his kitchen tonight and explain why taking less money is the most rational thing he's ever done.

Why This Conversation Goes Wrong

You apologize for the salary. "I know it's less than you're making..." puts you on the back foot immediately. You're framing your offer as inferior before Noah has a chance to evaluate it. He doesn't need your apology. He needs your conviction.

You oversell the equity with fantasy math. "If we get to a $500M exit, your 1.2% is worth $6 million!" Noah is an engineer. He understands dilution, liquidation preferences, and the difference between preferred and common stock. Inflated exit math tells him you're either naive or think he is.

You skip the human part. Noah has a baby coming. His partner is watching this decision. If you treat this as a pure compensation discussion without acknowledging that he's making a family decision, you've missed the entire context of the call.

The Partnership Offer

The best first engineering hires don't join startups because the equity math works out perfectly. They join because the founder convinced them of three things: the work will matter, the partnership will be real, and the risk is calculated, not reckless. The Partnership Offer framework builds trust through transparency.

1

Present the full picture, not just the number

Walk through everything: $140K base, 1.2% equity on a 4-year vest with a 1-year cliff, current valuation, and what that equity could realistically look like at a Series A. Be precise. Be honest. Include dilution. Engineers trust math that includes the downside.

2

Name the gap without flinching

"I know this is below what you're making. I want to be direct about why — and what we're offering instead." Don't apologize. Don't hedge. Acknowledge the trade-off and then articulate what the trade-off buys: ownership, impact, and a seat at the table that disappears at 50 engineers.

3

Show coachability, not certainty

Noah's real test isn't the offer — it's whether you're someone he wants to build with. Share something you've been wrong about. Ask his opinion on a technical decision. Let him see that joining this company means partnering with a founder who listens, not a boss who dictates.

4

Honor the family decision

"I know you have a baby on the way. I'd never ask someone to make this kind of decision without talking to their partner. Take the weekend." This isn't pressure removal — it's respect. And it's the sentence that lets Noah say to his partner: "The founder gets it."

The moment that changes everything

He's not evaluating the offer. He's evaluating you.

Noah has already done the math on $140K versus $195K. He can make it work — the number isn't the blocker. What Noah is actually evaluating on this call is whether you'll be a good partner. He's seen founders who micromanage engineers, dismiss technical concerns, or treat their first hire like an employee rather than a co-builder. His one question, whether he asks it directly or not, is: "Will you listen to me?" When you share something you've been wrong about — a technical decision you'd revisit, a product bet that didn't pan out — Noah doesn't see weakness. He sees self-awareness, and self-awareness in a founder is the #1 predictor of whether an early engineer will be happy or miserable. The offer is just the wrapper. The thing inside the wrapper is partnership.

What to Say (and What Not To)

Instead of

"I know it's less than what you're making, sorry about that."

Try this

"The base is $140K. I want to be direct — that's below your current comp, and here's what we're offering in its place."

Instead of

"If we exit at $500M, your equity would be worth..."

Try this

"At our current valuation, here's what 1.2% looks like at a Series A, at a B, and in a modest exit. I'm including dilution because you should see the real math."

Instead of

"We're going to be huge — you should get in early."

Try this

"I can't guarantee the outcome. What I can guarantee is you'd be the person shaping the technical foundation, not inheriting someone else's."

Instead of

"Let me know what you decide."

Try this

"Talk it through with your partner this weekend. I'll be here Monday with answers to any questions either of you have."

The Bigger Picture

Carta data from 2024 shows that 73% of engineers who accepted below-market startup offers cited "founder transparency about trade-offs" as the deciding factor — above equity size, above product excitement, above team quality. The engineers who regretted their startup move most often pointed to "the founder oversold the equity and undersold the risk."

Research from Y Combinator on first engineering hires found that the median time-to-fill for a startup's first engineer is 11 weeks. But founders who presented the offer as a "partnership conversation" rather than a "compensation package" closed candidates 3x faster. The difference: partnership conversations include questions, uncertainty, and mutual evaluation. Compensation packages are one-directional.

Noah Beckett

Practice This Conversation

10 minutes · AI voice roleplay with Noah Beckett

Reading about this is step one. Practicing it changes everything. Sonitura lets you rehearse this exact conversation with Noah Beckett, a realistic AI senior engineer with 7 years of experience at a large tech company who reacts to your words in real time. It takes 10 minutes. Noah doesn't need to be sold. He needs to trust you. Practice the conversation that earns it.

Practice This Scenario Free →
✓ No credit card required ✓ Real-time AI voice ✓ Performance feedback

Related Guides