Fractional · 1 to 3 days a week

Fractional Frontend Lead

For product teams that have outgrown "good ICs, no lead" but aren't ready to hire a full-time head of frontend. I take the lead seat 1 to 3 days a week, own the architecture and hiring calls, and turn a group of engineers into a team.

When teams need a fractional lead

The pattern is almost always the same. Hiring outpaced leadership, the founding engineer doesn't want the lead role, and decisions stack up because nobody owns them. A fractional lead clears that queue without committing the company to a six-figure full-time hire.

  • Outgrew the "lead engineer" arrangement

    The senior IC who was running things wants to go back to building. Or never wanted the role in the first place. The team needs an actual lead, but not yet full-time.

  • The design system has no owner

    Components are getting copied across apps. Prop APIs are drifting. Nobody owns versioning, distribution, or governance. The system stops being a system.

  • Hiring is stuck

    No rubric, no interview loop you trust, no calibrated bar. Either offers go to the wrong people, or the right candidates ghost. A fractional lead fixes the loop before more headcount gets burned.

  • Engineering decisions are delayed

    State management, routing, the next framework upgrade, the monorepo. Decisions sit in Slack threads for weeks because nobody has the authority (or appetite) to call them. I make the call and write down why.

What I actually do as a fractional lead

Architecture decisions

State, routing, data layer, module boundaries, monorepo strategy. Written ADRs so the rationale survives me leaving the engagement.

Hiring

Calibrated rubric, take-home or live-coding loop, structured debriefs. I sit on the panel and help your team learn to read senior frontend candidates.

Design system governance

Component review process, token discipline, versioning policy, and the harder call: what does NOT go in the design system.

Mentoring

1:1s with mid-level engineers who want to grow into senior. Career direction, code feedback, and the soft skills that actually unlock the next level.

Code review SOPs

A written standard for what gets blocked, what gets nitpicked, and what gets shipped. Less bikeshedding, faster merges, fewer regressions.

Cross-functional alignment

Sitting in on product and design syncs so frontend gets represented before tickets get written, not after. Fewer surprises at sprint planning.

What this is NOT

Being upfront about scope saves everyone time. A fractional lead role is a specific shape. Here's what it isn't.

  • Not full-time leadership

    If you need a head of frontend in the room every day, hire one. A fractional engagement caps at 3 days a week and isn't a substitute for someone whose calendar belongs to you.

  • Not project management

    I don't run standups, write tickets, or maintain Jira boards. I'll unblock those processes if they're stuck, but day-to-day delivery management belongs with your PM or EM.

  • Not solo product development

    I don't ship the product alone. The point of the role is to make your team faster and better. If you need a single engineer to build a thing end to end, hire a contractor instead.

Selected proof points

  • Built a reusable UI npm package consumed across multiple Next.js apps, cutting new-project setup by 40% and giving the team a single source of truth for components.
  • Established frontend SOPs (code review, PR templates, architecture decision records) that survived team growth and at least one framework migration.
  • Mentored mid-level engineers into senior roles by pairing on real PRs and writing concrete, kept-receipts career plans.
  • Owned hiring rubrics and interview loops that calibrated a small team without lowering the bar to grow it.

Frequently asked

How many days a week is a fractional engagement?
Typical is 1 to 3 days, with weekly syncs and async-first communication. The exact shape gets agreed in the first week based on what the team actually needs from the role.
Will you still write code?
Some. Most fractional value comes from decisions, hiring, and unblocking. I'll write code on critical paths and on the parts of the codebase where the team is least confident.
How long is a typical fractional engagement?
Open-ended. Minimum 3 months to make architectural changes stick. Most engagements roll quarter to quarter and end when the team has internalized the standards.
What's different from hiring a CTO advisor?
CTO advisors talk about engineering at the org level. I work inside your frontend team, attend their syncs, review their PRs, and own outcomes the team can point at.

Interested in working together?

Open for senior frontend roles, contracting, and engineering consulting.