Reddit · Primly Community

Reddit engineering manager interview loop: what they're actually evaluating

careerveteran · 4 replies

I went through the Reddit EM interview loop for a senior EM role (managing 8-10 ICs, L6 equivalent) earlier this year. Thought I'd share the shape of it since the EM track is underrepresented in writeups.

Full loop was 5 rounds: a hiring manager intro, then four panel rounds with cross-functional interviewers including a staff engineer, a PM, and an existing EM.

What they're actually testing:

The framing they gave me early on was that Reddit EMs are expected to be strong technical collaborators, not just people managers. They want you to have enough depth to participate in system design reviews and architecture decisions, not just run sprints. So the bar on technical depth was higher than I expected for an EM role.

Round by round: Hiring manager call (45 min): Mostly about your management philosophy, team-building, how you handle underperformers. Pretty standard. Also a culture fit screen, Reddit is proud of being weird and scrappy and they do probe for whether you fit that. People leadership (1 hr): A panel of two. Deep dive into specific situations: a performance issue you navigated, a time you had to push back on leadership, how you build psychological safety. They use a structured behavioral format and they do probe for the "so what happened after" a lot. Don't stop at the STAR method, keep going. Technical collaboration (45 min): Not leetcode. But they gave me a system design scenario and asked how I'd engage with my team on it, what questions I'd ask, how I'd know when to weigh in vs. when to let the tech lead own it. It's about your engineering judgment, not your ability to code. Cross-functional influence (45 min): A PM on the panel. Focused on roadmap prioritization, dealing with competing stakeholder priorities, how you've handled resource constraints. The specifics about Reddit here were questions about their growth/ad-product tension. Your questions / reverse interview (15 min): They allocate real time for this and the caliber of your questions matters. I asked about how they think about EM tenure, average team size, and what's hard about the business right now.

They move at a reasonable pace. Got feedback within a week of the onsite. The process felt respectful of time, which is increasingly rare.

If I were coaching someone: lean into specifics, not frameworks. They don't want to hear about "my leadership principles." They want to hear about the specific engineer you had to let go and how you handled that conversation.

4 replies

director_dee

The technical collaboration round is the one that trips people up. A lot of EM candidates default to 'I trust my team' as an answer, which sounds good but tells the interviewer nothing. What they want to see is: do you actually know enough to have an opinion, and do you know when to hold it vs. when to defer? Those are different skills.

mobile_mara

Seconding the thing about your questions mattering. I see so many EM candidates get all the way to the end and then ask 'what's the culture like' which after a full day of rounds is basically nothing. The cross-functional question at the end about 'what's hard about the business' is a really good one. Shows you've done your homework on the business, not just the tech stack.

firsttime_mgr

Saving this. I'm still a few years from interviewing at this level but this is the kind of concrete framing I never see in the generic 'how to interview as an EM' articles.

pm_priya

Interesting that a PM is in the panel for the EM loop. That cross-functional round where they ask about stakeholder priorities and roadmap tension is the one I'd really want to prep for if I were the candidate. PMs notice immediately when an EM doesn't understand how product decisions actually get made.