If you write software for a living and you're looking at a move into AI work, the Claude Certified Architect Foundations exam (CCAR-F) can look like a whole new field to learn. It isn't. A large share of what the exam tests is software engineering applied to a new kind of component: a model that reads your tool descriptions, follows your configuration, and makes decisions inside your system.
This guide walks through the exam's five domains and shows which ones build directly on experience you already have, and which ones will need the most study. Everything here comes from Anthropic's published exam guide, so you can check each point for yourself.
What the exam is looking for
Section 1 of the exam guide (CCAR-F) says the certification validates that practitioners can make informed decisions about tradeoffs when implementing real-world solutions with Claude. Questions are grounded in realistic production scenarios, and candidates need practical judgment about architecture, configuration and tradeoffs, not just conceptual knowledge.
Section 5 (CCAR-F) lists the six scenarios the exam draws from. Each sitting presents four of them at random:
- a customer support resolution agent
- code generation with Claude Code
- a multi-agent research system
- developer productivity tools
- Claude Code in a CI/CD pipeline
- structured data extraction
If you have shipped production software, most of that list will look familiar. Four of the six are the kind of system developers already build, maintain or use every day.
Tool Design & MCP Integration (18%): your API experience, pointed at a new reader
This is the domain where developer experience transfers most directly. Section 6 (CCAR-F) includes task statements on designing tool interfaces with clear descriptions and boundaries, and on implementing structured error responses for MCP tools.
If you have designed an API, you already think in contracts, inputs, boundaries and error codes. The guide makes the same argument you would make in a code review: a uniform "Operation failed" response prevents recovery, and a caller needs to know whether an error is retryable or not.
What changes is who reads your interface. Here the caller is a model. The guide's sample question explanations in Section 9 (CCAR-F) say tool descriptions are the primary mechanism a model uses to choose between tools, so a vague description causes wrong tool selection the way a vague API spec causes integration bugs. Our write-up of an agent that retried the same error 11 times shows what happens when an error message is written for a human instead of a model. The tool design domain guide goes deeper into the domain.
Claude Code Configuration & Workflows (20%): developer tooling you'll recognize
This domain is about setting up Claude Code for a team, and it reads like a developer tooling checklist. Section 6 (CCAR-F) covers CLAUDE.md files with a hierarchy and scoping, custom slash commands and skills, path-specific rules, when to use plan mode instead of direct execution, and integrating Claude Code into CI/CD pipelines.
If you have configured linters, maintained repo conventions or built a CI pipeline, the shape of this work is familiar: shared configuration in version control, rules that apply to some files and not others, automation that runs on every pull request. What you need to learn are the specific mechanisms, such as where each configuration file lives and which one wins when they overlap. The guide's sample questions test exactly that level of detail. Our guide to writing an effective CLAUDE.md file is a practical place to start, and our Claude Code domain guide goes further into the domain.
Agentic Architecture & Orchestration (27%): orchestration you know, with a new decision-maker
This is the largest domain on the exam. Its task statements in Section 6 (CCAR-F) include designing agentic loops, orchestrating multi-agent systems with coordinator and subagent patterns, implementing multi-step workflows with enforcement and handoffs, using hooks to intercept tool calls, and managing session state, resumption and forking.
Developers who have worked on job orchestration, state machines, middleware or distributed services will find the structure familiar. A hook that intercepts a tool call is recognizably an interceptor. Session resumption is recognizably state management.
The new part is that the component making decisions is a model, and a lot of the domain is about deciding what you leave to the model and what you enforce in code. The guide's preparation exercises in Section 8 (CCAR-F) start with building an agentic loop that checks the model's stop reason to decide whether to run another tool call or return a final answer. Our article on one question type the exam uses looks at that line between an instruction and a hook, gate or schema, and the agentic architecture domain guide goes deeper.
Prompt Engineering & Structured Output (20%): the least familiar ground
This is the domain with the least direct precedent in traditional development, so plan to spend real time on it. Section 6 (CCAR-F) covers designing prompts with explicit criteria to reduce false positives, few-shot prompting for consistent output, enforcing structured output through tool use and JSON schemas, validation and retry loops, batch processing, and multi-pass review architectures.
Parts of it will feel familiar. Schema validation and retry logic are ordinary engineering. But writing review criteria precise enough that a model stops flagging false positives, or choosing the two to four examples that teach it how to handle an ambiguous case, are skills most developers haven't needed before. Our prompt engineering domain guide is the place to start.
Context Management & Reliability (15%): half familiar, half new
Section 6 (CCAR-F) covers preserving critical information across long interactions, escalation and ambiguity resolution, error propagation across multi-agent systems, context management during large codebase exploration, human review workflows with confidence calibration, and preserving the source of information when combining findings.
Error propagation and observability will feel like home. Treating the model's context window as a limited resource will not. The guide notes, for example, that models reliably process the beginning and end of long inputs but may miss findings in the middle. Deciding when an agent should hand a case to a human, instead of retrying, is also a new kind of design judgment. Our context management domain guide covers the context side of this domain.
The honest gap: hands-on time with Claude
Your development background is a foundation, not a substitute. Section 2 (CCAR-F) describes the typical candidate as having six or more months of practical experience building with the Claude APIs, the Agent SDK, Claude Code and MCP.
The good news is that the guide tells you how to close that gap. Section 8 (CCAR-F) lists hands-on preparation exercises, including building a multi-tool agent with escalation logic, building a structured data extraction pipeline, and configuring Claude Code for a team development workflow. For a developer, these are the kind of builds you can start this week, and each one covers more than one domain.
Where to start
Start by finding out which of your skills are already exam-ready. The free diagnostic on our site samples all five domains and shows where you stand. Then build: pick one of the Section 8 exercises closest to your gaps and work through it with Claude. When you're ready for full practice, our 400 practice questions cover all five domains with an explanation for every answer.
You're not starting over. You're adding Claude to a set of skills you've already spent years building.
Quick answers
Do I need to be a developer to pass the CCAR-F?
No, but it helps. Section 2 of the exam guide describes the ideal candidate as a solution architect who designs and implements production applications with Claude. Much of the exam draws on software engineering judgment, so developers start with an advantage in several domains.
Which exam domain should developers study first?
Agentic Architecture & Orchestration carries the most weight at 27%. Prompt Engineering & Structured Output has the least direct precedent in traditional development, so it's worth scheduling real study time for it early.
How much Claude experience does the exam expect?
The exam guide describes the typical candidate as having six or more months of practical experience building with the Claude APIs, the Agent SDK, Claude Code and MCP.
Is there a Claude certification aimed at developers?
Anthropic also offers a developer exam, CCDV-F. Our comparison of CCDV-F and CCAR-F sets out how the two differ.
Originally published at claudecertifiedarchitects.com, an independent exam-prep site. Not affiliated with or endorsed by Anthropic.
Top comments (0)