Fractional CTO vs Tech Lead vs Engineering Manager: Roles Explained

Three job titles get casually swapped in conversations about technical leadership: fractional CTO, tech lead, and engineering manager. They sound similar. They solve different problems. Hiring the wrong one for your need is one of the most common (and expensive) mistakes Indonesian SMEs make in technical leadership.

Here’s the clean version of the differences.

What each one actually does

Fractional CTO

Time horizon: 1–3 years out. What technology decisions made today will affect the company in 18 months?

Scope: Strategic. Vendor selection, build-vs-buy decisions, hiring senior engineers, architecture review, runway planning. Translates between business and engineering at the executive level.

Reports to: Founder/CEO. Sits at the leadership table.

Day-to-day: 1–2 days a week of engagement. Most of the work is conversations, written assessments, and decision support.

Doesn’t do: write production code, run standups, manage individual engineer performance.

Tech Lead

Time horizon: 1–3 months out. What technical decisions made today will affect the next sprint cycle?

Scope: Tactical. Code architecture for the project they’re leading, technical mentoring of more junior engineers, code reviews, technical design of new features.

Reports to: Engineering manager or CTO.

Day-to-day: Full-time engineer. They write code, but their job also includes the technical leadership of one team or one product area.

Doesn’t do: company-wide strategy, hiring decisions outside their immediate team, vendor relationships.

Engineering Manager

Time horizon: 1–6 months out. How do I make this team ship reliably and grow people?

Scope: People + process. Performance reviews, hiring for the team they manage, removing blockers, ensuring delivery commitments are met.

Reports to: CTO or VP Engineering (or the founder, in smaller orgs).

Day-to-day: Full-time, mostly meetings, one-on-ones, planning. Some still code, most don’t.

Doesn’t do: high-level technology strategy, deep individual technical decisions (those go to tech leads).

How to tell which one you need

Three diagnostic questions:

1. Are decisions getting made badly because no one has the right authority?

If the team can’t decide whether to use library X or Y, you have a tech lead gap. If you can’t decide whether to commit to platform A or B, you have a fractional CTO gap. If decisions are made but never executed reliably, you have an engineering manager gap.

2. What’s the time horizon of the decisions you’re missing?

• This week’s technical decisions are getting made wrong → tech lead.
• Quarterly delivery commitments are missed → engineering manager.
• Strategic technology bets are made by gut feel → fractional CTO.

3. What’s the team size?

• 3–5 engineers, no leader → tech lead first. They can do strategic work too at this scale.
• 5–12 engineers → engineering manager + tech lead pair (often the same person). Possibly a fractional CTO for strategic moments.
• 12+ engineers → all three roles needed. CTO becomes full-time around here.

Common hiring mistakes

Three patterns we see consistently:

Hiring a fractional CTO when what’s needed is a tech lead

Founder feels overwhelmed by technical decisions, hires a fractional CTO. The fractional CTO produces strategic recommendations, but the team still doesn’t have anyone deciding tactical technical questions day-to-day. The strategic work doesn’t get implemented because there’s no one to lead the implementation.

The right hire was a tech lead with engineering management responsibilities. Cheaper and more useful for the actual gap.

Hiring an engineering manager who’s never built software

Common in companies that grew non-technical. They hire a generic project manager and call them “engineering manager”. The role fails because engineers don’t respect the person’s technical judgment, and the EM can’t translate engineering work into business outcomes.

Engineering managers should have shipped real software at some point. Pure project management is a different role.

Promoting a senior engineer to “CTO” of a 12-person team

Looks like a tidy promotion. The senior engineer is now CTO. They keep coding because that’s what they’re good at. The strategic and people work doesn’t get done. The team stalls.

Either give the senior engineer the tech lead title and bring in someone else for the strategic and people layer, or commit to retraining them as a leader (which takes 12–24 months and is expensive).

When you need more than one

Many Indonesian SMEs in the 30–80 employee range need multiple of these roles, just not all full-time:

• Fractional CTO (1 day/week) for strategic decisions.
• Internal tech lead (full-time engineer who also leads) for tactical technical decisions.
• Engineering manager (often the same person as the tech lead at this scale) for people and delivery.

The fractional CTO and the internal tech lead/EM work together. The fractional handles the decisions that span beyond the tech lead’s authority. The tech lead handles the day-to-day. Both are needed, but the fractional doesn’t have to be expensive.

If you’re trying to figure out which role your specific situation calls for, an hour of conversation usually clarifies it. We do those at no cost — and we’ll honestly tell you if your need doesn’t match what we offer.