Interview Experiences

Real candidates, real loops: every round, what was asked, and how it ended.

Share yours, earn XP

8 stories

Likes earn the author +10 XP for the first 3 likes each day

AdobeAccount Executive
Reported Jul 2026

Adobe Account Executive Interview Experience: prospecting task and no closure

The process lasted about four rounds and felt more demanding than a standard recruiter-to-manager path. It began with a discovery-style conversation and a peer interview. I was also asked to prospect for a meeting with the hiring manager. That task was awkward because the hiring manager did not answer calls and had a private LinkedIn profile, so outreach was not straightforward even though the pr…

No responseHR Screen0
AdobeAccount Executive
Reported Jul 2026

Adobe Account Executive interview: supportive first round followed by radio silence

The process felt normal and contained, with about three rounds. It began with a recruiter conversation, then a task, and finally a meeting with the hiring manager. Communication ran smoothly at first, and the recruiter was especially supportive. I received helpful, actionable feedback instead of vague notes. After the first round, the experience did not continue that way. I got nothing back. Ther…

No response0
AdobeResearch AnalystIntern
Reported Jul 2026

Adobe Research Analyst Interview Experience: One-hour research conversation

After a recruiter touchpoint, I had one technical conversation with a team member. It lasted an hour and stayed mainly focused on the research I had already done and where I wanted to take it during the internship. The process moved quickly. I had the interview and received a decision about two weeks later. There was not much jumping between steps. It was essentially a discussion about my work an…

OfferTechnical Screen0
AdobeSoftware Engineer
Apr 2026

Five Relaxed Rounds Built Around OOP and API Design

This one felt pretty comfortable to interview with — slow pace, none of that being-chased-the-whole-time feeling. Each round was an hour, and in some rounds close to half the time was just chatting. The problems were medium-to-easy, but they really like steering things toward object-oriented design and code design — the questions here are different from what other companies ask. A quick note: I'm…

Onsite0
AdobeSoftware Engineer
Feb 2026

Node.js and React OA, Failed Over a Sorting Gotcha

Locked — open it to unlock the full story with XP.

RejectedOnline AssessmentXP0
AdobeSoftware Engineer
Sep 2025

Scala Trivia, Then a Surprise LeetCode Classic

This is one of the many applications I scattered around blindly. I applied to GenStudio on the DX team (people on the forum say DX is a "poison team," same as AEP?). When I applied, it happened to line up with Adobe's legendary summer break, so by the time HR came back from vacation and finally reached out to me, I'd already piled up several rejection letters from other places, hah, wry laugh. Th…

RejectedTechnical Screen0
AdobeSoftware Engineer
Sep 2025

Four Rounds on the AEP Team, Recruiter Wanted More System Design Experience

This was for the AEP team — a pit that a friend referred me into. Four rounds total, overall not too hard. Round 1 was billed as tech/coding, but after we finished going over my resume, the interviewer just started asking about request latency analysis, plus some front-end/back-end fundamentals-style questions. I initially expected coding or system design, but it ended up basically being a conver…

Onsite0
AdobeSoftware Engineer
Jul 2025

Four Rounds, Team Shutdown, and a Month-Long Wait for Rejection

I finished interviewing right before they shut down the team at the end of last month. Then the HM took a two-week vacation, and after waiting almost a month, I got the classic "they were touched but rejected me anyway" treatment — moved to another candidate. It was for the AEP team, a referral pit from a friend. Four rounds total, overall not too hard. The first round was billed as tech/coding,…

RejectedOnsite0

What are interview experiences?

An interview experience is a candidate's own account of a hiring loop — not a question bank entry. It tells you the shape of the process: how many rounds there were, what each round actually tested, how long the gaps between them ran, and what the recruiter said at the end. That context is the part a question list cannot give you.

How to read them

Weight recent write-ups more heavily — interview loops change, often within a year. Read several for the same company and role rather than one: a single account tells you what one interviewer asked, while five tell you what the bar is. Note the outcome badge too, since a rejection write-up usually explains the gap far more precisely than an offer one.

Share your own

Every published experience earns 50 XP, and each of the first 3 likes it receives in a day earns you 10 XP more. Likes must come from established accounts; like-for-like swaps and likes from your own second account are not paid. Write it while the details are fresh — the round order, the exact prompts, and how much time you were given are what the next reader needs.

Share your experience to earn XP