So yeah, I interviewed for Adobe SDE Fresher last year through campus.

First round was an online test. Honestly, not scary but not free either. There were 2 coding questions. One was pretty straightforward strings + hashmap, something like longest substring / frequency stuff. The second one was trickier — needed sliding window + careful edge cases. If you rushed, you were dead. MCQs were basic CS: OS, DBMS, OOPS. Nothing out of syllabus. If you’ve done decent LeetCode, you’d clear this.

After that, got shortlisted for interviews.

Interview 1 (technical) started chill. The interviewer asked about my resume, then jumped straight into a DSA problem. It was a medium-hard, not some CP shit, just logic-heavy. I first gave brute force, then optimized. I got stuck once, but I kept explaining what I was thinking. That helped a LOT. He didn’t care that I didn’t get it in one shot — he cared that I was thinking properly. We discussed time complexity, space optimization, and a couple of edge cases.

He also asked a couple of follow-ups like “what if input size is huge?” and “can you reduce memory?”. No random trivia.

Interview 2 was different. Less DSA, more thinking. He asked me to design a very simple system — nothing fancy. Then some OOPS questions, like why use interface, real-life example of inheritance, stuff like that. Also asked how HashMap works internally. If you’ve actually coded and not mugged theory, you’re fine.

Final round was managerial / HR-ish. Very conversational. Asked about a project I liked, a time I messed up, how I deal with pressure, why Adobe. No trick questions. They just wanted to see if I’m normal and not a robot.

Overall vibe:
Adobe doesn’t try to scare you. They don’t expect genius. They expect clear thinking, decent DSA, and good communication.

If you’ve done 300–400 LC problems properly, Adobe is very doable. People fail mostly because they go silent, panic, or try to act oversmart.