Katkat

Topic

Software Engineering Fundamentals interview questions

1208 Software Engineering Fundamentals questions from 253 companies, with hints, runnable code and solution walkthroughs.

Questions1208

123 easy887 medium198 hard

Your progress0/1208

Software Engineering Fundamentals interview questions by the numbers

Last updated

Katkat has 1,208 Software Engineering Fundamentals interview questions from 253 companies; the most come from OpenAI (5%), Stripe (4%) and Amazon (3%). By difficulty: 10% easy, 73% medium and 16% hard. The most common round is Technical Screen (52%). Frequent concepts include Data Structures, Concurrency, System Design and Algorithms.

Companies (253)

Difficulty

  • Easy10% · 123
  • Medium73% · 887
  • Hard16% · 198

Interview rounds

  • Technical Screen52% · 625
  • Onsite37% · 448
  • Online Assessment8% · 96
  • HR Screen2% · 28
  • Other1% · 11

Roles

  • Software Engineer85% · 1026
  • Frontend Engineer4% · 51
  • Machine Learning Engineer2% · 30
  • Backend Engineer2% · 25
  • Data Scientist1% · 17

Frequent concepts

  • Data Structures8% · 97
  • Concurrency8% · 96
  • System Design8% · 93
  • Algorithms3% · 42
  • API Design3% · 42
  • Object-Oriented Design3% · 35

Showing 691–720 of 1208 results

  • Design the create, read, update and delete API for a document service, covering the resource model, endpoints, request shapes and status codes. It tests REST fundamentals plus production concerns such as concurrent edits, idempotent retries, pagination, authorization, deletion semantics and API versioning.

    MintlifyBackend EngineerSoftware Engineering FundamentalsOnsite
  • Recreate a screenshot-defined card and chip component through extracted design tokens, accessible semantics, responsive layout, and visual comparison.

    MintlifySoftware EngineerSoftware Engineering FundamentalsOnsite
  • A query on a large database table is slow and the columns it filters on have no index: should you add one? It tests reading query plans, weighing selectivity and query frequency against write cost, designing composite or partial indexes, and building an index safely on a busy production table.

    MintlifyBackend EngineerSoftware Engineering FundamentalsOnsite
  • Diagnose GPU input starvation across storage, CPU preprocessing, batching, transfer, and synchronization, then improve bounded overlap while preserving data correctness.

    Mistral AISoftware EngineerSoftware Engineering FundamentalsTechnical Screen
  • This question evaluates practical competencies in Python development environment setup, reproducible dependency management with lockfiles, virtual environment and interpreter management, secrets handling via environment variables, project structuring, and basic API integration.

    Mistral AISoftware EngineerSoftware Engineering FundamentalsTechnical Screen
  • This problem tests your ability to identify and debug concurrency issues and scheduling logic in a custom GPU resource manager.

    MithrilSoftware EngineerSoftware Engineering FundamentalsOnsite
  • Tests deep understanding of Unix shell semantics, process management, file permissions, and standard stream handling by diagnosing subtle failure modes in common shell one-liners and writing robust, production-grade replacements.

    ModalSoftware EngineerSoftware Engineering FundamentalsTechnical Screen
  • Tests formal inductive reasoning on randomized algorithms by proving the uniformity of the Fisher-Yates shuffle, and evaluates practical knowledge of common implementation pitfalls like off-by-one bounds and modulo bias.

    ModalSoftware EngineerSoftware Engineering FundamentalsTechnical Screen
  • Implement counting sort to order 100,000,000 single-digit integers using O(1) auxiliary space, and analyze performance from a hardware and memory-bandwidth perspective.

    ModalSoftware EngineerSoftware Engineering FundamentalsTechnical Screen
  • Work through the state and timing logic for a React memory-card game that remains correct under rapid clicks and restarts. The exercise examines stale closures, input locking, timeout cleanup, stable card identity, accessible interaction, and tests for race-prone transitions.

    MomentFrontend EngineerSoftware Engineering FundamentalsTechnical Screen
  • Build a crawler around a supplied fetch-and-parse API, then add bounded concurrency, atomic discovery, correct completion detection, and explicit failure semantics.

    MongoDBSoftware EngineerSoftware Engineering FundamentalsTechnical Screen
  • This question tests your ability to diagnose performance bottlenecks in a multi-threaded network server using I/O multiplexing, focusing on how blocking calls and thread management impact latency.

    MongoDBSoftware EngineerSoftware Engineering FundamentalsOnsite
  • Implement an evaluator for a serialized predicate expression tree against JSON documents, testing recursion, AST handling, and field resolution.

    MongoDBSoftware EngineerSoftware Engineering FundamentalsTechnical Screen
  • This question assesses your depth of knowledge regarding modern Python language evolution, the utility of popular libraries, and internal implementation details that impact memory and performance.

    MongoDBSoftware EngineerSoftware Engineering FundamentalsHR Screen
  • Implement an orchestrator for a finite concurrent web crawler featuring transactional URL state tracking, per-host politeness rate-limiting, classified error handling, and robust termination detection.

    MongoDBSoftware EngineerSoftware Engineering FundamentalsOnsite
  • Implement a UnionIterator that lazily merges two strictly sorted iterators of integers or strings into one strictly sorted iterator without duplicates, using constant extra memory. Tests iterator protocol design, one-element lookahead, cross-input deduplication, end-of-stream behavior and edge cases such as empty inputs.

    MongoDBSoftware EngineerSoftware Engineering FundamentalsTechnical Screen
  • Coding and design question from a technical screen: implement a rate limiter that admits at most n requests in any k-second sliding window, then make it thread-safe and key-specific. It tests window boundary semantics, amortized complexity, race conditions and locking, per-key state creation and memory bounds.

    MongoDBSoftware EngineerSoftware Engineering FundamentalsTechnical Screen
  • Implement a recursive search function to extract all values associated with a given key from deeply nested JSON documents containing arbitrary combinations of dictionaries and lists.

    MongoDBSoftware EngineerSoftware Engineering FundamentalsTechnical Screen
  • This question evaluates understanding of option Greeks (delta, gamma, vega), mental approximation of Gaussian probabilities, and the ability to reason about delta-hedged profit-and-loss under Black-Scholes model misspecification, categorized under Software Engineering Fundamentals for a Data Scientist role.

    Morgan StanleyData ScientistSoftware Engineering FundamentalsTechnical Screen
  • This question evaluates understanding of financial derivatives—specifically forwards and options—assessing competency in financial instruments, contractual rights and obligations, pricing concepts, and how these concepts inform data-driven modeling for a Data Scientist role.

    Morgan StanleyData ScientistSoftware Engineering FundamentalsTechnical Screen
  • This question tests the ability to design an efficient data structure for maintaining the top-K elements in a high-throughput stream with time-windowing requirements.

    NVIDIASoftware EngineerSoftware Engineering FundamentalsTechnical Screen
  • An engineering director asks how Java and Python differ and where each language is stronger or weaker. It tests understanding of execution models, static versus dynamic typing, concurrency and the global interpreter lock, ecosystems, and the judgment to recommend a language for a concrete project.

    NVIDIASoftware EngineerSoftware Engineering FundamentalsOnsite
  • A coding and concurrency question: count the distinct strings in an array with a hash table built from scratch, then keep the count correct when many threads insert at once. It tests hash table design, locks versus atomic compare-and-swap, and how work division and memory layout affect GPU and CPU performance for a million keys.

    NVIDIASoftware EngineerSoftware Engineering FundamentalsTechnical Screen
  • Prepare for a NVIDIA software engineering interview question about data pipeline reliability, backfills, and spark optimization. The prompt highlights practical reasoning, edge cases, trade-offs, and validation criteria without revealing the model answer.

    NVIDIAData EngineerSoftware Engineering FundamentalsTechnical Screen
  • This interview question evaluates requirements, scale assumptions, API/data design, architecture, trade-offs, failure modes, and rollout in a realistic interview setting. A strong answer for Define a Git workflow for CI states assumptions, handles edge cases, explains trade-offs, and shows how to validate the result clearly.

    NVIDIASoftware EngineerSoftware Engineering FundamentalsOnline Assessment
  • This interview question evaluates engineering fundamentals, trade-offs, examples, pitfalls, and operational implications in a realistic interview setting. A strong answer for Demonstrate software engineering fundamentals states assumptions, handles edge cases, explains trade-offs, and shows how to validate the result clearly.

    NVIDIASoftware EngineerSoftware Engineering FundamentalsOnsite
  • Design a thread-safe, bounded multi-producer multi-consumer (MPMC) circular buffer supporting blocking operations, timeouts, and graceful shutdown (close-and-drain).

    NVIDIASoftware EngineerSoftware Engineering FundamentalsTechnical Screen
  • This problem tests object-oriented design and data structure proficiency by requiring the implementation of a tracker that maintains the top-K most frequent entities within a sliding time window of events.

    NVIDIASoftware EngineerSoftware Engineering FundamentalsTechnical Screen
  • This interview question evaluates algorithm design, data structures, correctness, complexity, edge cases, and implementation details in a realistic interview setting. A strong answer for Design an IR for test workflows states assumptions, handles edge cases, explains trade-offs, and shows how to validate the result clearly.

    NVIDIASoftware EngineerSoftware Engineering FundamentalsOnline Assessment
  • This question tests the ability to apply Amdahl's Law to real-world hardware acceleration and understand the architectural constraints involved in GPU matrix multiplication.

    NVIDIASoftware EngineerSoftware Engineering FundamentalsTechnical Screen

More topics