How I scope a fractional lead engagement (and what I turn down)
Half-day to two days per week for architecture, hiring bar, and production judgment — not a full-time manager or feature factory.
Fractional lead roles go wrong when the buyer wants a cheap VP or unlimited on-call. I work as a fractional lead engineer for India tech teams that need senior judgment without a full-time hire.
What I say yes to
Architecture and review
- System design docs with explicit trade-offs
- PR / release review on critical paths
- Production incident support when I already know the system
Hiring bar
- Interview rubrics tied to real job tasks
- Calibration sessions with your existing leads
- “Should we hire this person?” decisions with written rationale
Unblocking
- One or two sticky technical decisions per week
- Pairing with your staff engineer on the hardest slice
Typical cadence: half a day to two days per week, three-month minimum so the work compounds.
What I turn down
| Request | Why | | --- | --- | | Full people-management HR load | Not my engagement model | | 24/7 pager rotation | Requires embedded team, not fractional | | Feature factory without design review | You need builders, not another IC queue | | Equity-only or “we’ll pay when we raise” | Cash or hybrid terms after paid discovery | | Rescue without repo access and a decision-maker | Scope cannot be honest |
If your need is mostly shipping features, hire a senior IC or run a full-stack product build with milestones instead.
How we start
- 20-minute discovery — confirm the workflow above matches your gap.
- Written proposal — days per week, monthly block, explicit out-of-scope list.
- First month retro — keep, expand, or end with no drama.
Next step
Book a discovery call or send a brief.
See also: What a 2-week AI automation sprint delivers.