Skip to content
devopssyscourse.org

/cohorts · developer · devops · security · sysadmin

We form the cohort first. Then we build the course.

We form small cohorts of developers, DevOps engineers, security engineers and system administrators with the same goal, then write the course plan and assemble the mentor team for that group.

cohort size
6–12 people
length
8–16 weeks
mentors
2–4 practitioners
cohort/devops-2026-11forming

$ cohort init --track devops --level working

  1. >collecting applications11/12
  2. >profiling skills9/11
  3. >forming cohort8 matched · level: working
  4. >drafting course planv0.3 · in cohort review
  5. >assembling mentor team2/3
  6. >start dateset when the plan is final

$

What forming a cohort looks like. Each step is explained below.
tracks

For people entering the field, and for people already in it.

Every track has entry levels for both. What matters is that the people in a cohort share a target. Background can differ; the goal cannot.

Starting out

You want a first role in one of these fields and need the skills, the proof and the vocabulary.

  • Helpdesk and support engineers moving to systems or DevOps
  • Career switchers with some code behind them, no team experience yet
  • Windows administrators adding Linux and automation
  • Analysts, testers and IT generalists moving into engineering

Going deeper

You already do this at work and want to close the gaps you can feel, or move to the next role.

  • Developers who inherited the pipeline, the cluster or the on-call
  • DevOps engineers moving toward platform engineering and SRE
  • Sysadmins taking the environment to hybrid cloud
  • Engineers who own security without a security team

Not sure which group you are in? Apply anyway. The profiling call exists for exactly that.

how-it-works

How a cohort comes together

Six steps, in this order. Nothing is charged until step four is done and you have seen the plan and the price.

  1. 01

    Apply

    5 minutes

    Tell us where you are, where you want to get to and when you can study. No CV required, no test.

  2. 02

    Profile

    30-minute call + a short practical

    A conversation with a mentor and a short hands-on exercise, so we know your real level, not the one on paper.

  3. 03

    Cohort forms

    typically 2–6 weeks

    We group 6–12 people with the same target, a compatible level and a schedule that works for everyone.

  4. 04

    Course plan

    1–2 weeks

    Written for this cohort: modules, labs, weekly rhythm, capstone and the tools your target employers actually use.

  5. 05

    Mentor team

    in parallel with the plan

    Two to four practitioners matched to the plan: a lead mentor, a lab mentor and guest practitioners for specific modules.

  6. 06

    Run

    8–16 weeks

    Two live sessions a week, labs on real infrastructure, weekly mentor hours and a capstone you present at the end.

how-it-works

The shape of a cohort

size
6–12 people with the same target
length
8–16 weeks, fixed when the plan is final
weekly load
6–10 hours including labs
sessions
2 live sessions a week, plus a mentor hour
format
Live online sessions, labs on real infrastructure and weekly mentor hours. On-site delivery can be arranged for company teams.
language
English
mentors
2–4 practitioners per cohort: lead, lab, guests
price
Quoted per cohort after profiling. It depends on the track, the length and the mentor team. You see the price before you commit to anything.
next intake
Cohorts are forming now for all four tracks.
mentors

Mentors are practitioners, assembled per cohort.

We do not keep full-time trainers. When a plan is final we match it with people who do that work today: a lead mentor who owns the sessions, a lab mentor for hands-on hours and guests for the specialist modules. Mentors are paid per cohort.

for-teams

Training a whole team on your own stack.

A company team is a cohort that already exists. We profile the team, write the plan against your actual systems and migration goals, and run it with your tooling. Capstones ship something you needed anyway.

faq

Questions people ask before applying

Do I need experience to apply?

No. Each track has an entry level for people with little or no professional experience in that area. What you need is a clear goal and the time to study. The profiling call tells both of us whether a cohort is the right next step for you now.

Is this a bootcamp?

No. A bootcamp runs the same curriculum for whoever signs up. We form the group first, then write the plan for that group and assemble mentors for that plan. Cohorts are 6–12 people, not 60.

How long until my cohort starts?

Typically 2–6 weeks after profiling, depending on how many people with a compatible target and schedule are in the queue. If no suitable cohort is forming, we tell you the expected wait rather than putting you in the wrong group.

What does it cost?

The price is quoted per cohort once the plan is final, because it depends on the track, the length and the mentor team. You see the price and the full plan before you commit. There is no fee for applying or profiling.

How much time does it take each week?

Plan for 6–10 hours a week: two live sessions, labs and a weekly mentor hour. Cohorts run 8–16 weeks depending on the plan.

Is it online or in person?

Live online by default, so a cohort can include people from different cities. Company teams can have sessions on site by arrangement.

Something else? Ask us directly.

Tell us where you want to get to.

Applying takes five minutes. Profiling is free and you keep the skills map. The cohort, the plan and the price come before any commitment.

Cohorts are forming now for all four tracks. We reply within two working days.