How hard is the Adobe Software Engineer interview?

Candidates most commonly rate the Adobe Software Engineer interview as medium, based on 201 reported interviews. About 11% of candidates who interview go on to receive an offer.

How many rounds is the Adobe Software Engineer interview process?

Candidates report 4 stages: Online Assessments, Technical Conversations, Onsite Interview, and Managerial Discussions. The interview process section above breaks down what each stage covers.

How much does a Software Engineer at Adobe make?

Reported compensation for Software Engineer roles at Adobe ranges from roughly $110k base to $340k total per year, varying by level, team, and location.

What topics come up in the Adobe Software Engineer interview?

Adobe Software Engineer interviews most often cover Data Structures & Algorithms (DSA), System Design, JavaScript, Low-Level Design (LLD), and Power BI, based on topics extracted from real candidate reports.

What questions does Adobe ask Software Engineer candidates?

Recent candidates report questions like "Reverse a Singly Linked List" and "Using SQL to Extract Insights". The question bank above tracks 20 questions for this role, ranked by how often they come up in Adobe interviews.

AdobeSoftware Engineer

Updated Jun 16, 2026

Adobe Software Engineer Interview Experiences 2026

Real, anonymous reports from people who interviewed for Software Engineer at Adobe, newest first and distilled into what to expect across the loop.

Get your personalized Adobe Software Engineer prep plan

Answer 3 quick questions and we will build a free study plan with the exact topics and questions to focus on.

Build my free plan

Hot & recentNewest first

2 months ago

Average Positive Raipur, Chhattisgarh

The process moved through five stages: resume selection, a reasoning and aptitude test, two technical interviews, and then an HR interview. I made it through the four earlier steps, but the HR round ended the process for me.

My first real technical experience combined coding with a recruiter screening, and then the next technical step was split into multiple parts with different interviewers. The coding segment was manageable, and I was able to talk through my approach, fix small syntax issues, and run the solution correctly within the time limit. What threw me off was the code review portion—there were serious scheduling hiccups: the interviewer joined late from the wrong location, and a login issue on the provided machine stole even more time. That left me with only a short window to work through a multi-page codebase, so I wasn’t able to finish the review the way I wanted. The final technical portion itself felt smooth by comparison.

2 months ago

My Adobe process for an SDE 2 role was surprisingly compact. I had an online assessment first, and then a virtual interview over Zoom.

The OA included two easy-to-medium DSA questions, and I honestly don’t remember the exact prompts anymore. After that, I met with an interviewer virtually for a set of three more DSA questions that ranged from easy up to hard. The format was a bit unusual: I needed to write code that was compilable on a document, and there weren’t test cases to run against. A lot of the emphasis felt like accuracy and clarity—getting the solution into a working form while explaining my reasoning.

Unlock every Software Engineer interview experience

Real Software Engineer interview experiences

Difficulty, sentiment and outcomes
New reports added every week

See all experiences

Share your interview experience

Interviewed here recently? Add yours to help the next candidate. You'll appear as Anonymous.

What to expect

Distilled from the reports

Interview Structure & Stages

The interview process typically consists of multiple stages, including an online assessment, technical interviews focusing on data structures and algorithms (DSA), and a final HR or behavioral interview. Candidates should expect a structured sequence that may vary in length and complexity.

Interview stagesOnline assessmentHR round

Technical Interviews Focus

Technical interviews often emphasize DSA questions, with a mix of coding challenges and theoretical discussions about programming fundamentals, JavaScript, and system design. Candidates should prepare for both practical coding tasks and conceptual questions related to their technical knowledge.

DSAJavaScriptSystem design

Coding Environment & Format

Candidates may encounter unique coding environments, such as writing code in documents without immediate testing capabilities, which can increase pressure. Familiarity with the expected format and clarity in communication during coding is crucial.

Coding formatNo test casesCommunication

Behavioral & Values Assessment

Behavioral interviews focus on past experiences, teamwork, and conflict resolution, often requiring candidates to articulate their thought processes and how their experiences align with the company's values. Candidates should be prepared for a conversational style that connects personal experiences to the role.

Behavioral questionsSTAR methodValues alignment

Logistics & Scheduling Challenges

Candidates have reported logistical issues, such as scheduling conflicts and unclear timelines, which can affect their overall experience and performance. It's advisable to clarify scheduling details early and be prepared for potential disruptions.

Scheduling issuesLogisticsTimeline clarity

Overall Difficulty & Candidate Experience

The overall difficulty of the interview process can vary, with some candidates finding it challenging due to the breadth of topics covered and the pressure of technical assessments. Candidates should be ready for a demanding experience that tests both technical skills and communication abilities.

Difficulty levelCandidate experiencePressure