First Engineering Hires at a Seed Startup

Your first engineering hires at a seed startup set the architecture, habits, and hiring standards that later teams inherit. The best start is to hire a senior generalist when ownership becomes the bottleneck, then add roles as new needs come up. Getting the profile, sequence, and offer right helps those early decisions compound and saves years of work undoing them.

Why the first engineering hire is unlike any later one

Good decisions by your first engineer multiply through later hires, and poor decisions do the same. Every new engineer joins a system with defaults already set. Those defaults include code quality, review culture, on-call expectations, and the standard for hiring the next person. Founders can spend years unwinding both technical debt and the hiring standards that helped create it.

The job therefore sits closer to a technical co-founder’s work than a standard senior engineering role. This engineer owns the whole stack and makes calls on the architecture before they have all the facts. There may be no process to guide them. They must turn uncertainty into working software while establishing how other engineers will work. A candidate who performs well within an established team may still struggle when building that structure is part of the job.

When to make the hire

Hire when the problem is validated, you can define 90-day outcomes, and technical work is personally blocking you. A working prototype and a few design partners give the hire a useful starting point. The practical signal is a daily choice between shipping the next feature and taking sales calls. Both need you, and neither can keep waiting.

Hiring before that point spends equity before you can support the person well. If you wait too long, you still have to make every technical decision. AI coding tools have made small teams more productive, so code volume alone is a poor trigger. The need is for judgment and ownership. Once that need is clear, start the search early enough to allow time to find the right person.

The profile that works at this stage

Look for a senior generalist with roughly a decade of experience who has shipped production systems across the stack. They should have owned products that they saw through to completion. Prototypes alone do not establish that they can live with architectural decisions after customers start using them. Strong candidates have been technical leads and made decisions without a committee. They can explain what happened after those decisions, including the consequences.

Startup experience helps, but it need not be mandatory. A senior engineer from a large company can fit if they have led a team and shipped end-to-end. Contributing to a large codebase is a different experience.

Junior engineers and career switchers need more help than a seed team can usually give. Narrow frontend or infrastructure specialists leave too much of the stack outside their scope. A management-first hire creates a different mismatch. A Head of Engineering or CTO without engineers to lead can be expensive and demotivating. Build toward five to eight engineers before you think about hiring someone for that leadership role.

The same generalist principle applies when your product depends on LLM features. Look for a senior software engineer who has shipped those features in production. Research credentials alone do not establish that fit. Hire a researcher when training the model is the product, and a shipper when the model supports the product. The trigger is a production feature touched weekly, informal or missing evals, and substantial founder time spent on AI plumbing.

The sequence after the first hire

Keep the early sequence focused on people who execute, with each role tied to a need the business already has. Hire two is a senior backend or infrastructure engineer within the first quarter. They make the system reliable as usage grows and split the technical load. Hire three is another full-stack or frontend engineer when the roadmap outruns two people and pull requests depend on one reviewer.

Hire four is a product-minded designer when engineers ship faster than the product can be scoped. UX debates consuming standup time are another signal. Hire five is a founding account executive once you can describe the buyer, buying trigger, and typical objections from personal sales experience. It is too early to hire a VP Sales before you have that knowledge. Hire six is a customer success lead when customers start asking each other questions or support exceeds your nighttime capacity.

Hires seven through nine are specialists in ML/AI, forward-deployed engineering, data/platform, or security, ordered by the product’s dependence on each capability. Begin those searches early because the roles are scarce. Engineering management comes when founders can no longer manage directly, around the tenth engineer. An internal promotion may come before an external search. These are need-based triggers rather than a fixed headcount schedule across engineering and other roles.

A VP Sales hired before founder-led sales will expect a playbook that has yet to be built. That mismatch can consume runway before the person leaves. It is also too early to hire a demand gen lead before a customer has read about the product. Neither role substitutes for establishing what customers respond to.

What to pay at seed

Pay close to market on base salary and use equity to offer upside. A candidate’s outside option is a funded offer at market rate. Your SAFE cap does not change that comparison. If the cash budget cannot support the seniority you want, accept that the hire may need to be less senior.

For US major tech hubs in 2026, the median founding engineer cash salary is $195,000. Pre-seed offers span a wider band above and below that figure. Treat the median as context. Base salaries for a senior software engineer can differ a lot by market, and equity and bonuses can add a lot to total compensation. Cash bonuses are uncommon at seed, while health benefits, remote setup, and reasonable PTO are standard additions.

Seed senior engineer equity spans a wide band, which narrows by Series A as dilution and team size compress grants. The second hire may receive a meaningful fraction of a percent, rising above one percent for strong candidates. Later grants generally taper as the team grows. Standard vesting runs four years with a one-year cliff. These ranges reflect stage and responsibility rather than a starting point for negotiating downward.

London candidates also have a tax consideration when comparing equity with a large-company salary. As of April 2026, the UK’s EMI scheme can make qualifying gains eligible for reduced Capital Gains Tax through Business Asset Disposal Relief. A statutory lifetime limit applies to those gains. Those tax rules can make the offer more appealing even when headline valuations are lower. Each priced round also typically dilutes existing shareholders materially, so the size of an early grant deserves careful attention.

How to evaluate the candidate

Evaluate how candidates think about systems they have built, using a short process grounded in realistic work. Start with a brief founder screen covering motivation, culture, and their understanding of seed-stage work. Then discuss systems they have shipped and owned. This connects their experience to the ambiguity and responsibility your role involves. A single conversation or a long round of academic interviews gives too little to go on when judging how candidates think.

Use a practical coding session of up to an hour and a half in the candidate’s preferred stack. Pair on a realistic problem. If uncertainty remains, an optional paid trial can take four to eight hours. Plan around roughly six to eight hours of candidate commitment, with clear expectations about any trial. Treat that time as a commitment from the company too.

For an AI-focused hire, build the assessment around a shipped artifact. A take-home should ask the candidate to ship something small and real. The result should connect to the profile you need. A big-tech-style algorithmic loop selects for a different kind of performance and can work against this search. The assessment should establish whether the candidate can turn model capabilities into a working product.

What the first ninety days should look like

The first three months should move the engineer from understanding the product to owning a meaningful part of it. In week one, prioritize onboarding and shadowing you on customer calls before code changes. During weeks two through four, have them ship small features end-to-end to learn the codebase.

By month two, the engineer should own a meaningful surface area with real customer impact. Month three then broadens their contribution into hiring, on-call work, and written engineering standards. That progression also explains why contractors rarely fit this role. They generally do not build culture, participate in hiring, or stay through the difficult early quarters. A three-month paid contract-to-hire arrangement can work when interviews leave real uncertainty.

Treat the end of month two as a decision point about fit. Has the engineer taken ownership of meaningful work? If they have yet to take ownership, act early, before month six. The checkpoint is more than a scheduled performance conversation. Delaying the decision spends time the company cannot recover.

Where to find the first engineer

Start with your own network for the first one or two hires, then move to board and investor contacts. A warm introduction transfers credibility and shortens the trust-building needed for a seed-stage move. Investors often know candidates open to that stage. If a warm referral is already in play, pursue it directly. Candidates who have stayed in touch over several months may also be ready when a role opens.

YC’s Work at a Startup gives YC-backed companies access to engineers already interested in startups. Engineers can create profiles and apply to listings. Companies can also browse that pool and reach out directly. Job boards help more with roles where candidates are easier to find and with later hires where more applicants help. Many of the strongest engineers, however, are not actively browsing.

Use a specialist contingency recruiting firm when your network is exhausted or the profile is scarce. ML, forward-deployed, and security engineers can justify a structured search. The model charges only when you hire. It can bring a shortlist of three to five vetted candidates. Set your salary band and equity range first, or the search may stall at the offer.

A CTO or VP of Engineering search fits a retained executive firm. For other roles, AI sourcing agents can help a small team source, screen, and draft outreach. You look through the shortlist and approve messages. At seed, direct contact remains practical because the hiring manager is usually a founder or early employee.

What engineers evaluate before joining

Prepare for candidates to examine the offer as carefully as you examine their work. Strong senior engineers have other good options and fair questions about the risks of joining a startup. Clear equity answers are part of that preparation. Give the grant’s share count and vesting schedule, together with the fully diluted shares outstanding. A percentage based only on issued shares can overstate their stake.

Candidates also need the strike price and current 409A valuation to understand the equity’s tax basis. Share the last round’s preferred price per share and date so they can assess the potential upside. These are concrete questions with concrete answers. Being open about the cap table includes sharing the fully diluted count and 409A before signing. A vague percentage leaves too much of the offer unexplained.

Prepare a runway answer expressed as a date, with candidates looking for a year and a half to two years. They may also look at the liquidation preferences in every series. Non-participating preferences are a good sign when they do that. A priced, fully subscribed last round with a new lead investor is another. Explain the actual terms rather than replacing them with general confidence about the company.

The candidate’s assessment extends beyond the equity documents. They will evaluate your technical credibility and the product’s market reality. They will also compare the actual role with your pitch. Be ready to discuss the scope they will own, using the same 90-day outcomes that justified opening the role.