Junior Backend to Senior Backend
A staged curriculum that takes a working junior backend engineer to a senior backend interview loop. Strengthens the algorithms and data-structures floor, builds the database and distributed-systems vocabulary senior interviewers expect, climbs through coding difficulty, and finishes with the system-design and behavioral evidence that decides senior offers.
Foundations: Algorithms and Data Structures
Most senior backend loops still open with a coding round. Refresh the patterns first - hash maps, two pointers, binary search, BFS/DFS - before climbing into systems work.
Coding: Easy patterns
Warm-up problems that lock in the core patterns: hash maps, two pointers, simple traversals. If any of these feel uncertain, slow down here - the senior loop assumes these are reflexive.
Coding: Medium patterns
Mid-tier coding problems are where most senior loops get decided. Aim to finish each in ~25 minutes with a clean solution and a concrete time/space analysis.
- 01CodeLongest Substring Without Repeating CharactersCoding · Medium
- 02Code3SumCoding · Medium
- 03CodeGroup AnagramsCoding · Medium
- 04CodeProduct of Array Except SelfCoding · Medium
- 05CodeNumber of IslandsCoding · Medium
- 06CodeCourse ScheduleCoding · Medium
- 07CodeKth Largest Element in an ArrayCoding · Medium
Coding: Hard patterns
Hard problems test whether you can structure an unfamiliar problem under pressure. You will not always finish - that is fine. Practice the framing, identify the right pattern, and code the cleanest correct version you can.
Database fundamentals
Senior backend interviews assume fluency with indexing, transactions, and the trade-offs between SQL and NoSQL. Anchor these before stepping into system design.
System Design basics
The bounded designs that show up in mid-to-senior loops. Each walkthrough covers requirements, capacity estimation, architecture, and trade-offs - the structure interviewers grade against.
- 01MCQSystem Design questions (25 suggested)Multiple choice category
- 02DesignDesign a URL Shortener (bit.ly)System Design · Medium
- 03DesignDesign a Rate Limiter (API Throttling)System Design · Medium
- 04DesignDesign a Distributed Cache (Memcached / Redis Cluster)System Design · Hard
- 05DesignDesign a News Feed (Twitter / Facebook)System Design · Hard
- 06DesignDesign a Chat System (WhatsApp / Slack)System Design · Hard
Behavioral: Ownership evidence
Senior backend offers turn on whether you can show ownership, push back when warranted, and learn from incidents. Build STAR answers around these themes before the loop.
- 01BehavioralOwnership (Amazon Leadership Principle)Behavioral · Amazon LP
- 02BehavioralDive Deep (Amazon Leadership Principle)Behavioral · Amazon LP
- 03BehavioralMissed Deadline or Production IncidentBehavioral · General
- 04BehavioralLeadership Without AuthorityBehavioral · General
- 05BehavioralLearning from FailureBehavioral · Microsoft
Browse other learning paths
Three role-targeted paths are live: Backend, SRE / DevOps, and ML Engineer. More are on the way - if you have a role you want covered, let us know.
View all paths →