Back to the journal
Career Jun 28, 2026 · 8 min

From tutorial to paycheck: the 90-day rewire

The three feedback loops we use to turn beginners into billable engineers — proposals, portfolios, and pull requests.

CT

Cohort Team

Mandola AI

Most career-switching engineers make the same mistake: they complete tutorials, then wonder why no one's hiring them. The gap isn't technical skill — it's the absence of proof that you can deliver value to a real person.

Our 90-day program is built around three feedback loops that close this gap systematically.

Feedback loop 1: Proposals

In week two, every cohort member writes a proposal for a real project. Not a toy project. Not a tutorial rehash. A real problem that a real person needs solved. This forces you to learn scoping, communication, and pricing before you write a line of code.

The proposals get reviewed by the cohort and the instructors. Most first drafts are terrible. That's the point. You learn more from a bad proposal reviewed by experienced people than from ten tutorials.

Feedback loop 2: Portfolios

By week six, you need a portfolio that demonstrates three things: you can write clean code, you can solve real problems, and you can communicate your decisions. Not a GitHub profile with 50 green squares. A curated collection of three to five projects that tell a story.

Each portfolio piece comes with a write-up: what the problem was, what you tried, what worked, and what you'd do differently. This is the artifact that gets you interviews.

Feedback loop 3: Pull requests

In the final eight weeks, you contribute to real codebases. Not open-source toy projects. Real systems with real users, real bugs, and real constraints. You submit pull requests, get code reviews, and learn what production code actually looks like.

This is where the transformation happens. The gap between "I can follow a tutorial" and "I can deliver value to a client" closes when you're working on code that matters.

The 90-day timeline

Days 1-30: Foundation. Environment setup, debugging skills, testing fundamentals. Days 31-60: Application. Building real projects, writing proposals, developing your portfolio. Days 61-90: Delivery. Contributing to real codebases, preparing for interviews, building your professional network.

It's not easy. It's not supposed to be. But it works.

Continue reading

Want to go deeper?

Join the next Mandola cohort.

Small groups. Weekly live sessions. Code reviews from engineers who ship Python for a living. Applications open on a rolling basis.