Real, anonymous reports from people who interviewed for Software Engineer at Adobe, newest first and distilled into what to expect across the loop.
I applied cold for an Adobe Software Engineer Intern position and got pulled into a virtual loop scheduled for November 2024. The process felt straightforward compared to the usual multi-step loops I’d heard about, and it stayed focused on the internship hiring motion rather than stretching into a long marathon.
My Software Engineering interview at Adobe ended up being a bit unusual. I went through three rounds, and despite what the job description suggested, there were no coding questions at all across the loop.
The interview process at Adobe typically consists of multiple rounds, often structured with a mix of technical and behavioral assessments. Candidates have reported loops ranging from a single round to as many as five, with timelines varying from a few days to several weeks.
Candidates can expect a strong focus on data structures and algorithms (DSA), with many interviews incorporating coding problems, often in a LeetCode-style format. Some candidates noted a shift towards system design and architecture discussions in later rounds.
Behavioral interviews are a significant part of the process, where candidates discuss their past experiences and how they align with Adobe's values. These discussions often follow technical rounds and are aimed at assessing cultural fit and communication skills.
The interview formats can vary, with some candidates experiencing live coding sessions, take-home assessments, or a mix of both. The take-home assessments may allow for external tools like AI, which can influence the approach to problem-solving.
Candidates have reported mixed experiences regarding feedback and communication throughout the process, with some feeling a lack of clarity or closure after interviews. The waiting period for decisions can also be a source of frustration.
Candidates suggest focusing on both technical fundamentals and the ability to articulate problem-solving approaches. Practicing coding under time constraints and preparing for behavioral questions that tie back to past experiences can be beneficial.
