What a Claude architecture certification looks like from a Workday chair
Anthropic's most senior architect exam has seven weighted domains. Most of them describe work that enterprise Workday practitioners have been doing for years.
I passed the Claude Certified Architect, Professional (CCAR-P) on July 22, about two weeks after Anthropic opened the exam.
A few people asked how someone who spends most of his day in Workday FDM, Accounting, data and process design got there that quickly.
The honest answer: most of it was not new. The genuine additions were agentic orchestration patterns, MCP's host-client-server model, and the data structures underneath them. The rest was the same business process, architecture, and governance design work I have been doing for years.
The Credly badge lists eight core skills:
Those are genuine AI skills. Most of them are also, in a different font, the success drivers of an enterprise Workday program.
Solution Design & Enterprise Architecture
Take document intake. OCR a supplier invoice, extract the fields, match to the PO and the receipt, route the exceptions, keep the audit trail. Set the confidence threshold too high and everything lands in a human queue. Too low and you post bad data to the ledger.
Anyone who has designed supplier invoice processing in Workday has already had that argument, with the same stakeholders, about the same trade-off. The extraction engine changed. The design problem did not.
Integration Architecture
Before Workday, I lived in PeopleSoft and infrastructure: four-tier installs on Linux and Unix across multiple databases, end to end. In Workday delivery, we have been fortunate to partner with customer teams pairing Workday with AWS for finance engineering.
Data retrieval, protocol selection, auth boundaries, observability. The exact same set of engineering questions, just with different nouns.
Governance, Risk and Stakeholder Management
This is the part that surprised me. More than a quarter of a deeply technical certification covers structured discovery, communicating trade-offs, SLA management, human-in-the-loop design, and compliance. Anthropic weighted stakeholder work like a technical domain.
Which is the real point. That room is where three unglamorous things get decided:
- Finding the opportunity that is actually worth automating
- Re-engineering the business process around it
- Running the change management so an agent can safely own part of it
If you have spent years solving complex data, process, and integration problems in ERP, you are much closer to AI architecture than you think.
The CCAR-P credential is issued by Anthropic and verifiable on Credly. Exam details, domain weights, and registration are published in Anthropic's official exam guide. Read Maturecloud's related perspective on composable data access and the enterprise protocol stack.
← Back to Perspectives