Went through the full Intel engineering manager loop in Q1 2026 for a role in their datacenter group out of Hillsboro. Sharing the structure because there's not much online that's current.
The loop was six rounds over two days, all virtual. Here's what each one actually covered:
Round 1: Recruiting screen. Thirty minutes, mostly "tell me about your management philosophy" and a high-level history walk. No gotchas.
Rounds 2-3: Behavioral panels. Both with senior ICs and a director. Heavy STAR format. Every question I got was variations on: how you handled underperformers, how you drove technical decisions you disagreed with, and one around navigating org ambiguity (Intel has a lot of it). Prepare cross-functional friction stories.
Round 4: Technical depth. This surprised me. They asked me to whiteboard a system design problem, which I expected, but then drilled on how I would have structured the team to build it. Not just "what would you build" but "who would own what seam and how do you detect if ownership is wrong." That framing caught me off guard.
Round 5: People leadership. One-on-one with a director. Less structured, more conversation. They want to know if you've managed through headcount cuts specifically. Intel has had multiple rounds of layoffs since 2023, and the interviewers were pretty direct that whoever they hire will need to be steady in that climate.
Round 6: Hiring manager. Mostly vision alignment and some light probing on technical credibility. Not the hardest round, but it sets the frame for leveling.
Leveling: they called the role "Senior Engineering Manager" but comp was closer to what you'd expect at a mid-level EM role at most mid-tier tech companies. If you're coming from a Big Tech EM role, calibrate expectations down 20-30% on total comp.
I was ultimately a no-hire. Feedback via recruiter was that I wasn't specific enough about team outcomes in the behavioral rounds. Which is fair. I'd been managing at a scale where I was three levels above the actual output, and I think I stayed too abstract.
If you're prepping, practice answering every story with a concrete team result: retention number, velocity delta, specific incident outcome. Not vibes. Intel's interviewers want receipts.