What we teach

Relevant, cutting-edge skills that address the needs of today's work environments

The world has changed and has never been so reliant on technical tools as it is today. Here is everything we teach, how each module is assessed, and the evidence a mentee walks away with.

Research & Exploration

Six tracks, taught against what the work actually requires

With BTMP we focus on teaching relevant, cutting edge skills. Choose a track to see its modules and the evidence it produces.

Hardware & Software Training

Systems fundamentals, Linux, networking, version control, two programming languages and the deployment pipeline that turns code into a running service.

Modules

  • Linux and shell fluency
  • Git, code review, CI/CD
  • Python and one compiled language
  • Databases and API design
  • Observability and on-call basics
Hardware & Software Training

Evidence produced

A deployed service with CI, tests and an on-call runbook.

How we assess

Four kinds of assessment, none of them a multiple-choice quiz

We grade what a person can demonstrate. That means more work for facilitators and more discomfort for mentees, and it is the only approach that survives contact with a real hiring loop.

TypeCadenceWhat it is
FormativeWeeklyExercises marked by the facilitator with written feedback within 48 hours. Not scored — the purpose is direction, not ranking.
Lab reviewFortnightlyYour cohort and a working engineer review each other's work against a published rubric. Everyone presents; everyone critiques.
CapstoneEnd of trackA substantial piece of work graded against the same criteria hiring teams use. Pass, revise-and-resubmit, or not yet.
Portfolio defenceBefore PipelinesA forty-minute oral defence of everything you built. This is the closest thing to the real interview loop.
Isometric layered board illustration

Credit for what you already know

Career changers can skip modules by passing the assessment cold. We would rather you spent your six hours a week on the gap than on revision.

Beyond the track

Soft skills are not soft

Every track carries the Pioneer Development strand: writing, estimation, feedback, conflict and negotiation. These are the skills that decide whether technical ability turns into influence.

Technical writing

Design documents, incident reports and the one-page summary a director will actually read.

Estimation

Breaking work down, sizing honestly, and saying the uncomfortable number out loud.

Feedback & conflict

Giving and receiving critique in code review without it becoming personal.

Negotiation

Compensation, scope and deadlines. Practised in role-play before it matters.

Entrepreneurial thinking

Spotting a market gap, sizing it, and deciding whether it is worth your next two years.

Working in public

Open source contribution, conference proposals and the discipline of being visible.

Found the track you want?

Applications take fifteen minutes and there is no entrance exam.