Discofork
Repository brief

jwasham/coding-interview-university

Read the upstream summary on the left, browse the cached forks below it, and load each fork comparison into the right-hand panel.

Cached analysis
cached 2026-03-30T10:28:05.783Z
3mo ago

jwasham/coding-interview-university

A large, highly starred study-guide repository for software engineering interview prep. It is a multi-month computer science roadmap with translated READMEs, extra resources, and language-specific resource lists, maintained on `main` and updated recently in 2024-2025.

GitHub
Loading tags...
Stars338,328
Forks81,626
Default branchmain
Last pushed2025-08-28T14:42:47Z
Recommended shortcuts

Jump straight into Discofork's strongest cached fork picks, or open a compare view in one click.

Forks

Choose a fork to inspect

20 of 20 fork briefs
Selected

Prefer this fork only if you specifically want the Simplified Chinese branch and are comfortable with a frozen, stale snapshot. If you want the latest curated interview-prep material, upstream is the safer choice.

Choose this fork only if you specifically want a frozen copy; otherwise, upstream is the better default because it is actively maintained and substantially ahead.

Prefer this fork only if you want the older Google-oriented framing and do not need upstream's much newer maintenance. Otherwise, upstream is the safer choice because it is far more current and better maintained.

Prefer upstream unless you specifically want this older Google-branded snapshot. For active study use, the parent repo is the better choice because it is maintained and materially more current.

Prefer upstream unless you specifically want a static fork with no extra changes; this fork adds no visible value and is materially behind.

Prefer upstream unless you explicitly want a frozen Google-branded snapshot. This fork offers little functional upside and is materially outdated.

Prefer this fork if you want a Korean-centric, lightly curated snapshot of the interview guide. Prefer upstream if you want the latest, most complete, and actively maintained version.

Prefer upstream unless you specifically need a frozen legacy snapshot; this fork offers no visible added capability and is substantially behind.

Choose the upstream repo if you want current interview-prep material. Choose this fork only if you explicitly want a near-original, frozen copy with essentially no maintenance.

Choose the upstream repository unless you specifically want an old frozen snapshot; this fork adds no visible capabilities and is materially stale.

Prefer upstream unless you specifically want an archival snapshot. This fork adds no visible functionality and lags substantially behind the maintained source.

Choose this fork only if you want a static, Google-centered snapshot. If you want current interview-prep guidance, translations, or recent resource updates, upstream is the better choice.

Prefer upstream. This fork adds no clear value beyond being a stale snapshot, and it is far behind on maintenance and content.

Prefer upstream unless you specifically want the Google-branded presentation; the fork looks stale, adds little or no new substance, and likely misses later upstream improvements.

Prefer upstream unless you specifically want a frozen, Google-branded snapshot. This fork does not show added functionality and is materially behind on content and maintenance.

Prefer upstream unless you explicitly want an old, frozen copy. This fork adds no visible capabilities and is missing substantial recent maintenance and content.

Prefer upstream unless you specifically want a much shorter, frozen snapshot of the study guide. This fork is useful as a trimmed reading aid, but it is too stale to recommend as a primary source for current interview-prep material.

Prefer upstream unless you explicitly need a frozen legacy copy. This fork offers no visible enhancements and is far behind current upstream maintenance.

Prefer upstream unless you specifically want the Google-branded framing; this fork adds little beyond that and is far behind current upstream content.

Prefer upstream unless you explicitly want a frozen historical snapshot. This fork adds no visible capabilities and is materially behind on maintenance and content.