Adobe Software Development Engineer (SDE) interview questions
based on 19 ratings - Updated Jun 15, 2026
Averageinterview difficulty
Mostly positiveinterview experience
How others got an interview
40%
Employee Referral
Employee Referral
40%
Campus Recruiting
Campus Recruiting
20%
Applied online
Applied online
Interview search
19 interviews
Viewing 1 - 5 of 19 Interviews
Adobe interviews FAQs
Software Development Engineer (SDE) applicants have rated the interview process at Adobe with 3.6 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 57% positive. To compare, the company-average is 59.9% positive. This is according to Glassdoor user ratings.
Candidates applying for Software Development Engineer (SDE) roles take an average of 11 days to get hired, when considering 7 user submitted interviews for this role. To compare, the hiring process at Adobe overall takes an average of 31 days.
Common stages of the interview process at Adobe as a Software Development Engineer (SDE) according to 7 Glassdoor interviews include:
Skills test: 44%
Phone interview: 44%
One on one interview: 11%
Here are the most commonly searched roles for interview reports -
The interview process consisted of three main rounds. The first round included a challenging LeetCode problem followed by a recruiter screening. The second round was split into three parts with different interviewers: a front-end expertise assessment, a code review, and a standard technical interview.
Unfortunately, the code review was a frustrating experience due to logistical issues. The interviewer arrived late and was in a different room, which, combined with a login issue on the computer they provided, left only 15 minutes for the assessment. The interviewer mentioned it was his first time conducting this type of interview and apologized for the rushed environment. Because of the severe time constraint, I wasn’t able to finish reviewing the multi-page codebase. In contrast, the final technical part went smoothly; the coding problem was manageable, and I successfully communicated my thought process, corrected minor syntax issues, and ran the code perfectly within the time limit.
Although I did not advance to the final managerial round, this remains my dream company. While it was upsetting to have technical and scheduling failures on their end compound the stress of a high-stakes interview, I hope to have another opportunity to interview and work there in the future.
Interview questions [1]
Question 1
How do I handle the different screen ratios for various devices when creating a web application?
Interview process was good almost 1hr interview i had but somehow didnt get the offer and it was so frustrating but what can we do about it communication skills matter even if you do both code
It was an online interview. The interviewer was friendly. I didnt know few things but he generously answer and told me the approach. Asked few DSA coding questions nd yes thats it