Note: hiring your first engineer when you're the founder-CTO

This is a note, not a deep-dive. Three rules I wish I’d had before I hired the first engineer at Waffy. They’re all I’d tell another founder-CTO today.

1. Hire the de-risker, not the all-rounder

The instinct as a founder-CTO is to hire someone who can do everything you do — mobile, backend, ops, data — so you can stop wearing one of the hats. That’s the wrong frame.

The right frame: what’s the thing in the next 12 weeks that, if it goes sideways, ends the company? Hire the engineer who de-risks that thing.

At Waffy, the answer was payments + PSP integration. We could have built mobile apps faster if I’d hired a mobile-first generalist. We would not have survived the first regulatory ask without an engineer who’d previously shipped to a payment processor. So I hired that engineer first, even though I knew it meant I’d be writing iOS code at midnight for another four months.

You’re trading discomfort for survival. Take the trade.

2. The first hire sets the engineering culture forever

A culture is the set of behaviors the team forgives. Your first engineer’s behaviors get forgiven by default, because there’s no one else to compare them to. If they ship without tests, the team will ship without tests. If they comment thoroughly, the team will. If they’re cavalier about production incidents, the team will be.

You can’t fix this later. You can document a culture-doc in Notion; the team will mirror the actual person sitting next to them, not the doc.

So: interview for the behavior, not the resume. If they’re a great engineer but their on-call instinct is “wait until morning”, you are buying a future where every team member’s on-call instinct is “wait until morning”. You will not undo that with culture training.

3. Pay them like a co-founder, even if they’re not one

The first engineer is doing a job no one else on the team understands. You can’t peer-review their work yet. You can’t replace them without losing 6 months of progress. They are operationally indistinguishable from a co-founder, even if equity-wise they’re at 0.5–2%.

Pay them accordingly. Salary band: the high end of senior-engineer for your geography, not the middle. Equity: more than feels comfortable. Visibility: in every founder-only conversation that touches engineering. Trust: total, until they break it once.

The math: a first engineer who’s 70% the cost of “fair” leaves within 18 months. They leave because they can see — sooner than you can — that the relationship is asymmetric. You lose ~6 months of company progress recovering from that. The cost of paying them fairly is much, much less than the cost of replacing them.

The shape it looks like

If I were starting Waffy today, the job description would be one line:

Senior engineer who’s shipped to a regulated payment system before. First engineer at a fintech. Comfortable being the only one on-call for ~6 months. Equity: 1.5–2%. Salary: top decile for Cairo or Madrid (your pick).

That’s it. No “10x”, no “rockstar”, no “full-stack”. The person who reads that and says yes is the person you want.

— Ahmed

Notes are short. If you want the longer version — the architecture story, the actual numbers — that’s in Build Notes. The next deep-dive lands shortly.