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 931–960 of 1208 results

  • Extend an expense rules engine with validated AND/OR/NOT expression trees, typed leaf operators, explicit missing-field semantics, and explainable evaluation.

    RipplingSoftware EngineerSoftware Engineering FundamentalsTechnical Screen
  • An object-oriented design and coding question about a logger with independent handlers that strip a configured string, truncate, uppercase or store messages, followed by a case-sensitive any-keyword search over stored logs. It tests extensible design patterns, indexing for fast search, and scaling a logger to production volume.

    RipplingSoftware EngineerSoftware Engineering FundamentalsTechnical Screen
  • Implement a task scheduler that manages parent-child task dependencies, applies custom multi-field tie-breaking priority rules, supports filtering, and handles dependency cycles.

    RipplingSoftware EngineerSoftware Engineering FundamentalsTechnical Screen
  • This question evaluates a candidate's ability to design and implement a RESTful web service, covering HTTP API design, CRUD operations, data modeling and persistence choices, input validation, pagination/sorting, and basic testing and documentation practices.

    RipplingSoftware EngineerSoftware Engineering FundamentalsOnsite
  • This question evaluates proficiency in network programming, HTTP/1.1 protocol parsing, concurrent server design, request routing and security (including path traversal protection), observability, testing, and graceful shutdown using only the language standard library.

    RipplingSoftware EngineerSoftware Engineering FundamentalsOnsite
  • Order CI build jobs so that prerequisites come first, more urgent jobs go earlier, filtered-out jobs are skipped without breaking ordering through them, and jobs can be grouped into parallel waves. Tests Kahn's algorithm, deterministic tie-breaking, cycle reporting, and turning a detailed spec into code.

    RipplingSoftware EngineerSoftware Engineering FundamentalsTechnical Screen
  • Senior backend coding question: process a batch of scheduler tasks by removing duplicates on description and due date, dropping completed tasks, sorting by priority, and placing each subtask directly after its parent. It tests clarifying ambiguous policies, orphan and cycle handling, O(n log n) design, and verified use of an AI coding assistant.

    RipplingBackend EngineerSoftware Engineering FundamentalsOnsite
  • Design an algorithm to filter a hierarchy of tasks where any task failing a predicate—or having any ancestor that fails or is missing—is excluded along with all its descendants, running in linear time and preserving original order.

    RipplingSoftware EngineerSoftware Engineering FundamentalsTechnical Screen
  • A two-part coding question on a poker-like card game: compare two five-card hands by a fixed type priority with ties broken card by card, then find the best and worst complete hands when the last cards are unknown. Tests hand classification, ordering keys, testing discipline and search over completions.

    RipplingSoftware EngineerSoftware Engineering FundamentalsTechnical Screen
  • Design an in-memory class that tracks hourly pay for theater stagehands across logged call times, keeps running cost totals, and settles wages up to a cutoff without ever paying the same minute twice.

    RipplingSoftware EngineerSoftware Engineering FundamentalsTechnical Screen
  • Coding question that asks for a task scheduler built from a detailed specification: tasks must come after their dependencies, follow priority or importance rules, and pass configurable filters. It tests topological ordering, deterministic tie-breaking, cycle handling and turning many interacting requirements into correct, tested code.

    RipplingSoftware EngineerSoftware Engineering FundamentalsTechnical Screen
  • Implement an in-memory ledger for hourly tutors that logs sessions, reports total and outstanding amounts in O(1), and invoices work up to a cutoff without ever billing the same minute twice. Tests stateful design, exact arithmetic, and handling of partial and late-logged work.

    RipplingSoftware EngineerSoftware Engineering FundamentalsTechnical Screen
  • This problem tests your ability to design a fluent interface (method chaining) that manages an internal queue of asynchronous operations to ensure tasks execute sequentially.

    RobinhoodFrontend EngineerSoftware Engineering FundamentalsTechnical Screen
  • Clarify friendship and money-transfer requirements, separate graph reachability from accounting, and reason about a conditional implementation and invariants.

    RobinhoodSoftware EngineerSoftware Engineering FundamentalsOnsite
  • Implement an algorithm to compute direct and total downstream referral counts for every employee in a directed graph that may contain duplicates, converging paths, and cycles.

    RobinhoodSoftware EngineerSoftware Engineering FundamentalsOnsite
  • Design an iOS timer around explicit state transitions, clock-based elapsed time, main-thread UI updates, callback ownership, and lifecycle behavior.

    RobinhoodSoftware EngineerSoftware Engineering FundamentalsTechnical Screen
  • This question tests your knowledge of secure microservice communication, the lifecycle management of sensitive credentials, and the operational procedures for mitigating security breaches.

    RobinhoodSoftware EngineerSoftware Engineering FundamentalsOnsite
  • Tests your ability to present a deep dive into an impactful software project you led or contributed heavily to, emphasizing architectural trade-offs, personal ownership, failure modes, and measurable outcomes.

    RobinhoodSoftware EngineerSoftware Engineering FundamentalsOnsite
  • Practice a project deep dive covering architecture, personal ownership, implementation decisions, validation, outcomes, and lessons learned.

    RobinhoodSoftware EngineerSoftware Engineering FundamentalsOnsite
  • Tests Jetpack Compose UI state management, coroutine lifecycle side-effects with LazyListState, and defensive hex color string parsing.

    RobinhoodAndroid EngineerSoftware Engineering FundamentalsTechnical Screen
  • Tests graph construction, topological sorting (Kahn's algorithm or DFS), cycle detection, and deterministic tie-breaking for modular dependency resolution.

    RobinhoodSoftware EngineerSoftware Engineering FundamentalsTechnical Screen
  • This question evaluates a candidate's ability to write SQL for temporal state reconstruction, including correct joins on composite keys, interpreting edit/audit logs, and reasoning about inclusive/exclusive timestamps.

    RobinhoodData EngineerSoftware Engineering FundamentalsTechnical Screen
  • Tests your ability to architect a scalable, accessible React component with dynamic state, efficient win-detection logic for large grid sizes, and robust handling of prop updates.

    RobloxFrontend EngineerSoftware Engineering FundamentalsTechnical Screen
  • A frontend coding question asking for a traffic light that cycles through its colors automatically, built with plain HTML, CSS, and JavaScript and no framework. It tests state machine design, timer management and cleanup, efficient DOM updates, accessibility, and how to test time-based UI code.

    RobloxSoftware EngineerSoftware Engineering FundamentalsOnsite
  • Implement an in-memory, rolling-window rate limiter supporting per-client limits, precise boundary expiration, and stale state cleanup.

    RobloxSoftware EngineerSoftware Engineering FundamentalsTechnical Screen
  • Design an in-memory profiler aggregator to track sampled call stacks across threads, returning the most frequent stacks globally and per-thread with deterministic tie-breaking.

    RobloxSoftware EngineerSoftware Engineering FundamentalsTechnical Screen
  • This question tests fundamental knowledge of thread-safe collections in Java and core distributed systems architectural patterns, specifically partitioning strategies.

    RokuBackend EngineerSoftware Engineering FundamentalsOnsite
  • Design a bot that plays Minesweeper and maximizes its chance of winning. The question tests how the bot turns revealed numbers into constraints, finds cells that are certainly mines or certainly safe, estimates the risk of every hidden cell when it must guess, and keeps each move fast and measurable over many games.

    RunloopSoftware EngineerSoftware Engineering FundamentalsTechnical Screen
  • Design an object-oriented cash register that manages multi-lot product inventory using FIFO accounting, executes atomic multi-item sales, and accurately tracks realized gross profit.

    SIG (Susquehanna)Software EngineerSoftware Engineering FundamentalsOnsite
  • Tests a candidate's ability to identify and fix critical C++ resource management bugs, specifically shallow copies leading to double-free errors and object slicing caused by improper pass-by-value semantics with polymorphic types.

    SIG (Susquehanna)Software EngineerSoftware Engineering FundamentalsOnsite

More topics