A founder reached out to me after a difficult first experience with a fractional CTO. She'd hired someone based on an impressive resume, a confident Zoom presence, and references she hadn't thought to probe deeply. Three months and $24,000 later, the engagement had produced a Notion doc full of technical recommendations she couldn't evaluate and a codebase that three subsequent developers told her needed to be restructured.
She asked me: "How was I supposed to know?"
The honest answer is that the signals were there. She just hadn't known what to look for. As someone who's been on both sides of this — as a fractional CTO interviewing for engagements, and as someone who helps founders evaluate technical candidates — I've identified seven patterns that reliably predict a poor engagement. Here they are.
Not sure what you actually need from a fractional CTO?
Before the interview process, it helps to get clear on what outcomes you're hiring for. I offer a free 30-minute call to help founders scope the engagement properly — so you interview for the right things from the start.
Book a Free CallRed Flag 1: They Lead with Technology, Not Your Business
If the first thing a fractional CTO candidate tells you is their preferred tech stack, that's information. Not good information.
The best fractional CTOs I've seen — and the approach I try to embody myself — lead with questions. What problem are you solving? Who's the customer? What does success look like in six months? The technology decisions follow from the business context, not the other way around.
A candidate who opens by telling you they "work primarily in AWS with a microservices architecture" before they've understood what you're building is showing you how they think. They're thinking about the tools first. That will cost you money.
What to ask instead: Open the interview by describing your business in two sentences and then asking: "What questions would you want answered before you'd feel comfortable making any technical recommendations?" A strong candidate will ask about your customers, your revenue model, your team, and your constraints. A weak one will ask about your tech stack.
Red Flag 2: Jargon That Doesn't Simplify When Asked
This is the one I tell every non-technical founder to test explicitly. Ask the candidate to explain a technical decision they've made recently. Then ask: "How would you explain that to a non-technical co-founder?"
Some candidates will shift naturally into accessible language — analogies, plain descriptions, clear trade-offs. Others will re-explain using the same terms, slightly slower. The second group is going to create an information bottleneck in your business. Every key technical decision will pass through someone you can't effectively evaluate, and over time that's a serious governance risk.
I've made it a practice to check in with every founder I work with: "Did that make sense? Can you explain the decision back to me in your own words?" If a fractional CTO candidate looks uncomfortable when asked to simplify, they will be uncomfortable when you need to understand what's being built and why.
Red Flag 3: No Structured First-30-Days Process
Ask every candidate: "Walk me through your approach to the first month of an engagement." The answer tells you a lot.
Strong candidates describe a discovery process: understanding the business model, auditing existing technical decisions, mapping constraints, aligning on what success looks like before any build decisions are made. They describe what questions they'd ask and why. They explain how they'd calibrate their advice to your specific stage.
Weak candidates describe starting to build. Or starting to fix things they've already decided are broken. They describe outputs before inputs. This is the pattern that produces $24,000 of Notion docs and restructured codebases.
Evaluating a fractional CTO and want a second opinion?
If you're in the process of interviewing candidates and want to sanity-check what you're hearing, I'm happy to be a sounding board. Non-technical founders shouldn't have to navigate this alone.
Get a Second Opinion30 minutes • No obligation • Honest feedback
Red Flag 4: References Are All Technical Peers
When you ask for references, pay attention to who they nominate. If the list is all CTOs, engineering managers, and lead developers — that's a signal. Those references speak to technical credibility. They don't tell you anything about what it's like to be a non-technical founder working with this person.
The references you want are founders. Specifically, non-technical founders who can answer: How did this person communicate when things went wrong? How did they explain decisions I couldn't evaluate myself? Did I feel more in control of my technology strategy by the end of the engagement, or less?
The question to ask founder references: "If you had to describe what it felt like to be a non-technical founder working with this person — not what they built, but what the experience was like — what would you say?" The answer to that question is much more predictive than any technical credential.
Red Flag 5: Vague on Availability and Scope
Fractional arrangements live and die on specificity. How many hours per week? What's the expected response time on Slack? How do they handle it when two clients need them on the same day? What exactly is in scope, and what requires a separate conversation?
If a candidate answers these questions with "it depends on what comes up" or "I'm pretty responsive," that's a problem. Good fractional CTOs have worked through these questions in previous engagements and have clear answers. They know their communication protocols. They know their conflict-of-interest policy. They know what they'll do and what they won't.
Vagueness here isn't humility — it's operational risk that will land on you. At $10,000–$15,000 per month, you should be able to get a clear statement of what you're getting.
Red Flag 6: Same Advice for Every Stage
Ask the candidate what they'd build properly from day one, even under time pressure, and what they'd explicitly defer until you had more runway. If the answer is generic — "it always depends" without specifics — or if it sounds like advice for a 50-person engineering team, that's a mismatch.
Stage-appropriate judgment is one of the most valuable things a fractional CTO brings to an early-stage company. What's essential at Series B is often actively harmful at pre-seed. A candidate who can't speak specifically about that distinction will apply enterprise patterns to a startup budget, and the result is usually expensive infrastructure that doesn't match the problem.
Red Flag 7: They've Never Said No to a Founder
This is the one most founders don't think to test. Ask: "Tell me about a time you recommended against something a founder wanted to build, and how that conversation went."
A fractional CTO who's never pushed back — or who can't recall a specific example — is either telling you what you want to hear in the interview, or they're a yes-person in the engagement. Neither is useful. The fractional CTOs who create real value are the ones who say "I understand why you want to build that, and here's why I'd recommend against it right now" — and can hold that position when the founder pushes back.
I've had those conversations with every founder I've worked with. Sometimes I'm wrong. But the willingness to have the conversation — clearly, directly, and with the founder's interests rather than their preferences as the reference point — is what makes the engagement worth the fee.
Ready to hire a fractional CTO who won't waste your runway?
I work with Australian startups from pre-seed to Series A — building MVPs, setting up technical teams, and helping non-technical founders make smart decisions without being held hostage to jargon. If any of the red flags above made you nervous about a current or potential engagement, let's talk.
Start a Conversation30 minutes • No obligation • Honest feedback