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 421–450 of 1208 results

  • Implement an asynchronous aggregation service that orchestrates calls to User, Payment, and Address downstream clients with dependency-aware concurrency, partial failure handling, and deadline enforcement.

    DoorDashSoftware EngineerSoftware Engineering FundamentalsOnsite
  • This question evaluates incident-response and operational debugging skills, focusing on diagnosing high memory usage in a distributed microservice architecture that includes caching and third-party integrations.

    DoorDashSoftware EngineerSoftware Engineering FundamentalsOnsite
  • Make concurrent rider addition and dispatch safe with atomic availability-to-assignment transitions, idempotent adds, narrow locks, and explicit distributed-state limits.

    DoorDashSoftware EngineerSoftware Engineering FundamentalsOnsite
  • Tests your ability to implement an idempotent, fault-tolerant workflow engine that safely executes financial transactions against an unreliable downstream ledger.

    DoorDashSoftware EngineerSoftware Engineering FundamentalsTechnical Screen
  • Plan scalable migration checks, detect silent zero-output failures, and define incident recovery and monitoring ownership without a separate QA team.

    DoorDashSoftware EngineerSoftware Engineering FundamentalsOnsite
  • Maintain dense map indices for uniform random selection and swap-with-last removal, including empty states, concurrency, and complexity checks.

    DoorDashSoftware EngineerSoftware Engineering FundamentalsOnsite
  • Implement a key-value store class with put, get and remove without using built-in dictionaries or sets, resolving collisions inside the store rather than raising them to callers. It tests hash table mechanics, collision strategies, deletion, resizing and precise average versus worst-case complexity claims.

    EaseSoftware EngineerSoftware Engineering FundamentalsTechnical Screen
  • This question evaluates a candidate's understanding of JavaScript recursion, array manipulation, API contract reasoning, and correctness when implementing a flatten utility.

    ElasticSoftware EngineerSoftware Engineering FundamentalsTechnical Screen
  • This question tests the ability to analyze algorithm correctness through probability theory and identify common pitfalls in pseudo-random number generation that lead to selection bias.

    EliseAISoftware EngineerSoftware Engineering FundamentalsTechnical Screen
  • A code-reading exercise: assess a short Python function that walks a list and swaps each element with a randomly chosen position at or before it. Tests tracing unfamiliar code, reasoning about whether every ordering is equally likely, input-type edge cases such as strings, and practical code-review judgment.

    EliseAISoftware EngineerSoftware Engineering FundamentalsTechnical Screen
  • An interview question on exposing a Python function as a REST API endpoint and testing it. It asks whether FastAPI counts as an endpoint, how an endpoint maps an HTTP request onto a function, and how you unit test such code, with a concrete example that covers edge cases and replaced dependencies.

    EngelhartSoftware EngineerSoftware Engineering FundamentalsTechnical Screen
  • A Python object-oriented programming interview question on abstract classes and method kinds. It asks what an abstract class is and whether it can be instantiated, how instance, class and static methods differ, what self and cls refer to, and why a static method would live inside a class at all.

    EngelhartSoftware EngineerSoftware Engineering FundamentalsTechnical Screen
  • A Python fundamentals interview question on how dictionaries store and look up values: what gets hashed, whether different keys can share a hash, how collisions are resolved and why average lookup is constant time. It also tests whether a list can serve as a key and which objects are allowed as keys.

    EngelhartSoftware EngineerSoftware Engineering FundamentalsTechnical Screen
  • A Python interview question on generators and decorators. It asks what a generator is, what yield does, why generators use less memory and what lazy evaluation means, then what a decorator actually does under the hood, testing precise language mechanics rather than memorized definitions.

    EngelhartSoftware EngineerSoftware Engineering FundamentalsTechnical Screen
  • A developer tooling interview question on Python virtual environments, why projects need them and how Conda and Poetry fit in, followed by practical Linux experience: which system you work on and which Unix commands you rely on to run and debug jobs on a server.

    EngelhartSoftware EngineerSoftware Engineering FundamentalsTechnical Screen
  • A database fundamentals interview question on relational indexes: what an index is, why it speeds up queries, why not every column should be indexed and how indexes affect write performance. It then asks how you would troubleshoot and tune a complex SQL query that runs extremely slowly.

    EngelhartSoftware EngineerSoftware Engineering FundamentalsTechnical Screen
  • A Python concurrency interview question covering how threads and processes differ, including their memory spaces, when to reach for multiprocessing, what the Global Interpreter Lock is and how it limits CPU-bound threads, and why async I/O is a good fit for network and other I/O-bound workloads.

    EngelhartSoftware EngineerSoftware Engineering FundamentalsTechnical Screen
  • Implement a deduction engine that evaluates whether target query statements are definitely true, definitely false, or cannot be determined, given a set of observed facts and unidirectional logical implications.

    Epic SystemsSoftware EngineerSoftware Engineering FundamentalsOnline Assessment
  • This question assesses a candidate's ability to architect a robust, production-ready React feature by integrating state persistence, error handling, testing strategies, and safe deployment practices.

    EquinixFrontend EngineerSoftware Engineering FundamentalsHR Screen
  • This problem tests foundational knowledge in software architecture, AI system design, and data structures by requiring the candidate to explain the trade-offs in building a RAG-based document retrieval system.

    EquinixSoftware EngineerSoftware Engineering FundamentalsTechnical Screen
  • This question evaluates API design, HTTP/web-service principles, data modeling, input validation, error handling, and system constraint reasoning when specifying endpoints, request parameters, response schemas, and practical limits.

    FaireSoftware EngineerSoftware Engineering FundamentalsTechnical Screen
  • A two-part coding problem on an e-commerce category hierarchy shaped as a DAG, where a product's applied discount is the largest discount on its category or any ancestor. The follow-up asks for an audit of which discounted categories appear in the ancestry of each bottom-level category, testing traversal order, deduplication and shared work.

    FaireSoftware EngineerSoftware Engineering FundamentalsOnsite
  • Write good tests and define integration tests evaluates engineering fundamentals, trade-offs, examples, pitfalls, and operational implications in a realistic interview setting. A strong answer states assumptions, handles edge cases, explains trade-offs, and shows how to validate the result clearly.

    FidelitySoftware EngineerSoftware Engineering FundamentalsOnline Assessment
  • Write a program that scans large text-format network logs and reports security attacks defined by rules, such as one source IP contacting more than 10 distinct destination IPs within 10 minutes. It tests parsing, per-source sliding-window state, optimizing a slow first version, and designing targeted test cases.

    FireworksSoftware EngineerSoftware Engineering FundamentalsTechnical Screen
  • Implement the final storage layer of a SQL engine: create databases, schemas, and tables, then insert, select, update, and delete rows with every change persisted to disk. It tests on-disk layout and catalog design, row identity, crash safety and durability, and the trade-offs between log-based and page-based designs.

    FivetranSoftware EngineerSoftware Engineering FundamentalsTechnical Screen
  • Tests your ability to design RESTful APIs and underlying data access patterns for a hierarchical learning management domain (Course -> Module -> Lesson) with authenticated user scoping, idempotent completion updates, and derived completion metrics.

    Fora TravelSoftware EngineerSoftware Engineering FundamentalsTechnical Screen
  • A 45-minute practical coding exercise: build a small service with create-workflow and execute-workflow APIs while using an AI coding assistant. It evaluates planning, implementing and verifying with the assistant, along with validation of workflow definitions, dependency-ordered execution and step failure handling.

    FurtheraiMachine Learning EngineerSoftware Engineering FundamentalsOnsite
  • Tests software engineering fundamentals and clean object-oriented design in Python by building an extensible, schema-validated point-cloud transformation pipeline with registry patterns and metadata tracking.

    GatikMachine Learning EngineerSoftware Engineering FundamentalsTechnical Screen
  • Tests your ability to architect an end-to-end reliability workflow combining resilient dependency handling, actionable telemetry, and safe continuous deployment with automated rollbacks.

    GeneralmotorsSoftware EngineerSoftware Engineering FundamentalsTechnical Screen
  • Tests understanding of RESTful API design principles, HTTP semantics, robust error handling, and strategies for backwards-compatible contract evolution.

    GeneralmotorsSoftware EngineerSoftware Engineering FundamentalsTechnical Screen

More topics