Real, anonymous reports from people who interviewed for Software Engineer at Adobe, newest first and distilled into what to expect across the loop.
After applying through the portal for an MTS 2 backend Java role, I got a callback and ended up with a single interview round. The whole session felt like a tight technical sweep across the fundamentals I had highlighted on my resume. I was asked to solve classic DSA-style problems, including merging overlapping intervals and a deep dive into an LFU cache concept. I also got pulled into object-oriented programming topics—covering the main pillars of OOP and general OOP concepts.
I interviewed for the MTS 2 role and the journey ended up being four rounds total. The first two rounds were technical, and they bounced between my work experience, design-style questions, and DSA. I kept feeling like they were trying to connect what I’d done before to how I’d think through problems, rather than treating it as purely theoretical.
The interview process typically involves multiple rounds, often starting with an online assessment followed by technical interviews and a final managerial round. Candidates can expect a structured sequence, with some reporting four to five distinct stages including technical and behavioral evaluations.
Technical interviews heavily emphasize data structures and algorithms (DSA), with many candidates facing LeetCode-style problems that range from easy to hard difficulty. Expect to demonstrate coding skills alongside reasoning and problem-solving approaches during these sessions.
Behavioral interviews often focus on team fit and past experiences, with interviewers looking for coherent narratives about candidates' work history and problem-solving approaches. Candidates should prepare to discuss their experiences in a way that aligns with the company's values.
Throughout the interview process, candidates are evaluated not just on technical correctness but also on their ability to clearly communicate their thought processes and reasoning. This aspect is crucial for success, especially in technical discussions.
Initial interactions with recruiters can vary significantly, with some candidates experiencing a mix of technical and behavioral questions. A strong recruiter interaction can set a positive tone for the rest of the process, while a poor experience may hinder candidates' confidence.
Candidates often report a lack of clear feedback or abrupt rejections, even after performing well in technical rounds. The outcome can depend on various factors, including team fit and the competitive nature of the applicant pool.