Curriculum detail

Modules, weekly time, and capstone work

Software Engineering

Modules that mirror a working codebase

Modules move from version control and testing into APIs, databases, and deployment. Learners typically commit about 15 hours per week, with live working sessions alongside independent build time. The capstone is a team-built application with a documented API, test coverage, and a deployed release.

Data

Modules built around real questions

Modules cover data cleaning, exploratory analysis, statistical modeling, and reporting. Learners typically commit about 14 hours per week across guided labs and project reviews. The capstone is an end-to-end analysis with a reproducible notebook, a written findings memo, and a short presentation to a reviewer.

Systems

Modules that follow the infrastructure lifecycle

Modules cover networking, Linux administration, containers, and monitoring. Learners typically commit about 16 hours per week, mixing hands-on lab environments with incident walkthroughs. The capstone is a provisioned service with defined alerts, a runbook, and a recorded failure-recovery exercise.

How learning progresses

Four phases from fundamentals to team review

01

Foundational concepts

Learners start with the core ideas and tools for their track, practicing each concept in short guided exercises before moving on.

02

Guided build work

Small projects apply those skills to realistic tasks, with instructors reviewing progress and pointing out common mistakes early.

03

Independent project

Learners design and complete a larger piece of work on their own, documenting decisions the way a working team would expect.

04

Supervised team code review

Teams review each other's work under instructor supervision, learning to give and receive feedback against the same rubrics hiring teams use.