Java Engineering Track
A guided stack of modules that keeps language fundamentals, service boundaries, and verification habits in sync—without pretending every team needs microservices on day one.
Language core
Records, modules, concurrency primitives, and reading bytecode-adjacent concepts so API code stays intentional.
Service architecture
Spring Boot APIs, gateway policies when they earn their cost, and explicit boundaries between synchronous and async workflows.
Test strategy
Layered tests, contract checks, and profiling hooks that keep refactors from becoming rewrite projects.
Language core
You will not memorize APIs—you will read JDK notes, compare preview features, and justify upgrades with risk tables your manager can skim in two minutes.
Service architecture
HTTP interfaces, auth, and operational hooks are taught as a system: timeouts, idempotency keys, and dashboards that prove whether a release is safe to leave unattended overnight.
Test strategy
Tests are budgeted like any other feature: contract tests for boundaries, targeted integration slices, and profiling budgets so performance stories survive code review.