Product Intern applicants have rated the interview process at Adobe with 3 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 67% positive. To compare, the company-average is 59.7% positive. This is according to Glassdoor user ratings.
Candidates applying for Product Intern roles take an average of 1 day to get hired, when considering 3 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 Product Intern according to 3 Glassdoor interviews include:
Skills test: 50%
Phone interview: 50%
Here are the most commonly searched roles for interview reports -
1 hour interview, asked a medium level DSA question (eg deleting node from a BST), followed by discussion of resume and OOPs related questions. The discussion for OOPs was centered around Java-related rules,
I applied through college or university. I interviewed at Adobe (Noida) in Aug 2025
Interview
It was mostly data structures and algorithm, two questions one from arrays and one from tree, then discussed about projects.
Achivements I had like hackathon and stuff and then I asked about their work and what they are working on.
I applied through college or university. I interviewed at Adobe (Campus) in Aug 2025
Interview
Project Discussion:
The interviewer started by asking about my projects.
The main focus was on backend development, specifically:
How I obtained the data
How I classified and analyzed the data
Technical Questions:
Data Structures & Algorithms:
Two questions were given, covering topics such as:
Greedy algorithms
Dynamic programming
Trees
Coding Skills:
I was asked to write pseudocode, perform dry runs, and discuss time complexity of the solutions
Binary Search:
Discussed the requirements and implementation of binary search
Core Programming Concepts:
Questions on basic OOP concepts were asked, including:
Classes and objects
Encapsulation, inheritance, polymorphism
Interview questions [1]
Question 1
ne main thing they focused on seems to be your backend project work—specifically how you obtained, classified, and analyzed the data. Everything else (DSA questions, OOP concepts, time complexity, binary search) was more like a follow-up to test your technical depth and problem-solving skills.