The production-grade engineering tier of the Code Crunch academy. Nine new and redesigned specializations across cloud, mobile, distributed systems, modern AI, embedded, and robotics — each one deep, intentional, open-source, and built to take an industry-ready developer to a senior specialist.
§ I · The Idea
The first seventeen tracks of the Code Crunch academy — C1 through C17 — make a self-taught developer employable. That is the achievement of the trunk: from absolute beginner to industry-ready, in the open, in one consistent voice. Crunch Labs is what comes next. It is the academy's production-grade tier — the arc that takes an employable engineer and turns them into the senior specialist their team learns from.
Labs tracks are deeper, longer, and more demanding. They assume you can already write a CRUD app, push to GitHub, run a test suite, and read a stack trace without panic. They go where the trunk ends: distributed systems theory before you write a microservice; bare-metal and an RTOS before you write firmware for a fleet; the agent loop before you wire up a framework.
"The trunk makes you employable. Labs makes you the senior person in the room."— Crunch Labs Charter, 2026
§ II · The Two Tiers
Every Labs track inherits the trunk's editorial style, weekly cadence, and open-source license. What changes is the depth, the cadence's expectation, and the deliverable bar at the end.
Tier I · C1 — C17
Beginner to industry-ready. The trunk (C1) and twelve specializations branching off it. Most tracks are 8–15 weeks.
Tier II · C18 + (Labs)
Industry-ready to specialist. Multi-quarter, project-heavy, deploy-or-die. 15-week intensive, 24-week semester, or 48-week mastery.
§ III · Who Labs Is For
Labs is opinionated about its audience. It is not a beginner's first move — but for the right learner, it is the most direct path to senior work.
Finished C1 and one specialization. Wants the next rung — deep specialization, not another survey.
One to three years on the job. Knows their codebase well, not the field. Ready for the production-grade tier.
Has shipped product in another discipline. Wants to specialize without a master's degree or a paid bootcamp.
Already senior in title — wants the gaps filled, the theory shored up, the on-call playbook earned.
§ IV · The Tracks
Seven brand-new Labs tracks, plus the C7 redesign and the C9 resolution. Every track has its own sub-brand, its own accent, its own tooling stack — unified under Code Crunch's editorial system. Each track ships a production capstone, a chaos-drill postmortem, and a career engineering pack.
Embedded Systems & IoT Engineering
Bare-metal to fleet-scale IoT. ARM Cortex-M, ESP32, RP2040; embedded C, Rust on embedded, MicroPython; FreeRTOS and Zephyr; MQTT, BLE-Mesh, LoRaWAN, Matter; TinyML on the edge; OTA, secure boot, fleet attestation. Firmware that ships.
Zephyr · FreeRTOS · ESP-IDF · embassy-rs · KiCad · OpenOCD · MQTT · TFLite Micro
C# & .NET Engineering
Modern .NET 9 from foundations to a polyglot deploy. C# 13, async/await, LINQ, EF Core; ASP.NET Core Minimal APIs; MAUI cross-platform; Blazor; the open-source backbone of the Microsoft stack. Resolves the former C11 numbering conflict.
.NET 9 · ASP.NET Core · EF Core · MAUI · Blazor · gRPC · Polly · MediatR · xUnit
Google Cloud Engineering
Production Google Cloud from IAM up. GKE, Cloud Run, Pub/Sub, BigQuery, Spanner, Dataflow, Vertex AI; Terraform IaC; OpenTelemetry; multi-region failover; Cloud Armor at the edge. Vendor-aware, never vendor-loyal.
GKE · Pub/Sub · BigQuery · Spanner · Vertex AI · Cloud Run · Terraform · OpenTelemetry
Amazon Web Services Engineering
The largest cloud, the deepest IAM. EKS, Lambda, DynamoDB single-table, S3, EventBridge, SQS, Step Functions, SageMaker, Bedrock; CDK and OpenTofu IaC; CloudWatch + X-Ray + OpenTelemetry; multi-AZ and cross-region.
EKS · Lambda · DynamoDB · S3 · EventBridge · Step Functions · CDK · SageMaker
iOS & Apple Platform Engineering
Swift 6 and Apple platforms at production depth. Strict concurrency, SwiftUI, SwiftData, StoreKit 2, App Intents, Widgets, Live Activities; Vapor for server-side Swift; multi-platform across iOS, iPadOS, macOS, visionOS; TestFlight to App Store.
Swift 6 · SwiftUI · SwiftData · Vapor · TCA · StoreKit 2 · App Intents · CloudKit
Android Engineering
Kotlin 2.x and Jetpack Compose to staff-level Android. Coroutines + Flow throughout; Hilt, Room, WorkManager, Compose for Wear OS; KMP code-sharing; Play Integrity; macrobenchmark + Baseline Profiles. Native, modern, open-source-leaning.
Kotlin 2 · Jetpack Compose · Coroutines · Hilt · Room · WorkManager · KMP · Wear OS
Microservices & Distributed Systems
From CAP and Raft to a polyglot multi-region system. gRPC + Protobuf, Kafka + NATS, Temporal, Istio / Linkerd; OpenTelemetry deep; SLI/SLO and error budgets; sagas; multi-region active-active; chaos engineering. Theory before tools, always.
gRPC · Protobuf · Kafka · Istio · Temporal · Postgres · OpenTelemetry · Kubernetes
AI Agent Systems Engineering
The modern AI engineering track. The agent loop, RAG done as engineering, memory systems, multi-agent orchestration; local inference on Ollama, vLLM, and NVIDIA NeMo; MCP servers; open-Claude-compatible (OpenClaw) runtimes; evaluation, safety, cost engineering. Distinct from C5.
LangGraph · Mastra · MCP · Ollama · vLLM · NeMo · Qdrant · LiteLLM · Langfuse · Ragas
Intelligent Robotics & Autonomy
A full year of robotics. ROS2, Gazebo / Isaac Sim, Nav2, MoveIt2; sensor fusion (IMU + LiDAR + depth); SLAM; learned policies (Diffusion Policy, ACT, OpenVLA); sim-to-real; language-conditioned manipulation; safety case construction. The mastery track.
ROS2 · Gazebo · Nav2 · MoveIt2 · OpenCV · Open3D · CUDA · Jetson · Isaac Sim · GTSAM
§ V · Pathways
Each pathway names the role it lands in. Pick a destination, follow the arrows. C1 is the prerequisite for every pathway.
C1 → C15 (DevOps) → C18 (GCP) or C19 (AWS) → C22 (Mesh)
~18 months post-C1. Lands at: cloud platform engineer, senior SRE, or platform architect on a small infra team.
C1 → C8 (Web) → C20 (Swift) or C21 (Droid)
~12 months post-C1. Lands at: senior iOS or Android engineer. Take both Labs tracks for cross-platform mobile leadership.
C1 → C5 (AI/DS) → C17 (Pro Python) → C23 (Agents)
~14 months post-C1. Lands at: applied AI engineer, agentic systems engineer, or LLM platform engineer at an AI-first company.
C1 → C7 (Wire) → C24 (Robotics)
~24 months post-C1. The mastery pathway. Lands at: robotics software engineer, autonomy engineer at an early-stage robotics company.
C1 → C16 (Pro Backend) → C15 (DevOps) → C22 (Mesh)
~15 months post-C1. Lands at: principal backend engineer, staff platform engineer, or distributed systems lead.
C1 → C14 (Linux) → C7 (Wire) (+ C18 or C19 for cloud edge)
~16 months post-C1. Lands at: embedded firmware engineer, IoT platform engineer, or edge-compute architect.
§ VI · The Quality Bar
Beyond the trunk's standards (syllabus, README, license, weekly content, working code), every Labs track meets three additional requirements before its status moves to ✅ Complete.
A track-specific design rationale: why these topics, why this order, why these tools. Every choice has a paragraph of justification.
One substantial, public, deployed system that exercises every phase. Architecture diagram. Live deploy URL. Five-minute video walkthrough. Chaos-drill postmortem.
Discipline-specific interview prep (system design + technical drills), a production on-call runbook, and a portfolio guide for three polished projects.
Where an open-source equivalent exists, we teach it first. Vendor tools are taught as the production scale path, never as the only path.
The same EB Garamond display, Ink/Parchment/Gold palette, and weekly cadence the trunk uses. Sub-brand accents tint; they never replace.
Every Labs track is GPL-3.0 — same as the trunk. Fork it, teach it, remix it. If you improve it, send the PR back so the next learner benefits.
Read the full Crunch Labs Charter for governance, naming, and sub-brand reservations.
§ VII · Getting Started
Crunch Labs is opinionated about its entry point. Before you pick a track, answer two questions for yourself.
# 1. Have you completed C1 (or have equivalent ~540 hrs of Python)? # If no — start with C1 first. Labs assumes the trunk's foundations. → /courses/codecrunch-convos # 2. Which destination are you working toward? # Pick a Pathway above (A–F) and follow the arrows. # Each track lists its specific prerequisites in its README. # 3. Once you've chosen, clone the curriculum and begin Week 1. git clone https://github.com/CODE-CRUNCH-WORLDWIDE/C<N>-<TRACK>.git cd C<N>-<TRACK> $EDITOR SYLLABUS.md # the table of contents $EDITOR week-01/README.md # begin
New to the academy? Start at C1 — Code Crunch Convos. Already past C1? Pick a Pathway.
§ VIII · Begin
Nine tracks. One open-source license. The same patient editorial voice the trunk has carried since 2024.