Adobe Product Analyst candidates describe a recruiter and HR-led start, then product-sense, SQL and analytics questions, and in one case a live panel case presentation. Here is what they report and how to prepare.
$123K
Avg. Base Comp
$147K
Avg. Total Comp
3-4 rounds
Typical Rounds
Not reported
Process Length
Candidates who interviewed for Adobe's Product Analyst role describe a mix of HR conversations and analytical questions, so prepare for both. Two of the three reports mention four rounds. The third describes an HR screen, a follow-up with an HR manager and a final in-office panel.
The analytical content varies by report. One candidate was asked product-management-style questions: a root-cause analysis of rising support tickets at Uber, a product design prompt about featuring Netflix for kids, and what Zomato could do about rising refund requests in one region. Another was asked SQL questions: finding users who neither liked nor commented on posts, and a cumulative revenue sum that resets each year, written with and without window functions. That candidate also got an analysis question on a TV campaign's effect on traffic and a question on flagging traffic anomalies automatically.
A third candidate's final round was a panel case presentation. They said it focused on problem framing and defending their approach, not on algorithmic questions. One panel also asked for a time the candidate used data to solve a problem, and whether they had used Adobe products and how they would improve them.
Practice structuring open-ended metric problems out loud, and rehearse SQL window functions. Prepare a short case you can present and defend under questioning. One candidate also mentions scheduling delays between stages, so plan for a possibly slow process. None of these three candidates were selected, so treat this as preparation guidance and not a prediction.
Synthesized from 5 candidate reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Adobe process.
I went through four rounds at Adobe for a Product Analyst role. The recruiter kicked things off, then I had a conversation with the hiring manager. What surprised me was how long it took to coordinate between stages — there were noticeable delays in booking the next interview, and my first interviewer had just joined the team and didn't know much about the role itself, which felt a bit disorganized.
The first formal round was behavioral with HR, mostly covering my background and education. I remember it being conducted primarily in Japanese, which I wasn't expecting, so that was a curveball to navigate. The final round involved a panel of three people who dug into my analytical thinking and how I'd work with data. They asked me to describe a time I'd leveraged data to solve a problem, and whether I'd used any Adobe products before. If so, how would I improve them? That question was interesting because it wasn't just about technical knowledge — they wanted to hear my thinking on product improvement.
The technical questions leaned heavily on SQL and analytical reasoning. I got asked about analyzing a TV campaign's impact on traffic: how would you structure the analysis, what metrics matter, and how do you calculate weekly averages? There were also questions about querying user behavior — finding users who neither liked nor commented on posts, which required careful SQL logic. One question had me write a cumulative sum of revenue that resets at the start of each year, both with and without window functions. The last one was about detecting anomalies in traffic data and designing a system to flag them automatically.
What I took away is that Adobe cares more about how you think through a problem and communicate your reasoning than purely getting the right answer. They want to see problem structuring, how you'd communicate findings to stakeholders, and whether you can turn analysis into actionable insights. The delay between rounds was frustrating, and honestly the whole process felt a bit slow and disorganized given how large the company is.
Prep tip from this candidate
Prepare for SQL-heavy technical questions that emphasize window functions, time-series aggregation, and anomaly detection logic. Beyond the code, practice articulating how you'd frame a business problem (like campaign impact analysis) and walk an interviewer through your analytical approach step by step — Adobe values thinking and communication as much as correctness.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Adobe
How would we build a model to detect fraud and text customers to approve or deny fraudulent transactions
| Question | |
|---|---|
| Google Maps Improvement | |
| Z and t-Tests | |
| Marketing Channel Metrics | |
| Hurdles In Data Projects | |
| Success Measurement | |
| Threaded Comments | |
| Search Ranking | |
| Testing Price Increase | |
| Data Preparation for Imbalanced Data | |
| Overfit Avoidance | |
| Confidence Interval Explanation | |
| Proof k-Means Converges | |
| Google Docs Drop | |
| POS Subscription Retention | |
| Analyzing Multiple Data Sources | |
| 2nd Highest Salary | |
| Comments Histogram | |
| Empty Neighborhoods | |
| Rolling Bank Transactions | |
| Top Three Salaries | |
| Closest SAT Scores | |
| Last Transaction | |
| Upsell Transactions | |
| Subscription Overlap | |
| Button AB Test | |
| Customer Orders | |
| First to Six | |
| WAU vs Open Rates | |
| Impression Reach |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report starting with a recruiter or a comprehensive HR screening that covers background, education and fit. One candidate then spoke with the hiring manager, and another had a follow-up with an HR manager. Expect to explain your experience and motivation for the role clearly.
One candidate who reached the second round reports being given short prompts and expected to lead the discussion. These included diagnosing a rise in support tickets, designing a Netflix feature for kids, and responding to rising refund requests in one region. Practice structuring metrics, hypotheses and next steps aloud.
One candidate reports SQL-heavy questions, including a cumulative revenue sum that resets yearly (with and without window functions) and finding users who neither liked nor commented. They also got a TV campaign impact question and an anomaly-detection design question. Other candidates may see different technical content.
Final rounds reported differ. One candidate gave an in-office case presentation to a panel of peers and was questioned on their reasoning. Another faced a panel of three asking about using data to solve a problem and how they would improve Adobe products. Prepare to present clearly and defend your approach.
