System Design at Adobe

Adobe's most recurring design prompt is a thread-safe configurable cache. It's an LRU or LFU store where the eviction policy is passed in at construction, and many threads read and write it at once. That prompt tells you what the round is made of. Most of what Adobe asks is general-purpose primitives: caches, file systems, typeahead, rate limiters. The bar is practical. Adobe wants a correct, clean design you can defend, and it weights that over scaling a product to a billion users.

The round is level-gated. New-grad and early-career loops usually skip system design and stay on coding and CS fundamentals. It enters the loop around the Computer Scientist level and grows from there. Senior candidates get a full design round, and Staff and above can get two. The level you land at often turns on this round, since the architecture conversation is where an otherwise strong loop gets down-leveled.

The Adobe angle

This round sets your level. It rarely sinks the hire. Forty-five minutes to an hour, an interviewer who builds alongside you instead of grilling you, and a strong bias toward a clean design over a sprawling one packed with words you cannot unpack. Adobe's loop is one of the gentler ones in big tech, and the design round keeps that tone. Gentle is not soft, though. The people grading you shipped Acrobat, Creative Cloud, and the storage underneath, so hand-waving gets spotted in seconds. Honest trade-offs move you up a level. Buzzword tours move you down one.

The shapes Adobe reaches for

Adobe design prompts cluster into four shapes, and the worked designs in this section take one each. Real-time collaboration is the domain anchor, co-editing a document the way Acrobat and Document Cloud do. A media and asset pipeline is the Creative Cloud shape, moving a large file from upload to a viewer's screen. Search and ranking covers typeahead with top-k. A distributed primitive covers the rate limiter. Three of the four are general-purpose, which matches what the round asks, and the collaborative editor is where Adobe's own domain shows up.

The Adobe angle

Three of these four prompts could come from anyone. One could not. Acrobat, Document Cloud, and the desktop apps all let people edit a shared document, and Adobe engineers have built and rebuilt the undo stack underneath that more times than they would care to count. So the editor is where domain knowledge actually pays. You model the document and sync over WebSockets. Conflicts resolve with operational transform or a CRDT, two ways to merge concurrent edits without a central lock. Undo has to stay correct while two people type at once. The cache, the typeahead, the rate limiter are primitives any shop might ask. Lead with the editor. It is the most Adobe thing in the room.

The four designs in this guide

Start with the collaborative document editor. It is the signature shape and the place where Adobe's domain knowledge counts, so it earns the lead. The other three are general-purpose primitives that the round asks just as often, each isolating a different axis.

The framework Adobe rewards

Requirements, entities, and API

Open by pinning requirements: what is in scope, what the throughput and latency targets are, and what you are deliberately leaving out. Nothing exotic about the arc, and that is the point. Spell out the read-versus-write skew, since a typeahead feed and a document-edit stream pull in opposite directions and the design lives on the heavy side. Put real numbers on the scale before you draw a single box.

From there, name the entities and write the API. Call out the objects the system turns on: a document and its edit operations, an asset and its renditions, a suggestion, a token bucket. Then write the interface as concrete endpoints you keep referring back to. On the collaborative editor this is also where you decide what an edit operation looks like on the wire, because everything downstream, sync and conflict resolution and undo, depends on that shape.

High-level design, then deep dives

Sketch the high-level topology next, walking one requirement at a time and naming the bottleneck you are punting at each step. Then go deep where the interviewer points, because the deep dives are the round. A clear high-level pass with one genuinely deep component beats a tour of six shallow ones. For the editor, that depth goes to conflict resolution and the undo stack. The asset pipeline drills transcoding and delivery, typeahead drills ranking and freshness, and the rate limiter comes down to the shared counter under concurrency.

The Adobe angle

The design round often blurs into low-level design, so be ready to reason in code. Adobe's design prompts lean practical, and several of them, the thread-safe cache especially, can turn into a request to sketch real classes and get the concurrency right. The interviewer may ask where a lock goes, how two threads avoid corrupting the shared counter, or how an undo stack stays consistent while edits arrive out of order. The System Design course drills the underlying mechanics, the queues, the consistency models, the storage engines. This section stays on the Adobe layer: the four shapes its round asks, worked end to end, with the concurrency and correctness reasoning the round keeps coming back to.