RecruitHow We Run a Founding Engineer Search
The pattern a founding-engineer search follows at Recruitmint, including where equity fits into calibration, described generally rather than as one client's story.
The pattern a founding-engineer search follows at Recruitmint, including where equity fits into calibration, described generally rather than as one client's story.
A founding-engineer search is unusually equity-heavy in its calibration stage, and getting that band wrong before you post the role is a common reason these searches stall. This describes the general pattern a founding-engineer search follows, not a narration of any specific past client search. The only named placements we disclose are the four published testimonials on our site.
Founding Engineer sits among the roles we name under Product, Technology & AI, alongside AI Engineer, Full-Stack Engineer and Staff Software Engineer. It is different from those other three in one specific way: the offer is rarely just a salary. It is a salary plus an equity grant, and that grant swings far more, company to company, than base pay ever does.
Carta's research on founding-engineer equity, drawn from real cap-table grants and published in December 2025, found a median first-engineer equity grant of 1.54 percent, with a 25th-to-75th-percentile range of 0.61 percent to 3.5 percent. That is Carta's data, not ours, and it is a useful anchor for a founder who has never priced this hire before.
The range matters more than the median. A founder calibrating a founding-engineer offer at the 25th percentile and a founder calibrating at the 75th percentile are not making a small adjustment, they are making structurally different offers, and candidates who have done this before will notice which one they are looking at. Stage, funding raised, existing team size and how much technical ownership the role actually carries all push the number around inside that band. A search that skips this conversation and jumps straight to sourcing tends to produce a shortlist the founder cannot actually close, because the offer was never calibrated to what the market expects for the scope described.
Base salary needs its own reference point, separate from equity. The U.S. Bureau of Labor Statistics reported a median annual wage of $133,080 for software developers in May 2024. A founding engineer is rarely a median software developer, the role usually carries more ownership and more risk, but that figure is a public starting point for the base-salary half of the conversation before equity gets layered on top.
The shape below is the same shape we run for other Product, Technology & AI roles, adapted for the fact that this one has an equity conversation built into calibration from the start.
Calibration establishes what the founding engineer actually owns, how senior the hire needs to be relative to the founder's own technical depth, and where the offer should land inside a base-plus-equity structure. This is the stage where Carta's 1.54 percent median and its 0.61 percent to 3.5 percent range get placed against the specific mandate: how early is the company, how much has already been built, what does the founder still need to own personally versus hand off. It is also where the BLS median wage figure for software developers gets used as a sanity check on the base half of the offer, adjusted for the fact that a founding engineer's scope is usually broader than a standard developer role.
Calibration also decides the model. A founder who knows the role cold and has interview bandwidth internally is a Sourcing Sprint candidate. A founder who needs someone to run assessment, interviews, offer and close end to end is a Full Search candidate. A team hiring a founding engineer alongside three or four other technical roles at once is usually looking at Embedded Partner. The Hiring Scorecard walks through this in about two to three minutes and recommends the model that fits.
Once the mandate and the equity band are set, sourcing and qualification identify, engage and qualify candidates against that specific standard, not a generic "senior engineer" search. For a founding-engineer role this usually means looking for people who have shipped something from close to zero before, who are comfortable with the equity-heavy, lower-cash-certainty structure the role implies, and who can operate without much scaffolding around them.
We search across six regions for this role: Western Europe, North America, the Balkans, Eastern Europe, the Middle East and Latin America. The strongest founding-engineer candidate for a specific mandate is not always in the founder's own city, and a search confined to one metro area narrows the pool before it starts. Our international AI engineer search walkthrough covers the same regional logic in more detail for an adjacent technical role.
Qualification against the calibrated mandate produces the shortlist. That is the deliverable under Sourcing Sprint, and the client takes it and runs interviews internally from there.
Under Full Search, run on a launch fee plus a success fee on placement, the process continues past the shortlist into candidate assessment, interviews, offer and close. For a founding-engineer search, the offer stage is where the equity calibration from step one actually gets tested against a live candidate: does the number discussed in the abstract during calibration still hold once a specific person with specific alternatives is at the table. Close is where base salary, equity percentage, vesting structure and start date all get finalized together, not negotiated piecemeal.
Fees for this model vary based on role seniority, search complexity and hiring volume, and executive-level, highly specialized and unusually complex searches are quoted individually. Pricing is available on request.
The table below is the kind of scorecard we use inside calibration to pressure-test a founding-engineer mandate before sourcing starts. It is worth running through even if you are hiring the role yourself.
| Criterion | What "clear" looks like | Evidence to ask for |
|---|---|---|
| Technical scope | The founder can name the three hardest technical problems this person owns in the first six months | A written list, not a title |
| Equity band | A specific percentage or range is set, referenced against Carta's median (1.54%) and 25th-75th range (0.61%-3.5%), December 2025 | A cap table showing what has already been allocated |
| Base salary | A number is set with the BLS software developer median ($133,080, May 2024) as one reference point, adjusted for scope | A comparable offer the founder has already extended or received |
| Vesting and cliff | Standard vesting terms are decided before an offer goes out, not negotiated candidate by candidate | A term sheet or cap table policy |
| Interview capacity | Someone technical is available to run structured interviews within the search's timeline | A named interviewer and a blocked calendar |
| Regional openness | The founder has decided whether the search is local-only or spans the six regions we work | A yes/no on remote and time zone tolerance |
A founding-engineer search rarely happens in isolation. It is usually the first of several Product, Technology & AI hires a founder is trying to sequence, alongside a first AI engineer or a staff-level hire once the team grows past the founding stage. Our guide to how to hire engineers and AI talent covers how that sequencing tends to work across the broader function, and the Hiring Scorecard is the fastest way to see which engagement model fits a specific mandate, whether that is one founding-engineer hire or several technical roles opening at once.
A founding-engineer search runs on the same pattern as any other Product, Technology & AI search we run: calibration, then sourcing and qualification into a shortlist, then either the client running interviews (Sourcing Sprint) or us carrying assessment through offer and close (Full Search, on a launch fee plus a success fee). What makes this role specifically harder to calibrate is the equity conversation, and Carta's December 2025 data (median 1.54 percent, 25th-75th percentile 0.61 percent to 3.5 percent) alongside the BLS's $133,080 median software developer wage (May 2024) are the two public reference points worth having in hand before that conversation starts. We search across six regions for this role, because the person who fits a specific founding-engineer mandate is not guaranteed to be local.
Carta's research, published in December 2025 from real cap-table data, puts the median first-engineer equity grant at 1.54 percent, with a 25th-to-75th-percentile range of 0.61 percent to 3.5 percent. Where a specific offer lands inside that range depends on stage, funding raised and how much technical ownership the role carries, which is why we treat this as a calibration question rather than a fixed number.
The U.S. Bureau of Labor Statistics reported a median annual wage of $133,080 for software developers in May 2024, which is a public reference point for the base-salary half of the offer. A founding engineer typically carries more scope than a median developer role, so that figure is a starting point for calibration, not the final number.
If the mandate is clear and interview capacity exists internally, a Sourcing Sprint hands over a calibrated shortlist and the founder runs interviews. If the equity and scope conversation is still unsettled, or there is no internal bandwidth to run assessment through close, a Full Search, run on a launch fee plus a success fee, manages the process end to end.
No. We search for this role across six regions: Western Europe, North America, the Balkans, Eastern Europe, the Middle East and Latin America, because the strongest candidate for a specific mandate is not always in the founder's own city.
Calibration sets the scope, seniority and equity band before sourcing starts, which determines who gets approached and what offer they are told to expect. A search that skips this step tends to produce candidates who do not match the eventual offer, which slows the process down rather than speeding it up.
What sets a founding-engineer or AI-engineer search apart from a standard tech hire, what the market pays, and how the search should be structured. Every compensation figure below is a cited public benchmark, not Recruitmint's own number.