How Fluent Are Your Developers in AI-Augmented Development?
A scored profile of true AI fluency in your dev team — going beyond tool usage to the judgment, prompt design, and failure-mode literacy that separates AI-augmented engineers from AI-using engineers.
- A scored profile across 6 dimensions — see exactly where you're strong and where the gaps are.
- Your biggest opportunities, mapped to specific next moves.
- A personalized video walkthrough from Shawn (optional) — a real read on your results.
Most conversations about AI in engineering start with tools — which IDE, which model, which agent. Fluency is a different question. It's not whether developers can open Copilot or Claude Code; it's whether they can structure prompts to get useful first-pass output, spot when the model is fabricating an API, curate context deliberately, read AI output with the skepticism of a senior reviewer, calibrate when AI is the right tool, and keep investing in the craft as the field moves. The gap between AI-using engineers and AI-augmented engineers is real — and invisible from a tool-license report.
This free assessment scores your developer team across six fluency dimensions and returns a clear profile in about six minutes. It's built from 27 years of technology leadership across Fortune 500 and growth-stage companies — the same lens a fractional CTO would bring to your first conversation about whether your developers are augmenting their judgment with AI or just typing less.
What developer AI fluency actually measures
Fluency is a profile, not a single number. The assessment evaluates six dimensions independently so you can see exactly where your developers are fluent and where they're still tool-using: Prompt Craft Depth (whether devs structure prompts to get useful first-pass output), Failure-Mode Literacy (whether they spot hallucinated APIs, fabricated functions, and plausible-but-wrong code), Context Hygiene (whether they supply the right project context — CLAUDE.md, working-set scope, system instructions), Critical Reading of AI Output (whether they read AI code with skepticism or merge whatever compiles), Decision Calibration (whether they know when to reach for AI and when to write by hand), and Continuous Learning Cadence (whether they're actively investing in fluency or coasting on what worked last quarter). The final question maps where targeted investment would most move the fluency score in the next two quarters.
Why fluency is different from productivity
Productivity asks how much output your developers get from AI. Fluency asks whether the underlying capability is being built. A team can show strong AI productivity metrics — high acceptance rates, lots of merged AI-assisted PRs — and still have shallow fluency, because the gains are concentrated in two or three enthusiasts and the rest of the team is merging whatever compiles. That gap is invisible from a productivity dashboard and corrosive over time: it produces inconsistent code quality, slow time-to-abandon on bad prompts, and a team that's one model upgrade away from being lapped. Fluency measures whether the capability is durable and broadly distributed — not whether last sprint's velocity looks good.
What you get at the end
You'll see an overall developer AI fluency score, a band that describes where you stand (from AI-Using through AI-Augmented), a per-dimension breakdown across all six pillars, and a map of your highest-value fluency investments across prompt craft, failure-mode literacy, context hygiene, critical reading, calibration, and continuous learning. From there you can request a personalized video walkthrough — a short, recorded read on your specific results and what a fractional CTO engagement would do for your developer team. No generic sales deck.
Frequently asked questions
What is developer AI fluency?
Developer AI fluency is the craft layer beneath AI tool usage: prompt design, failure-mode detection, context discipline, critical reading of AI output, calibrated tool choice, and continuous learning. A developer can use AI tools every day and still have shallow fluency. Fluency measures whether engineers are augmenting their judgment with AI — not just typing less.
How is this different from a developer AI productivity assessment?
Productivity measures the OUTPUT — how much AI-assisted code ships, acceptance rates, throughput impact. Fluency measures the CAPABILITY — whether individual developers can structure prompts, spot hallucinations, curate context, read AI code with skepticism, and know when to reach for AI vs. write by hand. You can have strong productivity numbers and shallow fluency. Fluency is the durable layer.
How long does the assessment take?
About six minutes. It's 18 scored questions across six fluency dimensions plus a final investment-mapping question covering where targeted fluency investment would most move the needle. Your progress auto-saves, so you can leave and come back without losing answers.
Is the assessment free?
Yes. The assessment and your scored results are completely free. You can optionally request a personalized video walkthrough of your results, which is also free.
Who is this assessment for?
It's built for CTOs, VPs of engineering, engineering managers, and tech leads who want a clear-eyed read on whether their developers are genuinely AI-fluent — or just AI-using — and which two moves would close the gap fastest.