Got the offerSDE 3 at Adobe
- Difficulty
- Process took
- 1-2 Weeks
- Rounds
- 4
- Format
- Remote
- Applied via
- Job Portal
How it went
- Your calmness is part of your evaluation.
- In behavioral rounds, don’t just say what you built.
- Talk about what changed because you built it, reduced latency, better retention, fewer outages, etc.
What they would tell you
- Your calmness is part of your evaluation.
- In behavioral rounds, don’t just say what you built.
- Talk about what changed because you built it, reduced latency, better retention, fewer outages, etc.
How to prepare
- For each DSA or system design problem you solve, don’t stop at the optimal code ask yourself, what would I change if latency became critical? What if memory was limited?
Round by round
- 1
DSA Round 160 min
This round focused on problem-solving skills and coding efficiency. I was given two medium-level problem which similar like these.
- 2
Low Level Design60 min
I was asked to design the LLD for a Chess game. We discussed key classes like Board, Piece, Player, and GameManager, along with their data members and methods. I wrote the class structure and method signatures, focusing on making the design clean and extensible like handling different piece movements and turn logic. We also talked briefly about managing game state and checking for valid moves.
- 3
HM Round90 min
The round began with the interviewer asking me about the most critical project I’ve worked on, and we briefly discussed the technical decisions and challenges involved. Then came a few theory-based C++ questions , things like null pointers, dangling pointers, void pointers, memory management, and smart pointers. It was more of a rapid-fire style, testing my understanding of C++ fundamentals. Next, I was given some small code snippets and asked to predict the output, followed by a couple of debugging questions. Also, I was given two problems
- 4
Director Round60 min
The round started with a behavioral question around my past projects. We then shifted to a problem-solving discussion. Instead of directly giving me the LRU Cache problem, the interviewer presented a real-world scenario involving memory constraints and asked me how I would design a solution. We discussed various approaches, and I proposed using the LRU caching technique.
What came up
A candidate-reported account, lightly edited. Interview processes change by team and date.