Teach the way you learned it — at 3 AM, with something on fire.
Devloud runs live cohorts where every lesson is a real production incident. We're looking for engineers who still operate production and want to teach it properly, without becoming a full-time trainer.
Who fits
Three things that matter more than a CV.
We've hired instructors with no teaching background and turned down people with years of it. This is what actually predicts whether a cohort goes well.
You still operate production
The teaching here is built on war stories. If you haven't been paged in two years, the incident labs won't ring true and the cohort will notice within a week.
You can be watched debugging
Sessions are live and two-way. Students share terminals and so do you — including the parts where you read the error message twice and try the wrong thing first.
You'd rather build labs than slides
Most of the prep is designing environments that break in a specific, teachable way. If that sounds more interesting than making decks, this is the right format.
The split
You teach. We run everything else.
The reason working engineers can do this alongside a job is that the operational load isn't yours.
Yours
- check_circleDesign the curriculum for your track, with our template as a starting point
- check_circleBuild the incident labs — we provide the infrastructure and the harness
- check_circleRun two or three live sessions a week for the length of the cohort
- check_circleReview assignments and answer questions in the cohort channel
- check_circleSit in on the closing game day and write the cohort's feedback
Ours
- doneThe platform — content studio, lab provisioning, live sessions, recordings
- doneCohort operations: scheduling, reminders, attendance, replays within two hours
- doneEnrolment, payments, instalments, invoicing and refunds
- doneMarketing the batch and filling the seats
- doneStudent support, so account and billing questions never reach you
The toolkit
What you get on day one.
Dashboard
Cohort health at a glance — attendance, lab pass rates, who's falling behind.
Content studio
Build modules and lessons, upload video, set what gates what.
Labs
Author and version incident labs, and see how each attempt went.
Sessions
Schedule live sessions, run the lobby, publish recordings.
Assignments
Set graded work and leave written feedback per submission.
Q&A
Answer cohort questions, publicly or privately.
Announcements
Message your batch without leaving the platform.
Earnings
Track what each cohort has earned you and when it settles.
Open tracks
Where we need instructors.
Not an exhaustive list — if you can argue engineers are being hired for something we don't teach, pitch it.
Kubernetes & Platform Engineering
CKA/CKS depth, operators, multi-cluster, GitOps
Site Reliability Engineering
SLOs, error budgets, incident command, chaos
Cloud Architecture
AWS and GCP landing zones, networking, cost architecture
AIOps & MLOps
Model serving on Kubernetes, drift detection, pipelines
How it goes
Four steps, and you can stop at any of them.
Nobody signs up to a cohort before teaching one paid session inside a live one.
Apply
Send us what you operate today, the track you'd want to teach, and anything you've taught or written before.
Technical call
Ninety minutes. We walk an incident together — you drive. It's the same thing we ask students to do.
Teach one session
A paid guest session inside a running cohort, so both sides find out whether the format fits before anyone commits.
Own a track
Scope a cohort, agree the commercial terms, and we schedule it and fill the seats.
Before you apply
How much time does a cohort actually take?add
Budget 8–10 hours a week while a cohort is running: two or three live sessions, assignment review, and time in the cohort channel. Curriculum and lab authoring is front-loaded before the batch opens and is the larger effort the first time you teach a track.
Can I do this alongside a full-time job?add
Most of our instructors do. Sessions run on weekday evenings and weekends IST for exactly that reason. What we ask is that the schedule is predictable — cohorts fail when sessions move around.
How are instructors paid?add
A per-cohort fee plus a share of enrolment revenue for the batches you run. The specific numbers depend on the track, cohort size and how much of the curriculum you author, so they're agreed in writing at offer rather than published here. Ask on the call and you'll get real figures.
Who owns the curriculum I write?add
Worth settling explicitly in your agreement — it varies with how much you author versus adapt from our template. Raise it early; we'd rather over-discuss it than have it surface later.
Do I need to have taught before?add
No. Teaching experience helps but production experience is the hard requirement — the first is coachable, the second isn't. The guest session exists so you can find out whether you enjoy it.
Can I teach something that isn't on your list?add
Yes, if you can make the case that engineers are being hired for it. Pitch it. Some of the tracks we run now started as an instructor's argument that we were missing something.
Tell us what you operate.
No CV needed to start the conversation. What you run in production, the track you'd teach, and the last incident that taught you something.