Inside Interim Head of Engineering, the Complete Guide for Operators

An interim head of engineering is a full-time, temporary engineering leader who runs your team for a defined window, usually three to six months, while you stabilise a crisis, cover a sudden departure, or search for a permanent hire. The role sits inside your org chart, owns delivery and the technical budget, and reports to the founder or the board. This guide is the studio's house position on the interim head of engineering: what the role does, what it costs, when it beats a fractional or permanent hire, and which deeper article to read next based on where you stand today. You are an operator weighing a real decision, not a reader collecting definitions, so every section closes with a rule you can act on.

Key takeaways:

• An interim head of engineering is a full-time temporary executive engaged for three to six months, while a fractional CTO works one to two days a week on an ongoing basis, according to AmazingCTO's 2025 comparison.
• The global fractional and interim executive market reached $9.4 billion in 2025 and is forecast to hit $24.7 billion by 2034, a compound annual growth rate of 11.3% (Dataintelo, 2025).
• UK interim engineering leaders bill £1,200 to £2,000 a day, or £60,000 to £90,000 across a six-month engagement (Boardman, 2025); continental European interim day rates run €1,000 to €2,500 (Robert Walters, 2026).
• La Boétie's house position: hire interim for continuity and a named handover date, hire fractional for a single outcome, and never sign either without a written exit plan.
• If you have not yet decided whether to hire at all, start with our interim versus permanent decision framework.

What an interim head of engineering actually does

The interim head of engineering owns four things at once: the delivery roadmap, the engineering team, the technical budget, and the reporting line to the founder or board. Unlike a consultant who advises from the outside, this leader is slotted into the organisation chart and carries the same authority a permanent head would, only for a fixed term. The distinction is load-bearing, because authority without a seat produces recommendations that nobody implements.

Will Larson, author of StaffEng and a chief technology officer who has led engineering at companies including Calm and Carta, describes one archetype of senior technical leadership as the Right Hand, a role that "extends an executive's attention, borrowing their scope and authority to operate particularly complex organisations." An interim head of engineering is the externalised version of that pattern: borrowed authority, full operational scope, and a deadline that forces decisions instead of deferring them.

Engineering velocity here means the rate at which committed work reaches production, not lines of code written. The work splits into three phases. Diagnosis runs the opening two to four weeks, where the leader maps delivery, team health, and technical debt before touching anything. Stabilisation follows: the leader unblocks the critical path, resets the roadmap to dates the team can actually hit, and rebuilds trust with the board. Handover is planned from day one rather than improvised at the end, so the organisation keeps every system, runbook, and decision the interim leader produced. In his widely cited essay on the first ninety days of an engineering leadership role, Larson argues that you must learn how decisions are actually made before you change any system, because skipping that step buys short-term wins and long-term distrust.

A disciplined interim audits the same ground in the first thirty days. The order matters more than the speed:

1. Delivery state. Map every in-flight project against its committed date and flag the work already late.
2. Team health. Identify single points of failure, attrition risk, and who actually ships.
3. On-call and reliability. Read the incident log and measure how much engineering time goes to firefighting versus building.
4. Architecture and lock-in. Document where the stack depends on a single vendor the company cannot leave.
5. Security posture. Check authentication, exposed secrets, and unprotected routes, the failure modes a rushed do-it-yourself build leaves behind.
6. Budget and burn. Reconcile the engineering spend against headcount and tooling contracts.
7. Roadmap honesty. Rebuild the plan around dates the team can defend in a board meeting.
8. Handover artefacts. Start the documentation that lets a permanent successor take over without an archaeology project.

The rule: an interim engagement that does not begin with a written thirty-day diagnosis is a contractor with a grand title, not a leader. For the day-by-day version of this sequence, our interim walkthrough traces a real engagement week by week.

The studio's house position on interim leadership

La Boétie carries a sovereignty thesis borrowed from Étienne de La Boétie's 1548 argument against voluntary servitude: technology must belong to the client, and no engagement should leave a founder more dependent than it found them. That thesis sharpens our view of the interim head of engineering, and it puts us at odds with most of the field on three points.

First, the field sells the interim as a stopgap, a warm body to hold the chair until the real hire arrives. We reject that framing. An interim engagement is the cheapest, most honest due diligence you will ever run on your own engineering organisation, because an outsider with authority and a deadline surfaces the truths your incumbents have learned to stop mentioning. Treating it as a placeholder wastes the single most valuable thing it produces, which is an unsentimental map of where you actually stand.

Second, the field optimises for speed of placement. We optimise for the exit. Every La Boétie interim engagement begins with a written handover plan and a named end condition, because an interim leader who becomes indispensable has failed at the one job that distinguishes the role from a permanent hire. The competitive landscape proves the gap: across the top five pages ranking for this topic, none publishes a dated benchmark, a named engagement, or a decision rule an operator could defend to a board. The category is full of surveys and short on positions, which is precisely the opening this hub is built to take.

Third, and this matters most to a founder leaving the US hyperscalers for a European stack, we refuse to build inside vendor-locked toolchains. An interim leader who wires your team to a proprietary platform they happen to know, then leaves, has sold you a new dependency dressed as a solution. Our interim leaders work in your repositories, with your accounts, on infrastructure you control, so the capability stays in the building after the engagement ends.

Those three positions compound into a practical test we apply before any interim head of engineering engagement begins. We ask the founder to name the single decision they most fear getting wrong, then we scope the engagement so that decision is made with evidence rather than urgency. A departed lead, a frozen launch, or a security exposure feels like a staffing emergency, but underneath it is almost always a decision the founder has been postponing: whether to rebuild, whether to recruit, or whether the current architecture can carry the next year of growth. The interim engagement earns its fee by converting that fear into a documented, defensible call, not by simply keeping the lights on until someone else arrives.

The rule: judge any interim head of engineering candidate on the strength of their exit plan, not their start date. If they cannot describe in concrete terms how they will make themselves unnecessary, they are optimising for the wrong outcome and you should keep looking.

How the interim head of engineering hub is organised

This pillar is the map; the hub underneath it is the territory. Every entry answers a single question an operator asks while deciding whether, when, and how to bring in temporary engineering leadership. We organise the hub in two tiers so you can go straight to the depth you need without reading everything in order.

The topical tier covers the operator-level decisions you make before you sign anything. The interim walkthrough traces a full engagement week by week, from diagnosis to handover. The interim engagement benchmarks publish the dated numbers: day rates, engagement length, and outcomes by company stage. The European interim field report reads the specifics of hiring temporary engineering leaders inside the EU, including the sovereignty and data-residency angle. The interim versus permanent decision framework is the decision tree for whether to hire interim at all. The board-level due diligence entry lists exactly what an investor checks before signing off on the spend.

The focal tier answers one sharp question each, for the operator who has already committed and wants the detail:

1. Comparison. The interim head versus contract leader piece scores the two engagement types on cost, scope, and risk.
2. Evidence. The scaleup interim case study is a full engagement teardown with numbers attached.
3. Failure analysis. The interim transition postmortem documents what went wrong on a handover and what we changed afterwards.
4. Anti-patterns. The interim anti-patterns catalog lists the mistakes that turn a fixed-term hire into a permanent dependency.
5. Money. The interim engagement cost breakdown itemises every line, from day rate to recruitment offset.

The rule: if you are early, read across the topical tier first; if you have already decided and want ammunition for a board, the focal tier is where the named numbers live. The rest of this pillar gives the house position on each fork so you arrive at those articles already knowing what we recommend.

Interim, fractional, or permanent: the hire that comes first

Most founders ask which leader to hire before they have settled the prior question, which is whether interim is the right shape at all. Three shapes compete for the same problem, and they are not interchangeable. The interim head of engineering is full-time and temporary. The fractional CTO is part-time and ongoing. The permanent head is full-time and indefinite. AmazingCTO's 2025 breakdown frames the choice cleanly: continuity points to interim, a specific recurring problem points to fractional, and a stable long-horizon mandate points to permanent.

The pattern in the table is the decision. If your engineering organisation is on fire or leaderless and delivery has stalled, you need a seat filled now, and that is an interim head of engineering. If your build is broadly healthy but you keep hitting the same architectural or hiring wall, a fractional CTO solving that specific problem is cheaper and lighter. If you have a stable mandate and the runway to recruit slowly, hire permanent and use an interim only to hold the line during the search.

The rule: match the shape to the problem's duration, not to your anxiety. A crisis is not a reason to rush a permanent hire you will regret; it is the textbook case for an interim. Our interim head versus contract leader, side by side scores the nearest-neighbour comparison in full.

What an interim engagement costs and how long it runs

The price of an interim head of engineering is one of the few areas where the field publishes usable numbers, and the spread is wide enough that an operator needs the ranges before negotiating. In the United Kingdom, interim engineering leaders bill day rates of £1,200 to £2,000, which works out to roughly £10,000 to £15,000 a month full-time and £60,000 to £90,000 across a typical six-month engagement, according to Boardman's 2025 analysis. Across continental Europe, Robert Walters' 2026 European interim management report puts day rates between €1,000 and €2,500, with a rule of thumb that an interim charges about 1% of the equivalent annual salary per day.

Duration tracks the problem. Interim engagements cluster in the three-to-six-month band because that is how long stabilisation and a clean handover take. Fractional engagements run longer, typically twelve to eighteen months, because part-time change accumulates slowly. Reading those two facts together gives the cost-control lever: a focused interim at full intensity often resolves in six months what a fractional arrangement stretches across a year and a half, and the total spend can land lower despite the higher day rate.

Three cost drivers move the number. Scale is the first, since a fifteen-engineer organisation costs more to lead than a team of four. Crisis depth is the second, because a leaderless team mid-incident needs more intensive coverage than a healthy team awaiting a planned successor. Specialisation is the third, as regulated domains such as finance or health carry a premium. The market context explains why these rates hold firm: the number of fractional and interim professionals doubled from 60,000 in 2022 to 120,000 in 2024, per the Frak Conference State of Fractional Industry report, yet demand for fractional CMOs, CFOs and CTOs still grew 68% across 2023 to 2024, keeping rates buoyant rather than eroding them.

The rule: budget the engagement against the problem's duration and the cost of the status quo, not against the day rate in isolation. A £90,000 interim that unsticks a stalled roadmap is cheaper than two more quarters of missed releases. Our interim engagement benchmarks hold the full dated table by company stage.

Three engagements where the interim playbook was load-bearing

The house position is only worth as much as the engagements behind it. The three cases below are anonymised from La Boétie's own work, with identifying detail removed and figures rounded, but the shape and the outcomes are real. Each one had a hard external trigger, which is the single best predictor of whether an interim engagement pays for itself.

A fintech savings platform, roughly twelve engineers, Paris, four-month engagement. The founding technical lead had left abruptly and two regulated product launches were frozen. The interim head of engineering spent the first three weeks on diagnosis, found that the release pipeline depended on one departed engineer's undocumented scripts, and rebuilt the deployment path on infrastructure the company fully controlled. Result: both launches shipped inside the engagement window, and a permanent head joined in month four against a clean, documented codebase.

A regulated insurance comparison product, six engineers, remote across two European timezones, five-month engagement. Growth had outrun the architecture and the team was spending more than 50% of its time on incidents rather than features. The interim leader reset the roadmap, instituted an on-call rotation with a defined incident process, and cut firefighting time substantially over the engagement. Result: feature throughput recovered, and the handover pack let the incoming lead skip the usual three-month archaeology phase.

An eco-transition marketplace, four engineers, founder-led, three-month engagement. The founder had built an impressive do-it-yourself prototype with AI coding tools, but it shipped with exposed environment variables, unprotected routes, and no authentication layer. The interim head of engineering triaged the security gaps in week one, re-platformed the fragile build into an architected system the founder kept ownership of, and trained the founder to evaluate the next two engineering hires. Result: a security posture fit for real users, and a founder who understood what to hire for next.

The rule: the interim engagements that pay for themselves are the ones with a hard external trigger, a departure, a launch, or a security exposure, where a seat must be filled by someone with both authority and a deadline. The full teardown of the second case lives in our scaleup interim case study, and the handover lessons from the first sit in our interim transition postmortem.

Which entry to read first, by your starting condition

This pillar is deliberately broad, so the fastest path through it depends on where you stand today. Match your starting condition to the question you need answered next.

• You lost your engineering leader this quarter and delivery has stalled. Read the interim walkthrough for the week-by-week sequence, then move to the engagement benchmarks for budget.
• You are not sure interim is even the right shape. Start with the interim versus permanent decision framework, which resolves the prior question before you spend on the wrong model.
• Your investors want sign-off before you hire. The board-level due diligence on an interim hire lists what a buyer actually checks, line by line.
• You are weighing an interim against a contract engineering leader. The interim head versus contract leader comparison scores both on cost and risk.
• You are building inside the EU and care about data residency. The European interim field report covers the sovereignty angle in detail.

The rule: read in the order your decision forces, not front to back. An operator three weeks into a crisis needs the walkthrough and the benchmarks; an operator still debating the model needs the decision framework first. The pillar exists to route you quickly, not to detain you.

What is changing for interim engineering leadership this year

The interim head of engineering is riding a structural shift, not a fad, and three forces are reshaping the role. The first is raw market growth. The fractional and interim executive market reached $9.4 billion in 2025 and is forecast to reach $24.7 billion by 2034 at an 11.3% compound annual growth rate, per Dataintelo's market research, with North America already at $4.1 billion and a 43.7% share. Gartner's Future of Work forecast expects more than 30% of midsize enterprises to keep at least one fractional or interim executive on retainer by 2027, which moves the role from improvised stopgap to standing line item.

The second force is the AI-era reset of what engineering leadership has to fix. Founders are arriving after a failed do-it-yourself attempt with AI coding tools, holding prototypes that demo well and break under real load. The interim head of engineering increasingly inherits this exact situation: an impressive surface over an insecure foundation, where the first job is not new features but hardening what already exists. The 47% year-over-year rise in fractional CTO opportunities reported by Fractional CTO Experts is partly this story, demand created by the gap between what AI tools ship and what production actually demands.

The third force, and the one most relevant to a sovereignty-minded founder, is the European stack migration. Operators leaving the US hyperscalers want temporary leaders who can run an EU-resident, vendor-neutral architecture rather than re-create the lock-in they are escaping. That requirement is changing who qualifies for the role: fluency in a sovereign stack is becoming a screening criterion rather than a nice-to-have. Our European interim field report tracks how this is playing out across the continent, market by market.

A fourth shift sits underneath those three: the buyer is changing. Five years ago the interim head of engineering was hired reactively, after a resignation letter landed. Today, with 72.8% of fractional and interim professionals holding fifteen or more years of experience according to the Frak Conference research, and with 74% of engagements sourced through relationships rather than job boards, the engagement is increasingly planned in advance and triggered by a board conversation rather than a crisis. That maturation favours studios that can show dated benchmarks and named outcomes over individuals trading on a single anecdote, which is the structural reason this hub commits to numbers the field tends to withhold.

The rule: the role is professionalising and the rates are holding, so the scarce input is not budget but a leader whose instincts match a sovereign, post-hyperscaler stack. Hire for that fit, not for a brand-name CV.

Where this hub sits in the fractional CTO family

Interim head of engineering is one hub inside the broader family of fractional CTO and technical leadership, and the family charter answers a single question: when and how should founders bring in technical leadership that is not a permanent CTO. The sibling hubs in the family address the adjacent decisions. One covers the fractional CTO engagement itself, the part-time ongoing model that competes with the interim for the same budget. Another covers technical advisory and the lighter-touch guidance a founder takes before committing to any seat. A third covers the due-diligence and audit work a portfolio investor commissions before backing a company, the engagement that often precedes an interim placement.

The hubs interlock because the decisions do. A board-level due diligence engagement frequently surfaces the need for an interim head of engineering; the interim engagement frequently ends with a clean handover to a permanent CTO; and the fractional model is the lighter alternative an operator chooses when the problem is recurring rather than acute. Reading them as a set, rather than in isolation, is how an operator avoids buying the wrong shape of help and paying twice. The natural bridge between this hub and the permanent-CTO end of the family is the decision framework, which forces the duration question before any contract is drafted.

The rule: pick the hub that matches your problem's duration and acuity, then drill into its entries. The family is designed so that no single hub oversells its own model at the expense of the right answer.

FAQ: interim head of engineering

What is an interim head of engineering?

An interim head of engineering is a full-time, temporary engineering executive who runs your team for a defined period, usually three to six months, while you stabilise a crisis, cover a departure, or recruit a permanent leader. They sit in your org chart, own delivery and the technical budget, and report to the founder or board. The defining feature is a planned exit: the role exists to make itself unnecessary by a named date.

How long does an interim engagement last?

Interim engineering engagements typically run three to six months, long enough to diagnose, stabilise, and hand over cleanly. That contrasts with fractional CTO arrangements, which run twelve to eighteen months because part-time change accumulates slowly, according to AmazingCTO's 2025 comparison. If a proposed interim engagement has no end condition written into it, that is a warning sign the role has been mis-scoped as a permanent hire.

How much does an interim engineering leader cost?

In the United Kingdom, interim engineering leaders bill £1,200 to £2,000 a day, roughly £60,000 to £90,000 across a six-month engagement, per Boardman's 2025 figures. Continental European day rates run €1,000 to €2,500, following Robert Walters' 2026 rule of thumb of about 1% of the equivalent annual salary per day. Scale, crisis depth, and domain regulation are the three drivers that move the number most.

Interim head of engineering or fractional CTO: which should I hire?

Hire an interim head of engineering when you need continuity in a filled seat: a crisis, a sudden gap, or stabilisation before a permanent hire. Hire a fractional CTO when you need a specific recurring problem solved without a full-time seat. The deciding question is whether your problem is continuity, which favours interim, or a defined outcome, which favours fractional. Our decision framework entry resolves the edge cases between them.

Can an interim head of engineering hire my permanent team?

Yes, and a strong one should. Recruiting and onboarding the permanent successor, or the engineers that successor will lead, is one of the highest-value tasks an interim performs, because they evaluate candidates with first-hand knowledge of the team's real gaps. The handover plan should explicitly include who was hired and why, so the incoming permanent leader inherits a documented rationale rather than a roster of strangers.

What happens when the interim engagement ends?

A well-run engagement ends with a documented handover: an up-to-date roadmap, runbooks, architecture notes, and a rationale for every significant decision, all owned by the company rather than the departing leader. The exit condition is agreed at the start. If the organisation cannot operate without the interim leader at the end, the engagement failed at its defining task, regardless of how much shipped along the way.

How La Boétie runs an interim head of engineering engagement

La Boétie is a venture studio, digital agency, and technical consultancy that operates as a single flexible team of senior engineers across multiple timezones. When you bring us in as your interim head of engineering, you get an opinionated partnership rather than a seat-warmer, and the engagement is built around three commitments.

Diagnosis and stabilisation. We open every engagement with a written thirty-day diagnosis across delivery, team health, security, and vendor lock-in, then unblock the critical path. Our team has run this triage across builds in finance, insurance, legal, psychology, and eco-transition, so we recognise the failure patterns fast, including the insecure do-it-yourself AI prototypes founders increasingly arrive with.

Delivery leadership. We hold the seat at full intensity, reset the roadmap to dates the team can defend, and report to your board in language an investor trusts. Because the team is multilingual and works across multiple timezones, coverage does not lapse when a single engineer is offline.

Handover and sovereignty. We build the handover from day one and we refuse vendor lock-in, working in your repositories and on infrastructure you own. You keep everything we build, which is the throughline of every La Boétie engagement and the practical form of our sovereignty thesis.

If you are weighing an interim head of engineering and want a clear-eyed read on whether it is the right move, the next step is a studio introduction call. Bring your situation, and we will tell you honestly whether you need an interim, a fractional, or simply a different next hire. We would rather route you to the correct decision than sell you the wrong engagement.

Conclusion

The decision in front of you is not really about a job title; it is about matching the shape of help to the shape of your problem. A crisis, a departure, or a launch that cannot slip calls for a full-time seat filled fast and vacated cleanly, and that is exactly what an interim head of engineering is for. A recurring strategic problem calls for a fractional CTO, and a stable long mandate calls for a permanent hire. Get that match right and the cost takes care of itself; get it wrong and no day rate is cheap. The studio's house position holds across every fork in this hub: hire for the exit, refuse the lock-in, and keep ownership of what gets built. Use this pillar to find the entry that fits your starting condition, and when you are ready to decide whether an interim head of engineering is your move, talk to a team that will tell you the truth about it.

Sources

Further reading:

• Interim walkthrough, the operator walkthrough
• Interim engagement benchmarks, the numbers that matter
• European interim field report
• Interim versus permanent decision framework
• Board-level due diligence on an interim hire
• Interim head versus contract leader, side by side
• Scaleup interim case study
• Interim transition postmortem

External sources:

• Fractional Executive Market Research Report : Dataintelo, 2025
• 10 Statistics That Prove Fractional Work Is the Future : Fractionus, 2025
• Staff Archetypes : StaffEng, Will Larson, 2021
• Your First 90 Days as CTO or VP Engineering : Irrational Exuberance, Will Larson, 2020
• Interim vs Fractional vs Outsourced CTO : AmazingCTO, 2025
• Interim CTO vs Fractional CTO UK : Boardman, 2025
• European Interim Management Trends and Rates : Robert Walters, 2026
• Fractional CTO Jobs and Opportunities Market Guide : Fractional CTO Experts, 2025
• What a Fractional CTO Costs in 2026 : A.Team, 2026