The questions, and what a good answer sounds like.
Fifteen role guides written for interviewers. Each question comes with the signal a strong answer carries, the follow-up probe, and the red flags. Inside Expert Hire the same idea runs as a live bank of most-asked questions from real companies, with your own progress on top.
Every guide on this page is free to read. No sign-up, no gate.
- 1,064 questions in the product
- 61 companies
- 15 role guides here
- Progress, streaks and badges
Most people use a question bank wrong.
They scroll it. Recognising a question is not the same skill as answering it. Here is the loop that moves a score, whether you are preparing for an interview or writing one.
Pick a lane, not a list.
Choose the stack you will be interviewed on, or the one you are hiring for. Work one guide end to end before opening a second. Fifteen half-read guides teach less than one finished one.
Answer before you read the answer.
Every prompt is followed by the signal a strong answer carries. Read the prompt, say your answer out loud, then read the signal and mark the gap. The gap is the point. Reading the model answer first teaches nothing.
Rehearse the follow-up, not the question.
Real interviews are won on the second question. Each guide lists the follow-up probes an interviewer reaches for once your first answer lands. That is where a memorised answer falls apart. Practise the probe, not the headline.
Learn the red flags on both sides.
The red flags tell a candidate what to stop saying and an interviewer what to listen for. Sorting the whole dataset when a heap would do, or calling a generator faster without saying why, reads the same way from either chair.
Then take it live.
Reading a question is not the same as answering it under time pressure. Once a guide feels comfortable, run the same ground as a scored round: a mock interview against a target company, or a coding test that executes your code.
Where the scoring comes from.
Every round Expert Hire runs, practice or hiring, lands on one rubric and one readiness score. The methodology page covers what is measured and how a score traces back to the transcript and the code.
Do not memorise a list.
An interviewer who has heard the same rehearsed paragraph forty times discounts it. Use the prompts to find the topics you cannot explain, then go and learn those topics.
Do not confuse coverage with readiness.
A hundred questions in a weekend, forgotten by Friday. Spacing matters more than volume, which is why the in-product bank tracks a streak and a solved-today count, not just a total.
Do not interview off trivia.
If a question has one right answer and no follow-up, it measures recall, not engineering. Structured interviews compare candidates on the same prompts scored against the same signals, which is the only way a shortlist survives a challenge.
Fifteen role guides, grouped by the round they belong to.
Each guide opens with what the round is really testing, then works through categories of questions. Every question carries four things: the prompt as you would ask it, the signal a strong answer gives you, the follow-up probes to reach for next, and the red flags that should end up in your notes.
Languages and runtimes
Depth in the language a service is actually written in: memory, concurrency, error handling and the failure modes that only show up in production.
Python Interview Questions
Practice and screen Python developers with questions covering data structures, async programming, frameworks, testing, and production debugging.
Java Interview Questions
Screen Java developers with questions on OOP, concurrency, JVM internals, Spring Boot, microservices, and production reliability.
Go Interview Questions
Evaluate Go engineers on concurrency, error handling, interfaces, and operational discipline for production services.
Node.js Interview Questions
Evaluate Node.js engineers on the event loop, streams, async patterns, framework judgment, and production debugging.
TypeScript Interview Questions
Screen TypeScript developers on type system depth, inference, generics, narrowing, and pragmatic application across frontend and backend codebases.
Web, mobile and product surfaces
Everything a user touches. Rendering, state, performance, accessibility and the shipping discipline that keeps a release from rolling back.
React Interview Questions
Evaluate React developers on hooks, state management, performance, accessibility, component design, and modern frontend architecture.
Frontend Interview Questions
Screen frontend engineers on browser fundamentals, performance, accessibility, framework judgment, and product craft.
iOS and Swift Interview Questions
Evaluate iOS engineers on Swift, SwiftUI, concurrency, lifecycle, and production discipline for App Store releases.
Android and Kotlin Interview Questions
Screen Android engineers on Kotlin, coroutines, Jetpack Compose, lifecycle, and shipping discipline at Play Store scale.
Data, platform and machine learning
The layer that carries the load. Schema and query judgment, pipelines and orchestration, deployment and incident response, and models once they are live.
SQL and Database Interview Questions
Screen candidates on schema design, query performance, indexing, transactions, and operational database judgment.
DevOps and SRE Interview Questions
Evaluate DevOps and SRE candidates on Kubernetes, CI/CD, infrastructure as code, observability, and incident response.
Data Engineering Interview Questions
Screen data engineers on pipeline design, modeling, orchestration, data quality, and production-grade analytics infrastructure.
Machine Learning Interview Questions
Evaluate ML engineers on modeling, evaluation, deployment, monitoring, and applied judgment around real production systems.
Architecture and behavioral
The two rounds that decide senior hires. Trade-off reasoning against a whiteboard, and evidence of how someone actually works with other people.
System Design Interview Questions
Assess architecture judgment with prompts for scalability, data modeling, reliability, observability, and trade-off communication.
Behavioral Interview Questions
Run structured behavioral interviews focused on collaboration, ownership, conflict, decision-making, and growth.
A static list cannot tell you where you are.
The guides on this page are the editorial half. Inside Expert Hire, Question Bank is a working surface: the most-asked questions from real companies, filterable four ways, with your own progress, streak and badges on top.
What you are looking at: the Question Bank surface in a student account. A header reading 1,064 questions and 61 companies, a progress card showing a percentage, a current streak with a personal best and a solved-today count, six locked badges, per-stream bars, and a filter row for companies, streams, topics and levels. Below it, the question table: company, question, an Easy, Medium or Hard chip, and the topic tags.
Filters that match how you search.
Narrow by company, stream, topic and level, then add a time filter. The bank in the screenshot carries 1,064 questions across 61 companies, well past the point where scrolling works.
Topic tags on every question.
Each row is tagged with what it tests. Array and Hash Table, Design, Heap and Linked List, Tree and DFS, next to an Easy, Medium or Hard chip. That is how you find your weak topic instead of your weak day.
A progress percentage that is yours.
Solved counts roll into one percentage, with per-stream bars underneath so a strong software score cannot hide a weak aptitude one. A static page cannot tell you what you have already answered.
Streaks, solved-today and badges.
A current streak with a personal best, a solved-today counter, and badges at first solve, 10, 50 and 100 solved, plus 3-day and 7-day streaks. Spacing beats cramming, so the product counts days as well as questions.
Not every batch is a software batch.
The guides on this page are engineering-heavy because that is where structured interviewing is hardest. The in-product bank runs wider: progress is tracked per stream, so a core-branch student or a commerce student gets a bar of their own instead of a software leaderboard they can never enter.
| Stream | Who it is for | What it covers |
|---|---|---|
| Software/Coding | Engineering and IT roles | Data structures, design questions and the language depth the 15 guides on this page cover. |
| Aptitude | First-round campus screens | Quantitative, logical and verbal sets, the gate most large drives put in front of everything else. |
| Civil | Core civil engineering | Discipline questions for students whose placement drives are not software at all. |
| Electrical/EEE | Core electrical and electronics | The other half of a core-branch batch that a software-only bank leaves with nothing to practise. |
| Finance & Commerce | Commerce and finance hires | Questions for the accounting, analyst and commerce roles that campus drives fill in volume. |
| HR/Behavioral | Every role, every stream | The round nobody prepares for and everyone is scored on. It has its own guide here too. |
Mock interviews against a target company.
Pick the company you are interviewing with from 900+ companies in the mock interview picker, or hit Surprise me, then pick the round and difficulty. Ethan runs the round in voice, and the questions adapt to what you say. Practice history keeps every attempt with a score and the delta against your last one.
See mock interviewsCoding tests that actually execute.
Reading a solution is not the same as writing one that passes hidden test cases. A coding round runs your submission in a sandbox, returns each case pass or fail with its runtime in milliseconds, and adds a complexity verdict on top.
See coding testsThe same questions, read three different ways.
A candidate reads a question bank to find their gap. A placement cell reads it to find the gap across a batch. A recruiter reads it to write a round that holds up when someone asks why one candidate ranked above another.
Turn the list into a score.
Work a guide, then prove it. Practice runs on Prep Credits, bought once as a pack with no subscription: a mock interview costs 5, a coding test 3, a resume review 1. Every attempt is stored with a score and the change since your last one. The levels view splits you into technical, communication and behavioural, so you can see which one is dragging.
- Repeatable mock interviews, any company and round, 5 credits each
- Practice history with a score, a delta and an insight line
- One-time credit packs, downloadable GST invoice
See the batch, not the anecdote.
Question banks are included in the one per-student campus rate, finalised on a call. Practice activity rolls into a cohort readiness view. It shows an overall readiness score, interview and resume coverage, a week-over-week trend, and how many students are still below the placement bar. Exports run per student, per company and per drive.
- Per-stream progress so core branches are not invisible
- Branch-wise and multi-campus analytics
- Free placement ERP with migration handled by our team
Ask the same question to everyone.
These guides exist so an interview can be written down before it is run. Build the round in four steps: Basic Details, Round Configuration, Questions, Workflow. Turn Enable workflow off on the job and it drops to two. Then pick the mode. Resume screening, AI interview, human-led interview, AI prompt assessment and coding test all score onto one rubric, so a shortlist is a comparison rather than an opinion.
- Follow-ups and red flags you can lift straight into a round
- AI and human rounds mixed in the same pipeline
- Every score traceable to transcript and code on the reportcard
Where these questions go next.
A question bank is the raw material. These pages cover what you build from it: the round, the rubric, the score, and the language people argue about all three in.
Scoring methodology
What is measured in a round, how a rubric is applied, and why every score has to trace back to a transcript or a piece of code.
ReadStructured interview software
The case for asking every candidate the same questions, and what changes in a hiring loop once you do.
ReadHiring and AI glossary
Plain definitions for the terms that show up around these guides: structured interview, readiness score, adverse impact, proctoring.
ReadThe interview platform
Where a question gets asked: AI voice rounds, human-led rounds with a notetaker, and the reportcard that comes back.
ReadCoding tests
Sandboxed problems with real execution against hidden test cases, scored on correctness, efficiency and code quality.
ReadCase studies
What structured rounds changed for campuses, staffing desks and in-house teams that were screening at volume.
ReadQuestion bank, answered.
What candidates, placement cells and interviewers ask about these guides.
Still have a question? Book a demo and we will run a round with you live.
Stop reading questions. Start answering them.
Run the round instead of rehearsing it. Build a structured round with your own questions, or put a candidate through an AI interview and get a reportcard with the evidence attached.
30-day free trial with 75 Hire Credits. Card required, nothing charged for 30 days.