Skip to content
Preptima

Interview questions by topic

Browse technical interview questions across DSA, system design, Java, frontend, telecom, QA, data and domain roles. Each area groups the topic-level question sets and links to the newest worked answers.

DSA interview questions organised by tested pattern: arrays, hashing, rotated arrays, dynamic programming, graphs, heaps and sliding windows, so you learn transferable coding-round techniques instead of memorising puzzles.

System Design

70 questions

Open-ended design rounds broken into the building blocks they draw on, plus full case studies worked end to end with explicit trade-off reasoning.

Object-oriented design rounds where you produce classes, interfaces, and interactions rather than infrastructure boxes and arrows.

Language-agnostic service engineering: the protocols, boundaries, and failure handling that sit between a coding round and a full system design round.

Java & Spring

41 questions

Language and framework depth for JVM roles, covering the internals that separate framework users from engineers who understand what runs underneath.

Python

22 questions

Python for backend, automation, and data roles, including the runtime behaviour that surprises candidates who only know the syntax.

Server-side JavaScript depth, where nearly every question eventually reduces to understanding the event loop and the type system.

.NET & C#

15 questions

C# language semantics and ASP.NET Core service internals for Microsoft-stack interviews.

Go

8 questions

Go for infrastructure and high-throughput services, where concurrency idioms carry most of the interview weight.

Browser-platform depth, framework reasoning, and the frontend-specific design round that full-stack candidates are least prepared for.

Databases & SQL

28 questions

Query-writing rounds and the storage-engine reasoning behind why a query is slow, for backend, data, and DBA roles alike.

DevOps & Cloud

37 questions

Platform and infrastructure questions for DevOps, SRE, and any backend role expected to own its service in production.

QA & Testing

36 questions

The full QA spectrum kept deliberately separate: manual craft, automation engineering, and performance testing are different interviews with different rubrics.

Data engineering, ML engineering and LLM/RAG interview questions covering pipelines, model evaluation, overfitting, retrieval, embeddings, vector search and production AI systems.

Prompting and structured output, context and tokens, adaptation, evaluation, inference economics, injection defence, and running LLM features in production.

Retrieval-augmented generation end to end: ingestion, embeddings and vector indexes, hybrid search and reranking, retrieval evaluation, permissions, and agentic tool use.

Machine Learning

24 questions

The modelling half of an ML loop: supervised and unsupervised methods, features and leakage, metric choice, imbalance, deep learning foundations, forecasting and ranking.

Everything between a model that works in a notebook and one a business depends on: reproducibility, feature and training infrastructure, registries, serving, drift, cost and governance.

CS Fundamentals

26 questions

The core-subject rounds common in campus hiring and still used to probe depth in experienced interviews.

Rounds specific to senior, staff, principal, and architect titles, where the subject is judgement and organisational impact rather than code.

Business Analysis

21 questions

Requirements craft for BA and functional-consultant roles, where the interview tests elicitation and precision rather than technology.

Product Management

22 questions

The PM loop as it is actually run: product sense, analytical, execution, and strategy rounds, each with its own scoring rubric.

Solution-engineering and presales-architect interviews, which uniquely test commercial instinct and live communication alongside technical depth.

The EM loop, which mixes people scenarios, delivery judgement, and enough retained technical credibility to lead engineers.

Scrum master, agile coach, and delivery-manager interviews, where framework recall gets you screened in and scenario judgement gets you hired.

The round candidates most often under-prepare, treated as a skill with structure rather than small talk, including the rubric interviewers score against.

The recruiter and HR rounds that gate the technical loop and decide your compensation, where most candidates improvise and lose money.

Domain knowledge as a skill rather than as a subject: why it decides between two technically equal candidates, how the vocabulary gates entry, and how to acquire it deliberately instead of absorbing it over a decade.

How a bank works underneath the app: the ledger that must always balance, the rails money moves over, the identity and financial-crime controls wrapped around it, and the regulatory reporting that constrains every design decision.

Capital Markets

20 questions

Trading, clearing and settlement systems, where correctness is measured in audit trails and the constraints are latency, determinism and an immovable settlement calendar.

Insurance

19 questions

Policy and claim systems, where the engineering difficulty is product configurability and time: effective dates, retroactive change, and a record that must be reconstructable as at any past instant.

Clinical and payer systems, where the record is legally significant, interoperability is decades of overlapping standards, and interrupting a clinician has a real cost.

The path from browse to delivered and back again, where inventory is the central consistency problem and every edge case is a real order belonging to a real person.

Systems that model the physical world, where recorded state diverges from reality by default and reconciliation is continuous rather than exceptional.

Telecom

18 questions

Telecom domain interview questions covering OSS/BSS architecture, BSS billing and charging, service provisioning, logical network inventory, rating, mediation and 5G service models.

Plant and shop-floor systems, where the OT/IT boundary is a hard constraint and a bad deploy can stop a production line.

The rules that reach into system design across every industry, and the difference between having a control, implementing it, and being able to evidence it.

Platform & DevEx

6 questions

Developer experience, internal tooling, and self-service platforms.

Security & InfoSec

11 questions

Application security, threat modeling, and incident response.

Cross-functional delivery, risk mitigation, and dependency management.

Smart contracts, consensus, and decentralised architecture.

Multiplayer state, tick rates, and low-latency UDP networking.

Firmware, RTOS, and edge constraints.

ASIC, FPGA, and Verilog development.

Low-latency C++, order books, and algorithmic trading.

iOS, Android, and cross-platform architecture at scale.

3D math, rendering pipelines, and headset optimizations.

Advocacy, community, and developer experience.

Design systems, accessibility, and user research.

Docs-as-code, OpenAPI, and information architecture.

Agile Coaching

3 questions

Scaled agile, release trains, and organizational transformation.

Onboarding, adoption, and enterprise account management.

Engineering embedded with a customer: their data, their constraints, and a problem nobody has specified yet.

Online assessments, aptitude tests, internships, graduate schemes and campus hiring: the rounds students and new graduates face before their first job, wherever they apply.

Director, VP, head-of and CTO interviews: strategy, organisation design, AI adoption, build versus buy, budgets and business cases, and the case studies, take-homes, presentations and executive panels these loops use.

Every kind of round, not just the coding one

A real loop is several different examinations wearing one name. These are orthogonal tags rather than folders, so a question can be scenario-based and senior and hard without being duplicated into three places.

  • Scenario-based660

    A realistic situation you must diagnose, decide on, or work through out loud.

  • Design527

    Open-ended architecture or component design with trade-off defence.

  • Conceptual457

    Direct knowledge checks on how something works and why.

  • Coding172

    Write or debug working code, usually in a shared editor.

  • Case Study172

    Extended business or product case worked end to end.

  • Behavioural128

    Past-experience questions scored against a competency rubric.

  • HR & Screening41

    Recruiter-round logistics, motivation, and compensation questions.

  • Take-home6

    Asynchronous assignments and what reviewers actually grade.

By difficulty

Medium is where most candidates are actually separated, so that is where the weight sits.

  • Easy38
  • Medium433
  • Hard644

By seniority

One question is often asked at several levels; the bar shows how many carry each.

  • Entry / Fresher155
  • Mid-level810
  • Senior1012
  • Staff / Principal / Architect804
  • Lead / Manager329
  • Director / VP / CTO44