The mentors
What we require of every mentor
Currently employed as a data engineer
Not a former engineer, not a full-time trainer. Someone shipping and maintaining pipelines this quarter.
Has interviewed candidates
They know what hiring managers actually test for, because they have sat on that side of the table.
Teaches from real incidents
Sessions are built around failures they debugged. Outages, bad migrations, cost blowouts, not tidy textbook examples.
Reviews work like a colleague
Assignments come back with the kind of code review a senior engineer would leave on a pull request.
Who you'll actually learn from
We publish a mentor's name, employer and photo only once they have approved it themselves.
Plenty of programmes decorate this page with logos and headshots that do not survive a reference check. We would rather show you nothing than show you something we can't stand behind. Ask on your career call and we'll tell you exactly who is teaching the next cohort, where they work, and what they will cover.
Why practitioner-led works
Current, not historical
Tooling and expectations move fast. Someone doing the job now knows what changed this quarter; someone who left five years ago does not.
Real interview standards
A mentor who runs interviews can tell you what a weak answer sounds like, and stop you giving one.
Judgement, not just syntax
Documentation teaches syntax. What it cannot teach is which architecture to pick, and what it costs you when you pick wrong.