TopGit
GitHub Repo Review

LeetCode Company-Wise Problems: Interview Prep by Company

liquidslr/leetcode-company-wise-problems
LTopGit review image for liquidslr/leetcode-company-wise-problems
Review by Topgit.dev for liquidslr/leetcode-company-wise-problems, with GitHub repository stats and README context.
Quick verdict

LeetCode Company-Wise Problems turns LeetCode's own company tags into ready-to-open CSV files, one per firm. It's genuinely useful for narrowing a study list before a specific onsite, but it's a raw data dump, not a curriculum โ€” there's no difficulty curve, no explanations, and no guarantee the tags still match what that company asks this quarter. Treat it as a filter on top of LeetCode, not a replacement for solving problems there.

Stars
โ˜… 28.0k
Forks
โ‘‚ 5.5k
Contributors
๐Ÿ‘ฅ 1
Language
โ€”
License
See repository
Topic
โ€”
Updated
Jun 2026

What this repository contains

LeetCode Company-Wise Problems is a GitHub repository of CSV files, one per company, each listing LeetCode questions tagged for that company's interviews. The lists sit inside a companies directory and split into questions from the last 30, 60, and 90 days plus an all-time list where LeetCode's tag data supports one. There's no web app here โ€” just the raw CSVs, plus a link to the maintainer's separate System Design Notes repo.

Why target company-specific questions

Grinding LeetCode's full problem set in order treats a Uber online assessment and a Meta onsite as the same exam, when interviewers at each company actually pull from a narrower, tag-tracked pool. LeetCode already exposes company tags to Premium subscribers, but browsing them one company at a time inside the site is slow once you know exactly which firm you're interviewing with next week. Company-Wise Problems just pre-sorts that same tag data into a flat file per company, so you can jump straight to the Amazon or Google folder instead of filtering LeetCode's UI by hand.

What the lists offer

  • โœ“A company directory: separate CSV files, one per company, including Amazon, Google, Meta and Uber going by the repo's own topic tags.
  • โœ“Time-window splits inside each file for the past 30, 60, and 90 days, plus an all-time list where LeetCode's tag data supports it.
  • โœ“Coverage that spans both the online-assessment stage and the onsite interview stage, per the repo's own topic tags.
  • โœ“Every row maps to an actual LeetCode question carrying that company's tag โ€” this is the tag data reorganized, not a rewritten problem set.
  • โœ“A linked companion project, System Design Notes, for the system-design side of interview prep the CSVs themselves don't touch.
How this repository's GitHub stars have grown over time. Source: star-history.com.View the star history โ†—

How to use these lists effectively

  • โ€ขPull the folder for the company you're actually interviewing with and work through its all-time list first.
  • โ€ขCheck the 30-day file when the interview is close โ€” it's the closest proxy here for what that company is asking right now.
  • โ€ขLook up each question's difficulty and topic on LeetCode itself, since the CSVs list titles, not difficulty ratings.
  • โ€ขPair it with the maintainer's System Design Notes repo once the loop includes a system-design round.

Strengths

  • โœ“Free access to a company-tag split that LeetCode normally gates behind a Premium subscription.
  • โœ“The 30/60/90-day plus all-time split lets you match study time to how soon the interview actually is.
  • โœ“Zero setup: clone the repo or open the CSV for the company you're interviewing with, no build step involved.
  • โœ“Covers assessment-stage prep as well as onsite-stage prep, going by the repo's own online-assessment topic tag.

Known gaps and accuracy concerns

  • โ–ณCompany tags come from LeetCode's own tagging system, which LeetCode itself treats as a historical/community signal, not a confirmed preview of a given interview loop โ€” this repo just repackages that same uncertainty into files.
  • โ–ณNo difficulty ratings are included.
  • โ–ณNo topic breakdowns or explanations sit in the CSVs either โ€” just question titles, so everything else gets looked up on LeetCode separately.
  • โ–ณFreshness depends on the maintainer re-exporting the tags by hand; the source material's own last-updated note points to June 2025, so anything a company has added to its tag pool since then won't be reflected.

Other ways to prep for technical interviews

Frequently asked questions

How accurate are LeetCode company tags on this list?

LeetCode Company-Wise Problems inherits its accuracy from LeetCode's own company tags, which LeetCode itself describes as based on user-submitted and historical data rather than confirmed current interview content โ€” treat the lists as a starting filter, not a guarantee of what a specific loop will ask.

Is LeetCode Premium required to see company-tagged questions?

LeetCode Premium is required to view company tags directly inside LeetCode's own interface. LeetCode Company-Wise Problems exists specifically to make that same tagged data browsable for free, as CSV files organized by company.

Which companies have the most questions in the collection?

The README doesn't publish per-company question counts, so there's no confirmed ranking of which folder is largest. The repo's own topic tags do call out Amazon, Google, Meta, and Uber by name, which confirms those companies are covered, but not which has the most questions.

How often is this list updated with new problems?

The repository's own description and README point to June 2025 as the most recent update noted in the source material. LeetCode Company-Wise Problems doesn't publish a fixed update schedule, so treat any given company folder as current only as of that stated update.

Are difficulty levels included for each question?

Difficulty levels are not part of LeetCode Company-Wise Problems' CSV files, which list only question titles grouped by time window. Check the difficulty rating on LeetCode itself before building a study plan around a given list.

Can I contribute company-tagged questions I have encountered?

The README doesn't describe a contribution process for LeetCode Company-Wise Problems, such as a CONTRIBUTING guide or a submission format. Since it's a public GitHub repository, opening an issue or pull request is the standard route, though the maintainer's review process isn't documented.

Who should try it โ€” and who should skip

This fits someone with a confirmed interview at a specific company and a short runway โ€” you already know the target, so a pre-filtered list beats browsing LeetCode's full catalog by hand. It's less useful if you're still building fundamentals: with no explanations or difficulty ratings, a beginner just gets a wall of question titles and no path through them. Skip it too if you'd rather trust LeetCode's own Premium company-tag feature over a community re-export of the same signal.

Related repositories

Source & attribution

Based on the liquidslr/leetcode-company-wise-problems GitHub repository and its README.

GitHub data ยท last synced Aug 15, 2026Reviewed by Henry
โ† Back to TopGit

Want a second opinion on leetcode-company-wise-problems?

Ask an AI that can read this page โ€” one click and you get its take on leetcode-company-wise-problems.

GitHub