Skip to content

Engineering Team Onboarding System

Most engineering teams have no shared definition of “knows Git”. People arrive with wildly different models, the gaps only surface during an incident, and onboarding is a link to some documentation and a hope.

This is the programme and the paperwork to fix that.

  • One Git workflow, written down. A standards document the team has agreed to, instead of eight private conventions.
  • Faster onboarding. A new engineer follows four weeks of sequenced reading, labs and checkpoints rather than absorbing habits by osmosis.
  • Fewer Git incidents. The programme’s week 1 and 2 are the recovery and branching material that prevents the force-push-to-main class of problem.
  • Better pull requests. Week 3 is review practice, CODEOWNERS and the rules a pull request must satisfy.
  • GitHub governance you can audit. Repository governance and CI/CD standards checklists that say what is required and why.
  • Security practice as a default. Week 4 covers least-privilege tokens, secrets, and the workflow patterns that cause incidents.

Ten team files, plus the Professional Toolkit’s twenty-four for every engineer.

  • 30-day programme — four weeks (the model; working on a branch; working with the team; CI/CD and security), each with reading, a lab and a checkpoint the learner and manager both see. Ends with guidance on adapting it.
  • Skills assessment — 19 skills across six areas at three levels, as a CSV
  • Scoring guide — how to run it, the levels, reading the results, turning gaps into a plan, and what not to do with the results
  • Git standards template — branching, commits, pull requests, merging, rebasing, protected branches, secrets and an exceptions process; adapt and adopt
  • Repository governance checklist
  • CI/CD standards checklist
  • Onboarding completion checklist
  • Manager checklist — before day 1, each of the four weeks, end of programme, and the things that go wrong
  • Learner checklist — the engineer’s own copy

Every team tier includes the toolkit — the CODEOWNERS, pull request and issue templates, five workflow templates, decision guides and repository checklists the programme’s weeks refer to.

Editable throughout: Markdown for documents, CSV for the assessment, YAML for workflow templates. Nothing is locked to a proprietary format, and everything is intended to be adapted to your organisation rather than adopted verbatim.

Before buying, find out where your team stands. The Git & GitHub Team Readiness Assessment is twelve questions, takes five minutes, scores in your browser and points at the lessons that address each gap.

Small Team

$499one-time

Up to 10 engineers.

  • The Professional Toolkit for every engineer
  • 30-day onboarding curriculum with weekly checkpoints
  • 19-skill team assessment (CSV) with scoring guide
  • Git standards template: branching, commits, PRs, merging, secrets
  • Repository governance, CI/CD standards and completion checklists
  • Week-by-week manager checklist and learner checklist

Up to 10 engineers in one organisation.

Get Small Team

Enterprise

Contact us

Organisation-wide licensing.

  • Everything in Engineering Team
  • Organisation-wide internal distribution
  • Terms and invoicing agreed directly

Organisation-wide. Terms agreed directly.

Enquire about Enterprise

Payment is through the checkout provider’s hosted page; the receipt and download link arrive by email, usually within minutes. The download is one archive with the ten team files and the toolkit. First week: the manager reads manager/manager-checklist.md (“Before day 1”), runs the skills assessment with the team, and picks the start date. The 30-day programme begins from there. Questions about running it: contact us.

More than 50 engineers, or several teams? Enterprise licensing is agreed directly.

Not a training service. There is no instructor, no live session and no support contract. It is a programme you run yourself.

Not a certification. Nothing here issues a credential, and the completion checklist is an internal tool, not an accreditation.

Not a replacement for the free curriculum. It sequences and supplements it.

The whole curriculum, all the labs and the learning paths are free and complete. Run a team through a learning path first. If that works for you and the missing piece is structure, assessment and standards documents, this is that piece. If it does not work for you, this will not fix it.

Frequently asked questions

How is this different from the Professional Toolkit?
The toolkit is files for one engineer — templates and checklists to drop into repositories. This is a programme for a group: a four-week curriculum, an assessment to find where each person actually is, a standards document the team agrees to, and the checklists a manager runs it with. Every team tier includes the toolkit.
Is there an instructor, live session or support contract?
No. It is a programme you run yourself, built on the free lessons and labs. The manager checklist is the run-book.
What does the assessment measure?
Nineteen skills across six areas — Git model, branching, pull requests, GitHub, CI/CD and security — each at three levels. The scoring guide explains how to run it fairly, how to read the results and how to turn gaps into a plan. It is a CSV, so it drops into a spreadsheet.
How is it licensed?
By organisation and seat count: Small Team covers up to 10 engineers, Engineering Team up to 50. The Engineering Team tier includes editable source so the standards document can become your internal document. Larger organisations are handled on enquiry.
Can we see the material before buying?
The curriculum sequences the free learning paths and labs, so the substance is all public. The team readiness assessment is a free, shorter version of the skills assessment's approach. What you cannot see beforehand is the standards template and the manager checklists.
What is the refund policy?
Refund terms are stated in the Terms and at checkout.