Best solution
Try first. When you reveal it, compare the approach, not just the code.
Complexity:
Interview-ready, architect-ready.
One pattern, one classic, one concept, one decision. Every day.
Today's reps
Each one takes 10β30 minutes. Finishing any of them keeps the streak.
This week in the curriculum
Principal Architect & VP of Engineering, 52 weeks.
Technical:
Leadership scenario:
Start the 52-week curriculum to get a lesson and a leadership scenario every week.
Pattern progress
Three problems per pattern. These patterns cover most coding interview questions.
Practice lanes
Pick one when you have more time.Field notes
Good references, open to everyone.Coding problems are widely known interview problems that candidates commonly report from big-tech loops, written here in original wording. They are not official, verified or leaked company questions. The curriculum and scores are a self-study framework, not a hiring standard. Security and compliance notes are summaries, not legal advice. Progress and code drafts stay in this browser.
Patterns first, then the classics.
Learn the 18 patterns behind most LeetCode problems, then prove them on 30 well-known interview problems.
Problems are widely known interview problems in original wording, not official or leaked company questions. Interviews in Python, Java or C# use the same patterns; practise talking through your approach before you code.
Senior β Staff β Principal β Architect β VP
The concepts, design problems and 52-week plan for Principal Architect and VP of Engineering.
The engineering leadership roadmap
With your background in .NET, AWS, Azure, microservices, databases and leading teams, the gap isn't another language. It's large-scale distributed systems, architecture trade-offs, organizational design and engineering strategy.
Your progress
What to prioritize, by quarter
Highest priority: the foundation for Staff+, Principal and architecture interviews. Check a concept when you can explain it, compare its trade-offs and apply it in a production architecture. Tap a concept to read its summary.
How to answer any design problem
Practise saying each step out loud, in this order, for every exercise.
The big five
More essential exercises
Trade-off reps
Quick decisions. Pick an answer, then read the reasoning.12-month Principal Architect & VP of Engineering curriculum
Weekly structure
Reference project
Goal:
| Week | Technical lesson and practical exercise | Leadership scenario | |
|---|---|---|---|
Assessment rubric
Use the same scoring every month. Rate each competency from 0 (not demonstrated) to 5 (exceptional); scores are weighted.
Your year-long engineering portfolio
The evidence: what you can show an interviewer or your leadership at the end of the year.
Books
In reading order. Designing Data-Intensive Applications first.
Google Engineering Practices
Summaries are paraphrased; the linked pages are the authoritative wording. Public guidance on writing and reviewing code, not a company question bank.
Security & breach response
Rehearse breach response, then write the code that prevents the next one.
Security Study Guide
A cybersecurity book: Linux and networking foundations, web security, blue-team defense and certifications.
- Companions for OverTheWire Bandit, TryHackMe and PortSwigger's Web Security Academy
- Every major web bug class with the fix in C# and NestJS
- Security+, OSCP, PNPT and BTL1 compared, plus a 12-week plan
- Tonight's chapter, reading progress and resume-where-I-stopped
Hacking Lab
Deliberately vulnerable apps in Docker, real CTF platforms, and missions against your own code.
- One Docker Compose file for OWASP Juice Shop, DVWA, Metasploitable 2 and Kali
- Mission checklists for each target, linked to the study guide
- CTF log for picoCTF, HackTheBox, TryHackMe and live events
- Own-code missions that only open on your local machine