practice a little every day, paws crossed ♡
System Design 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 181–210 of 1311 results
- AsanaMediumSoftware EngineerDesign a Real-Time Like Counter for Collaborative Tasks
This problem tests the ability to design a distributed, high-concurrency counter system that maintains strict consistency while ensuring low-latency updates for collaborative task management.
System DesignTechnical ScreenDistributed SystemsRedisConcurrency - AsanaMediumSoftware EngineerDesign a Twitter-like microblogging service
This question evaluates system design competencies including scalable architecture, data and API modeling, feed generation trade-offs, storage and caching strategies, consistency expectations, and operational concerns such as rate limiting, abuse mitigation, and observability.
System DesignTechnical Screen - Assorted HealthMediumSoftware EngineerDesign a Conversational Flight Search, Booking, and Price-Tracking Service
Design a conversational flight service that turns vague travel intent into grounded multi-leg search, safe booking, and useful price alerts. Cover clarification, authoritative supplier data, repricing, idempotent payment flows, shared price watches, quotas, privacy, and graceful degradation at large scale.
System DesignOnsite - AtlassianMediumSoftware EngineerCompute top-N posts in a workspace
This question evaluates skills in designing scalable, low-latency analytics and aggregation systems, covering event tracking, time-windowed ranking, stream processing, storage trade-offs (OLTP vs OLAP), caching, API design, and handling late or duplicate events.
System DesignOnsite - AtlassianMediumSoftware EngineerDesign Monitoring and Reliability for 99.99% Availability
Design a comprehensive observability and reliability framework to guarantee 99.99% availability for a multi-tenant cloud collaboration platform. The design must cover Service Level Indicators (SLIs), Service Level Objectives (SLOs), automated burn-rate alerting, dependency fault isolation, and chaos recovery testing.
System DesignOnsiteSREObservabilityDistributed Systems - AtlassianMediumSoftware EngineerDesign Scalable Product Backends
This problem tests your ability to design a high-throughput, distributed task management system, focusing on data modeling, concurrency control, and scalability for collaborative features.
System DesignOnsiteScalabilityDatabase ModelingConcurrency - AtlassianEasySoftware EngineerDesign a Data Stream Processor
This question tests your ability to design a scalable, reliable stream processing pipeline capable of ingesting, filtering, and persisting real-time events while managing system state.
System DesignTechnical ScreenDistributed SystemsData PipelinesScalability - AtlassianHardFrontend EngineerDesign a Fast Product Search Page: Search Input over an Unbounded Catalog Grid
A front-end system design question about a product search page with a search input above a grid of results drawn from a catalog of unbounded size. It probes the component tree, where search state should live, and how the candidate keeps typing responsive and results fast when the result set can never be loaded all at once.
System DesignTechnical Screen - AtlassianEasySoftware EngineerDesign a Rate Limiter Service: Components, Scaling and Precision Trade-offs
A three-part system design question about a rate limiter service: the components a simple limiter needs, how to scale it as users grow and what breaks, and how to make limits more precise. It tests shared counters, atomic updates, hot callers, failure policy and the accuracy trade-offs between rate limiting algorithms.
System DesignTechnical Screen - AtlassianMediumSoftware EngineerDesign a Social-Media Comments and Notifications System
Design social comments with APIs, indexed pagination, durable notifications, retry deduplication, and measured read/write scaling for hot posts.
System DesignOnsite - AtlassianMediumSoftware EngineerDesign a distributed rate limiter service
This question tests the ability to design a scalable, low-latency distributed rate-limiting service that handles high-concurrency requests across multiple microservices.
System DesignTechnical ScreenDistributed SystemsCachingScalability - AtlassianMediumMachine Learning EngineerDesign a scalable chatbot platform
This problem tests your ability to architect a scalable, stateful chatbot system that integrates RAG (Retrieval-Augmented Generation) with low-latency conversational requirements.
System DesignOnsiteLLMRAGScalability - AtlassianHardSoftware EngineerDesign a scalable tagging system
This question tests a candidate's ability to design scalable data models and distributed indexing strategies for a multi-tenant tagging system. It evaluates system design competency across storage, caching, sharding, and consistency trade-offs — core skills assessed in senior software engineering interviews.
System DesignTechnical Screen - AtlassianMediumSoftware EngineerDesign a simple greeting-card web app
This question assesses the ability to design a scalable, functional MVP for a greeting-card service, focusing on user-generated content storage and retrieval.
System DesignTechnical ScreenAPI DesignDatabase ModelingScalability - AtlassianMediumSoftware EngineerDesign a tagging system and REST APIs
This question evaluates a candidate's ability in RESTful API design, data modeling, concurrency control, idempotency, pagination, and indexing/search strategies for a multi-tenant tagging system. It is commonly asked in the system design category to assess architectural decision-making and both conceptual understanding and practical application of endpoints, schema, and edge-case handling.
System DesignOnsite - AtlassianMediumSoftware EngineerDesign an access control system (RBAC + resource-based)
This question evaluates a candidate's ability to design a scalable authorization system incorporating RBAC and resource-based ACLs, testing competencies in access-control models, data schema design, policy evaluation, API design, caching strategies, and audit logging.
System DesignOnsite - AtlassianMediumSoftware EngineerDesign an image crawler for unlimited URLs
This question evaluates a candidate's ability to design scalable, fault-tolerant distributed systems for web crawling, covering competencies in concurrency, queueing and scheduling, deduplication, storage architecture, and observability.
System DesignOnsite - AtlassianMediumSoftware EngineerDiagnose why a scaled system became slow
Tests systematic incident triage, observability strategies, and root-cause analysis across distributed tiers (caching, connection pools, databases, compute) when a scaled service suffers severe latency degradation.
System DesignTechnical Screensystem-designobservabilityperformance-debugging - AtlassianHardSoftware EngineerEnsure thread-safe updates to org hierarchy
Ensure thread-safe updates to org hierarchy 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 - AtlassianMediumFrontend EngineerFront-End Design of an Emoji Picker with a Search Field
A candidate-driven front-end system design discussion about an emoji picker with a search field. It tests how a candidate scopes the component, models and loads the emoji catalog, ranks search results, keeps a grid of thousands of emoji fast, and supports keyboard and screen-reader users.
System DesignTechnical Screen - AtlassianMediumSoftware EngineerStore a hierarchy and return all children
This question evaluates understanding of hierarchical data modeling, REST API design, database schema choices (e.g., adjacency list vs alternatives), and systems-level concerns like scalability, pagination for large subtrees, and cycle prevention.
System DesignOnsite - AttentiveMediumSoftware EngineerDesign Broadcast Scheduling APIs
This question evaluates a candidate’s ability to design scalable, reliable broadcast and scheduling systems, covering API design, data modeling, distributed scheduling, delivery semantics, idempotency, retries, and operational fault-tolerance.
System DesignTechnical Screen - AttentiveMediumSoftware EngineerDesign Robust Large-Input Processing
This question evaluates debugging and root-cause analysis, memory management, streaming/chunked data processing (including correctness across chunk boundaries), and system reliability aspects such as observability, testing, and recovery for large-input backends.
System DesignTechnical Screen - AttentiveMediumSoftware EngineerDesign Storage for a Flexible Metrics Monitoring System
This problem tests the ability to design a time-series storage system by balancing read/write throughput, data retention policies, and query performance at scale.
System DesignTechnical ScreenTime-SeriesDatabaseData Modeling - AttentiveMediumSoftware EngineerDesign a Data Puller for a Third-Party API Capped at 3 Requests per Second
Design a service that pulls and syncs data from a third-party API that enforces a hard limit of 3 requests per second. It tests global rate limiting across distributed workers, retry and backoff behavior, incremental sync with checkpoints, and prioritizing work when demand exceeds the request budget.
System DesignTechnical Screen - AttentiveHardSoftware EngineerDesign a Kafka-Fed Event Analytics System for Long-Term Analysis
A system design exercise to build an event analytics system that ingests very high-volume, concurrent event streams from Kafka and stores them for long-term analysis. It tests Kafka topics, partitions, consumers and consumer groups, delivery guarantees, and durable, queryable storage design.
System DesignOnsite - AttentiveMediumSoftware EngineerDesign a Product Catalog Ingested From Full Retailer Snapshots With Admin Overrides
A system design question about a product catalog built from full retailer snapshot files, with 50,000 retailers, 11,000 read queries per second and a 400 ms latency target. It tests snapshot diffing, recovery from a mistaken upload, admin overrides that survive retailer updates, scaling ingestion, and observability.
System DesignOnsite - AttentiveMediumSoftware EngineerDesign a Real-Time Ad Serving System with Budgets and Impression Tracking
Design a real-time ad serving system that picks an eligible ad for each ad request, returns it within a tight latency budget, and records impressions and clicks for billing. Tests candidate retrieval and ranking, campaign data freshness, budget enforcement across many servers, and a deduplicated event pipeline.
System DesignOnsite - AttentiveMediumSoftware EngineerDesign a Reliable Third-Party Data Ingestion Service
Design an extensible, resilient data ingestion service capable of extracting data from heterogeneous third-party APIs while managing rate limits, pagination state, schema drift, and fault recovery.
System DesignOnsiteData IngestionDistributed SystemsRate Limiting - AttentiveMediumSoftware EngineerDesign a Scalable Catalog Service
Design a high-throughput, read-heavy catalog service supporting draft/publish lifecycles, item versioning, search projections, and resilient rollback mechanisms.
System DesignOnsiteCQRSE-CommerceCaching
Asana
Atlassian
Attentive