mentorOS finds what you can actually do, assigns missions that close the gaps, and checks weeks later that it stuck.
Free while it's new.
Hi, I'm Pip.
I'll find out what you already know, then hand you real work to prove the rest.
Each step climbs on the one before it. Nothing moves until there's evidence that it should.
1. Assess
A diagnostic with real questions: code to read, bugs to find, scenarios to reason through.
2. Plan
A short path where every step says why it is there.
3. Build
Missions instead of lessons. You make something and hand it in.
4. Evaluate
What you did well, what needs work, the idea behind it, and what to do next.
5. Adapt
Your skill estimates move with the evidence, and so does your next mission.
6. Recheck
Weeks later, an unannounced question finds out whether it stuck.
A percentage means nothing on its own. Each estimate keeps the answers, missions and checks that moved it, and says how sure it is. When the evidence is thin, Pip says not yet, and shows you where to start.
SQL
Intermediate, medium confidence
sql Knowledge check on indexes: pass
+0.05sql Surprise check on isolation levels: missed
−0.06sql Mission, schema for a task app: partial
+0.04sql Diagnostic, JOIN scenario: strong
+0.12Not yet.
Caching builds on HTTP, and your HTTP evidence is still thin: two checks, both partial. Start there.
Instead of chapter four, you get something to make, a reason it is next, and the criteria it will be judged on.
Build a tiny HTTP server
Build mission, about 60 minutes. Hand in a repo link and a short write-up.
Weeks after you learn something, a short unannounced question measures what you kept, not what you finished.
Surprise check, five minutes.
Explain what happens between typing example.com and the page appearing.
Pip knows your skills, your path and the mistakes you've made. Ask why something works, ask to be tested, or ask for a hint. Inside an assessment, a hint never gives the answer away.
Why does my count drop when I join orders to customers?
Before I explain: what do you think happens to a customer with no orders when the join runs?
It gets dropped?
Exactly. A plain JOIN only keeps rows that match on both sides. Try LEFT JOIN and count the orders side.
Pick more than one. Missions can cross them: a secure sensor that reports to an API counts toward electronics, backend and security at once.
Software Engineering
Programming, web, databases and systems.
Cybersecurity
Attacks, defences and secure design.
Data Analysis & Analytics
SQL, analysis and communicating insight.
Electronics & Physical Engineering
Circuits, microcontrollers, sensors and builds.
UI/UX & Product
Interface design, usability and product thinking.
Computer Science Foundations
Algorithms, data structures, networking and systems.