📒 problems 📖 glossary
Mock interview
46:30
ready
of 46:30
Lesson 1 · Start

A SWE interview guide built around how you actually study.

You're the kind of person who builds a mock-interview app instead of buying a course. This guide matches that. It's structured as a learning path — 108 short lessons, each ~3–10 minutes, with a quick quiz at the end. Read any lesson, then pass quizzes in order to advance your progress. Every pattern ties to a problem in your SoloMock bank — and the pattern lessons now drop you straight into a runnable code editor that grades your solution in the browser.

This guide assumes you can already write basic Python — variables, loops, functions, lists and dicts, and reading an error message. Never written a line of code? Start with the dedicated Programming Basics guide first — it teaches programming from absolute zero, in Python — then come back here. From this guide's first lesson onward, the path takes you from comfortable-with-Python to ready to land and hold your own in a junior software-engineering job.

It goes past the interview, too: a full Engineering craft phase covers the actual job — team git, CI/CD, containers, cloud, observability/SRE, distributed systems, caching, message queues, data modeling, auth/security, and software design — so you leave knowing how the code you ship actually runs in production.

Lessons
108
17 phases · ~3-10 min each
Quizzes
101
Threshold shown per quiz · retake anytime
Final boss
20 Qs
need 16 to clear
Everything saves to your browser — progress, quiz scores, notes, mastery on each SoloMock problem. Top-right gives you a mock-interview timer with phase coaching, plus your problem tracker and glossary.

How to use this: don't skip the framework lesson next — it's the loop that every later pattern hangs off. After that you're in pattern territory. Read ahead whenever you like; each passed quiz unlocks the next assessment.

Everything is taught here, in full — you never have to leave the site to learn. Lessons that go deeper link to a companion lesson inside the guide ("→ Going deeper"); the only outside links are the occasional optional "Go deeper (optional)" reference at the end of a lesson, never something you need to follow to keep up.