New! Listen to Concept to Cloud - Real stories from the trenches of software engineering
Tom Barber

Fractional Director of Engineering

The fractional CTO who sent you images from Mars.

Tom comes into engineering teams that need to turn things around, hold a ship date they are missing, or steady a platform that cannot afford another bad quarter. Fifteen years of running the room, from JPL to compliance-critical fintech.

15+
Years of leadership
50
Person teams delivered
NASA
3 NASA Honor Awards
8
Years at JPL
6+
Industries shipped in

Profile

A career spent walking into engineering rooms that needed someone in them.

Tom Barber spent eight years inside NASA’s Jet Propulsion Laboratory, holding engineering roles across the Voyager Interstellar Mission and the Mars 2020 Perseverance rover. Three NASA Honor Awards, including the Mars 2020 PIXL Development Team. The images the rover sent back to Earth came through infrastructure his teams built and ran.

He left JPL to do the same work in more places. Director of Engineering at a global risk advisory firm, leading a fifty-person team building a financial-crime detection platform under heavy regulation. Director of the Princeton Research Accelerator, ramped up from a fractional engagement into a twenty-person research-data operation. Fractional Director at Consilient, doing federated learning where the data can never be pooled. Former VP of Apache OODT, the open-source data management framework that came out of JPL and has been running in production for two decades.

Almost all of it on a contract or fractional basis. That is not a side effect of the market. It is the shape of the work he has deliberately chosen.

“Most engineering teams don’t need a full-time Director. They need someone who’s done the job before to help figure out what good looks like, and how to get there.”

His current argument for why now: AI is exposing a gap. Not in engineering itself, which the tools have accelerated, but in the leadership around it. The teams that will pull ahead over the next few years, he says, are the ones where someone senior is still holding the shape of the work, deciding what gets built and what does not, and keeping the loop honest. Tom has written about it.

What that looks like in practice is a Director who lands in the room, reads it fast, holds the seat while the team stabilises, and hands off cleanly when someone else is ready to take the chair. Fractional as method, not as pitch.

“If we’re a fit, we’ll know quickly. If we’re not, I’ll tell you who is.”

Who it’s for

Teams that need a Director in the room.

  • Funded startups

    Outgrown the founding engineer, not ready for a full-time hire. Need someone to set direction, build a team, and ship.

  • Mid-market companies

    Team scaling, tech lead just left, or new practices to adopt. Need experienced leadership to steady delivery and level up the org.

  • Enterprise initiatives

    A specific programme, platform migration, new product line, or a regulated-environment build with a hard deadline.

What you get

The full Director remit, flexed to fit.

  • Team building and hiring

    Roles, specs, interviews, onboarding, and the engineering culture that ships consistently.

  • Technical strategy

    Direction, build-vs-buy calls, engineering standards, and stack aligned with your business plan rather than the other way round.

  • Process and delivery

    CI/CD, sprint cadence, incident response, the operational rhythm that turns a team into an organisation.

  • Mentoring and growth

    1:1s, growth frameworks, code review culture, and coaching the engineers who will outlast the engagement.

How we engage

Three shapes. The one that fits the moment.

The right seat depends on what your team needs and how long they will need it. All three start with a fifteen-minute conversation to figure that out.

01 · Contract / Interim

A senior seat, held for a season.

Short-term, defined-scope engagements. Filling a gap after a founder or CTO transition, leading a specific programme with a clear end date, or steadying a team through a critical delivery window. Weeks to a few months.

02 · Fractional

An embedded part-time Director.

Ongoing part-time seat, held for months or quarters, embedded in your weekly cadence. The most common shape. Held long enough to run the practice, hand off cleanly, or bridge into a permanent hire.

03 · RetainerBest offer

Standing access, after a full engagement.

A lighter, standing relationship for teams Tom already knows deeply. Available after twelve months of prior fractional or contract engagement, so he can keep the standard high and give you his best work when it matters. Board prep, hard-call sounding-board, and the check-ins that keep the practice honest after the seat has stood down.

Fractional CTO vs a dev shop

They solve different problems, and founders often shop for one when they need the other.

A dev shop

Builds what you spec

You hand over a spec and they ship against it. The right call when you already know what to build and just need the hands to build it. What you do not get: someone owning the technical strategy, the hiring, or the trade-offs when the spec meets reality.

A fractional CTO

Decides what to build, and how to run engineering

Sets technical direction, makes the build-versus-buy and architecture calls, hires and shapes the team, and answers to the board. The right call when the question is “what should we build, and how should we run engineering,” not just “can you build this.”

Plenty of teams need both, in sequence: the CTO to make the calls, then a build team to execute them. If you are not sure which you need, that is the first thing we will work out on a call. (Comparing against an advisory relationship instead? See fractional CTO vs CTO advisory.)

Questions you’ll probably ask first

Honest answers to the things that come up before a fit call.

Fractional CTO vs fractional Director of Engineering, which do I need?

A fractional CTO is usually right when you have no senior technical voice on the team and need a strategic head, board-facing, tech-vs-business trade-offs, founder-counsel. A fractional Director of Engineering is right when you already have a CTO or technical founder and need someone who can actually build the team, run delivery, and operate the engineering org. CTO sets direction; DoE runs the shop. Many startups think they want a CTO and actually need a DoE.

How is fractional Director of Engineering priced?

Monthly retainer, paid in advance, use it or lose it. $12,000 to $25,000 per month depending on engagement size and days held; we'll scope the exact number on the first call.

What's the minimum engagement length?

Three months as standard. Shorter engagements can be arranged if they fit, usually for a specific initiative with a clear end date.

Will you work alongside our existing engineering team?

Yes, or help you build one. Working alongside an existing team or tech lead is the most common shape; building a team from scratch is the second.

Will this convert to a full-time role?

No, fractional is the offering. If you decide you need a full-time Director of Engineering, I'll help you find one and hand the role over cleanly.

Remote, hybrid, or on-site?

Remote with some time on-site, scheduled around your team. We're based in Washington DC; the rhythm depends on the engagement, we'll agree what works on the first call.

How is this different from a contract engineer or interim CTO?

Contract is fine, interim is fine, and when the engagement ends I'll hand everything over to whoever steps into the role. The difference is the shape of the work: a Director sets technical direction, builds the team, and runs delivery; a contract engineer ships against a spec; an interim CTO holds the seat. Sometimes you need one, sometimes the other, we'll figure that out together.

Every engagement starts with a conversation.

No pitch deck, no sales funnel, just a conversation about what your team needs and whether I can help.

Talk to our team

15 minutes · Zero obligation · Real engineering talk