← All open source projects

Interviews

kdn251/interviews

Interviews is a collection of technical interview preparation materials around algorithms and data structures.

Forks 12,884
Author kdn251
Language Java
License MIT
Synced 2026-06-20

What it is

Interviews is a repository for technical interview preparation. It gathers topics around data structures, algorithms, practice platforms, mock interviews, and review material.

It is not trying to be an academic textbook. Its goal is practical: help candidates build a preparation map and see the topics that often appear in developer interviews.

How preparation is organized

The material is grouped by major topics: linked lists, stacks, queues, trees, graphs, sorting, dynamic programming, and other fundamentals.

Practice links and mock interviews matter because algorithms are not only about knowing the answer. You need to explain aloud, write under time pressure, and check edge cases.

Preparation plan

This example shows how the repository can become a weekly plan: topic, practice, and explanation stay together.

Language: Markdown
## Week 1
- Arrays and strings: solve 15 problems
- Linked lists: implement reverse and cycle detection
- Trees: practice traversal explanations
- Mock interview: one timed session

## Review
- Write down failed edge cases
- Repeat weak patterns

Why it helps

Interview preparation often becomes a chaotic set of problems. The repository gives a skeleton: which structures to review, which problem types to solve, and where to practice.

It also reminds readers that interviews test more than the final answer: explanation, complexity, examples, and adaptation after feedback matter.

Strengths

The main strength is practical focus. Many topics here appear in real technical interviews and work well as a checklist.

It is also simple. You can open the table of contents, pick a weak topic, and start practicing.

Limits

A list cannot guarantee interview success. Companies differ in format, language, expectations, and system design depth.

It is also risky to memorize patterns without understanding them. A small change in the problem can break a memorized answer.

Who it fits

Interviews helps students, early developers, and people returning to algorithms before a job search.

The best use is with an error log: failed tasks, missed edge cases, and patterns to revisit after a few days.