practice a little every day, paws crossed ♡
Software Engineer Interview Questions
Practice 9403 coding, system design and machine learning questions from 546 companies, sorted by role, topic and interview round. Every question has step-by-step hints, a code runner that supports 8 languages and an AI mentor; members also get the full solution walkthrough.
- 9403
- Questions
- 546
- Companies
- 11
- Topics
- 8
- Languages
Showing 961–990 of 1189 results
- RipplingHardSoftware EngineerDesign a scalable expense rules engine
This question evaluates system-design and data-modeling competency for building a scalable, multi-tenant rules engine (category: System Design) that supports per-entity and aggregate (trip-level) evaluations, backward-compatible APIs, explainability/auditability, parsing/validation of string-typed inputs, and operational concerns like determinism, idempotency, and resilience. It is commonly asked to assess trade-off reasoning around extensibility, evaluation semantics (priority, combinators, short-circuiting), aggregation and caching strategies, and API/data-model stability, with a level of abstraction that is practical application focused while requiring conceptual architectural trade-offs and concrete design details.
System DesignTechnical Screen - RipplingMediumSoftware EngineerDesign a scalable logging system
This question evaluates a candidate's ability to design scalable, reliable logging and observability infrastructure, testing competencies in distributed systems, ingestion pipelines, indexing and data modeling, storage and retention policies, multi-tenancy, and performance/reliability trade-offs.
System DesignOnsite - RipplingMediumSoftware EngineerDesign a user behavior monitoring system
This question evaluates a candidate's ability to design scalable, low-latency user event ingestion and analytics pipelines while reasoning about data storage choices and aggregate correctness trade-offs.
System DesignOnsite - RipplingHardSoftware EngineerDesign a user behavior tracking system
This question evaluates competency in designing scalable event-driven systems, covering client SDKs and server ingestion, buffering and delivery guarantees, schema evolution, storage trade-offs for interactive dashboards versus large-scale warehousing, enrichment placement, and privacy/compliance controls.
System DesignTechnical Screen - RipplingMediumSoftware EngineerDesign an ad-click aggregation and enrichment pipeline
This question evaluates system design and data engineering competencies, focusing on large-scale streaming ingestion, aggregation, enrichment joins, deduplication, and trade-offs between request batching and latency for mobile networks.
System DesignOnsite - RipplingMediumSoftware EngineerDesign centralized log ingestion and query system
This problem tests your ability to design a distributed log processing pipeline capable of handling high-throughput ingestion and efficient time-range retrieval.
System DesignTechnical ScreenDistributed SystemsLoggingData Pipelines - RipplingMediumSoftware EngineerDesign delivery driver payment system
A Rippling software-engineer system-design screen: build an in-memory, object-oriented driver-payroll service with add_driver, record_delivery, get_total_cost, pay_up_to, and get_total_cost_unpaid. It tests time-interval accounting, integer-cents money math, idempotent partial-vs-whole payout state, double-pay prevention for overlapping work, and a clean path from prototype to a transactional, indexed production design.
System DesignTechnical Screen - RipplingMediumSoftware EngineerDesign in-memory delivery billing core APIs
This problem tests your ability to design an efficient in-memory service for managing delivery billing, requiring careful consideration of concurrency, precision in monetary calculations, and optimized aggregation of billable events.
System DesignOnsiteConcurrencyData StructuresAPI Design - RipplingMediumSoftware EngineerDesign personalized news aggregation service
This question tests the ability to design a scalable news aggregation system that balances real-time content ingestion with personalized ranking for a large user base.
System DesignTechnical ScreenScalabilityDistributed SystemsRanking - RipplingHardSoftware EngineerDesign several large-scale systems
This question tests the ability to design a distributed, high-concurrency reservation system that requires strong consistency for inventory management and low-latency read access for search.
System DesignHR ScreenScalabilityConcurrencyConsistency - RipplingMediumSoftware EngineerExtend rules for trip-level aggregates and outputs
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 Extend rules for trip-level aggregates and outputs states assumptions, handles edge cases, explains trade-offs, and shows how to validate the result clearly.
System DesignTechnical Screen - RipplingEasySoftware EngineerHow would you scale rule evaluation?
This question tests your ability to design a high-throughput, rule-based processing engine that balances performance, scalability, and maintainability under high load.
System DesignTechnical ScreenRule EngineScalabilityCaching - RipplingMediumSoftware EngineerPrevent Duplicate Payments Under High Load
Design a highly reliable payment processing system that guarantees exactly-once execution and prevents duplicate charges during high-concurrency spikes and downstream failure scenarios.
System DesignOnsiteDistributed SystemsPaymentsConcurrency - RivianMediumSoftware EngineerDesign and Debug an Automotive Sensor and Camera-Blockage System
Tests your ability to design an automotive perception sensor layout and lens-blockage detection system, define safe vehicle degradation strategies, and systematically troubleshoot intermittent false-positive diagnostic alerts in the field.
System DesignTechnical ScreenAutonomous VehiclesComputer VisionEmbedded Systems - RobinhoodMediumSoftware EngineerDesign Payment Processing with Idempotency and Reconciliation
Design a resilient payment processing system that interfaces with third-party payment gateways, guarantees exactly-once execution via idempotency, manages complex payment state machines, and resolves discrepancies via reconciliation.
System DesignOnsitePaymentsIdempotencyDistributed Systems - RobinhoodMediumSoftware EngineerDesign a Cron Job Scheduler for 100K Jobs With At-Least-Once Execution
A system design question about a cron job scheduler that stores about 100,000 recurring job definitions, runs up to 10,000 jobs at once and guarantees at-least-once execution. It tests data modeling, including whether a schedule belongs on the job, finding and dispatching due jobs at scale, and failure handling with leases and retries.
System DesignOnsite - RobinhoodHardSoftware EngineerDesign a Distributed Scheduler with At-Most-Once Runs
Design a distributed scheduler around strict at-most-once run starts, durable identities, ambiguous crashes, SLA failures, queue recovery, logs, and notification outboxes.
System DesignOnsite - RobinhoodMediumSoftware EngineerDesign a Fault-Tolerant Distributed Job Scheduler
This question tests the ability to design a distributed, fault-tolerant system capable of scheduling and executing tasks reliably at scale, emphasizing durability, state management, and consistency.
System DesignOnsiteDistributed SystemsReliabilityTask Queues - RobinhoodMediumSoftware EngineerDesign a Photo Management Service
This question evaluates a candidate's ability to design scalable, reliable photo management systems, focusing on API design, storage architecture, metadata modeling, album management, and operational concerns for large numbers of users and photos.
System DesignOnsite - RobinhoodMediumSoftware EngineerDesign a Reliable Distributed Job Scheduler
This question tests the ability to design a distributed, fault-tolerant job scheduler capable of handling job lifecycle states, worker coordination, and consistent scheduling across multiple tenants.
System DesignTechnical ScreenDistributed SystemsSchedulingReliability - RobinhoodMediumSoftware EngineerDesign a Task Scheduler and Executor
Design a high-scale task scheduler for one-time, cron-like, fixed-rate, and fixed-delay execution. Cover versioned task and attempt states, due-time indexing, safe concurrent claims, retries, leases, backpressure, idempotency, recurrence semantics, and recovery.
System DesignOnsite - RobinhoodMediumSoftware EngineerDesign a distributed job scheduler
This question tests the ability to design a fault-tolerant, scalable distributed system capable of scheduling one-time and recurring background tasks with guaranteed execution semantics.
System DesignOnsiteDistributed SystemsScalabilityDatabase Design - RobinhoodEasySoftware EngineerDesign a distributed job scheduler service
This question evaluates understanding of distributed systems and microservice architecture, scheduling and timeout semantics, fault tolerance, scalability, and data modeling for job metadata, run history, and logs.
System DesignTechnical Screen - RobinhoodMediumSoftware EngineerDesign a job scheduler with SLA and logs
This question tests the ability to design a distributed, fault-tolerant job scheduling system capable of meeting strict SLAs and providing audit-ready logging.
System DesignTechnical ScreenDistributed SystemsTask QueuesScalability - RobinhoodMediumSoftware EngineerDesign a live and historical stock quote API fed by a redundant exchange trade feed
A system design question that asks for a stock quote API serving live prices at about 10 million requests per second and one-day, one-month and one-year history at about 1 million, fed by two redundant exchange trade connections. It tests sequence-number arbitration, gap replay, fan-out of live state, bar aggregation and caching at scale.
System DesignOnsite - RobinhoodMediumSoftware EngineerDesign a secure trading app on AWS
This System Design question evaluates secure cloud-based architecture on AWS, covering competencies in authentication and authorization, PII handling and auditability, API and data model design, and scalable low-latency market-data retrieval.
System DesignTechnical Screen - RobinhoodMediumSoftware EngineerDesign an At-Most-Once Job Scheduler
This question tests the ability to design a distributed, fault-tolerant job scheduler that guarantees tasks are executed no more than once, focusing on state management and concurrency control.
System DesignOnsiteDistributed SystemsConcurrencyFault Tolerance - RobinhoodMediumSoftware EngineerDesign an Order Execution System for Market and Limit Orders with Cancellation
A system design question about building the order execution system for a retail brokerage, where users place market and limit orders and can cancel them. It tests order execution flow, order state transitions with partial fills and cancels, failure handling, tracking user balances, and scaling the design to millions of orders.
System DesignOnsite - RobinhoodMediumSoftware EngineerDesign authorization and audit logging systems
This question tests your ability to design a scalable, low-latency authorization framework and a reliable, tamper-proof audit logging system for a financial platform.
System DesignOnsiteSecurityAuthorizationAudit Logging - RobloxEasySoftware EngineerDesign Multi-Dimensional Request Rate Limiting
Design a distributed, low-latency rate limiting service capable of enforcing multi-dimensional limits (e.g., by user ID, IP address, and endpoint) across a large-scale gaming platform.
System DesignTechnical ScreenDistributed SystemsRate LimitingCaching
Rippling
Robinhood
Roblox