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 1081–1110 of 1208 results

  • Write a configurable linter for restaurant-listing CSV rows that reports missing fields, length violations, whole-word banned terms, and too-low or too-high word overlap between fields after normalization. Tests robust CSV parsing, text normalization, rule-driven design and edge-case thinking.

    StripeSoftware EngineerSoftware Engineering FundamentalsTechnical Screen
  • A staff-level Stripe code review exercise: review a realistic production pull request, decide what blocks the merge, and write the actual comments. It tests review prioritization, scrutiny of tests and failure modes, comment severity labeling, and how you adapt the delivery of feedback for early-career versus senior authors.

    StripeSoftware EngineerSoftware Engineering FundamentalsOther
  • A programming exercise that turns customers' subscription records into a chronological schedule of lifecycle emails, such as a welcome email at the start and an expiration email at the end. It tests date arithmetic, deterministic ordering of same-day emails, and a rule design that makes new email types easy to add.

    StripeSoftware EngineerSoftware Engineering FundamentalsTechnical Screen
  • Clarify proximity metrics, destination eligibility, tie rules, and capacity before designing a request-routing algorithm.

    StripeSoftware EngineerSoftware Engineering FundamentalsOnline Assessment
  • Build a validator for a CSV of company records that flags missing fields, values outside length limits and forbidden words, then measures word overlap between fields while ignoring case, spacing and words such as LLC. It tests robust CSV parsing, text normalization, rule-driven design and edge-case testing.

    StripeSoftware EngineerSoftware Engineering FundamentalsTechnical Screen
  • This question evaluates object-oriented design, system extensibility, interface and responsibility definition, and integration with external services in the context of a recommendation engine.

    StubHubSoftware EngineerSoftware Engineering FundamentalsTechnical Screen
  • This question evaluates debugging and implementation skills across frontend-backend interaction, including authentication/configuration, client-side state management, streamed response handling, request cancellation, and reasoning about API payload contracts.

    SupioSoftware EngineerSoftware Engineering FundamentalsTechnical Screen
  • This problem tests your ability to design a thread-safe allocator that manages a finite resource pool under high concurrency, focusing on atomic updates and race condition prevention.

    TargetBackend EngineerSoftware Engineering FundamentalsOnline Assessment
  • This problem tests your ability to design a robust, deterministic data cleaning pipeline that handles input parsing, data validation, and precision-safe numeric handling.

    TeslaData EngineerSoftware Engineering FundamentalsTechnical Screen
  • Tests multi-threaded synchronization, atomic operations, barrier synchronization, and coordinated condition handling across concurrent threads.

    TeslaSoftware EngineerSoftware Engineering FundamentalsOnsite
  • Implement a non-mutating JSON merge utility with recursive object handling, configurable array merge strategies, and an extensible design for custom merge policies.

    TeslaSoftware EngineerSoftware Engineering FundamentalsTechnical Screen
  • Tests your ability to clearly explain distributed systems architecture, justify technology selections (such as Go, Java, Spark, and Elasticsearch), and discuss operational bottlenecks and fault tolerance from real production experience.

    TeslaSoftware EngineerSoftware Engineering FundamentalsHR Screen
  • This question evaluates understanding of reliability and runtime fundamentals in backend engineering, covering competencies such as fault tolerance, end-to-end request lifecycles, API gateway degradation, storage engine selection for search, and the distinction between compilers and interpreters.

    TeslaBackend EngineerSoftware Engineering FundamentalsOnsite
  • Tests your ability to write resilient HTTP client logic in Python using requests, distinguishing between retryable and non-retryable errors, handling rate limits, and safely parsing JSON.

    TeslaSoftware EngineerSoftware Engineering FundamentalsTechnical Screen
  • Explain reduce semantics, derive ordered map and filter with a reducer, and compose them over table rows while handling empty input and accumulator costs.

    TeslaSoftware EngineerSoftware Engineering FundamentalsTechnical Screen
  • Implement an invariant analysis engine to identify recurring bugs across production incident traces, pin down the earliest violating step, and flag failures recurring above a frequency threshold.

    TeslaSoftware EngineerSoftware Engineering FundamentalsHR Screen
  • This problem tests your ability to manipulate array elements in-place while managing constraints on stability and the treatment of special values like zeros.

    TeslaSoftware EngineerSoftware Engineering FundamentalsOnsite
  • Tests depth-first search with backtracking on a 2D grid, covering cycle prevention, branching path exploration, termination criteria, and lexicographical ordering.

    TeslaSoftware EngineerSoftware Engineering FundamentalsOnsite
  • Processes scheduled onto a Linux server cluster randomly crash while being created, and the interviewer plays the system while you hunt for a planted cause. It tests Linux troubleshooting commands for processes, memory, network and disk I/O, and reasoning about how cron jobs spawning tens of thousands of threads can break other workloads.

    TeslaSoftware EngineerSoftware Engineering FundamentalsOnsite
  • This question tests your systematic approach to troubleshooting production incidents in distributed architectures using metrics, distributed tracing, structured logs, and change audit trails.

    TeslaSoftware EngineerSoftware Engineering FundamentalsHR Screen
  • Assess Spring IoC, AOP, JDBC, Security 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.

    TestGorillaSoftware EngineerSoftware Engineering FundamentalsOnline Assessment
  • Add a click listener to a button evaluates requirements, assumptions, structured reasoning, trade-offs, and verification in a realistic interview setting. A strong answer states assumptions, handles edge cases, explains trade-offs, and shows how to validate the result clearly.

    The Trade DeskSoftware EngineerSoftware Engineering FundamentalsTechnical Screen
  • Evaluates API and in-memory data structure design, search and sorting semantics, user-associated operations, versioning/audit history, data normalization, and edge-case handling within the Software Engineering Fundamentals domain.

    The Trade DeskSoftware EngineerSoftware Engineering FundamentalsOnline Assessment
  • This problem tests foundational software engineering knowledge across Python internals, database indexing, and testing strategy through a multi-part conceptual assessment.

    TikTokSoftware EngineerSoftware Engineering FundamentalsTechnical Screen
  • This question assesses the ability to structure a comprehensive automated regression suite for a RESTful API, focusing on test case selection, validation strategies, and maintenance.

    TikTokSoftware EngineerSoftware Engineering FundamentalsTechnical Screen
  • This question assesses the candidate's deep understanding of C++ memory management, the runtime implementation of polymorphism, and the performance characteristics of standard containers.

    TikTokSoftware EngineerSoftware Engineering FundamentalsTechnical Screen
  • This question evaluates a candidate's understanding of Java concurrency primitives and concurrent collection implementations, focusing on thread-safety, synchronization mechanisms, lock-free techniques, and blocking versus non-blocking queue behavior.

    TikTokSoftware EngineerSoftware Engineering FundamentalsTechnical Screen
  • Tests understanding of the TLS handshake, asymmetric vs. symmetric cryptography in HTTPS, certificate authority verification, and the mechanics of forward secrecy versus intercepting HTTPS proxies.

    TikTokSoftware EngineerSoftware Engineering FundamentalsTechnical Screen
  • This question evaluates understanding of modern NLP model architecture and evaluation metrics, specifically Transformer block components, key distinctions between GPT and BERT including pretraining objectives and usage, and precision/recall interpretation, testing competencies in deep learning architecture knowledge, model selection reasoning, and metric-based evaluation within the Software Engineering Fundamentals domain for a Machine Learning Engineer role. It is commonly asked because it probes both conceptual understanding of architectures and pretraining paradigms and practical application of performance trade-offs—assessing conceptual understanding alongside practical application in threshold-based precision versus recall decisions.

    TikTokMachine Learning EngineerSoftware Engineering FundamentalsTechnical Screen
  • Implement and compare key design patterns evaluates requirements, scale assumptions, API/data design, architecture, trade-offs, failure modes, and rollout in a realistic interview setting. A strong answer states assumptions, handles edge cases, explains trade-offs, and shows how to validate the result clearly.

    TikTokSoftware EngineerSoftware Engineering FundamentalsTechnical Screen

More topics