Hiring certified engineers
Architect vs Developer staffing on a Claude engagement
Developer-certified engineers build the tools and agents. Architect-certified engineers decide what must not be built. Here is how we staff both so you do not get a clever system nobody can govern.
June 8, 2026/3 min read/Claude Certified Engineers
Staffing a Claude project as "an AI person" is how you get a Developer-shaped system with no Architect-shaped constraints. The exams split the work on purpose. We staff the same split.
Developer Foundations is the person who can implement tool use, MCP servers, prompt caching, and Claude Code workflow without turning your repo into a science fair.
Architect Foundations is the person who designs the whole solution: eval, budgets, guardrails, human queues, environments, and the story InfoSec will accept.
Architect Professional is the person who can lead that design across multiple teams and surfaces (API, Bedrock, Vertex, desktop, Claude Code).
Associate still matters. It is responsible daily use. We require it. It is not sufficient to own production tools.
What goes wrong when you skip Architect review
A Developer-certified engineer, unsupervised, will usually ship something that works in a happy-path transcript. That is not nothing. The failures show up as:
- An MCP server that is a remote shell with a friendly name.
- An eval suite that scores prose and misses tool contracts.
- A six-week plan that is actually four agents and a platform.
- Cost that cannot be forecast because caching was never a design input.
Architect review is the habit of cutting scope and naming the irreversible tools. On this bench, every engagement has at least one Architect-level engineer, and a second certified reviewer on the code. Not whoever was idle.
That is also why we do not list names. Engineers sit in client repos under NDA. You meet the assigned people in scoping. You get roles, specialisms, and cert levels on the site.
How we match the ticket to the cert
| Problem you named | Primary cert on the work | Architect still reviews |
|---|---|---|
| Tool schemas, MCP adapter, Salesforce/SAP verbs | Developer | Yes. Especially execute vs draft. |
| Eval harness, judges, CI gates | Architect (eval lead) | Yes. Thresholds are a product decision. |
| Prompt injection, PII, review queues | Architect (security) | Yes. |
| CLAUDE.md, first PR, enablement | Developer (coach) | Yes. So enablement is not a workshop. |
| Six-week production outcome | Developer on the impl, Architect on the brief | Always. |
Audit vs build vs embedded does not change this. A two-week audit without Architect review is a lint pass. A build without it is a demo with better lighting. Embedded without it is a contractor who will say yes.
Enable your Developers. Still staff Architect review.
Certification Enablement takes your engineers through Associate, Developer, and Architect using your repo. That is the right long-term move. It does not mean a brand-new Developer-certified teammate should own production design in week one.
Hire for the filter, then put Architect-level review on the brief, the tool list, and the eval thresholds. Developer-certified people should write most of the code. Architect-certified people should be allowed to delete tools from the spec. If nobody in the room can delete a tool, you do not have architecture. You have a backlog.
Questions
- What is the difference between Claude Developer and Architect certification?
- Developer covers building on the platform: API, tool use, MCP, caching, and agentic workflows. Architect covers designing the whole solution. Professional covers leading enterprise rollouts across teams and deployment surfaces.
- Do we need an Architect-certified engineer for a six-week build?
- Yes, at least on review. A Developer-only team will ship tools. An Architect-level reviewer asks whether those tools should exist, what the eval gate is, and who inherits the system.
- How is an engagement staffed?
- With the specialist the problem needs (agents, MCP, eval, security, enablement), plus a second certified reviewer. You meet the specific engineer during scoping. We do not publish names.