Adobe Software Engineer Interview Experience (2026) - Real-time Log Analytics & Make Array Unique, Offer

Adobe uses HackerRank with two problems and the style is a weird blend of logic puzzles and classic data-structure work. I got a simplified file-path canonicalization problem (think LeetCode 71 with relative navigation plus symlinks) and a binary-tree balance check. Both solvable, both boring if you have seen them before. The platform itself is the more annoying part because the editor is finicky on long lines and the test runner is slower than LeetCode.

[[problem/597?company=18|Sum of All Addition Expressions]] is a flavor of the string-parsing style Adobe likes, even though it was not the specific problem I got.

Virtual Onsite (5 rounds)

Round 1: Coding — Make Array Unique with Minimum Cost

Problem: Given an array of integers with duplicates, make all elements distinct by incrementing duplicates. Minimize the total cost of increments.

I sorted the array and did a single pass, bumping any element that was less than or equal to the previous unique value. Every bump contributes to the cost. O(N log N) for the sort, O(N) for the sweep. The interviewer asked about the case where N is in the tens of millions and sorting is the bottleneck; I talked through a counting-sort variant when the value range is bounded, and a bucket-plus-overflow structure when it is not.

[[problem/599?company=18|Make Array Unique with Minimum Cost]] is the exact problem.

Round 2: Coding — Maximize Work Schedule Bonus

Problem: Given a list of shifts with variable bonus values and overlap constraints, pick a non-overlapping subset that maximizes total bonus.

Weighted interval scheduling. Sort by end time, binary search for the latest compatible shift, and DP where dp[i] = max(dp[i-1], bonus[i] + dp[compatible(i)]) . I wrote it iteratively with a BST over end times to find the predecessor quickly. The interviewer asked for the recursive memoized version as a follow-up and then for the proof that greedy by value alone fails. I worked a small counterexample on the side panel.

[[problem/596?company=18|Maximize Work Schedule Bonus]] maps directly.

Round 3: System Design — Commenting Service for Creative Cloud

Problem: Design a collaborative comment and annotation system for files shared inside Creative Cloud.

I started with the user-facing flow: users attach comments to anchors inside a document (coordinates for images, time offsets for video). Storage was a comments table partitioned by document ID, with a secondary index by anchor. Real-time fan-out for live editing was a WebSocket server with per-document channels backed by Redis pub-sub. The interviewer pushed on conflict resolution when two users comment on the same anchor simultaneously and on how to expire orphaned comments when anchors move. I described a vector-clock style reconciliation and a background GC job for orphans.

Round 4: OOD — Design a PDF Rendering Pipeline

Problem: Object-oriented design for a PDF renderer that handles text, images, forms, and annotations.

I sketched a PDFDocument containing ordered Page objects, each holding a list of PageElement subclasses (TextElement, ImageElement, FormElement, AnnotationElement). The renderer was a visitor over the element tree with a RenderContext carrying the current page state. The interviewer pushed on how to plug in a new element type without changing existing code, and I walked through the visitor plus a registry of element-to-renderer handlers. We finished with a discussion of how to handle memory for giant scanned PDFs.

Round 5: Behavioral with Hiring Manager

Standard behavioral set. Tell me about a time you had a cross-team conflict. Tell me about a project that slipped. What do you do when you disagree with a code review. The hiring manager was particularly interested in how I had dealt with legacy code because the team he was staffing was about to own a large migration. No coding this round.

Result

Offer came nine days after the onsite. Adobe pays below the top FAANG bands but the work-life balance is genuinely better and the document-tooling problem space is underrated. I negotiated a modest sign-on and equity bump and accepted.

Tips

1. Adobe's HackerRank round has unusual breadth. The prep guides say 60-plus questions in the pool and that number is credible. You cannot memorize it; drill the pattern families (string manipulation, tree recursion, interval problems) until the scaffolding is automatic.
2. Read the Adobe careers blog for product context. The hiring manager rounds will probe how much you understand about Document Cloud or Creative Cloud. A ten-minute read before the loop pays dividends.
3. Expect OOD on every senior-plus loop. Most SWE blogs gloss over this but Adobe's onsite almost always includes one pure OOD round. Practice the Visitor, Strategy, and Registry patterns cold.
4. System design rounds bias toward creative tools. Comment systems, collaboration primitives, and rendering pipelines show up more than URL shorteners or chat apps.
5. Adobe values the "engineering judgment" answer. When pushed, do not retreat into handwaves. They would rather hear you talk about tradeoffs out loud, including ones you do not have perfect answers for.
6. Behavioral with the hiring manager carries real weight. I watched two friends wash out here despite clean coding rounds. Have three stories about legacy-code wrangling or migration work ready to go.