Initially when I applied , I thought of a huge brand name and good challenging work, Here the story goes they will call for written test, conduct 4-5 rounds of interview and at the end when it comes to salary they give like peanuts, Well its not there fault too. the company is just 3-4 billion dollar company and recently they were in news as there profit has reduced because of compensation factor Which make us to think a lot. What made me angry was the fact that they should have discussed the salary thing in the first place rather than wasting individual time. If you are thinking of its like a google company think again, (Seeing there revenue number its not at all justified), its better to go for yahoo,linkedin and amazon and many other more in the market better than adobe. This is the feedback from my friend, Mostly adobe wants all the IIT folks to work in there company for campus recruit, but here is the catch, they will give you 10lac pa , but out of that 30-40% is stock option which u can encash after 3-4 years. I remember my company,which recruiting from IIT-mumbai and they pay much better than adobe and no trap like stock option

I had a friend refer me for this position. The HR team did not ask for my availability before scheduling the interviews and directly sent invites for the first two rounds on the same day they were conducting interview drive. I requested a reschedule because the timing did not work for me, but I received a one-line response saying they could not reschedule the interview. I still decided to attend because Adobe is a well-regarded company. Round 1 focused on DS/Algo, coding proficiency, and problem-solving fundamentals. It went quite well. The interviewer was patient, helpful, and asked relevant questions. Round 2 was supposed to focus on frontend concepts, problem solving, deep JavaScript knowledge, browser APIs, UI architecture, and hands-on coding. However, the interviewer instead asked a system design problem. The experience was confusing because the interviewer herself did not seem fully clear on the expectations. During requirement clarification, she initially mentioned that the task was only to build a real-time collaborative text editor. Later, the requirements shifted toward designing a drawing/design tool with real-time collaboration, and several points that were explicitly stated as “out of scope” were suddenly brought back into scope. Overall, it felt like the interviewer already had a specific solution in mind, possibly from a predefined reference, and was only looking to hear that exact approach. It ended up being a frustrating experience because the interview focus kept changing and the expectations were unclear.