Code, systems, data, cloud, and tools

Technical Interview Questions

Practice for technical interviews with this free question bank by language, framework, database, and cloud tool. Get runnable code, answers, and scoring tips.

Filter this directory by language, tool, role, company, or interview format.

Python Interview QuestionsThe 65 Python questions interviewers actually ask, with direct answers, runnable code, and what the interviewer is listening for. Grouped for freshers, intermediate, and experienced rounds.Java Interview QuestionsThe 65 Java questions interviewers actually ask, with direct answers, runnable code, and what the interviewer is listening for. Grouped for freshers, intermediate, and experienced rounds.JavaScript Interview QuestionsThe 65 JavaScript questions interviewers actually ask, with direct answers, runnable code, and what the interviewer is listening for. Grouped for freshers, intermediate, and experienced rounds.C Interview QuestionsThe 60 C questions interviewers actually ask, with direct answers, runnable code, and what the interviewer is listening for. Grouped for freshers, intermediate, and experienced rounds.C++ Interview QuestionsThe 60 C++ questions interviewers actually ask, with direct answers, runnable code, and what the interviewer is listening for. Grouped for freshers, intermediate, and experienced rounds.C# Interview QuestionsThe 60 C# questions interviewers actually ask, with direct answers, runnable code, and what the key signal is. Grouped for freshers, intermediate, and experienced rounds.TypeScript Interview QuestionsThe 60 TypeScript questions interviewers actually ask, with direct answers, runnable code, and what the interviewer is listening for. Grouped for freshers, intermediate, and experienced rounds.Go Interview QuestionsThe 60 Go questions interviewers actually ask, with direct answers, runnable code, and what the key signal is. Grouped for freshers, intermediate, and experienced rounds.

Topic directory

Use the topic pages after you know what to practice

Choose a section, open the exact topic named in the role, then add one fundamentals page if the round includes coding or design.

Interviewer scoring model

How strong interview answers are judged

Most technical interviews are not scored on the final answer alone. They also score how you reach it, test it, and explain it. Use this table as a self-review checklist after each practice session.

SignalWhat the interviewer looks forGood evidenceWeak evidence
Problem understandingClarifying questions, assumptions, constraints, inputs, outputs, and success criteria.You restate the problem, ask one or two sharp questions, and define what the answer must handle.You answer a different problem or miss a stated constraint.
ReasoningA defensible approach, comparison of alternatives, and awareness of complexity.You compare two options and explain why one fits the data size, latency, cost, or role need.You name a pattern but cannot explain why it is correct.
ExecutionReadable code, correct logic, safe state handling, and steady debugging.You write code in small steps, dry run it, and fix mistakes calmly.Your implementation depends on luck, hidden assumptions, or interviewer rescue.
VerificationTests, edge cases, complexity, failure modes, and production checks.You test normal, boundary, invalid, and large cases and can explain time and space cost.You stop after the first sample passes.
CommunicationClear thinking, concise explanation, tradeoff language, and openness to feedback.You explain what you are doing before you do it and adjust when new information appears.You go silent, over-explain low-value details, or ignore interviewer hints.

Preparation by profile

Choose a roadmap

The right prep path depends on the signal the role needs. Freshers must prove fundamentals. Senior engineers must prove judgment. Data, AI, and cloud roles need evidence that the work survives production constraints.

1

Fresher

One language, DSA basics, OOP, SQL, operating systems, networks, and two project stories.

Proof: You can solve medium basic problems, explain complexity, and connect college or portfolio projects to engineering choices.

2

2 to 5 years

Primary stack, API design, debugging, database choices, production incidents, and tradeoffs.

Proof: You can explain a feature you shipped, a bug you debugged, and a design choice you changed after feedback.

3

Senior engineer

System design, reliability, migration plans, team interfaces, review quality, and operational judgment.

Proof: You can explain why a design is good enough now, when it will fail, and what you would change next.

4

Data or AI role

Data quality, metrics, experimentation, model evaluation, Python data tools, and production failure modes.

Proof: You can explain why the metric matches the business problem and what can go wrong after launch.

5

DevOps or cloud role

Linux, networking, containers, cloud primitives, CI/CD, observability, security basics, and rollback plans.

Proof: You can explain how a service is deployed, monitored, scaled, and recovered after a failed release.

Practice traps

Mistakes that make answers look weaker

MistakeWhy it hurtsFix it this way
Practicing only memorized answersInterviewers change constraints to see whether you understand the idea.Practice each question with one changed constraint, then explain what changes in the answer.
Skipping clarificationYou can solve the wrong problem even when your code is correct.Start with inputs, outputs, size, errors, latency, and edge cases.
Ignoring testsCorrectness is not visible until you prove behavior with examples.Test a normal case, empty case, duplicate case, boundary case, and large case.
Over-indexing on one topicMost loops score multiple signals across coding, design, communication, and role skills.Prepare one primary stack, one fundamentals track, and one role-specific track.
Not practicing aloudTechnical interviews are performed while someone is watching and asking follow-ups.Do timed mock sessions and explain your reasoning while writing or drawing.

Related interview question directories