How a Non‑Technical Consultant Became a Successful Facebook PM

Interview Summary

Why he switched from consulting to product management;

How he succeeded as a PM at Facebook without a technical background;

How to become an outstanding non‑technical PM.

Q: What motivated you to transition from consulting to product management?

A: I discovered the role by chance. At the time I didn’t have strong aspirations to become a PM, but Facebook was looking for a consultant from McKinsey who could move into a PM position.

At first I was surprised because many PMs usually have titles like engineer, designer, CEO, or COO. I felt lucky to land the PM role at Facebook.

Q: What do you think are the purpose and goals of a PM?

A: Product management requires deep understanding of resource integration, user experience, market, and users. Even without a technical background, you still need to know some programming concepts and be able to communicate effectively with team members from different disciplines.

Two key points:

Have a profound understanding of the product you are building, including how users interact with it, their needs, and frustrations.

Learn to communicate efficiently. You rely on engineers to implement code, so you must clearly explain what you want and what needs to be done.

The primary goal of a PM is to get the product launched and released.

Q: What are your thoughts on non‑engineers working as PMs in a tech‑heavy company?

A: I don’t think lacking a technical background prevents you from being a good PM. When I uncovered the potential of the role, I asked myself, “Can I succeed without a technical background?” Facebook gave me the confidence that I could.

Effective communication with engineers and designers doesn’t require knowing every line of code; it requires using the right terminology and being able to mobilize internal resources.

I strongly recommend learning to ask the right questions and use the correct terminology.

For example, when Facebook launches a new feature, you as a PM need to understand the explanations about implementation, design, and other elements. You may not need to grasp every technical detail, but you must understand the language used in discussions to contribute meaningfully.

This isn’t to say a technical background is unnecessary; rather, you don’t have to be an engineer or designer before becoming a PM.

Q: What strategies do you use to defend the authority and responsibilities of a PM in a technical company?

A: I focus on three areas. First, I spend a lot of time learning extensive product knowledge, studying both front‑end and back‑end aspects (e.g., what features Facebook could add and how they might impact users). Second, I think strategically about how I would use a product (e.g., how I use Graph Search daily). Third, I consider the product’s scale and coverage from a macro perspective (e.g., what products exist that Facebook doesn’t, and what I would add if I built them).

Thinking about a product from these three levels—high, medium, and low—gives you deep insight, enabling you to make informed, wise decisions for your product.

Original source: The Product Manager Handbook (includes Q&A with ten renowned PMs; the series will continue to be updated).

Translated and submitted by Tobbi.