Software Engineer 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 64% positive. To compare, the company-average is 59.8% positive. This is according to Glassdoor user ratings.
Candidates applying for Software Engineer roles take an average of 24 days to get hired, when considering 172 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 Engineer according to 172 Glassdoor interviews include:
One on one interview: 27%
Phone interview: 20%
Skills test: 15%
Group panel interview: 11%
Presentation: 9%
Background check: 7%
IQ intelligence test: 6%
Personality test: 3%
Drug test: 2%
Other: 1%
Here are the most commonly searched roles for interview reports -
Came in via acquisition, so my experience won't be relevant to Adobe. As such, I will discuss my interviews for other team members and support from Adobe HR. Pretty standard set up with 3-4 interviews in one day, and director/VP level interview if applicable. All my interview have been of a technical nature, and I will basically ask a couple of "vetting" questions around the tech stack we use. Following that, I will ask the candidate to rate him/herself on proficiency with certain technologies or processes (1-10 scale) depending on rating I will ask questions of a difficulty to see how their rating matches with my rating. If there is time after this, I will ask questions that are open ended for them to share a time when they did X, where X is something along the lines of "disagreed with technical direction of another individual or manager", "applied a good engineering practice, and what was the practice?" or some other answer that gives information both from what they decide to share, as well as how they describe the disagreement/learning/etc. I don't typically do a coding exercise, since the rating system basically helped me triangulate their proficiency.
Interview questions [1]
Question 1
As mentioned above, I am not trying to stump the person I interview, but rather gauging what they share on a question such as "name a time you disagreed with technical direction of another individual or manager and how you responded" as I find it gives me a better sense of what they are like during the "day job" part of their previous employer and not how sharp they are on the spot with a whiteboard.
The interview process consisted of two technical interviews and one interview with the hiring manager - one coding interview about a very simple two sum problem, and another one about ml knowledge in general. The hiring manager interview has to test if I would be a good fit for the team.
Interview questions [1]
Question 1
Two sum leetcode and ml questions about llms and other ml topics.
Started with 1 recruiter round
It then proceeded towards a conversation with the Hiring Managers.
Lastly, there were 4 onsite rounds in 2 different bursts (first 2 at the same time, and if accepted then the last 2 at a single go)
Coding Challenge style of questions followed by a system design challenge that includes easy and medium problems to solve. Done on the whiteboard with the help of interviewers back and forth