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.
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.
Topic directory
Choose a section, open the exact topic named in the role, then add one fundamentals page if the round includes coding or design.
Language rounds with code you can run.
Browser, framework, and API rounds.
Server frameworks and service architecture.
SQL, NoSQL, and data stores.
The core theory every technical round assumes.
Pipelines, containers, and infrastructure.
Modeling, analytics, and the LLM stack.
Test design, automation, and tooling.
Defensive and offensive security rounds.
Enterprise suites, hardware, and specialized stacks.
Prep by the engineering job you're targeting.
Interviewer scoring model
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.
| Signal | What the interviewer looks for | Good evidence | Weak evidence |
|---|---|---|---|
| Problem understanding | Clarifying 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. |
| Reasoning | A 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. |
| Execution | Readable 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. |
| Verification | Tests, 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. |
| Communication | Clear 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
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.
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.
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.
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.
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.
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
| Mistake | Why it hurts | Fix it this way |
|---|---|---|
| Practicing only memorized answers | Interviewers change constraints to see whether you understand the idea. | Practice each question with one changed constraint, then explain what changes in the answer. |
| Skipping clarification | You can solve the wrong problem even when your code is correct. | Start with inputs, outputs, size, errors, latency, and edge cases. |
| Ignoring tests | Correctness 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 topic | Most 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 aloud | Technical interviews are performed while someone is watching and asking follow-ups. | Do timed mock sessions and explain your reasoning while writing or drawing. |
Practice behavioral, situational, negotiation, and assessment questions across every round and stage, with sample answers in Hyring’s free question bank.
Search or browse interview questions across HR, sales, marketing, analytics, support, project, and technical. Every page includes direct answers and examples.
Prepare for company interview processes at Amazon, Google, Microsoft, TCS, Infosys, Wipro, Accenture, and more. Get free questions and answers for each.