Skip to content

Tracks

Every language, framework, database and cross-cutting skill we grade, and how much of each is ready.

Languages

  • Types, collections, LINQ, async and the language features .NET interviewers probe first.

    230 questions
  • Core language, collections, generics, streams, concurrency primitives and the JVM basics.

    228 questions
  • The Python interviewers expect: data model, comprehensions, generators, typing and the standard library.

    222 questions
  • Closures, the event loop, prototypes, promises and the quirks that trip people up in front-end loops.

    221 questions
  • The type system beyond annotations: narrowing, generics, utility types, and how to model real domains.

    216 questions
  • Goroutines, channels, interfaces, error handling and the idioms Go reviewers care about.

    236 questions
  • Modern PHP: types, OOP, Composer, error handling and the runtime model.

    210 questions
  • Blocks, modules, metaprogramming basics and idiomatic Ruby.

    214 questions
  • Ownership, borrowing, lifetimes, traits and error handling without a garbage collector.

    210 questions
  • Memory, RAII, templates, the STL and modern C++ features.

    217 questions
  • Null safety, coroutines, data classes and Kotlin idioms on the JVM and Android.

    217 questions
  • Optionals, value types, protocols and concurrency in Swift.

    210 questions
  • Engine-agnostic SQL: the joins, aggregates, subqueries and set logic every data interview starts with.

    216 questions

Frameworks

  • Dependency injection, the middleware pipeline, EF Core, auth and the questions every .NET backend loop asks.

    215 questions
  • Beans, auto-configuration, Spring MVC, Data JPA, security and testing.

    213 questions
  • ORM, migrations, views, middleware, forms and Django REST Framework.

    244 questions
  • Pydantic models, dependency injection, async endpoints and OpenAPI.

    218 questions
  • The runtime: event loop, streams, modules, process model and performance.

    246 questions
  • Routing, middleware, error handling and structuring an Express API.

    213 questions
  • Modules, providers, DI, pipes, guards, interceptors and testing in Nest.

    210 questions
  • Rendering, hooks, state, effects, performance and the mental model behind them.

    223 questions
  • App Router, server components, rendering modes, caching and data fetching.

    217 questions
  • Reactivity, the Composition API, components, routing and state.

    210 questions
  • Components, DI, RxJS, change detection, forms and routing.

    210 questions
  • Eloquent, routing, middleware, queues and the service container.

    205 questions
  • ActiveRecord, conventions, controllers, callbacks and background jobs.

    205 questions
  • Widgets, state management, layout, navigation and platform channels.

    207 questions
  • The bridge, native modules, navigation, styling and performance on mobile.

    207 questions

Databases

  • T-SQL, indexing, execution plans, isolation and the tuning questions SQL Server shops ask.

    221 questions
  • Joins, window functions, EXPLAIN, MVCC, indexes and PostgreSQL-specific features.

    239 questions
  • InnoDB, indexing, EXPLAIN, isolation levels and MySQL specifics.

    214 questions
  • PL/SQL, packages, cursors, optimizer hints and Oracle-specific SQL.

    202 questions
  • The embedded database: typing, transactions, indexes, WAL and its limits.

    202 questions
  • Document modelling, the aggregation pipeline, indexes, transactions and replication.

    210 questions
  • Data structures, caching patterns, persistence, pub/sub and cluster.

    207 questions
  • Inverted indexes, mappings, analyzers, queries, aggregations and cluster basics.

    206 questions
  • Partitioning, consistency levels, query-first modelling and compaction.

    202 questions

Cross-cutting

  • Complexity, arrays, hashing, trees, graphs, sorting and the patterns behind coding rounds.

    241 questions
  • Scaling, caching, queues, consistency, storage choices and the trade-offs behind them.

    245 questions
  • The stories interviewers ask for: ownership, conflict, failure, ambiguity and impact, told in STAR.

    200 questions
  • Resources, verbs, status codes, versioning, pagination, idempotency and errors.

    228 questions
  • Branching, merging, rebasing, history surgery and collaboration workflows.

    210 questions
  • Images, layers, networking, volumes, then pods, services, deployments and scaling.

    210 questions
  • The test pyramid, TDD, mocks vs fakes, flaky tests and what to test at each layer.

    210 questions
  • Injection, auth failures, XSS, CSRF, secrets, crypto basics and secure defaults.

    209 questions
  • Threads vs async, races, locks, deadlocks, memory models and safe patterns.

    210 questions
  • Brokers, delivery guarantees, ordering, idempotency, dead letters and event-driven design.

    207 questions
  • Compute, storage, networking, IAM, managed databases, serverless and cost.

    210 questions