Coding interview library
Pick a company and see the LeetCode problems candidates have reported for it, grouped by how recently they appeared. Filter by difficulty and topic, sort by frequency or acceptance rate, and track what you have saved, solved or need to retry – all in one list with direct links to each problem.
Included in every Access Pass, from ₹299. One-time payment, nothing auto-renews.
Company lists are most useful in the last few weeks before an interview, once your fundamentals are in place. Start with the questions marked most frequent in the recent time windows, because they show what that company has been asking lately. Solve them for patterns – sliding window, two pointers, BFS, binary search on the answer – rather than memorising solutions, since interviewers often change the details.
Before opening each problem, use practice mode to write down your approach, its time and space complexity and the edge cases. Explaining your thinking out loud is a big part of how you are judged.
Use the retry mark honestly. If you needed a hint or looked at the solution, mark the question for retry and come back to it two or three days later. Being able to solve it cold the second time is a much better sign of readiness than a long list of questions you have seen once.
If your interview is about a month away, a structure like this keeps you moving:
Hiring processes differ. Product companies and startups usually run one or more DSA rounds with medium to hard problems, and add system design for experienced roles. Large IT services companies often start with an online assessment that combines aptitude, reasoning and easier coding questions, followed by technical and HR interviews. Use the company's own list together with its official hiring process to decide where to put your effort.
The library is built from a public, community-maintained dataset of company-wise LeetCode interview questions on GitHub, refreshed as periodic snapshots. Frequency reflects how often candidates reported a question, not official information from the company. Topic labels are assigned from problem titles, so treat them as a rough filter. HireToolX is not affiliated with LeetCode; problem links open on LeetCode itself.
It comes from a public, community-maintained GitHub dataset of company-wise LeetCode interview questions, and HireToolX loads periodic snapshots of it. Each question links to the original problem page on LeetCode. HireToolX is not affiliated with LeetCode, and the lists are not provided or endorsed by the companies themselves.
No. The lists show questions candidates have reported for a company, which helps you spot recurring patterns and prioritise practice. Interviewers often change problems or ask new ones. If you understand why a solution works and can explain it clearly, you are prepared for variations as well as repeats.
More than 650 companies, including global tech firms such as Google, Amazon, Microsoft and Meta, and companies hiring in India such as Flipkart, TCS, Infosys, Wipro, Accenture, Zoho, Swiggy, Zomato, Paytm, Razorpay and Meesho. Search the company list in the tool; if a company is missing, practise with similar companies' lists.
Frequency is a relative measure of how often a question was reported for that company in the selected time window. Higher frequency suggests a question or pattern has come up more often. Sort by frequency within the last 30 days or 3 months to see what has been asked recently.
There is no magic number. Covering the main patterns well matters more than the count. A practical approach is to work through core topics first, then solve your target company's most frequent recent questions, and finally revisit every question you marked for retry until you can solve it without help.
Yes. Saved, solved and retry marks, practice notes and checklist ticks are stored in your browser on the device you use. They stay there when you come back on the same browser, but they do not sync to other devices, and clearing your browser data removes them.
Sign in, then open the tool from your dashboard.
