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 151–180 of 1189 results
- AppleMediumSoftware EngineerDesign ad click aggregator and file sync service
This question tests the ability to design a high-throughput event processing system for ad clicks and a scalable file synchronization service, focusing on data consistency, idempotency, and distributed storage patterns.
System DesignOnsiteDistributed SystemsData IngestionConsistency - AppleMediumSoftware EngineerDesign an Accurate Click Aggregator
This question tests the ability to design a high-throughput, fault-tolerant system for tracking ad clicks while ensuring exactly-once processing or deduplication at scale.
System DesignTechnical ScreenScalabilityData PipelineDeduplication - AppleHardSoftware EngineerDesign and scale a Yelp-like platform
This question evaluates system design and engineering skills including data modeling, indexing, geospatial and full-text search, caching, replication and sharding for a high-scale reviews platform, together with key generation, storage layout, redirects, rate limiting and analytics for a URL-shortening service, probing the ability to balance scalability, consistency, availability, and operational complexity. It falls under the System Design / Distributed Systems / Databases domain and is commonly asked to assess architectural reasoning and trade-off analysis, testing both conceptual high-level design and practical implementation considerations such as performance, fault tolerance, and operational constraints.
System DesignOnsite - AppleHardSoftware EngineerDesign video platform and catalog system
This System Design question evaluates proficiency in large-scale architecture, API and storage design, data modeling, scalability and consistency trade-offs, ingestion and indexing pipelines, CDN and caching strategies, and operational concerns such as reliability, observability, security, and multi-region deployments across video-sharing and marketplace catalog domains. It is commonly asked in technical interviews to test architectural judgment and trade-off reasoning, emphasizing high-level practical application and operational planning rather than low-level implementation details.
System DesignOnsite - AppleHardSoftware EngineerImplement a robust REST API method
Implement a robust REST API method 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 - AppleHardSoftware EngineerMigrate a monolithic wallet to microservices
This question evaluates a candidate's ability to design and plan a safe, compliant migration of a high-scale digital wallet from a monolithic architecture to microservices, covering service decomposition, data ownership, transactional consistency, security and key management, compliance, observability, and deployment strategies.
System DesignTechnical Screen - AppleMediumSoftware EngineerObject-Oriented Design: Hotel Room Booking System
Tests object-oriented domain modeling, interval-overlap availability logic, and concurrency control strategies to prevent double bookings in a hotel reservation system.
System DesignOnsiteObject-Oriented DesignConcurrencyDatabase Design - AppleMediumSoftware EngineerRedesign an Existing Relational Database to Reduce Read Latency
A staff-level screen question about an existing service whose normalized relational database serves slow reads: explain how you would change the data model and read path to cut read latency. Tests diagnosis of slow reads, trade-offs between read cost, write cost and data freshness, and safe rollout on a live system.
System DesignTechnical Screen - AppleMediumSoftware EngineerScale Digit-Square Convergence Requests
This question evaluates a candidate's competency in designing scalable, low-latency distributed services that combine algorithmic optimization and caching to handle massive request volumes for a numerical convergence operation.
System DesignTechnical Screen - Applied IntuitionMediumSoftware EngineerDesign Sensor Data Processing With AI-Assisted Implementation
Design an end-to-end ingestion, validation, and storage pipeline for high-frequency sensor telemetry from autonomous vehicle fleets. The focus is on handling raw versus derived data, schema modeling, fast time-range queries, and robust validation.
System DesignTechnical ScreenTime SeriesData PipelineIoT & Robotics - Applied IntuitionHardSoftware EngineerDesign a job scheduler
This question evaluates competency in designing scalable, durable distributed job schedulers, covering multi-tenant architecture, queuing and metadata persistence, execution semantics, idempotency, retries/dead-lettering, failure handling, and observability.
System DesignOnsite - Applied IntuitionMediumSoftware EngineerDesign a real-time 3D playback system for recorded vehicle logs
Design a system that plays recorded vehicle log data back as a smooth, seekable 3D scene without downloading the whole log first. It tests chunked, time-indexed streaming, prefetching and caching around the playhead, aligning data streams of different rates, and handling heavy sensor data at scale.
System DesignOnsite - Applied IntuitionMediumSoftware EngineerDesign a simulator to replay left-turn videos
This question assesses the ability to architect a high-throughput simulation system capable of retrieving, syncing, and replaying synchronized sensor data streams for autonomous vehicle testing.
System DesignOnsiteData StreamingStorage OptimizationLatency - Applied IntuitionHardSoftware EngineerDiscuss productionizing event-timeout detector
Discuss productionizing event-timeout detector 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 - Applied IntuitionHardSoftware EngineerWalk through a recent project design
This question evaluates the candidate's proficiency in end-to-end system design—covering requirements definition, architecture and component design, data modeling, scalability, trade-off analysis, and operational readiness—within the System Design domain for a software engineer role.
System DesignTechnical Screen - ApplovinHardSoftware EngineerDesign UberPool matching with zero Manhattan detour
This question evaluates system design and algorithmic reasoning for constrained spatio-temporal matching and routing, covering Manhattan-distance geometry, matching algorithms, API and data model design, and scalability/consistency considerations.
System DesignTechnical Screen - AsanaMediumSoftware EngineerDesign a Collaborative Todo List
This question evaluates system-design skills for building real-time collaborative applications, covering data modeling, read/write paths, real-time synchronization, concurrent edits and reordering semantics, permission models, and consistency trade-offs within the System Design domain.
System DesignOnsite - 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 - 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 - 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
Apple
Applied Intuition
Asana
Atlassian