Coding Interview University: A Self-Study Plan That Skips the Degree
A complete computer science study plan to become a software engineer.
At a glance
- What is it?
- John Washam's coding-interview-university is a curated, multi-month study plan for software engineering interviews at large companies. It is a reading list and schedule, not a tool, and its value depends entirely on your discipline and time.
- Who is it for?
- Adopt this plan if you have basic coding skills, several months of study time, and a target interview at a large tech company. Do not adopt it if you are a beginner or need a structured course with deadlines.
- Can I use it commercially?
- Yes, with credit. CC-BY-SA-4.0 allows commercial use as long as you credit the authors and indicate what you changed. It is written for creative content, so check how it applies to any code.
- Is it still maintained?
- Yes. The repository last received commits 8 days ago.
- What is it written in?
- GitHub does not report a main language for this repository.
Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.
Star history
- jwasham/coding-interview-university364,399 ★ · +5,267
| Repository | 2026-08-18 | 2026-11-15 |
|---|---|---|
| jwasham/coding-interview-university | 359.1k | 364.4k |
5,267 Stars in the last 89 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
What This Plan Actually Solves
Coding Interview University addresses a specific pain: a self-taught programmer or a bootcamp graduate who wants a job at a large software company but lacks the Computer Science fundamentals that a degree would provide. The README states it is a study plan for software engineering, not frontend or full-stack development. The author, John Washam, claims he used it to land a job at Amazon after studying 8-12 hours a day for several months. The plan is not a course; it is a curated list of topics, links, and book recommendations, organized into a sequence. It solves the problem of not knowing what to study. That is its core value: it tells you the topics and the order, so you do not waste time deciding what comes next.
The Mechanism: A Curated To-Do List, Not a Tool
The repository is mainly a single large README file, not an application or a script. There is no code to run, no package to install. The mechanism is purely informational: a table of contents that lists topics like algorithmic complexity, data structures (arrays, linked lists, stacks, queues, hash tables), trees, sorting, graphs, recursion, dynamic programming, and even more advanced topics like NP-completeness and floating point numbers. Each topic has links to external resources, mostly videos and articles. The README includes a daily plan section. The plan is self-directed: you read, watch, practice, and mark items as done. It is a checklist, and its effectiveness depends on your ability to follow through.
Getting Started: Commands, Config, and Prerequisites
There are no commands to run or configuration keys to set. The 'installation' is simply cloning the repository or reading the README on GitHub. The prerequisites are stated clearly: a little experience with coding (variables, loops, methods/functions), patience, and time. The plan assumes you can already write basic programs. To use it, you open the README, choose a programming language (the README has a section on that), and start with the first topic. The author advises against studying as much as he did, noting he wasted time on unnecessary topics. There is no versioning or release cycle; the repository is a living document on the main branch. You get updates by pulling the latest changes.
Where It Falls Short: Scope and Maintenance
The plan has clear limitations. First, it is aimed squarely at large company interviews, not at becoming a well-rounded engineer. The README explicitly says it covers about 75% of a CS degree, enough for an interview. It omits frontend and full-stack topics entirely. Second, the content is a static list of links. Over time, external resources can go stale or disappear. You may encounter dead links. Third, the plan is not adaptive. It does not assess your current level or adjust the sequence. If you are weak in one area, you are on your own to find extra practice. Fourth, the author's personal story of 8-12 hours a day for months is not a realistic benchmark for most people. The README itself warns you will not need to study as much, but the sheer volume of topics can be intimidating. For a complete beginner, this plan is the wrong tool because it assumes basic coding fluency.
A Real Alternative: Roadmap.sh's Computer Science Roadmap
The README itself points to an alternative: Kamran Ahmed's Computer Science Roadmap at roadmap.sh. That roadmap is a visual, interactive guide that covers a complete CS curriculum, not just interview topics. The difference in approach is significant: roadmap.sh is a structured, step-by-step visual map, while coding-interview-university is a single linear list. Roadmap.sh also includes links to resources for each topic, similar to this repo. If you prefer a visual overview and a broader scope, roadmap.sh is a better starting point. However, coding-interview-university has a more focused, interview-specific emphasis, which can save time if your goal is purely to pass a technical interview.
Maintenance and Licensing: What You Are Getting Into
The repository is licensed under CC-BY-SA-4.0, which means you can share and adapt the content as long as you give credit and share your adaptations under the same license. That is permissive for personal use, but if you plan to create a derivative study plan for a course, you must comply with the share-alike clause. The repository is not archived, and the default branch is main, and the last push was 2025-08-28. There are no recent releases, which suggests the project is not actively versioned. The README has been translated into many languages, which indicates community involvement, but that does not guarantee the core content is current. The maintenance cost for a user is low: you read the README and check links yourself. The upgrade cost is also low, but you must manually re-check the list for changes. If the author stops updating, the plan may become outdated, especially in fast-moving areas like system design.
Who Should Adopt It and What to Verify First
This plan is for a specific person: someone with basic programming skills, a target interview at a large company, and the self-discipline to work through a long checklist without external deadlines. It is not for someone who needs structure, feedback, or a community. Before you start, verify that the external resources are still accessible. Check the book recommendations and video links; if many are dead, the plan loses its value. Also, confirm that the daily plan section matches your available time. The author's schedule was extreme, and the README warns against replicating it. A realistic approach is to use the topic list as a guide and allocate your own hours. The plan is free, so the cost of trying it is low, but the time cost is high. If you are preparing for a non-technical role, this is the wrong tool. If you are aiming for Amazon, Facebook, Google, or Microsoft, the topics are directly relevant. The Final Review section at the end of the topics of study is a good place to start your own checklist. That is the concrete next step: open the README, read the daily plan, and decide if you can commit to the time.
Editorial conclusion
Adopt this plan if you have basic coding skills, several months of study time, and a target interview at a large tech company. Do not adopt it if you are a beginner or need a structured course with deadlines. Before starting, verify that the linked resources are still alive, because the README is a static list of links. The plan is a personal artifact, not a maintained curriculum, so treat it as a checklist to filter, not a syllabus to follow blindly.
Frequently asked questions
How do I study for a coding interview?
Coding Interview University is a multi-month study plan for becoming a software engineer at a large company, and it asks for three things up front: a little coding experience with variables, loops and methods or functions, patience, and time. The author says he studied 8-12 hours a day for several months while following it, and advises readers to study less than he did because he wasted time on material he did not need.
What is asked in a coding interview?
The plan's topic list is its answer: algorithmic complexity and Big-O, arrays, linked lists, stack, queue, hash tables, binary search, bitwise operations, trees and binary search trees, heaps, five sorting algorithms, directed and undirected graphs with both adjacency representations, then recursion, dynamic programming, design patterns, combinatorics and probability, caches, processes and threads, testing, tries, Unicode, endianness and networking.
How are coding interviews done?
The plan's Getting the Job section covers Update Your Resume, Find a Job, Interview Process and General Interview Prep, plus what to be thinking of when the interview comes and what questions to have for the interviewer. Everything after that point is marked optional in the README, including a System Design, Scalability, Data Handling block gated on having 4+ years experience.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/jwasham-coding-interview-university)Star history chart for your README
[](https://hysenlabs.com/projects/jwasham-coding-interview-university)Was this useful?