Data Engineering at Adobe

Adobe's 4.1 Glassdoor rating is among the highest of the companies we track, but the Blind sentiment runs mixed, and that gap tells you something real. The Glassdoor score likely reflects genuine stability: no tracked layoffs in the past 12 months, and pay runs above other Technology companies. The Blind signal is where the friction surfaces. Adobe moves at enterprise software pace, which means tooling decisions go through multi-team alignment cycles and a data engineer's ability to ship cleanly depends on navigating product and platform dependencies they don't control. What you get is a well-funded, durable employer with a broad technical surface and competitive pay. What you give up is velocity: engineers who want to own infrastructure end-to-end and move fast tend to find Adobe's coordination overhead frustrating after 18 months. The neutral happiness tier, roughly flat, suggests that friction is stable rather than worsening, but it's not going away.

Adobe is not in a growth sprint. 9 open data engineering roles across 3 cities, with Bangalore carrying the largest share, which signals the company is staffing deliberately rather than expanding the DE org aggressively. 3 executive departures in the past year is worth watching: executive turnover at that rate can shift data platform priorities in ways that don't always surface until a new leader resets roadmaps. The low 30-day layoff risk is encouraging for near-term stability, and the absence of layoffs in the past year supports the read that Adobe is managing headcount through attrition and selective hiring rather than cuts. For someone joining now, the most likely 12-month scenario is steady work on existing platform investments, with trajectory depending heavily on which product area they land in and how the post-departure leadership alignment settles.

Adobe's core data problem is surface fragmentation at scale. Creative Cloud, Experience Cloud, and Document Cloud each generate distinct telemetry streams, usage signals, and behavioral events, and the data engineering team's job is to unify those streams into shared infrastructure that product, marketing, and analytics teams can actually consume. That means the day-to-day work sits at the intersection of pipeline ownership and cross-product data modeling: engineers are defining schemas that have to survive across product boundaries, building orchestration that respects SLAs owned by different business units, and managing a multi-cloud environment where AWS, Azure and Databricks appear across the live stack. The breadth of Adobe's product surface makes data modeling decisions unusually load-bearing here; a schema choice that works cleanly in one product context can create backfill obligations across 3 or 4 downstream consumers.