Verizon · Primly Community

Verizon product manager interview questions: my full loop (consumer product team)

intl_isla · 4 replies

Applied from the UK, got through the full Verizon PM interview process for a remote-eligible Senior PM role on their consumer product side. Sharing the questions because the PM process at Verizon is pretty different from standard tech-company PM loops.

First: the context. Verizon's PM org sits closer to traditional product management in a large corporation than startup-style product. If you're used to Amazon PM interviews with 14 leadership principles and a writing sample, or Google where you might get an analytical question involving a billion users, calibrate down a bit. This felt more like interviewing at a well-run enterprise than a tech-native company. Not a criticism, just a reality check.

Phone screen with recruiter: Standard. Why Verizon, current comp range, timeline.

Hiring manager interview (45 min): She asked two behavioral questions and one "tell me about a product you admire and why." The product I picked was Duolingo (I was going for something familiar with good retention mechanics) and she asked good follow-up questions about what I'd change and how I'd measure success.

Panel onsite (3 rounds, 45 min each):

Round 1 (Senior PM, cross-functional): Product sense. "Walk me through how you'd redesign the Verizon app for a customer who wants to manage their family plan." Standard product design question. They want CIRCLES-ish structure but don't need to see the framework explicitly. User segments, pain points, prioritized features, metrics for success.

Round 2 (Engineering partner): Technical fluency for PMs. No coding. They gave me a scenario about an API latency spike affecting a customer-facing feature and asked how I'd work with the eng team to diagnose and communicate it. They're checking that you can read a basic dashboard, understand what "p95 latency" means, and know how to write a good incident update to leadership.

Round 3 (Behavioral, Director-level): Four STAR questions. Themes: managing stakeholders with competing priorities, delivering bad news, a time you used data to change your mind about a product decision, and one about cross-functional influencing ("tell me about a time you got alignment from a team you didn't manage").

What I didn't get: No estimation question, no market sizing, no written case. I've heard some Verizon PM teams do a take-home case but this team didn't.

Timeline: 5 weeks start to finish. Still waiting on the offer as of this post.

4 replies

jordan_pm

"Calibrate down from Amazon PM" is genuinely useful framing. Verizon is product management in the older sense of the word. More about program coordination and stakeholder management than the obsessive user-centric framing you get at tech-natives. Not worse, just different. Did the director in round 3 seem to be assessing culture fit or actual PM skill?

content_cole

The API latency round for PMs is more common than people think and a lot of PMs completely blank on it. "p95 latency" is the kind of thing you should absolutely know before any PM loop, not just Verizon. Good call-out.

intl_isla

Agreed. I think the bar is "can you have an intelligent conversation with an engineer about the incident" not "can you debug the root cause yourself." I talked about checking whether the latency spike was consistent across regions or isolated, which seemed like the right level of thinking for a PM.

apm_aisha

5 weeks is long. Were there periods where you heard nothing or was it pretty communicative throughout? I always get anxious in the silence.