How to Vet a Fractional CTO: Questions to Ask, and Red Flags to Run From

A lot of "fractional CTOs" are consultants who changed their LinkedIn title — and lately, bolted "AI" onto it. The good ones will transform your company; the wrong one will cost you a year and a lot of runway. Here's a founder's vetting checklist — the questions that separate a real operator from a résumé, and the red flags that should end the conversation. Use them on me, too.

1. Have they actually owned it?

Ask: "Tell me about a technology decision you owned that went wrong — and what it cost." A real operator has scar tissue and describes it plainly. Someone who has only ever advised — never had their name on the outcome — will dodge or give you a rehearsed non-answer. You want someone who's been accountable for real, expensive decisions, including the ones that blew up. That's where judgment actually comes from.

2. Can they go from strategy to hands-on?

A fractional CTO has to live in two worlds. If they can only talk strategy, you've hired an expensive consultant. If they can only code, you've hired a senior engineer with a fancy title. Test both: ask them to whiteboard how they'd approach a real decision you're facing, live. A real operator gets specific fast and asks sharp questions back. Vagueness under a concrete question is the tell.

3. Independence or dependence?

Ask: "What does handoff look like? How will my team be stronger when you're gone?" The right answer is about making you independent — documentation, a plan you own, your people leveled up. The wrong answer quietly makes you more dependent. Anyone building a moat around themselves is optimizing for their retainer, not your company.

4. Real AI fluency, or AI theater?

This is the new axis, and it matters more every month. Everyone says they're "AI-augmented" now, so test it: "Show me specifically how AI changes the way you work — and tell me where AI quietly wrecks an engineering org."

A real operator answers both halves fast. They can show the concrete workflows — code review at scale, a diagnostic pass, spec generation — and they can name the failure modes: slop accumulating unreviewed, security holes, false confidence, teams getting worse because they stopped thinking. The fake does one of two things: hypes AI like it's magic, or can't talk about it at all. You want the adult in the room — someone who uses AI hard and is honest about its limits. Anyone selling only the hype is exactly the wrong person to trust with this.

5. Fit and references

Fit: have they operated at your stage and in your domain — especially if you're regulated? Scaling a 300-person org and getting a seed-stage startup to product-market fit are different skills.

References: talk to past clients, and ask the real question — not "were they good," but "what did they change, and would you hire them again for the hard thing?" Vague praise is a yellow flag; a specific story is green.

Red flags to run from

All buzzwords, no specifics — including "AI" buzzwords — they can't get concrete about your situation.
No written artifact — they won't show a sample plan or diagnostic. Real operators think in writing.
Can't name a failure — nobody good has a clean record.
AI hype with no limits — if they can't tell you where AI goes wrong, they don't actually understand it.
Vague on scope and price — a real one right-sizes the engagement to your decisions.
Promises certainty — "I'll 10x your engineering with AI" is a pitch, not a plan.
Hides behind NDAs for everything — some confidentiality is normal; being unable to describe any past work is not.

Now use it — on me too

Take this list to everyone you talk to, me included. If you want to put me through it, book a call. If you'd rather start by seeing the kind of written work I do, an AI-augmented Technology Diagnostic is a low-commitment way to find out.

Not ready to talk to anyone yet? The free AI-First Readiness Scorecard will at least tell you where you stand.

Tom Lang provides AI-augmented fractional and interim CTO leadership through Heart of the Rockies Management Consulting, and has led engineering organizations from founding teams to hundreds of people across regulated, reliability-critical industries.