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 151–180 of 1208 results

  • Implement a thread-safe in-memory event tracker that records events and reports the events and their count within a sliding time window. Tests time-ordered storage with amortized eviction, window boundary semantics, lock scope and clock choice, out-of-order events, and memory under high event rates.

    AppleSoftware EngineerSoftware Engineering FundamentalsOnsite
  • Explain functional regression testing, reproducible performance benchmarks, and how to reduce shared HPC resource use without weakening test coverage.

    AppleAccessories Software QA EngineerSoftware Engineering FundamentalsOnsite
  • This question evaluates understanding of digital architecture, microarchitecture, and logic‑level techniques for improving chip performance without process advances, along with competence in performance/power/area (PPA) trade‑off analysis and arithmetic block design.

    AppleSoftware EngineerSoftware Engineering FundamentalsTechnical Screen
  • Implement a fixed-capacity least-recently-used cache with constant-time get and put, then discuss two follow-ups: cutting the shared-state writes that every read causes when it updates recency, and making the cache safe and fast under concurrent access, including how eviction order changes.

    AppleSoftware EngineerSoftware Engineering FundamentalsOnsite
  • This question tests the ability to design a thread-safe iterator for a binary search tree (BST) that remains consistent even if the underlying tree structure is modified during iteration.

    AppleSoftware EngineerSoftware Engineering FundamentalsTechnical Screen
  • Optimize QA benchmark turnaround and shared HPC usage by profiling execution, controlling resources, and separating runtime savings from faster reporting.

    AppleSoftware EngineerSoftware Engineering FundamentalsOnsite
  • Parse a strict HTTP access-log format and summarize valid requests, client errors, server errors, invalid lines, and failure percentage. The prompt tests full-field validation, precise metric denominators, status boundaries, streaming aggregation, and privacy-safe diagnostics.

    AppleSoftware EngineerSoftware Engineering FundamentalsTechnical Screen
  • A coding exercise in which the HTML parser prompt is deliberately vague, so the candidate must first pin down input, output and edge cases with concrete examples. It tests building a tree from nested markup in one pass, handling void and malformed tags, and answering a query with a depth-first traversal.

    AppleSoftware EngineerSoftware Engineering FundamentalsOnsite
  • Reduce regression false failures with reviewed acceptance rules, then classify causes and severity without confusing test categories with observed outcomes.

    AppleSoftware EngineerSoftware Engineering FundamentalsOnsite
  • Implement a function that runs several slow, failure-prone backend API calls concurrently and returns the first successful result within a single overall timeout. It tests concurrency primitives, deadline handling, reporting when every call fails, and cleaning up calls that are still in flight, using threads, futures, or async code.

    AppleSoftware EngineerSoftware Engineering FundamentalsTechnical Screen
  • A progressive Java coding exercise that asks whether a store is open at a given time as its schedule grows from one daily window to selected weekdays, several windows per day, and overnight windows that cross midnight and wrap from Sunday to Monday. It tests time modeling, boundary handling, and keeping evolving code readable.

    AppleSoftware EngineerSoftware Engineering FundamentalsTechnical Screen
  • Implement a token manager in which each token expires a fixed time-to-live after it is generated or renewed, renewals extend only unexpired tokens, and a query counts live tokens. The follow-up asks how to keep it correct and fast under heavy concurrent reads and writes.

    AppleSoftware EngineerSoftware Engineering FundamentalsTechnical Screen
  • Explain how to troubleshoot a Kubernetes pod that has a problem, starting from its status, container states and events. Tests mapping Pending, ImagePullBackOff, CrashLoopBackOff, OOMKilled and not-Ready states to likely causes, using logs, debug containers and node checks, and separating mitigation from root cause.

    AppleSoftware EngineerSoftware Engineering FundamentalsTechnical Screen
  • Assess QA benchmark validity using comparable baselines, measurement variation, practical impact, and clear ownership of regression thresholds and known issues.

    AppleSoftware EngineerSoftware Engineering FundamentalsOnsite
  • This question tests your ability to navigate, critique, and extend a modular codebase designed for evaluating agentic PDF processing pipelines, focusing on evaluation metrics and robust system architecture.

    AppleMachine Learning EngineerSoftware Engineering FundamentalsTechnical Screen
  • A C++ internship screen exercise: read an unfamiliar class that owns a heap array and write an example program showing callers how to use it correctly. It tests code comprehension and C++ fundamentals such as RAII, deleted copy operations, move semantics, noexcept, explicit constructors and const-correctness.

    AppleSoftware EngineerSoftware Engineering FundamentalsTechnical Screen
  • A hands-on build exercise over recorded vehicle drive logs stored in MCAP, with Protobuf-encoded camera and location messages. The candidate ingests the runs, designs storage and a time index, exposes APIs to list runs and query messages by timestamp, then demos the result and explains how they worked with an AI coding assistant.

    Applied IntuitionSoftware EngineerSoftware Engineering FundamentalsOnsite
  • Given two hours, an AI coding assistant and an S3 bucket of unfamiliar vehicle log data, build a minimal 3D log playback app and then present it in 30 minutes. The exercise tests data exploration, tight scoping, verifying AI-generated code, and explaining trade-offs and future work clearly.

    Applied IntuitionSoftware EngineerSoftware Engineering FundamentalsOnsite
  • This question evaluates understanding of parallel GPU programming, deterministic reduction ordering, and numerical stability in floating-point arithmetic, within the domain of parallel algorithms, GPU/CUDA programming, and numerical computing for a Software Engineering Fundamentals / Machine Learning Engineer role.

    Applied IntuitionMachine Learning EngineerSoftware Engineering FundamentalsTechnical Screen
  • Design parsing and type-resolution boundaries for interdependent message definitions, clarifying schema versus encoded input, forward references, recursion, and validation.

    Applied IntuitionSoftware EngineerSoftware Engineering FundamentalsTechnical Screen
  • This problem tests your understanding of multi-threaded synchronization primitives, memory ordering, and circular buffer logic in a low-latency environment.

    Applied IntuitionSoftware EngineerSoftware Engineering FundamentalsTechnical Screen
  • Implement an in-memory reassembler in C that reconstructs out-of-order chunked TLV messages, validates chunk bounds and duplicates, and detects message completion.

    Applied IntuitionSoftware EngineerSoftware Engineering FundamentalsTechnical Screen
  • This problem tests the ability to design an in-memory key-value store that supports nested transactions, including atomic commits, rollbacks, and precise state management across layers.

    Applied IntuitionSoftware EngineerSoftware Engineering FundamentalsTechnical Screen
  • This question evaluates understanding of language design and implementation skills, including lexical analysis, parsing into an AST, expression evaluation with operator precedence and unary operators, variable assignment semantics, and runtime error reporting.

    Applied IntuitionSoftware EngineerSoftware Engineering FundamentalsOnsite
  • Implement and analyze a quadtree-based search algorithm that locates all vehicles on a 2D grid using a Boolean square-scan API.

    Applied IntuitionSoftware EngineerSoftware Engineering FundamentalsTechnical Screen
  • Implement size and field-type lookups over a simplified protobuf-style schema in which messages embed other messages, then write the parser that builds the schema from raw text. Tests schema data modeling, handling of nested, cyclic and unknown message references, clear error behavior, and robust parsing of proto-like definitions.

    Applied IntuitionSoftware EngineerSoftware Engineering FundamentalsTechnical Screen
  • Scale a working small-grid cellular-automaton fire-spread simulation to a dense multi-million-cell board that no longer fits in memory, by computing each generation with a three-row sliding window read from one file and streamed into another. Tests memory estimation and disk-backed algorithm redesign without changing the core update rule.

    Applied IntuitionSoftware EngineerSoftware Engineering FundamentalsTechnical Screen
  • Write a per-tick controller that fires a drone's thruster so it clears wall openings on unseen, randomized canyons. Tests modeling deterministic physics, depth-limited lookahead search, and choosing a horizon that generalizes.

    AqrData ScientistSoftware Engineering FundamentalsOnline Assessment
  • Build an autopilot for a Flappy Bird-style game that decides on every step whether the bird should flap so it flies through pipe gaps whose heights vary across unseen maps. Tests modeling the game's physics, planning ahead under a time budget, collision handling, and generalizing beyond a single map.

    AqrData ScientistSoftware Engineering FundamentalsOnline Assessment
  • Write a controller that decides, on every tick, whether a mini-submarine should blow ballast to rise through reef-pair gaps of varying heights on unseen maps, using a short deterministic lookahead search.

    AqrData ScientistSoftware Engineering FundamentalsOnline Assessment

More topics