1:1 Mentorship

Unlock your career.

Twelve weeks, 1:1, to take you from junior to mid-level with something to show for it. Not a course, not recorded content: someone senior reading your code every week and asking why you did it that way.

I want a seat →

Send me an email and I'll reply with a time. The diagnosis is a 60-minute call, free and with no strings attached.

12 weeks45min a week3 seats per cycle
01Who it's for

You ship in the dark

The code works and you can't explain why. Copy, tweak, run it until it passes. You can live like that — you just can't grow like that.

You get stuck and stay stuck

With nobody to ask, a two-hour bug turns into three days. What's missing is a method for investigating, not effort.

You want mid-level for real

Not the title: the bar. Deciding on your own, defending the decision, and shipping something another person can maintain later.

This isn't for someone starting from zero. You already write code, and you need 6 free hours a week — actually free, not free on paper.

02How it works
1

Session zero

A 60-minute conversation to understand where you are. You leave with an honest diagnosis and a one-page plan. If I think it's not the right moment, I'll say so.

2

Anchor project

You pick a system of your own and build it across the full three months. Not twelve loose exercises: one project that grows, rots a little, and gets fixed with you inside it.

3

Weekly session

45 minutes, same day and time every week. The agenda comes from what you shipped that week — not from slides.

4

Reviews in between

I go into your PRs and comment. Stuck mid-week? An answer within 24 business hours. This is where the mentorship actually happens.

03The track

The project stays the same from start to finish. What changes each block is the bar I review it against.

W1–2

The invisible fundamentals — Git as a unit of reasoning, and a method for debugging. By the end of week 2 the project runs locally and looks ugly — as it should.

W3–6

Code someone else maintains — Names, functions, handled errors, tests. By week 6 the project is readable and tested.

W7–9

Understanding the system — What happens between the click and the database. By week 9 it's live, with a public URL and working login.

W10–12

Teamwork and positioning — Code review, working agreements, and the project documented the way you'd show it in an interview.

04Seats
December cohort

1 of 3 seats left

What's included

  • A 45min session every week, same day and time
  • Reviews on your PRs between sessions
  • An answer within 24 business hours when you're stuck
  • A written action plan, revisited every four weeks

Three seats per cohort — that's what I can take on without the quality dropping. Send me an email and we'll set up the diagnosis call.

Ready for the next step?

Send me an email telling me where you are and we'll set up the call. If it doesn't make sense for you right now, I'll be the one to say it.

I want a seat →