Adobe Senior Computer Scientist Interview Experience and HLD DSA Questions
Interview Experience
Recently I gave Adobe Sr CS interview and here are the question. Round1
HLD Design a Book my show kind of Application. Detail discussion around the DB selection with the concurrency control. Also dis
Full Details
Recently I gave Adobe Sr CS interview and here are the question. Round1
HLD Design a Book my show kind of Application. Detail discussion around the DB selection with the concurrency control. Also discussed about the low latency for the booking and confirmation. I believe I had explained all the deep dives. Round2 DSA: Interview said she will ask 2 DSA question to evaluate. asked me https://leetcode.com/problems/heaters/description/ Started with brute force approach but could come to the final solution covering all the edge cases and whole one hour we discussed one question only
Verdict
Rejected
About This Question
This is a candidate experience report from a adobe interview for a swe role (senior level) during the system design round reported in 2026.
It covers the following topics: Os, System Design .
Topics
More Adobe Interview Questions
About Adobe Interview Reports
This question was reported by a candidate who interviewed at Adobe. LeakCode aggregates interview reports from 10+ sources, including 1Point3Acres, Glassdoor, LeetCode Discuss, Blind, Reddit, Indeed, and Nowcoder. Each report is translated where necessary, deduplicated against existing entries, and tagged by company, role, round type, and reporting date.
Use this question as one calibration data point, not a memorization target. Companies typically rotate their question pools every 2-4 months; the exact wording of a 2024 question may differ from what you encounter today. The underlying pattern, difficulty level, and follow-up depth at Adobe are the higher-signal extractions to take from this report.
For broader preparation context, the Adobe interview process typically includes a recruiter screen, one or two technical phone screens, and a 4-5 round on-site loop covering coding, system design (at L4+ levels), and behavioral. Reports tagged on LeakCode show the round-by-round distribution and typical difficulty calibration. To browse questions filtered by round type and seniority, use the company hub linked above.
How To Practice This Type of Question
Solve similar problems on LeetCode under timed conditions (25-35 minutes per medium difficulty). The goal is pattern recognition: recognize the underlying technique (sliding window, two-pointer, BFS, memoized recursion, etc.) within 60-90 seconds of reading. Strong candidates verbalize their hypothesis out loud before coding, then iterate based on feedback. Weak candidates dive into implementation immediately, lose time on the wrong approach, and run out of time for follow-ups.
Companies update their question pools every 2-4 months. The exact wording of any given question may have been retired by the time you interview. Focus your prep on the pattern, not the specific problem. The patterns that appear in Adobe reports consistently are the ones worth investing in; one-off niche problems are not.
During Your Adobe Round
Apply the standard interview round template: clarify requirements (2-3 minutes), state your approach out loud and confirm direction with the interviewer (3-5 minutes), code with narration (15-25 minutes), test with concrete examples including edge cases (5 minutes), discuss optimization or trade-offs if time permits (5 minutes). This template is universally accepted across FAANG and adjacent companies; deviating from it produces weaker interviewer feedback signal.
The single most predictive failure mode in Adobe reports tagged "no hire": not asking clarifying questions. Interviewers are explicitly trained to weight this. Strong candidates ask 3-5 clarifying questions even on problems that look obvious; weak candidates dive into code immediately. The clarifying-question check is often the first signal recorded in the interviewer's written notes.