Claude Certification Tracks: A Complete Guide to the 4-Track Curriculum

The rohitg00/ai-engineering-from-scratch repository offers four distinct Claude certification tracks—Developer Foundations, Architect Foundations, Architect Professional, and Associate Foundations—each defined by JSON metadata that drives a unified, data-driven curriculum engine.

This open-source certification program provides role-based pathways for professionals validating their Claude expertise. All track definitions reside in certifications/claude/tracks/*.json, utilizing a standardized schema that powers automated lesson sequencing, domain-weighted exam scoring, and consistent assessment pipelines across all certification levels.

The Four Claude Certification Tracks Offered

The curriculum defines four specialized tracks targeting distinct expertise levels and professional roles. Each track is identified by a unique slug and stored in a dedicated JSON file under the tracks directory.

Developer Foundations (ccdv-f)

Defined in certifications/claude/tracks/ccdv-f.json, the Claude Certified Developer – Foundations track targets builders who need to construct production-grade Claude applications. The credential focuses on the complete development lifecycle: building, integrating, securing, testing, and shipping Claude applications, agents, workflows, tools, and MCP servers.

Architect Foundations (ccar-f)

The Claude Certified Architect – Foundations track (ccar-f) is designed for technical decision-makers. According to the source metadata, this certification validates the ability to "make sound production tradeoffs across Claude Code, the Claude Agent SDK, the Claude API, and MCP." This foundational architect track emphasizes cross-platform integration decisions rather than deep implementation details.

Architect Professional (ccar-p)

Stored in certifications/claude/tracks/ccar-p.json, the Claude Certified Architect – Professional track represents the advanced tier for systems architects. The certification encompasses the full lifecycle of "secure, observable, production-grade Claude systems from discovery to iteration." This track demands mastery of enterprise deployment patterns, observability strategies, and iterative improvement methodologies.

Associate Foundations (ccao-f)

The Claude Certified Associate – Foundations track (ccao-f) serves non-developer professionals who utilize Claude for business and research workflows. The metadata specifies this track validates the ability to "use Claude safely and effectively for business, research, analysis, and productivity workflows," emphasizing safe usage patterns rather than technical implementation.

Certification Track Schema and Architecture

Each track JSON follows a rigid common schema that enables the curriculum engine to generate uniform UI experiences while preserving role-specific content. The architecture enforces separation between data and presentation logic.

Core Metadata Fields

Every track file contains standardized identification fields:

• id / slug – Unique identifiers used in URL routing and internal references (e.g., ccdv-f)
• credential – The human-readable certification name displayed on certificates
• shortName – Concise UI label (e.g., "Developer Foundations")
• level – Technical tier classification (e.g., "Foundational technical")
• summary – One-sentence description used in catalog listings and search metadata

Domain Weighting and Learning Objectives

The domains array drives exam construction and lesson prioritization. Each domain object contains:

• id and name – Domain identification
• weight – Percentage contribution to final scoring (e.g., agents-workflows ≈ 14.7% for Developer Foundations)
• objectives – List of specific learning outcomes

This modular weighting system ensures proportional emphasis across technical areas, with the curriculum engine calculating exam composition directly from these weights.

Unified Assessment Pipeline

All tracks share identical assessment architecture through the assessments array, which enforces a consistent diagnostic + mock structure. This unified contract allows the CI system to generate tests automatically across all four tracks without hard-coded exceptions. The schema also includes studyPlans (pre-crafted schedules such as 21-day intensive plans) and deepDives (optional phase lesson references for extended study).

Loading Track Metadata Programmatically

Because the curriculum is entirely data-driven, you can consume track definitions directly from the JSON files. Below is a Python implementation that loads track metadata, extracts the credential name, and enumerates domain objectives:

import json
from pathlib import Path

def load_track(slug: str) -> dict:
    """Load a certification track JSON file from the repo."""
    path = Path(__file__).parent / "certifications" / "claude" / "tracks" / f"{slug}.json"
    with path.open(encoding="utf-8") as f:
        return json.load(f)

track = load_track("ccdv-f")  # Change to ccar-f, ccar-p, or ccao-f as needed

print(f"Credential: {track['credential']}")
print("Domains and objectives:")
for d in track["domains"]:
    print(f"- {d['name']} ({d['weight']}%):")
    for obj in d["objectives"]:
        print(f"  • {obj}")

This script enables CLI tooling, dashboard generation, or automated validation of curriculum completeness. The lessons array within each track references paths under certifications/claude/lessons/, while assessments link to certifications/claude/assessments/, creating a fully navigable content graph.

Summary

• Four distinct tracks serve specific roles: Developer Foundations (ccdv-f), Architect Foundations (ccar-f), Architect Professional (ccar-p), and Associate Foundations (ccao-f).
• JSON-driven architecture in certifications/claude/tracks/*.json eliminates hard-coded logic, allowing the curriculum engine to generate UI and exams from data.
• Domain weighting system ensures exam questions proportionally reflect learning objectives, with weights defined in the domains array of each track file.
• Unified assessment contracts enforce consistent diagnostic and mock exam structures across all certifications, simplifying CI generation and test maintenance.

Frequently Asked Questions

What are the four Claude certification tracks available in the repository?

The repository defines four tracks: Developer Foundations (ccdv-f) for application builders, Architect Foundations (ccar-f) for technical decision-making, Architect Professional (ccar-p) for production system ownership, and Associate Foundations (ccao-f) for business and research professionals. Each targets a distinct expertise level, from basic safe usage to professional-grade system architecture.

How does the curriculum weight different technical domains across tracks?

Each track's domains array assigns a specific weight percentage to technical areas (e.g., agents-workflows, security, MCP integration). These weights drive both lesson sequencing and final exam scoring, ensuring proportional emphasis aligns with role requirements. The Architect Professional track, for instance, weights full-lifecycle system ownership more heavily than the foundational track.

Where are the certification track definitions stored in the codebase?

Track metadata lives in certifications/claude/tracks/ with four primary JSON files: ccdv-f.json (Developer), ccar-f.json (Architect Foundations), ccar-p.json (Architect Professional), and ccao-f.json (Associate). These files cross-reference lesson content in certifications/claude/lessons/ and assessments in certifications/claude/assessments/.

Can I programmatically extract certification requirements without hard-coding track details?

Yes. Because the curriculum uses a data-driven JSON schema, you can load any track definition using standard file I/O operations on the track files. The Python example in the section above demonstrates loading slugs, credentials, and domain objectives directly from the repository structure, enabling automated curriculum dashboards or custom study plan generators.

{
  "mcpServers": {
    "instagit": {
      "command": "npx",
      "args": ["-y", "instagit@latest"]
    }
  }
}