Why your founding engineer role has been open for four months

By Ken Vermeille. Senior mobile engineering, embedded in your team in 5 days. 15 years, 4 founder exits. The alternative to a 6 month, $200K hire.

The job post asking one person to do everything is the reason you cannot hire anyone, and it is the most expensive line item you are not tracking.

You have a founding mobile engineer role open. It has been open for months. You have decided the market is tight, or the candidates are weak.

The market is fine. Your job post is the problem, and it is quietly spending a quarter of runway you are not getting back.

Here is the one I read this week, lightly anonymized. Founding mobile engineer, React Native. 200 to 250K, a little equity. One paragraph asks for one year of experience. The next asks for two. Team of six, building a social platform for AI mini apps.

The job: build and ship the entire app across iOS and Android, own the mini app runtime, the feed, the creation flow, and sharing, and make the architecture calls on performance and animation. One person.

Nobody good enough to do that has two years of experience. Nobody with two years of experience can do that. So the seat stays empty, and every week it stays empty is a week you are not in market.

You scoped a team and tried to buy it with one salary

I read two more the same afternoon.

One wanted a single founding engineer to own the mobile platform end to end, ship the AI features, define the infrastructure, and integrate TikTok, Meta, Instagram, Shopify, and the backend. Five external services. One person. They offered dental.

The other wanted a senior engineer in New York, 150 to 225K, to own the entire app, architect the infrastructure, build the wallet and rewards and travel flows, and personally own payments, authentication, and consumer data. The fintech surface of the whole company. One hire.

Same mistake in all three. You priced a team as one role and addressed it to one person. That is not something better sourcing fixes. You wrote a job no qualified person will accept, and the few who do accept it are telling you something about their judgment before they write a line of code.

What you are actually buying if someone says yes

Assume you find someone good. Here is what that one hire gets you.

A solo engineer on React Native owns two operating systems that disagree with each other. Code that runs clean on iOS breaks on Android, and the reverse, and you will not see it in the demo. You will see it after launch, when 3% of your Android users cannot open the app and you find out from a one star review. That is your churn and your support load, not the engineer's bad afternoon.

You also handed one person payments and consumer data on the side. Wallet and payment work has native rules that do not forgive shortcuts. Miss one and Apple rejects the build and your launch slips a month. Miss another and you ship a data hole you discover at the worst possible time. Money needs an owner whose only job is the money. You gave it to the person already building the feed.

The first hire does do everything for a while. The mistake is running your company as if that is permanent. It is a bridge to a real engineering function, not the function itself, and bridges are not where you put your users and your revenue.

The question your post forgot to ask

Every one of these companies is building AI features. None of them screened for the one skill that decides your AI bill.

I covered the economics last issue, so here is the short version. A senior who knows your codebase gets the agent to ship the right change for about a dollar. A weaker hire prompts and re prompts, burns a thousand, ships something worse, and looks productive on the credit dashboard. You are the one paying that bill. Your post should have asked the only question that protects it. If we hand you a budget, is it gone by the 14th.

Three decisions that fill the seat and protect the money

All three are yours to make, not the candidate's.

Scope the role to reality and it will fill. A two year engineer cannot build a high traffic consumer app, with or without AI. Either pay for the experience the scope demands, or cut the scope so a real person can say yes. Right now you are doing neither, which is exactly why the seat is empty and the runway is moving.

Screen for one thing. Can they ship code that survives real users and makes money. Not LeetCode. Not a take home the model solves in another tab. Put them on your actual product for a few paid weeks and watch how they get unstuck and how they spend credits. That is the only signal AI cannot fake, and it is the one that protects your spend.

Hire two, not one. You will resist this because two reads as more burn. One unicorn is a single point of failure you are paying 225K to create. The day they quit, your product goes dark and nobody left can find the bug. Two engineers who review each other's work, one owning the core and one owning the money, give you a product that survives a resignation and a codebase two people actually understand. That is cheaper than it looks the first time something breaks.

The cold start

Your first real mobile engineering function is a cold start. The first hundred days decide whether the product snaps to life or stalls, and the clock running underneath it is your runway. A four month vacancy spends that clock on nothing.

The faster start is a function that already has the bench. The iOS depth, an owner for the money, a second set of eyes on every change, in market in days instead of the quarter it takes to fail to hire one person who can do all of it. That is what we build at Vermillion. Because your first hundred days do not pause while a req sits open.

AI did not make one engineer equal to a team. It made a good team faster and a bad job post more expensive.

You can leave the unicorn rec open another four months. Or you can be in market next week.

The Cold Start, by Ken Vermeille. We build embedded senior engineering for product companies.

Forward this to your favorite founder.