The 10 AI Persona Types: Understanding AI Fluency Profiles

When a candidate completes an AISA assessment, they receive a persona — one of ten types that describes their relationship with AI. The persona is not a score. It is a profile: a qualitative picture of how someone thinks about, uses, and builds with AI systems. Two candidates with similar composite scores can receive different personas if their strengths fall in different dimensions.

This matters because the question employers actually need answered is not "How good is this person with AI?" but "How does this person work with AI, and does that match what we need?" A Tactician who executes reliably with mainstream tools is a different hire than a Builder who has shipped custom AI products. Neither is universally better — they are different profiles suited to different roles and team needs.

This guide covers all ten personas in order from least to most advanced AI engagement. For each, we explain what defines them, what differentiates them from adjacent types, and what they signal in a hiring context. If you are evaluating candidates, building a team, or trying to understand your own assessment results, this is the reference document.

Quick Comparison Matrix

The Persona Spectrum

Personas are ordered along a spectrum from least to most advanced AI engagement, but "advanced" does not always mean "better for the role." A Tactician is a stronger hire for an operations manager position than an Oracle who has deep ML knowledge but no interest in day-to-day workflow optimization. The spectrum reflects depth and breadth of AI engagement, not universal job fitness.

The ten personas cluster into five tiers:

• Beginner — Bystander, Dabbler
• Emerging — Copy-Paster, Sceptic
• Proficient — Enthusiast, Tactician
• Advanced — Conductor, Builder
• Elite — Architect, Oracle

---

1. The Bystander

Tagline: AI is on the radar, but not in the routine.

The Bystander knows AI exists. They have read headlines, heard colleagues talk about ChatGPT, maybe watched a demo. But they have not meaningfully used AI tools themselves. The AISA assessment may be their most hands-on AI interaction to date.

This is not a judgment about intelligence or capability. Many experienced professionals — including senior leaders — fall into this category because their existing workflows have not yet demanded AI adoption. The Bystander's defining characteristic is awareness without action: they know AI is important but have not crossed the threshold from knowing to doing.

What differentiates them from a Dabbler: The Dabbler has tried things. They have typed prompts, experimented with tools, and formed early opinions. The Bystander has not taken that step. The gap is behavioral, not intellectual.

What this means for employers: A Bystander needs structured onboarding — not just tool access, but guided practice with clear use cases relevant to their role. The good news: Bystanders who complete onboarding programs often progress rapidly because they have no bad habits to unlearn. The risk: without intervention, they will remain Bystanders indefinitely.

Growth path: Start with one AI tool applied to one recurring task. The goal is not mastery — it is habit formation.

Read more: The Bystander AI Persona — A Complete Guide

---

2. The Dabbler

Tagline: Tries things out — hasn't locked in a rhythm yet.

The Dabbler experiments. They have asked ChatGPT questions, tried image generation, maybe used an AI writing assistant once or twice. But nothing has stuck. Their AI usage is sporadic — a prompt here, a quick question there — with no sustained pattern or workflow integration.

What makes Dabblers interesting is that they have already cleared the biggest hurdle: they are willing to try. Many people never get past the reluctance to engage with AI tools at all. The Dabbler's problem is not motivation — it is consistency. They try things without a framework for evaluating whether those things worked, so they do not build on previous experiments.

What differentiates them from an Enthusiast: The Enthusiast has crossed from experimental to intentional. They are not just trying tools — they are developing opinions about which tools work for which tasks, and they are improving over time. The Dabbler's experiments do not compound.

What this means for employers: Dabblers respond well to structure. Give them specific AI use cases for their role, pair them with someone more advanced, and check in regularly. They already have the curiosity — they need a path.

Growth path: Pick one workflow where AI could save 30 minutes per week. Use the same tool for the same task for two weeks straight. The shift from dabbling to developing happens when experimentation becomes routine.

Read more: The Dabbler AI Persona — A Complete Guide

---

3. The Copy-Paster

Tagline: Uses AI regularly — takes the output at face value.

The Copy-Paster is a daily AI user. They have integrated AI into their work and get real value from it. They write prompts, get outputs, and ship them — often without significant review or iteration. The name is not derogatory: it describes a real and common pattern where someone has built AI into their routine but has not developed the critical evaluation skills that separate productive use from reliable use.

Copy-Pasters are often among the most prolific AI users on a team. They generate content, draft emails, summarize documents, and write code with AI assistance at high volume. The gap is in quality control. They accept first-pass results, do not verify factual claims, and rarely iterate on prompts to improve output quality. This works fine for low-stakes tasks. It becomes a liability when the stakes rise.

What differentiates them from a Tactician: The Tactician also uses AI regularly, but with a verification step. They evaluate outputs, iterate on prompts, and have developed a sense for when AI output needs human review. The Copy-Paster skips that step — not out of laziness, but because they have not yet developed the instinct for when output quality matters.

What this means for employers: Copy-Pasters are productive hires who need quality guardrails. Pair them with review processes, establish output verification checklists for high-stakes work, and invest in training that focuses specifically on output evaluation and critical thinking. They already have the AI habit — they need the AI judgment.

Growth path: Before using any AI output in work that others will see, spend 60 seconds asking: "What could be wrong with this?" That single habit separates the Copy-Paster from the Tactician.

Read more: The Copy-Paster AI Persona — A Complete Guide

---

4. The Sceptic

Tagline: Questions everything — the output, the tool, the hype.

The Sceptic approaches AI with genuine critical thinking. They do not accept claims about AI capabilities at face value — not from the tools themselves, not from vendors, and not from enthusiastic colleagues. This skepticism is not uninformed resistance. Sceptics often have a clear-eyed understanding of AI limitations that many frequent users lack.

The paradox of the Sceptic is that their strongest trait — critical evaluation — is one of the most valuable AI skills, but it manifests as under-use. They question AI so thoroughly that they do not use it enough to develop the practical skills (prompting, workflow integration, tool selection) that would make their critical thinking even more effective. They are sitting on a foundation that many AI users would envy, but they are not building on it.

What differentiates them from a Bystander: The Bystander has not engaged. The Sceptic has engaged enough to form informed opinions — they just happen to be cautious ones. A Sceptic can articulate specific reasons why AI output might be unreliable. A Bystander cannot, because they have not tried.

What this means for employers: Sceptics are excellent for roles where AI risk management matters — compliance, legal review, quality assurance, editorial oversight. They are natural reviewers of other people's AI-generated work. The management challenge is encouraging them to use AI more, not less. Pair them with a Tactician or Conductor who can demonstrate practical value, and let them apply their critical lens to real workflows rather than hypothetical risks.

Growth path: Take one task where the Sceptic currently does everything manually. Use AI for it with a side-by-side comparison: AI output vs manual output. Evaluate both critically. The Sceptic's own evaluation skills will show them where AI adds value — and where it does not.

Read more: The Sceptic AI Persona — A Complete Guide

---

5. The Enthusiast

Tagline: Curious, capable, and picking up speed.

The Enthusiast is on a trajectory. They are actively building AI skills across multiple dimensions — trying new tools, refining their prompting techniques, developing repeatable patterns. They are not yet specialized or deeply expert in any one area, but the direction is clear and the rate of improvement is high.

What distinguishes Enthusiasts from more advanced personas is breadth over depth. They know a bit about many things: several AI tools, various prompting techniques, a range of use cases. They have not yet gone deep enough in any single dimension to reach Tactician-level reliability or Conductor-level orchestration. But they are the most likely persona to get there within 6-12 months, because they are actively learning and iterating.

What differentiates them from a Tactician: The Tactician has depth in their primary tools and workflows — they are reliable and efficient within their lane. The Enthusiast has breadth — they are exploring more territory but have not yet locked in the deep competence that defines the Tactician. Think of it as: the Tactician knows their tools cold; the Enthusiast is still shopping.

What this means for employers: Enthusiasts are high-upside hires. They learn fast, adapt to new tools, and bring energy to AI adoption initiatives. They are ideal for roles where AI practices are still being established — they will help shape the team's approach rather than just executing an existing playbook. The risk is that their enthusiasm can outpace their judgment: they may adopt new tools before properly evaluating them, or overestimate AI capabilities in areas where they lack deep experience.

Growth path: Pick one dimension — prompting, workflow integration, or tool landscape — and go deep. The Enthusiast's breadth becomes a superpower once it is anchored by genuine expertise in at least one area.

Read more: The Enthusiast AI Persona — A Complete Guide

---

6. The Tactician

Tagline: Gets things done with AI — fast and reliably.

The Tactician is the backbone of AI-capable teams. They use mainstream AI tools well, consistently, and productively within their existing workflows. They communicate clearly with AI systems, iterate on outputs when needed, and have developed reliable patterns for the tasks they handle regularly. They are not pushing the cutting edge of AI tooling — they are executing well within proven territory.

Tacticians are defined by reliability. When they use AI for a task, the output is consistently good. They have moved past the experimentation phase entirely: they know which tools work for which tasks, they have templates and approaches that they reuse, and they can teach others to replicate their workflows. This makes them enormously valuable in teams that need AI adoption to scale — the Tactician is the person who makes AI usage repeatable and teachable.

What differentiates them from a Conductor: The Tactician excels within individual tools and established workflows. The Conductor orchestrates across multiple tools and builds complex multi-step pipelines. A Tactician might be excellent at using Claude for code review — the Conductor connects Claude to their CI pipeline, routes different types of review to different models, and automates the entire process. The gap is single-tool depth vs multi-tool orchestration.

What this means for employers: Tacticians are immediately productive hires for any role that involves regular AI usage. They require minimal onboarding for AI tools and will quickly establish reliable workflows. They are also excellent mentors for less experienced team members. The limitation: they may not drive innovation in how AI is used. If you need someone to reimagine workflows or build new AI-powered tools, look further up the spectrum.

Growth path: Identify a multi-step workflow that currently requires manual handoffs between AI interactions. Automate those handoffs. The transition from Tactician to Conductor starts when you move from using AI tools to connecting them.

Read more: The Tactician AI Persona — A Complete Guide

---

7. The Conductor

Tagline: Orchestrates AI across the workflow, not just within it.

The Conductor has moved beyond using individual AI tools well. They design and operate complex workflows that span multiple AI systems, often connecting them to non-AI tools and data sources. They understand which tool is best for which subtask, how to route information between systems, and how to maintain quality when output from one AI feeds into another. They configure, customize, and orchestrate — but typically work with existing tools rather than building new ones from scratch.

The Conductor's signature skill is systems thinking applied to AI. Where a Tactician sees individual AI interactions, the Conductor sees pipelines. They might use one model for initial drafting, another for analysis, a third for code generation, and tie them together with automation tools, custom prompts, and quality gates. This orchestration capability is increasingly valuable as organizations move from "everyone uses ChatGPT sometimes" to "AI is embedded in our operational infrastructure."

What differentiates them from a Builder: The Conductor assembles existing components into sophisticated workflows. The Builder creates new components — tools, products, or systems that did not exist before. A Conductor might build a complex content pipeline using Zapier, Claude, and a CMS. A Builder might write a custom application that does something no existing tool combination can achieve. The distinction is configuration vs creation.

What this means for employers: Conductors are ideal for roles that require workflow design, process automation, and cross-functional AI implementation. They are the people who turn a team's ad-hoc AI usage into scalable operational processes. They excel in operations, project management, and technical program management roles where the value comes from connecting systems rather than building them.

Growth path: Identify a workflow that cannot be solved with existing tools. Build a custom solution — even a simple script or API integration. The transition from Conductor to Builder happens when you start creating, not just configuring.

Read more: The Conductor AI Persona — A Complete Guide

---

8. The Builder

Tagline: Has actually built something with AI.

The Builder has crossed a threshold that most AI users never reach: they have created something. Not configured an existing tool, not assembled a pipeline from pre-built components — actually built a tool, product, workflow, or system that uses AI in a way that required writing code, designing architecture, or solving novel technical problems. The thing they built might be for personal use, for their team, or for customers. What matters is that they learned by doing.

Builders develop a fundamentally different understanding of AI than people who only use AI as consumers. They have encountered the real constraints: API rate limits, token costs, hallucination rates in production, the gap between demo-quality output and production-quality output. This practical experience gives them judgment that no amount of tool usage can replicate. They know what AI is good at because they have tested its boundaries firsthand.

What differentiates them from an Architect: The Builder has created useful things. The Architect designs complex, multi-system integrations at production scale. A Builder might create a custom Slack bot that uses Claude to summarize meeting notes. An Architect designs a system where multiple AI components interact with each other, with databases, with user interfaces, and with external APIs — and the whole system needs to be reliable, scalable, and maintainable. The gap is craft vs engineering at scale.

What this means for employers: Builders are strong hires for product and engineering roles where AI is a core part of the value proposition. They can evaluate AI capabilities realistically because they have shipped real work. They bridge the gap between AI strategy ("we should use AI for X") and AI execution ("here is how we actually build X"). They are also excellent at estimating effort and identifying risks in AI projects, because they have lived through the build process.

Growth path: Take something you have built and make it production-grade: add error handling, monitoring, fallback logic, and documentation. Or integrate it with other systems. The Builder becomes an Architect when they start thinking about systems, not just products.

Read more: The Builder AI Persona — A Complete Guide

---

9. The Architect

Tagline: Builds highly complex integrated systems using AI.

The Architect operates at a level of technical sophistication that is rare even among strong AI practitioners. They design and build multi-system architectures where AI components interact with each other and with non-AI systems at production scale. They think in terms of data flows, failure modes, scaling constraints, and system reliability — not just "does the AI output look right?" but "how does this system behave under load, when the model is slow, when the input is adversarial, when the downstream system is unavailable?"

Architects are distinguished by the scope and complexity of what they build. Where a Builder creates a useful tool, the Architect designs the infrastructure that multiple tools run on. They make decisions about model selection, orchestration patterns, caching strategies, cost optimization, and monitoring that affect entire engineering organizations. They understand AI deeply enough to make sound architectural decisions, but their primary focus is on the system, not on the underlying technology.

What differentiates them from an Oracle: The Architect builds complex systems using AI. The Oracle understands AI itself at a fundamental level — the mathematics, the training processes, the theoretical capabilities and limitations. An Architect knows that a particular model hallucinates more on certain types of queries and designs around that limitation. An Oracle understands why the model hallucinates — the training data distribution, the attention mechanism's behavior, the decoding strategy's impact on output quality. The Architect's knowledge is applied; the Oracle's is foundational.

What this means for employers: Architects are senior technical hires suited for AI platform teams, infrastructure roles, and technical leadership positions where the challenge is not "can we use AI?" but "how do we build AI into our product architecture reliably at scale?" They are rare and valuable. If you are hiring for this level, you already know it — the role typically involves words like "platform," "infrastructure," or "principal" in the title.

Growth path: Go deeper into the technology itself. Read papers, understand training dynamics, experiment with fine-tuning or model evaluation. The Architect becomes an Oracle when the curiosity shifts from "how do I build with this?" to "how does this actually work?"

Read more: The Architect AI Persona — A Complete Guide

---

10. The Oracle

Tagline: Understands AI at its core — not just how to use it.

The Oracle has what the rest of the spectrum does not: deep understanding of AI as a technology. They understand or build AI models. They work with machine learning and large language models at a technical level — training, evaluation, fine-tuning, architecture design. Their critical analysis of AI outputs comes not from pattern recognition ("this looks wrong") but from first-principles reasoning ("this is wrong because the training distribution does not cover this domain, and the model is extrapolating in a way that the architecture is not designed for").

Oracles are not just advanced users who kept going. They represent a qualitatively different relationship with AI. Where every other persona relates to AI as a tool to be used (with varying degrees of skill), the Oracle relates to AI as a technology to be understood, extended, and built upon. They might work on model training, evaluation benchmarks, alignment research, or novel AI architectures. Their daily work is the AI itself, not work assisted by AI.

What differentiates them from an Architect: The Architect builds sophisticated systems that use AI. The Oracle understands the AI inside those systems. An Architect might design an RAG pipeline with optimal chunk sizes, embedding selection, and retrieval strategies. An Oracle understands why certain embedding models produce better results for certain domains, how the attention mechanism affects retrieval quality, and what the theoretical limits of the approach are. Both are elite practitioners — the difference is what they are expert in.

What this means for employers: Oracles fill roles in ML/AI research, AI platform engineering, CTO/VP Engineering positions at AI-native companies, and advisory roles where deep technical judgment about AI capabilities is the primary value. They are the people you bring in when the question is not "should we use AI?" or "how do we build with AI?" but "what is AI actually capable of, and where is the technology heading?" They are also the most expensive and hardest-to-hire personas on the spectrum, for obvious reasons.

Growth path: The Oracle is the final persona on the spectrum. Growth at this level is about frontier contributions — advancing the state of the art, mentoring the next generation of AI practitioners, and applying deep knowledge to problems that nobody has solved yet.

Read more: The Oracle AI Persona — A Complete Guide

---

How Personas Are Assigned

AISA personas are not based on a single score threshold. They are assigned based on the shape of a candidate's dimension profile — which of the five scoring dimensions are strongest and how they relate to each other. Two candidates with the same composite score can receive different personas if their strengths fall in different areas.

For example, a candidate who scores highly on Critical Thinking and Safety but moderately on Workflow Integration is more likely to be classified as a Sceptic than a Tactician, even if their overall scores are similar. The persona captures how someone engages with AI, not just how much.

This design means that personas are not a simple ranking. They are a typology. A Sceptic is not "worse" than an Enthusiast — they are different. The Sceptic brings critical evaluation skills that the Enthusiast may lack. The Enthusiast brings adaptability and learning speed that the Sceptic may not demonstrate. The right hire depends on what your team needs, not on which persona sounds most impressive.

Using Personas in Hiring

The most common mistake employers make with personas is treating them as a linear ranking and only hiring from the top. This leads to over-indexed teams — all Builders and Architects with no one asking whether the AI output is actually correct (that is the Sceptic's job) or whether the workflow is teachable to the rest of the team (that is the Tactician's job).

A well-balanced AI-capable team includes:

• Tacticians for reliable execution and workflow documentation
• Sceptics for quality assurance and risk evaluation
• Conductors for process design and cross-tool integration
• Builders for creating custom AI-powered tools and products
• Enthusiasts for adaptability and early adoption of new tools

The "best" persona is always the one that matches the role requirements, the team's existing composition, and the organization's AI maturity. An engineering team that already has three Architects and no Tacticians does not need a fourth Architect — they need someone who can make their sophisticated systems usable by the rest of the organization.

For a deeper dive into the scoring framework behind personas, see The AISA Rubric: 5 Dimensions of AI Proficiency. For implementation guidance on using assessment data for team development, see Closing the AI Skills Gap: An Implementation Playbook.