Hiring a founding engineer in London requires a clear building mandate, a locally relevant package and a realistic route from first conversation to start date. The role should be understandable without relying on the title to explain its responsibilities.

Start with what the company needs to achieve, then work through the engineering decisions, working arrangements and offer terms that support it. This guide sets out Corellia’s recommended approach.

In this guide

Define the first six months of work

A founding engineer needs to know which product outcomes they will own and what state the product is in today.

Describe the users, the part of the product that must work next and the constraints around it. Distinguish between building a first version, improving an existing system and supporting customers who are already paying. Those jobs may need different strengths even if the technology list looks similar.

Write a short brief covering the following:

  • The delivery outcome that makes this hire necessary.
  • The architecture and product decisions they can make.
  • The technical debt or uncertainty they will inherit.
  • The help available from founders, advisers and colleagues.
  • The responsibilities that may change as the next people join.

Use the founding engineer brief to agree those points before outreach. If the founders disagree about the mandate, interviews will not resolve that disagreement for them.

An early engineer should not have to guess whether the real job is coding, customer implementation or becoming the company’s technical leader. Make the balance explicit.

Separate a builder from a future manager

Hands-on delivery and people management should be assessed separately, even if one person may eventually do both.

Specify whether this hire will be the only engineer, join an existing technical founder or take over work built by a contractor. Explain who will review decisions, especially when the engineer is the first full-time technical employee.

If you expect them to hire a team, agree which responsibilities they will retain afterwards. Avoid offering a future leadership title without deciding whether you actually want a manager or a senior individual contributor.

For a non-technical founder, bring a qualified technical assessor into the process. Their job is to examine the skills required by the business, including judgement and communication. It is not to make candidates pass an unrelated test of their own favourite tools.

The technical leadership mandate guide helps separate authority, delivery and people responsibilities before settling on a title.

Source for the work rather than a narrow pedigree

A useful London candidate list starts with evidence of relevant work, then expands beyond familiar company names.

For a customer-facing product, look for engineers who can explain how they turned user feedback into a working feature. For infrastructure, look for ownership of reliability and difficult operational trade-offs. For applied AI, distinguish a demonstration from a system that someone has had to evaluate and maintain.

Search channels can include former colleagues, introductions through advisers and investors, relevant open-source work, technical communities and targeted direct approaches. University networks may help where the work calls for particular research skills, but a degree or institution should not stand in for the assessment.

Do not assume public GitHub activity is a complete account of an engineer’s ability. Give candidates a way to discuss work they can share without disclosing confidential code. Ask the same questions about ownership and outcomes regardless of where the evidence comes from.

Write outreach around one relevant connection between their work and yours. Explain the problem and working arrangement before asking for a substantial time commitment.

State the real London working arrangement

Office attendance and travel need to be explicit because London roles do not all offer the same working week.

Two employer adverts checked on 31 October 2026 illustrate the difference: one requires five days a week in a central London office; another describes a hybrid role with one day a week at a London co-working space. [Sources 1 and 2]

State where the team meets, which days are required and what the in-person work is intended to achieve. Include regular overlap with overseas colleagues. A candidate should not discover late in the process that a nominally London role involves routine late calls or travel.

If you are open to relocation, decide what support you can offer and when it would be needed. Keep working-pattern questions separate from assumptions about a person’s family, nationality or other personal circumstances.

Build a UK package rather than convert a US one

A London package should be assessed in pounds against relevant London roles, with salary, bonus, pension, benefits and equity explained separately.

Do not convert a US salary band using an exchange rate and call the result a London benchmark. A comparison needs matching role scope and a clear view of the package components. The three-city compensation guide explains the questions to ask before treating different packages as equivalent.

Start with the salary guide, checking whether your selection shows real advert evidence or a modelled estimate. Neither an advertised range nor a modelled result is an accepted offer. Sparse evidence should remain visible rather than being hidden behind a precise-looking number.

Current adverts also demonstrate why a title alone is insufficient. Two founding engineer adverts checked on 31 October 2026 listed £60,000 to £120,000 and £40,000 to £80,000 respectively. [Sources 1 and 2]

Explain what determines the eventual offer within your own approved band. If the candidate’s expected scope is materially greater, resolve the scope before trying to negotiate around it.

Explain EMI options without promising a tax outcome

EMI is a UK employee share-option arrangement with eligibility conditions, not a general label for any startup equity grant.

GOV.UK sets out qualifying conditions and explains that the tax treatment depends on the terms and circumstances. Do not describe every proposed grant as EMI before eligibility and the scheme have been checked. Rules change, so use current official guidance and qualified advice rather than a remembered threshold. [Source 3]

Give candidates a written explanation of the instrument, number of options, percentage basis, exercise price, vesting, leaving provisions and approvals. Explain when the percentage was calculated and what is not yet final.

Keep hypothetical outcomes separate from cash compensation. A future company valuation does not by itself establish what an employee could receive.

If your team cannot explain a term, involve the person administering the scheme. A clear follow-up is more useful than an improvised answer during an offer call.

Assess relevant decisions and agree a realistic start

The assessment should reveal how the engineer works, while the hiring plan should account for the steps required before they can join.

Ask for a walkthrough of something delivered, including what they personally owned, a difficult trade-off and what changed after use. Follow with a bounded exercise related to your actual problem. Agree the evaluation criteria, permitted tools and time commitment in advance.

Before making the offer, confirm notice obligations and a feasible start date. Do not assume that every London engineer has the same notice period. GOV.UK explains the statutory minimum and the importance of the employment contract; an individual’s contractual obligations may be longer. If a candidate has a one- or three-month notice period, plan around their confirmed terms rather than assuming early release. [Source 4]

Employers must check a person’s right to work in the UK before employing them, using the applicable process. Where sponsorship or restrictions may be relevant, obtain specialist advice early and apply checks consistently. [Source 5]

Assign one owner for the offer, outstanding checks and communication through to joining. Maintain contact without creating an unofficial expectation that the candidate starts working before their agreed start date.

Questions founders ask

Is a founding engineer the same as a technical co-founder?

No. Agree employment, ownership and authority explicitly. A senior employee should not be expected to infer founder-level responsibilities from a job title.

Is EMI available to every London startup?

No. Company, employee and grant conditions apply. Check the current GOV.UK guidance before describing an offer as qualifying. [Source 3]

Should we require previous startup experience?

Only when you can explain the relevance. Assess delivered work, judgement and appetite for the actual environment, rather than using a previous title as a proxy.

How much notice will an engineer need to give?

Check their actual contract and circumstances. Do not build a hiring plan around an assumed market-wide notice period. [Source 4]

Can we hire someone who needs sponsorship?

That depends on the role, person and your ability to meet the relevant requirements. Obtain immigration advice before promising support or a start date.

Can Corellia help clarify the brief?

Yes. Founding engineer recruitment can begin with outcomes, technical expectations and package trade-offs before a search starts.

Examples are individual adverts, not benchmarks. Legal and tax points are summaries; take professional advice.

Sources

Sources checked 31 October 2026.

  1. London founding engineer advert, office-based: advertised salary and office arrangement. Checked 31 October 2026.
  2. London founding engineer advert, hybrid: advertised salary and hybrid arrangement. Checked 31 October 2026.
  3. GOV.UK, Enterprise Management Incentives: eligibility and tax overview.
  4. GOV.UK, giving notice: notice and contract obligations.
  5. GOV.UK, checking a job applicant’s right to work: employer checks and official routes to further guidance.

If you are planning a London founding engineer hire, Start a conversation.