HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
jwasham
coding-interview-university
Learning & Reference2016–2026
jwasham / coding-interview-university

coding-interview-university

A complete computer science study plan to become a software engineer.

Learning & ReferenceScience & EngineeringData & DatabasesLibraries & SDKs
Explore on GitHubRead Hacker News discussions
44Distinct people
63Mentions
0Explicit recommenders
364.3KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

A complete computer science study plan to become a software engineer.

GitHub

Where it is used

No documented product use was verified in the last source check.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

Mentioned in the same Hacker News threads. That is not proof they are substitutes.

This week on Hacker News

Nov 8–Nov 15 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/15/2026, 5:03:38 AM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year63 dated mentions

Observed mentions: 2016-08-12 12:59:47 UTC to 2026-05-01 15:14:24 UTC.

0510152016-01-01 00:00:00 UTC to 2017-01-01 00:00:00 UTC (exclusive): 9 mentions; 6 submissions, 3 comments20162017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 17 mentions; 5 submissions, 12 comments2018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 14 mentions; 0 submissions, 14 comments2019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 8 mentions; 3 submissions, 5 comments2020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 6 mentions; 3 submissions, 3 comments2021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments20212022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 4 mentions; 3 submissions, 1 comments2023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments2025-01-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2026-01-01 00:00:00 UTC to 2027-01-01 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments. Incomplete calendar period.2026*

* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20162016-01-01 00:00:00 UTC2017-01-01 00:00:00 UTC963
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC17512
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC14014
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC835
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC633
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC101
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC431
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC101
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC110
20252025-01-01 00:00:00 UTC2026-01-01 00:00:00 UTC101
2026 (partial)2026-01-01 00:00:00 UTC2027-01-01 00:00:00 UTC110

What Hacker News says

1 sources
harttle·Mar 17, 2021
I got this push message from Hacker News this morning and felt obliged to post my opinion on the "LeetCode thing" cause I'm currently trying the same thing as you are. I have a master degree on CS and 4 years of professional experience and trying to keep moving forward. I don't believe solving LeetCode problems well is something that you have to be gifted to achieve. Ironically, I believed it once upon a time. I got very frustrated when failed tech interviews for Microsoft and Google when I was a new-grad and trying to find a decent job. I know it's frustrating to just look at somebody finishing all the contest problems in 10min and you're scratching your head for many hours or even a whole day. Believe me I was literaly doing this for a long time. But I started my professional occupation anyway. What I did then is keep trying for several
Read the rest
years since I know I'm stupid and stubborn. It turns out to be promising in the third year doing so. I gradually find out there IS a way! There is a clear and straightforward path to do better in algorithm problems: just get a full list of basic data structures and algorithms, understand them all by watching youtube videos, learning online courses (MIT online courses helped be a lot), and practice tens of problems in each subject until you get sick of it. Currently I get 2481 points in LeetCode contest and I'm preparing for my next period of career and hope these hard work finally pay off! In case someone need it, these 2 lists are very comprehensive and helped me a lot: * https://github.com/jwasham/coding-interview-university * https://techdevguide.withgoogle.com/ Hope it helps!
In 5 years of leetcode with no progress. I'm giving up

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.