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 541–570 of 1189 results
- LinkedInMediumSoftware EngineerDesign a Global Calendar Service
This question evaluates competence in designing scalable, time-zone aware calendaring systems, covering API and data model design, recurrence representation, daylight saving semantics, conflict detection, storage strategy, and consistency trade-offs.
System DesignOnsite - LinkedInHardSoftware EngineerDesign a Multi-Region Malicious-IP Detection System
Design a globally distributed, low-latency edge security service that detects and blocks malicious IP addresses across regions, featuring decentralized evaluation, asynchronous intelligence sharing, and rapid false-positive rollback.
System DesignTechnical ScreenDistributed SystemsSecurityLow Latency - LinkedInMediumSoftware EngineerDesign a Personalized Job Suggestions Page for LinkedIn Members
Design the LinkedIn page that suggests open jobs to a signed-in member, from candidate retrieval and filtering to ranking, pagination and serving. Tests large-scale recommendation architecture, freshness for new and closed postings, feedback logging, latency budgets and graceful degradation.
System DesignOnsite - LinkedInMediumSoftware EngineerDesign a Ranked Social Feed with Hybrid Fan-Out
Design a scalable, read-heavy ranked social feed supporting millions of users. The system must balance fan-out-on-write and fan-out-on-read while ensuring read-your-own-writes consistency for authors.
System DesignOnsiteDistributed SystemsCachingSocial Network - LinkedInMediumSoftware EngineerDesign a Scalable Calendar Service
Design calendar event storage and time-range reads, explain concurrent edits and scaling, and clarify recurrence and notification requirements.
System DesignOnsite - LinkedInMediumSoftware EngineerDesign a Scalable Error Message Counting Service
Design a service that receives application error messages and reports how often each distinct error occurs over time. It tests grouping varied messages into error signatures, absorbing bursty write traffic during incidents, time-windowed aggregation, top-error queries and count accuracy under failures.
System DesignOnsite - LinkedInEasySoftware EngineerDesign a Top-K Ranking Service
This question tests the ability to design a distributed, low-latency system capable of maintaining and serving a real-time 'Top-K' list of items (e.g., trending hashtags) across a massive stream of incoming data.
System DesignOnsiteScalabilityStreamingCaching - LinkedInMediumSoftware EngineerDesign a Top-K search words service
The question evaluates understanding of scalable, low-latency analytics and search-event systems, including high-throughput event ingestion, Top-K aggregation across all-time and sliding windows, normalization/deduplication trade-offs, and multi-region consistency considerations.
System DesignTechnical Screen - LinkedInMediumSoftware EngineerDesign a company-wide monitoring system
This question evaluates skills in designing large-scale observability and monitoring systems, covering telemetry collection (metrics, logs, traces), high-throughput ingestion, storage and scaling strategies, alerting pipelines, and operational trade-offs like cardinality, retention, and backpressure.
System DesignOnsite - LinkedInMediumSoftware EngineerDesign a malicious-URL checking service using an isMalicious API
This question tests your ability to design a high-throughput, low-latency URL reputation checking service, focusing on caching strategies, scalability, and system resilience.
System DesignOnsiteCachingScalabilityResilience - LinkedInMediumSoftware EngineerDesign a metrics platform without alerting
This problem tests your ability to design a high-throughput time-series metrics system, focusing on ingestion pipelines, efficient storage schema for multi-dimensional data, and query performance.
System DesignOnsiteTime-SeriesScalabilityData Modeling - LinkedInHardSoftware EngineerDesign a scalable calendar system
This question evaluates a candidate's ability to design a scalable, multi-tenant calendar platform, testing competencies in distributed systems architecture, API and data-model design for events/recurrence/time zones, access control and privacy boundaries, notification pipelines, and external integration.
System DesignOnsite - LinkedInMediumSoftware EngineerDesign a scalable key-value store
This system design question evaluates expertise in distributed systems and scalable storage architecture within the System Design domain, focusing on data partitioning, replication, durability, consistency models, and low-latency operation.
System DesignOnsite - LinkedInMediumSoftware EngineerDesign an exception monitoring system with top‑K
This question tests the ability to design a high-throughput distributed system capable of ingesting, deduplicating, and aggregating exception logs to provide real-time top-K statistics.
System DesignOnsiteStreamingScalabilityData Modeling - LinkedInMediumSoftware EngineerDesign an in-memory key-value store using maps
This question evaluates skills in in-memory data modeling, concurrent access control, time-complexity reasoning for expected O(1) operations, and storage engine considerations such as durability, compaction, and TTL when restricting indexing to map/dictionary primitives.
System DesignOnsite - LinkedInHardSoftware EngineerDesign distributed parallel job processing
This question evaluates understanding of distributed systems architecture, parallel job scheduling, fault tolerance, coordination and concurrency control, API and data model design, idempotency, observability, and capacity planning for multi-tenant, heterogeneous workloads.
System DesignTechnical Screen - LinkedInMediumSoftware EngineerDesign scalable job scheduler and query dashboard
This question evaluates a candidate's system design skills in building a scalable, fault-tolerant job scheduling system and efficient near-real-time time-window querying, focusing on distributed scheduling, storage and indexing strategies, partitioning, and reliability guarantees, and is commonly asked to probe trade-offs among scalability, latency, availability, and consistency. Belonging to the System Design domain, it examines both high-level architectural thinking and practical application-level considerations such as data modeling, query/index design, operational concerns like hot partitions, and horizontal scaling.
System DesignOnsite - LinkedInMediumSoftware EngineerExplain database transactions and ACID
This question evaluates a candidate's understanding of database transactions including ACID properties, isolation levels (read uncommitted, read committed, repeatable read, serializable), common anomalies (dirty reads, non-repeatable reads, phantom reads), MVCC, and commit/rollback semantics, testing competency in transactional correctness and concurrency control. Commonly asked in System Design and database contexts because it probes reasoning about data integrity, visibility, and durability under concurrent workloads, and it tests both conceptual understanding of transactional guarantees and practical application of isolation behavior in relational database systems.
System DesignTechnical Screen - LinkedInHardSoftware EngineerReduce Stale Listings in a Job Marketplace
Design an auditable staleness-detection and remediation engine for a global job marketplace that aggregates heterogeneous signals, enforces graduated interventions, and supports low-latency employer appeals.
System DesignTechnical ScreenDistributed SystemsEvent-Driven ArchitectureAudit Logging - LinkedInEasySoftware EngineerReview a Web Application Architecture
This question evaluates system design competencies such as scalability, reliability, fault tolerance, database architecture, load balancing, external dependency management, and observability, and is categorized under System Design.
System DesignTechnical Screen - LinkedInMediumSoftware EngineerScale a NoSQL Key–Value Store to One Million QPS
Design a distributed, highly available NoSQL key-value store capable of serving 1M QPS across 50 million key-value pairs with low p99 latency.
System DesignOnsitesystem-designnosqldistributed-systems - Lowe'sHardSoftware EngineerExplain cloud computing fundamentals
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 Explain cloud computing fundamentals states assumptions, handles edge cases, explains trade-offs, and shows how to validate the result clearly.
System DesignTechnical Screen - Luma AIMediumSoftware EngineerBuild Collaborative Document Editing Shared by People and AI Agents
A take-home asks you to build collaborative document editing in which people and AI agents edit the same document, then defend its scaling limits and add approval, audit history and selective revert for agent edits. Tests concurrency control, real-time sync, anchoring slow agent edits, attribution, and prototype scoping.
System DesignOnsite - Luma AIMediumSoftware EngineerBuild a Scalable Text-to-Speech Service Prototype, Then Defend and Extend It
An 8 to 12 hour take-home asks you to build a scalable text-to-speech service with AI coding agents, then defend its trade-offs and scaling limits in a product review and plan a new customer requirement. Tests 0-to-1 scoping, streaming and batch synthesis design, capacity reasoning, and estimation and roadmap skills.
System DesignOnsite - LyftMediumSoftware EngineerDesign One-to-One Messaging Across Multiple Devices
Tests the ability to architect a real-time, one-to-one messaging system supporting multi-device synchronization, push notifications, idempotent message delivery, and reliable cursor-based history pagination.
System DesignOnsitesystem-designdistributed-systemsmessaging - LyftMediumSoftware EngineerDesign a Distributed Web Crawler
Design a distributed web crawler that starts from seed URLs and scales across roughly 1,000 heterogeneous worker devices. The question covers canonical URL identity and crawl scope, a durable partitioned frontier with atomic deduplication, host-level politeness and robots handling, lease-based coordination with at-least-once delivery and idempotent effects, fetch/parse/storage schemas, near-duplicate detection, recrawl and backpressure, capacity estimation, safety controls, and the enqueue/status/results API. A common Lyft software engineer onsite system design question testing distributed-systems judgment, correctness under retries, and operational thinking.
System DesignOnsite - LyftHardSoftware EngineerDesign a Donation Platform
A Lyft onsite system design question: design an online donation platform that processes one-time and recurring donations through an external payment provider while guaranteeing no lost, duplicated, or wrong-amount charges. It tests payment-flow correctness, idempotency, append-only ledgers, reconciliation, data modeling, consistency tradeoffs, and scaling for donation spikes.
System DesignOnsite - LyftEasySoftware EngineerDesign a Fault-Tolerant Wikipedia Archiver
Design a fault-tolerant system that archives Wikipedia and keeps versioned content current using one reliable coordinator, many unreliable untrusted workers, and durable blob storage. Cover policy-aware discovery, large-frontier deduplication, task assignment, result validation, safe publication, failure recovery, and recrawling.
System DesignOnsite - LyftMediumSoftware EngineerDesign a One-to-One Chat Service
Design a durable one-to-one chat service with conversation ordering, idempotent sends, offline replay, and secure multi-device delivery.
System DesignOnsite - LyftMediumSoftware EngineerDesign a Wiki Crawler That Keeps Every Stored Page at Most Five Days Stale
A system design question about crawling and storing all the content of a wiki while keeping every stored page no more than five days stale. It tests capacity estimates, the crawl frontier and scheduling, change detection, storage of page versions, politeness limits, failure recovery, and monitoring of freshness.
System DesignOnsite
LinkedIn
Luma AI
Lyft