How to Hire a Fractional CTO: 12 Questions That Separate Operators from Resume Padders

The fractional CTO market is crowded in 2026 and the quality variance is enormous. For every operator with twenty years of hard-won scars, there are three people who added the title to their LinkedIn last month after reading a blog post. The problem is that from the outside, on a 30-minute intro call, they can sound identical.

This article is the hiring guide I would give any founder if I were on the other side of the table. It is a set of twelve questions designed to surface the things that actually matter, plus the red flags that tell you to pass, plus the one reference check that is worth more than ten others combined. It will not guarantee a perfect hire — no interview process can — but it will dramatically improve your odds.

Fair warning: I am writing this as someone who is a fractional CTO. If I am doing my job honestly, I should be giving you questions that would be hard for me too. I think the questions below clear that bar. You can be the judge.

Before the interview: the one-page prep

Before you talk to any candidate, take 20 minutes and write down your honest answers to three questions. You are going to use these in every interview.

What is the biggest technical problem you are facing right now? Not in the abstract. The actual one. "We are about to lose a customer because our uptime is bad." "We do not know whether to migrate off our current vendor." "Our lead engineer is burning out."

Who is on the team today, and what do you know about how each of them is doing? Names, roles, the one-sentence version of how they are performing.

What does success look like in 90 days? Not vibes. Concrete outcomes.

The candidates worth hiring will be able to engage with those three answers specifically. The candidates who are not worth hiring will respond with generic frameworks. The gap is obvious once you are looking for it.

The twelve questions

I have grouped these into four buckets. Ask all twelve. Do not skip to the favorites.

Bucket 1: Have they done the job?

1. "Walk me through the last fractional CTO engagement you finished. What was the state of the company on day one, and what was the state on the day you left?"

This is the single most revealing question in the whole list. It forces a specific story with a start, a middle, and an end. Listen for: names (even anonymized), numbers, actual decisions, actual hires, actual codebase changes. Watch for: vague arcs, passive voice, "we helped them" without specifics. A real operator can tell this story for 15 minutes with concrete details. A resume padder cannot.

2. "What did you get wrong at that engagement? What would you do differently?"

Every real engagement has at least one thing that did not work. Maybe a hire did not pan out, a migration took longer than expected, a recommendation the founder ignored. A candidate who cannot name a single thing they would do differently is either lying or has not examined their own work. Both are disqualifying.

3. "Give me an example of a time you pushed back on a founder's strategic decision and changed their mind."

A fractional CTO who cannot say no to a founder is not a CTO. Listen for a specific instance. Listen for what the founder wanted, what the CTO said, why, and what the outcome was. A great answer is often uncomfortable to tell, which is why it is a good test.

Bucket 2: How do they actually work?

4. "Walk me through your first 30 days at a new engagement. Specifically."

This question is a trap for people who do not have a real playbook. They will give you a generic three-phase framework: "discover, plan, execute." Real operators will get much more specific: what they do in week 1, what the artifacts are, which meetings they run, which conversations they have, what they expect to ship by day 30. If you want a reference answer, I wrote up my own 30-day playbook in a separate article. Their answer does not have to match mine, but it should be equally specific.

5. "What does your weekly operating rhythm look like with a client? Walk me through a real week."

Same trap. A great answer will include specific meetings, specific days, specific artifacts, and specific 1:1 cadence. A weak answer will talk about "agile practices" and "being available." If they cannot describe a week in concrete terms, they do not have a weekly rhythm.

6. "How do you work with a non-technical founder who is anxious about engineering?"

Listen for empathy, humility, and specific habits — written updates, clear metrics, translation work between the team and the founder. Do not hire anyone who answers this with variations of "I tell them to trust the process." That is a CTO who has never actually worked with a non-technical founder and has definitely read a book about it.

Bucket 3: Can they actually do the technical work?

7. "Tell me about a recent architectural decision you made. What were the options, what did you pick, and why?"

You are listening for real technical depth, not resume keywords. The answer should be specific enough that you could ask follow-up questions for 20 minutes. If you are non-technical and you cannot follow the answer, ask the candidate to explain it to you in plain English — a great CTO can do this in real time without condescension.

8. "How do you approach AI-assisted development with the teams you work with? What are the guardrails?"

In 2026 this is a required question. Every fractional CTO should have a clear, opinionated answer about AI-assisted development. Listen for specifics about tools, workflows, review practices, and the senior-junior gap. Watch for either extreme: "I do not use any of those tools" is a red flag for staleness, and "I let the AI do everything" is a red flag for recklessness.

9. "The team has a flaky integration with a critical vendor. It breaks once a week. What do you do in your first week as their CTO?"

A scenario question designed to reveal how they actually think. Good answers include: understanding the problem before fixing it, looking at the logs and metrics, talking to the engineer who owns it, assessing whether it is the vendor or the integration code, deciding whether to invest in the fix or the workaround or a replacement. Bad answers jump straight to a solution without any diagnostic work.

Bucket 4: Culture, fit, and honesty

10. "When does your engagement end, and what does it look like when you leave?"

A great fractional CTO is actively planning their own exit from day one. Listen for: specific exit criteria, a handoff plan, a view on what triggers the transition to a full-time CTO or an internal promotion. A candidate who has no exit plan is either planning to become permanent (which may be fine, but say so) or has never actually wrapped up an engagement cleanly.

11. "What kinds of companies do you decline to work with? Why?"

Every real operator has a list. They will not work with founders who will not take feedback. They will not work in deeply regulated verticals without the right expertise. They will not work below a certain minimum commitment because they know it will not succeed. A candidate who says they work with everybody is either desperate or inexperienced.

12. "What would you want to know about my company and me before you accepted this engagement?"

Flip the interview. A real fractional CTO interviews you as hard as you interview them, because a bad engagement hurts both sides. Listen for questions about founder expectations, team culture, decision authority, and honesty in the relationship. A candidate who has no questions of their own is a candidate who is going to take any engagement, which is not a good sign.

Red flags that are almost always disqualifying

A few patterns that should end the conversation.

They will not name a single specific former client. Anonymization is fine. Vagueness about whether the engagements were real is not. "I've worked with many startups" is a dodge.

Their rate is suspiciously low. Below $150 per hour in the US market in 2026, you are almost certainly getting a junior or mid-level engineer with an inflated title, not an operator with CTO experience. The exceptions are rare.

They are available to start immediately and have unlimited capacity. Good fractional CTOs are capacity-constrained. If someone can give you 4 days a week starting tomorrow, ask why.

They cannot articulate how the engagement will end. This is a leadership tell. People who have done the job know what the end looks like.

They talk about "the team" as if engineers are interchangeable. Watch the language. Great CTOs talk about specific people and specific dynamics. Weak ones talk about "the team" as a black box.

They resist a written 30-day plan. Any candidate who does not want to commit to specific month-one deliverables is protecting themselves from accountability. That protection comes at your expense.

They are dismissive of AI-assisted development. In 2026, any technology leader who has no opinion on AI-assisted development and no practical experience with it is a leader who stopped learning a year ago. That is a problem.

The one reference check that matters

Candidates will usually offer you a list of references. Call them, but know that they are selected to say good things, and they will.

The reference check that actually matters is the one the candidate did not offer. Find one yourself.

Look at the candidate's LinkedIn. Find a past client — a founder they worked with. Email that founder cold with a short note: "I am considering hiring [name] as a fractional CTO and I would love 15 minutes of your honest perspective." Most founders will take the call. Many will be more candid than the listed reference because they did not know they were going to be one.

Ask that founder three questions:

"If you were hiring a fractional CTO again today, would you hire this person? Why or why not?"
"What were they best at, and what did they struggle with?"
"If I told you I was about to sign a six-month engagement with them, what would you want me to know that I probably have not been told?"

The answers to those three questions will tell you more than any resume, any portfolio, and any first-round interview.

What to do after the interviews

Once you have run the twelve questions with two or three candidates, here is how I would decide.

Pass on anyone who cannot tell a specific story in Bucket 1. If their engagement history is vague, nothing else matters. Move on.

Shortlist the candidates who handled the scenario in Question 9 the way you would want them to handle a real incident. How they think under that kind of pressure is how they will think when your site goes down at 2am.

Have the shortlist write a short proposal. Two or three pages on what they would do in the first 30 days at your company specifically, with the information you have shared. This is the single best predictor of engagement quality. Paid trial work is also an option for longer engagements, but for most fractional roles the proposal is enough.

Check the unlisted reference on your top candidate before you sign anything.

Trust your gut on fit after the evidence is in. Not before. Gut-first hires are how founders end up with the smooth talker instead of the operator.

Counterpoint: the interview is not the engagement

One honest caveat: the best fractional CTO interview is a real working session, not a conversation. If you can, structure a two-week paid engagement — a "tryout" — before the full commitment. This is surprisingly common in the fractional CTO market, and it is better than any interview I could design. Two weeks of actual work together reveals everything. If a candidate refuses a paid tryout, that is information too.

Your next move

If you are in the middle of interviewing fractional CTOs right now, save this page and run the twelve questions with your next candidate. You will see the difference within the first three questions.

If you have not started interviewing yet, start by writing out the one-page prep at the top of this article. That exercise alone will sharpen your interviews in ways I cannot do for you from a distance.

Where I come in

If you are about to interview fractional CTOs and you want to see what it looks like on the other side of these questions, book a 30-minute call and I will walk you through my answers to all twelve, live, with real examples. You should be doing that with three or four candidates anyway — I am happy to be one of them, and if at the end you decide I am not the right fit, you will still leave with a much better sense of what "right" looks like for you.