Object-Oriented and Low-Level Design

Most Adobe loops at the mid level and above carry a round the rest of big tech treats as optional. It is a dedicated object-oriented and low-level design round, run as live machine-coding on a shared screen. You get a real-world thing to model, and over forty-five to sixty minutes you build the classes on screen. The entities, the interfaces between them, who owns what, and the methods other code calls. It is graded on the engineering quality of what you type rather than on a green test sheet.

Three things decide this round, and they are the same three every time. Clean class structure that follows SOLID, so each class has one job and the design extends without surgery. The right design pattern in the one spot a requirement varies. And the Adobe twist that separates this loop from a generic OOD round: thread-safety. The interviewer finishes the happy path, then asks what happens when two threads touch your structure at the same instant. A design that looks correct on screen but corrupts its own state under two concurrent calls is the exact failure this round is built to surface.

The Adobe angle

Adobe is one of the few companies that runs OOD and low-level design as its own scored round rather than folding it into system design. The classics show up by name, parking lot and elevator and a card game among them, and so does a distinctive concurrency flavor: a thread-safe cache, a read-write lock, a thread-safe message box. The grading rubric is consistent. Clean classes that follow SOLID, a pattern named where it belongs, and a real story for what happens under concurrent access. Adobe also values readable, partial, correct code over a sprawling design that does not run, so build the smallest version that works and narrate every decision as you go. The smallest thing that runs wins.