"What questions should I ask a fractional CTO before hiring"

"Ask about specific outcomes at similar-sized companies (not just big logos), how they handle disagreements with CEOs, how many companies they work with simultaneously, what the first 30 days look like, and how they measure their own success. Red flags: vague answers about 'improving processes,' inability to name concrete metrics they've moved, or jumping straight to technology recommendations before understanding your business."

Questions to Ask a Fractional CTO Before You Hire Them

Most founders have never hired a CTO before — full-time or fractional. They don’t know what good looks like, which means they don’t know what questions to ask. I’ve been on both sides of this conversation, and the questions that actually reveal whether someone can do this job are different from what most people expect.

Here are the questions I’d ask if I were hiring a fractional CTO — and what the answers should sound like.

“What specifically changed at your last two engagements?”

This is the single most important question. The answer should include concrete, measurable outcomes. “Reduced deployment cycle from weekly manual releases to automated daily deploys.” “Identified that the offshore team was delivering code at half the velocity of the in-house team and restructured the engagement, saving $15K/month.” “Built the hiring pipeline that brought in a VP of Engineering and two senior architects.”

If the answer is “I helped them think more strategically about technology” or “I improved their engineering processes,” press harder. What process? How did it improve? What metric moved? Vague answers usually mean vague impact.

“Tell me about a company you worked with that was our size.”

This is about fit, not pedigree. A CTO who’s only worked at 500-person companies may not understand the constraints of a 15-person startup where every engineer wears three hats and there’s no dedicated DevOps person. Similarly, someone who’s only worked with 5-person teams may not have the organizational design experience needed at 40 engineers.

The best answer includes a company at a similar stage, with similar constraints, where they drove outcomes relevant to your situation.

“How many companies are you working with right now?”

There’s a right answer here, and it’s 2-4. One company means they’re not really fractional — they’re underemployed and using you as a bridge to a full-time role. Five or more means they’re spread too thin to provide meaningful engagement. I typically work with 3-4 companies, which gives me enough bandwidth for each while maintaining the cross-pollination benefit that makes the fractional model valuable.

Follow up: “How do you handle it when two clients need you at the same time?” The answer should describe a clear system — structured schedules, async communication norms, escalation protocols for genuine emergencies.

“What does the first 30 days look like?”

The right answer is some version of: listen, diagnose, then act. If someone says they’ll come in and start making changes in week one, they’re either reckless or selling you something. No competent CTO makes architectural or organizational changes before understanding the existing system, the team dynamics, and the business context.

My own first month is almost entirely diagnostic — 1-on-1s with every engineer, architecture review, deployment process observation, incident history review, and mapping the gap between the technical roadmap and the business roadmap. By day 30, I have a prioritized action plan. Not before.

“How do you handle it when your recommendation conflicts with what the CEO wants?”

This question reveals character. The wrong answer is “I defer to the client — it’s their company.” That’s a yes-person, not a CTO. The also-wrong answer is “I insist on my way because I’m the expert.” That’s an ego problem.

The right answer is something like: “I present the data and the consequences of each path as clearly as I can. If the CEO still chooses a direction I disagree with, I document my concerns and commit to making their decision work as well as possible. If it’s a decision that fundamentally compromises the system or the team, I say so directly — even if it’s uncomfortable.”

“What’s your approach to AI and emerging technology?”

This is a trap question, and it’s useful. If the candidate immediately starts talking about how every company needs to adopt AI yesterday, they’re following hype, not thinking strategically. If they dismiss AI entirely, they’re not paying attention.

The right answer acknowledges that AI is a genuine shift but evaluates it in terms of your specific business context. Where can AI reduce costs or create competitive advantage for your company? Where is it premature or risky? The answer should be specific to your situation, not generic.

“How do you measure your own success?”

I measure by outcomes that matter to the business: Did deployment frequency increase? Did we avoid a bad hire or a wrong vendor? Did cloud costs become predictable? Did the board gain confidence in the technical trajectory? Did the team ship the things that mattered?

If someone measures by hours logged or meetings attended, they’re billing for presence, not impact.

“Can I talk to a previous client?”

Any fractional CTO worth hiring should be willing to connect you with at least one reference — ideally a CEO or founder they’ve worked with. Ask the reference the same question: “What specifically changed because of this person?” The answer should match what the candidate told you.

“What would make you turn down this engagement?”

This might be the most revealing question of all. A good fractional CTO has a clear sense of where they add value and where they don’t. “If you need someone writing production code” or “if you have 200 engineers and a functioning leadership team” or “if the budget doesn’t support enough hours for real impact” — these are honest answers that show self-awareness.

If someone says “I can help any company with any technology challenge,” they’re either delusional or desperate. Neither is what you want in a strategic advisor.