These are HLD questions of the kind Adobe actually asks — the patterns reported from Adobe's AI-engineering rounds, where design trade-offs, scale and failure modes matter as much as definitions. Treat this page as a mock interview: say every answer out loud before revealing it. If one surprises you, the lesson behind it is linked at the bottom.
Adobe HLD concept questions
Adobe interviewers (Creative Cloud-adjacent teams) often ask about designing storage for large user-generated assets (PSD/video project files, sometimes gigabytes each) that need to sync across a user's devices. What's the core architecture?
Asked in
Adobe's APIs (e.g. for image/video processing) often rate-limit by compute cost, not just request count — a request to process a 4K video should count for more than a request to resize a thumbnail. How would you design this?
Asked in
Adobe HLD applied & hands-on questions
Adobe-style: a user requests a video export that takes 2 minutes to process. Design the request flow so the user's app isn't stuck waiting on a single HTTP request for 2 minutes.
Asked in
How to use this page: Adobe rarely asks something you've never seen — they ask a standard HLD concept and then push one level deeper ("why?", "what would you do if..."). Master the concept in the HLD course lessons, and the follow-up stops being scary.
Keep practising: Caching Explained, Databases at Scale, Design a URL Shortener and Interview Framework cover what most Adobe HLD rounds test.