Katkat

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 361–390 of 1189 results

  • DoorDashHardSoftware Engineer
    Design Real-Time Driver Pay Aggregation

    This question evaluates competence in designing scalable, fault-tolerant streaming systems and implementing correct time-windowed aggregation logic, testing skills in distributed systems, stream processing, and data correctness; it belongs to the system design domain and streaming/real-time data engineering and spans both conceptual architectural thinking and practical application-level concerns. It is commonly asked to probe reasoning about correctness under at-least-once delivery and messy inputs (out-of-order, duplicate, late, or malformed events), operational resilience, and trade-offs between throughput, latency, and auditability in production-scale pipelines.

    System DesignTechnical Screen
  • DoorDashHardSoftware Engineer
    Design a 3-day donation platform

    This question evaluates competency in designing scalable, highly available payment-enabled distributed systems, including skills in traffic spike handling, idempotency and reconciliation, real-time totals and leaderboards, latency and throughput planning, and compliance/privacy considerations.

    System DesignOnsite
  • DoorDashMediumSoftware Engineer
    Design a Customer Review Page

    This question tests the ability to design a scalable review system capable of handling high-write volume, media storage, and efficient retrieval with pagination.

    System DesignTechnical ScreenAPIDatabaseScalability
  • DoorDashMediumSoftware Engineer
    Design a Donation Service with Reliable Payment and Payout Tracking

    Design donation collection and charity payouts with a PSP, idempotent state transitions, durable ledger records, asynchronous provider events, and reconciliation.

    System DesignOnsite
  • DoorDashMediumSoftware Engineer
    Design a Donation System for a Three-Day Fundraising Campaign

    Design a donation system for a fundraising campaign that runs for exactly three days, where donors choose a charity, pay through a payment processor and see running totals. It tests payment idempotency and reconciliation, handling a time-boxed traffic burst, avoiding write hotspots on totals, and fraud protection.

    System DesignOnsite
  • DoorDashMediumSoftware Engineer
    Design a Food Item Review and Customer Reward System for a Delivery App

    A DoorDash system design prompt to build a food item review system for a delivery app that also rewards customers for reviewing. It tests product judgment on open questions, verified-purchase writes, cached rating aggregates, and designing a practical, abuse-resistant reward program with reliable crediting.

    System DesignOnsite
  • DoorDashMediumSoftware Engineer
    Design a Food Rating System

    This problem tests your ability to design a distributed, read-heavy rating and review system that handles high concurrency and ensures data integrity.

    System DesignOnsiteDistributed SystemsCachingAPI Design
  • DoorDashMediumSoftware Engineer
    Design a Food Review Platform

    Design a food review platform for discovery, ratings, review text, optional dish-level content, and trusted aggregates. Define entity and review contracts, search and read paths, moderation, abuse resistance, privacy, scaling, and operational recovery.

    System DesignOnsite
  • DoorDashHardSoftware Engineer
    Design a Food Review System for a Delivery App, Focused on the Database Schema

    System design question for the review feature of a food-delivery platform, where customers rate and review the food from delivered orders and others browse ratings. The focus is database schema design: tables, keys, constraints, indexes, rating aggregates, and how edits, deletes and moderation keep them correct.

    System DesignOnsite
  • DoorDashMediumSoftware Engineer
    Design a Food Review and Voting System

    Design a scalable review and voting platform for dishes and restaurants, focusing on transactional vote changes, aggregate counter consistency, hot-item read/write scaling, and stable pagination.

    System DesignOnsiteDistributed SystemsDatabasesCaching
  • DoorDashHardSoftware Engineer
    Design a Food-Item Review System

    Design an item-level review and rating platform for food delivery that handles high-throughput reads, asynchronous sentiment and moderation pipelines, and near real-time score aggregations.

    System DesignOnsiteDistributed SystemsData ModelingCaching
  • DoorDashMediumSoftware Engineer
    Design a Menu Item Review and Rating System for a Food-Delivery Platform

    A system design question on a menu review feature for a food-delivery platform, where customers rate and review the menu items they ordered. It tests requirement prioritization, detailed review schema and API design, rating aggregation, caching and moderation, and time management that still reaches a deep dive.

    System DesignOnsite
  • DoorDashHardSoftware Engineer
    Design a Multi-Service Workflow Engine

    Design a resilient, distributed workflow orchestration engine capable of executing multi-step business processes across heterogeneous services with strict guarantees around durability, idempotency, and failure recovery.

    System DesignOnsiteDistributed SystemsSaga PatternWorkflow Engine
  • DoorDashEasySoftware Engineer
    Design a Real-Time Monitoring System

    This problem tests your ability to design a high-throughput observability pipeline capable of ingesting, storing, and alerting on time-series metrics from a distributed fleet of services.

    System DesignOnsiteObservabilityTime-SeriesDistributed Systems
  • DoorDashMediumSoftware Engineer
    Design a Refund Workflow as a Directed Acyclic Graph

    Design a resilient, stateful workflow orchestration engine to process complex order refunds as a Directed Acyclic Graph (DAG), ensuring idempotency, crash recovery, and financial consistency.

    System DesignOnsitesystem-designdistributed-systemsworkflow-engine
  • DoorDashMediumSoftware Engineer
    Design a Review and Rating System for Food Delivery Menu Items

    Design a review and rating system for a food-delivery platform, where customers review the individual menu items they received and every menu shows each item's rating. It tests data modeling, purchase verification, incremental rating aggregation, caching for read-heavy menus, moderation, and handling bursts on popular items.

    System DesignOnsite
  • DoorDashMediumSoftware Engineer
    Design a Sliding-Hour Top-Restaurants Service

    This problem tests the ability to design a high-throughput, real-time analytics system that maintains a top-k leaderboard over a sliding time window.

    System DesignOnsiteStreamingAnalyticsDistributed Systems
  • DoorDashHardSoftware Engineer
    Design a distributed cron job scheduler

    Design a distributed cron job scheduler 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.

    System DesignOnsite
  • DoorDashMediumSoftware Engineer
    Design a donations service with 3-day rolling totals

    This question evaluates a candidate's competency in designing scalable, low-latency streaming data systems, covering event-time windowing, rolling-window aggregation, idempotency for duplicate events, late/out-of-order handling, and auditability.

    System DesignOnsite
  • DoorDashMediumSoftware Engineer
    Design a multi-channel notification system

    This System Design question evaluates distributed-systems and API-design skills—scalability, reliable fanout, multi-channel integration, delivery guarantees (retries, idempotency, deduplication), rate-limiting, subscription/preferences modeling, and observability.

    System DesignOnline Assessment
  • DoorDashHardSoftware Engineer
    Design a notification system

    This question evaluates a candidate's competency in designing scalable, reliable multi-channel notification platforms, covering distributed systems, multitenancy, API and storage schema design, queuing and retry strategies, rate limiting, observability, localization, A/B testing, and compliance considerations like GDPR.

    System DesignTechnical Screen
  • DoorDashMediumSoftware Engineer
    Design a resilient bootstrap API

    This question evaluates skills in resilient API aggregation, fault-tolerant microservice orchestration, and reliability engineering, focusing on defining API contract semantics and handling partial failures at the architectural/system-design level (service-to-service abstraction); category/domain: System Design.

    System DesignTechnical Screen
  • DoorDashHardSoftware Engineer
    Design a resilient dasher payment system

    A DoorDash software-engineer system-design interview question: design a resilient Dasher payment system that computes payouts from order lifecycle events (accept/fulfill/cancel). It spans event-driven ingestion, idempotency and exactly-once-vs-at-least-once semantics, data modeling for high write throughput and per-dasher pay-period queries, timezone/DST handling, detection and remediation of missing or out-of-order data, batch-vs-streaming reconciliation, reliability, and consistency trade-offs.

    System DesignTechnical Screen
  • DoorDashHardSoftware Engineer
    Design a scalable Instagram-like platform

    Design a scalable Instagram-like platform 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.

    System DesignTechnical Screen
  • DoorDashHardSoftware Engineer
    Design a service aggregator with robust error handling

    Design a service aggregator with robust error handling 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.

    System DesignTechnical Screen
  • DoorDashMediumSoftware Engineer
    Design an Alert Notification Service for Downstream Consumers

    Design a reliable, scalable alert and event notification delivery platform that decouples upstream producers from heterogeneous downstream consumers with independent fan-out, isolation, retries, and dead-letter handling.

    System DesignTechnical ScreenDistributed SystemsMessage QueuesEvent-Driven
  • DoorDashHardSoftware Engineer
    Design an Online Course Marketplace Review System Schema

    Design the review and rating feature of an online course marketplace where only learners who completed a course may rate it, with the discussion centered on table design, keys, constraints, and the indexes each read path needs.

    System DesignOnsitesystem-designdatabase-designschema
  • DoorDashHardSoftware Engineer
    Design an async donation payment platform

    This question evaluates a candidate's ability to design scalable, reliable payment systems and asynchronous processing pipelines, covering competencies in distributed systems, idempotency, data modeling, security/PCI compliance, retry and dead-letter strategies, and observability.

    System DesignOnsite
  • DoorDashHardSoftware Engineer
    Design consistent hashing for sharding

    This question evaluates understanding of consistent hashing, replica placement, dynamic membership, weighted load distribution, rebalancing impact, and related distributed-systems competencies for routing and sharding.

    System DesignOnsite
  • DoorDashMediumSoftware Engineer
    Design consistent hashing with a sorted map

    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 Design consistent hashing with a sorted map states assumptions, handles edge cases, explains trade-offs, and shows how to validate the result clearly.

    System DesignTechnical Screen