From Junior to a strong Mid-Level .NET engineer — through practical learning, weekly sessions, and real code reviews.
An event ticketing API built the way a junior builds it: auth with refresh token rotation, events and ticket tiers, a booking module with real transactions and optimistic concurrency, mock payments and email. Large services, no tests, no caching — deliberately, because you need to feel the pain before the fix means anything.
Same repository, better code. The 200-line BookingService splits into single-responsibility pieces, event search moves behind a Specification, test coverage passes 70%, and every unhandled error goes through one global handler with structured logs you can search in Seq.
A full reorganization into Domain, Application, Infrastructure and API, with a rich domain model, CQRS through MediatR pipeline behaviours, Redis cache-aside on event availability, and the whole stack — API, database, Redis and Seq — running from one docker-compose up.
A written audit of your own project against a checklist: double-booking impossible under race conditions, no N+1 on any endpoint, every non-public endpoint authenticated, a full booking traceable in Seq, no secrets committed. Real numbers, and the fixes you applied after finding them.
Biweekly calls to unblock you, review your direction, and keep momentum going.
Real feedback on your project code — the same standard used in production reviews.
A group of other students at the same stage, for accountability and questions.
Pounds are for students paying from inside Egypt. If you are paying from outside Egypt, the dollar price applies.
Engineers with at least six months of real experience — internship, full-time or freelance — who can already write a working ASP.NET Core API and have used SQL or EF Core. It is not a course for learning to program from scratch.
Five to seven hours: one live session plus the assignment that follows it. Assignments are graded against a written checklist, so the time goes into building rather than watching.
A live session at the start of the week — explanation plus live coding — then the assignment during the week, then a written code review within 48 hours of submission. The next session opens by revisiting the two or three mistakes that came up most across the group.
No — one project, TicketFlow, from the first week to the last. Months 1–2 you build it as plain N-Layer, months 3–4 you refactor it, months 5–6 you rebuild it as a modular monolith. The git history is the evidence of what changed, and it is what you show in an interview.
No. Months 1–6 are what get you to Mid-Level. Month 7 is 120 interview questions across four simulation sessions, for anyone preparing to interview soon.
Every session is recorded and the recording stays available to you. The commitment is to watch it within the same week, so the assignment still lands on time.
Once you complete the onboarding process and decide to continue with the mentorship, the payment becomes non-refundable. No refunds will be issued after onboarding.
Yes. You can split the total payment into two installments, paid over the first two months of the mentorship.