Great Benefits, Poor Engineering
Great Benefits, Poor Engineering
Adobe has great benefits: the insurance is the best I've ever had, there's a sabbatical every 5 years, etc.
If you're a software engineer, you don't want to work in consulting.
Engineering ability is looked down upon. Good engineers are often not promoted, and poor engineers are often promoted as long as they talk to the right people.
Your time is strictly tracked, down to 15-minute increments.
You will be actively discouraged from going to conferences if it means taking time off work. You can forget about ever having your conference ticket paid for unless you're lucky enough to be working for a large client project.
Product engineering will also look down on you coming from consulting. So movement is very difficult, even if it's to a position that you're extremely qualified for.
Let engineers be engineers. Get project managers and stop wasting engineers' time managing their own projects. Learn how to identify engineering talent and fix your metrics for promotions.
Was this helpful?
Adobe Interview Questions
Adobe Interview Experiences
Software Engineer
There was one HR-like team round before the loop. The three rounds in the loop were: 1. Technical LeetCode 2. Behavioral 3. System Design LeetCode was hard, and System Design was very low-level, with back-to-back questions.
Software Engineer (Internship)
The process started with an Online Assessment (OA), followed by a final round interview. The OA was generally easy. The team likely had too many applicants overall. There was an optional kickstarter Zoom meeting.
Software Development Engineer 2
First, there was an initial hour-long meeting with a manager to discuss two recent projects I had worked on. The next round was three technical interviews, each with two team members. This was followed by a final interview with a director.
Software Engineer
Lehi, Utah, United StatesMarch 22, 2025There was one HR-like team round before the loop. The three rounds in the loop were: 1. Technical LeetCode 2. Behavioral 3. System Design LeetCode was hard, and System Design was very low-level, with back-to-back questions.
Software Engineer (Internship)
Lehi, Utah, United StatesMarch 12, 2025The process started with an Online Assessment (OA), followed by a final round interview. The OA was generally easy. The team likely had too many applicants overall. There was an optional kickstarter Zoom meeting.
Software Development Engineer 2
Lehi, Utah, United StatesApril 17, 2024First, there was an initial hour-long meeting with a manager to discuss two recent projects I had worked on. The next round was three technical interviews, each with two team members. This was followed by a final interview with a director.
