I interviewed with Adobe as part of the SheCodes hiring program. After clearing the Online Assessment, I was shortlisted for the Technical Round (TR).
The TR started with a brief introduction. Since my preferred language is Java, the interviewer asked about core OOP concepts, including compile-time vs runtime polymorphism and their implementation in Java. We discussed method overloading vs overriding.
The round then moved to Data Structures. I was asked questions on Linked Lists, including a problem that required the Fast and Slow Pointer technique, and an Array-based Two Pointer problem, which I coded during the interview. There was also discussion on applications of Trees and when to use different data structures. Towards the end, I was asked about Operating System concepts, including the thread life cycle.
After this, I had an HR round focused on behavioral questions and Adobe’s core values. The discussion was mainly around teamwork, handling challenges, cultural fit, and long-term goals.
Overall, it was a positive experience. The interviewers were friendly, and the process focused on fundamentals and problem-solving approach rather than tricky questions.
Interview questions [1]
Question 1
implement compile-time vs runtime polymorphism in Java, linked list slow and fast pointers related question
3 Rounds 1-Recruiter 2-HM 3- 3 team members including VP of Product It was not bad as it was for an internship so you will be find as long as you study your basic PM info
I applied through university. I interviewed at Adobe (Chandigarh) in Nov 2025
Interview
great experience the oa was quite competitive, as more than 700 + students appeared and only 14-15 got selected. In the OA, they asked 2 questions: one was a medium-level string-based question and other was a medium- to hard-level graph question. I faced difficulty because of integer overflow, i.e., the " long long" error.
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,