Went through the Starbucks Technology EM loop earlier this year for a role on their mobile commerce team. This is my breakdown from the hiring side of experience, since I've also been an interviewer at previous companies.
The loop has five rounds. Recruiter screen, hiring manager intro, a technical panel (two ICs), a leadership/behavioral panel (cross-functional stakeholders), and a final with a director. Total elapsed time was about six weeks.
What they're really measuring.
For an EM role at Starbucks, the behavioral bar is weighted heavily toward scope and ambiguity tolerance. A lot of their initiatives cut across store ops, supply chain, digital product, and enterprise IT simultaneously. They want to know you've navigated that kind of multi-stakeholder complexity before, not just managed a clean product team.
Specific themes that came up multiple times: How do you handle competing priorities when two VPs disagree? Tell me about a time your team's technical debt caused a business incident. How did you handle cleanup? How do you balance delivery timelines with keeping engineers happy and not burning people out?
Technical depth. They're not going to ask you to code, but they do probe depth. Expect a conversation about architecture tradeoffs. In my case: mobile API design, handling graceful degradation when the ordering backend is slow, that kind of thing. Don't show up as a purely people-manager type with no technical opinions.
Leveling. I was interviewing at L8, which maps roughly to EM of 6-10 engineers. The comp was competitive for a Seattle company outside FAANG. I got a verbal offer in the range of $260-275k total, base plus annual bonus structure rather than RSUs, which is a different model than you see at pure tech companies.
One honest note. The pace of change in how they think about engineering culture is real. They're not a startup, they're a 50-year-old retail company trying to act like a tech company. That's either exciting or exhausting depending on your personality. Be honest with yourself going in.