Skip to content

Start Here — Simple Enough Onboarding

Welcome. This is your onboarding: a guided path from new joiner to a placeable DevOps junior — someone with real foundations who can defend their work to a stranger (interview-ready) and has a portfolio to show for it. It's ≈ 2–3 weeks, and you do real work from the first tool module on.

How it works (read once)

  • One path, one rhythm. The course is an ordered list of modules — see the catalogue. Every module is the same five beats: Learn → Pair → Do → Prove → Retain. You learn the rhythm once; only the topic changes.
  • Your tutor is an agent. Open Claude Code in this repo and drive the onboarding-tutor skill — it explains, pairs, quizzes you, and runs the gate. It coaches; it never does the exercise for you.
  • You must defend your work. Every module ends at a Socratic gate: explain what you built, why, what breaks, and which parts the agent wrote + how you verified them. "It works but I can't say why" does not pass — that's the point, and it's exactly how a technical interview probes you.
  • Gated progression. The next module unlocks only when you've passed the current gate.

Your first hour

  1. Do Setup & ways of working — it walks you through cloning the repo, setting your own git identity, installing Claude Code, and installing Anki (your flashcards auto-import on every git pull).
  2. Track yourself as you go: click Mark this module complete at the top of a module page once you pass its gate. The roadmap shows your live progress and a "Next up" pointer to what's next.
  3. Go to step 1 in the catalogue and work straight down.

The finish line

The last two steps are your placement arc: - Capstone — ship a real, curated ticket end to end and defend every choice, then assemble a portfolio (the capstone PR + your gate-logs + deck mastery). - Interview & Placement — rehearse defending it out loud.

Passing the capstone = onboarded. Your portfolio is what Simple Enough shows a client.

Getting help

  • The tutor first — it's always on, inside Claude Code.
  • Your mentor for the capstone gate and anything the tutor can't resolve.
  • If the material is wrong or unclear, say so. Every cohort improves the course by design — the gate-log's "weak spots" line is how that feedback gets captured.