Skip to content
QSWEQB

All sections

Subjects are the browse hierarchy. Round type, seniority, and difficulty are filters applied on top, because a single question is often relevant to several roles and several kinds of round at once.

Coding-round questions organised by the pattern they test rather than by problem name, so you learn transferable techniques instead of memorising individual puzzles.

System Design

17 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

15 questions

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

Python

12 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#

10 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

13 questions

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

DevOps & Cloud

13 questions

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

QA & Testing

18 questions

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

Questions for data engineering, ML engineering, and the LLM-application roles now appearing in mainstream hiring loops.

CS Fundamentals

11 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

14 questions

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

Product Management

14 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

14 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

12 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

12 questions

Operator systems either side of the OSS/BSS line: provisioning a service on a network, and turning its usage into money.

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.