How to answer conflict and influence questions in a Director, VP, CPO interview
"Tell me about a time you had a conflict" and "tell me about a time you influenced without authority" come up in behavioral interviews at every level. At the Director, VP, and CPO levels, these questions tend to probe something more specific: whether you optimize for your team or for the company.
In Google and Meta terms, a Director role at most other companies maps roughly to L7, and VP and CPO roles map roughly to L8 or L9, though it varies with company size and scope.
The narrative to avoid is to default to advocating for your own team's priorities in a conflict. At Director level that might be occasionally fine. At VP and CPO, it becomes a failure mode. A CPO who only advocates for more resources for product at the expense of what the business needs can lose the CEO's trust that they are running product for the whole company, and that trust is what lets a CPO own product direction in the first place.
A strong conflict or influence story at these levels shows you making the conflict productive: aligning people who do not share your goals or your way of seeing the product, without formal authority, and without leaving organizational debt, like a decision that keeps getting relitigated or 2 teams intentionally working around each other.
Escalation is part of that, and it is easy to get wrong in either direction. Letting a disagreement grind on for months is one way. Escalating everything is the other, and a VP who takes every cross-functional disagreement to the CEO is failing at the job, even when the CEO sides with them. The skill is making the conflict productive first, knowing when it truly needs a leader above both of you, and escalating it in a way that brings your counterpart with you.
A lot of my coaching happens after clients land the role, on exactly these cross-org conflicts. In that work, the leaders whose escalations build trust tend to do the same few things. Those are the things this post covers, and they are also what a strong interview story shows.
What changes about peer conflict at the Director, VP, and CPO level?
Earlier in a career, a conflict story is often about 2 people who want different things for the same project, and a strong answer shows how you worked it out together. As you go up, 3 things change: what the conflict is about, who it is with, and how reversible a wrong call is.
What is being contested. For a Director, conflicts are usually about scope, resources, or sequencing within a well-defined product area. A VP's conflicts are often on multiple product areas that each make sense on their own but together give customers a patchwork experience. The patchwork is a result of shipping the org chart instead of shipping one coherent product. By CPO, the conflict is frequently about product strategy itself, including whether the CPO has earned enough trust with the CEO to own product direction or keeps relitigating that boundary.
Who it is with. Directors are often across from a peer leader in another product area or function. For a VP, the other side is more often another VP or the head of another function. A CPO works with the heads of sales, finance, marketing, and legal, and might disagree with the CEO or founder directly. That last case has no neutral arbiter, because the CEO is both the other party and the person who decides. Escalation is off the table, and disagreeing productively while keeping trust becomes the whole job.
How reversible a wrong call is. A Director-level conflict that goes wrong might cost a quarter. A CPO-level one, like a failed bet on a new product area or a broken relationship with the CEO, can shape the company's direction for years. Strong VP and CPO candidates show they understood that asymmetry: which parts of the decision could be undone, which could not, and how that shaped what they pushed on.
I wrote more about how expectations change across these levels in How to ace your L7, L8, or L9 product leadership interview.
When should you escalate a conflict with a peer?
At the Director, VP, and CPO level, most conflicts should be made productive before anyone escalates them. That means understanding what the other leader is measured on and cares about, finding the goal you share, and shaping the options together. Many disagreements end there, and escalating them anyway creates organizational debt.
Escalation becomes the right call when resolving the disagreement requires a trade-off that neither of you has the authority to make, because it means deciding whose goal the company puts first. That decision belongs to a leader accountable for both orgs, such as a shared VP, the CPO, or the CEO. A few signs that you have reached that point:
You agree on the facts and still disagree. When you and your peer read the same data and reach different conclusions because of what your orgs are measured on, more data or more meetings will not settle it.
The question underneath is a bet for the company. Resolving it means deciding whose goal the company puts first, such as revenue now or user trust over time. Only a leader accountable for both orgs can decide that.
Waiting has a cost the company will feel. Duplicated work, a strategy that stalls, or customers who start to see the seams between orgs.
Once you see these signs, there is no need to wait for the disagreement to drag on, or for more data. Part of growing into a Director role is learning to act before the picture is complete, and at VP and CPO the scope is too large to ever have full information.
More data rarely settles a disagreement about whose goal comes first, and a conflict story where you went and got all the data before acting would suggest you are not at that level yet.
The moment the signs appear, often after the first substantive conversation with your peer, is the moment to escalate. Jeff Bezos described what happens when nobody does in his 2016 letter to Amazon shareholders: without escalation, "the default dispute resolution mechanism for this scenario is exhaustion," and whoever has more stamina ends up deciding. Escalating early, well before anyone is worn down, is the decisive choice.
Knowing when to escalate is only part of the judgment. How you escalate matters just as much, because an escalation that blindsides your peer or arrives as a complaint can leave the same organizational debt as a conflict left to grind on.
What makes an escalation graceful?
A graceful escalation is collaborative. You and your counterpart go to the leader together, with the decision described in a way either of you could have written. In practice, that usually looks like this:
Agree with your counterpart that it needs to go up, and go together. Jeff Weiner described LinkedIn's version of this as clean escalation: when 2 people are still misaligned after 5 days, they go to the decision maker together and explain exactly where they disagree.
Describe the decision in terms of the goal both orgs share. The leader should see the trade-off, with neither side's position framed as the right one.
Bring options with the trade-off in each, and your recommendations. Include options that cost your own side something. You and your counterpart can each give your own recommendation.
Commit fully to the decision that comes back. That includes the case where the leader picks an option you argued against.
From VP onward, there is one more layer: sharing decision-making with the people around you. As leaders gain authority, it is natural to keep more decisions close, so that more of them route through you. The leaders who keep growing tend to do the opposite. They push decision-making control, context, and resources down and out, to the leaders on their own team and to peer orgs, so that good decisions can happen without them in the room.
In my experience, that shift is much of what separates a Director from a VP, and a VP from a CPO. In practice, it looks like changing how decisions get made so fewer disagreements need to go up at all: agreeing with another org up front on what information moves between teams, from whom, and by when, or making the product strategy clear enough that leaders outside product can use it to make their own decisions.
All of this happens at work, long before the interview. What the interviewer hears is the story, and the same story can be told in a way that shows this judgment or in a way that hides it.
How to tell an influence story around the escalation
As an illustrative example, a common version of this story sounds like this:
Our company strategy was to start monetizing the AI assistant my org owned with ads. The ads team believed sponsored results woven into answers would be useful to people if they were relevant and clearly labeled, and I pushed to keep ads in a separate section until we understood the effect on trust. I shared our user research, here’s what the data said... I met with the ads director 1:1, led joint workshops, eventually we agreed on a limited test. Here’s how we went about testing it....
That story shows conviction, and the outcome is fine, but it sounds like a leader advocating for their own team: the candidate brought more research to win the argument, it ended in a compromise.
An interviewer at the Director, VP, and CPO level may hear someone optimizing for only their team. The story also leaves out why the 2 orgs disagreed, what the company stood to gain or lose, and whose call it was.
Another version of the same story sounds like this:
Company strategy was to start monetizing our consumer AI assistant with ads this year, and the ads org and my org each owned part of it. The ads org was measured on revenue and believed sponsored results woven into answers could be genuinely useful to people, as long as they were relevant and clearly labeled. My org was measured on usage and on whether people trusted the answers enough to act on them. I wanted ads kept in a clearly marked section below each answer until we understood the effect on trust. We both looked at the same early test: revenue per session was much higher when sponsored results were woven in, and repeat usage dipped among people who saw them. The ads director read the dip as a short-term reaction that better relevance would fix. I read it as an early sign of lost trust. In our first conversation, we agreed on the data and still disagreed, because each of us was reading it against our own org's goal. I offered a middle path: weaving sponsored results in, clearly labeled, only on shopping questions, where people already expect product suggestions. The ads director saw the merit in it and still could not agree to it, because it would leave their org well short of the revenue target leadership had set for the year, and changing that target was not their call or mine. That was when I knew we needed to escalate together. Where the ads belonged was a question of how much user trust the company was willing to trade for near-term revenue, and neither of us owned that decision. I proposed that we take it to our CPO together, and we jointly presented 3 options: 1. Sponsored results woven into every answer 2. A separate section below every answer 3. The middle path, with the ads org's revenue target for the year adjusted to match: woven in and clearly labeled only on shopping questions, with a separate section everywhere else. I recommended the middle path, and the ads director recommended weaving them into every answer. Our CPO chose the third option and lowered the ads org's target for the year. It let the company start earning where people already expected product suggestions, and it kept the harder mistake to undo, losing trust across every answer, off the table while we learned. It also meant giving up the ad-free answers I had started out wanting, and I owned that trade-off with my own team. I committed to the decision, and I put my effort into how the decision would be judged. I proposed that repeat usage and answer trust become guardrails in the ads org's goals alongside revenue, and the ads director agreed to co-own them with me, along with the point at which we would revisit the decision. Those guardrails became the standard the company used for later decisions about ads in its AI products, and they meant neither org needed to relitigate this one.
The plan in this story is a collaborative escalation: agreeing with the ads director that it needed to go up, writing the decision up together with both recommendations in it, and bringing it to the CPO together.
The story also makes clear why the conflict existed, why it was time to escalate, what was at stake for the company, that the candidate acted on an early test instead of waiting for more research, and how the candidate moved off their own starting position and owned that trade-off with their team, putting the company's bet ahead of their own team's metric.
It also shows exactly what the candidate influenced without authority: the middle option the CPO chose, and trust guardrails written into another org's goals.
That is what clear thinking looks like in an influence story, and it is the kind of judgment that can separate levels in these questions.
How to prepare your stories this week
Pick 2 conflict or influence stories where the other side was a leader at your level or above, and the disagreement came from how your orgs were measured.
For each one, write down the point where it needed to go to a leader above both of you, and why neither of you could resolve it alone.
Write down what you and your counterpart brought to that leader together, and what it would have cost the company if nobody had.
Check the ending. If it ends with you winning, look for a moment where you committed to a decision you argued against. That moment often shows more of your judgment than the win.
FAQ
How do I answer "tell me about a time you had a conflict with a peer" in a Director or VP interview?
Pick a story where the conflict came from how 2 orgs were measured. Explain what each side was measured on, the point where the decision needed a leader above both of you, how you and your counterpart brought it to that leader together, and what you did after the decision. At the Director, VP, and CPO level, a strong answer shows that you optimized for the company over your own team, made the conflict productive, and knew whether it needed to go up.
When should you escalate instead of resolving a conflict yourself?
When resolving it requires a trade-off neither of you has the authority to make, usually because the company has to decide whose goal comes first. A clear sign is that you and your peer agree on the facts and still disagree. Escalate as soon as you see that, together with your peer, well before anyone is worn down.
Should my conflict story end with me winning?
Not necessarily, and at the Director, VP, and CPO level it often lands better when it does not. A story where you committed to a direction you argued against because it was right for the company can show more judgment than one where you won the argument. What matters is that you can explain why the final decision was right for the company and what you did to make it work.
Does talking about escalation make me look like I can't make decisions?
It can, if the story does not make clear why the decision was not yours alone to make. When the conflict required trading one org's goals against another's, bringing it to a leader accountable for both is the decisive choice. Make that reason explicit, and show that you and your counterpart brought options and recommendations together, so the interviewer hears judgment about where a decision belongs.
How does influence without authority change from Director to VP to CPO?
Director-level influence stories often involve scope, resources, or sequencing, and show how you fit your product with a peer's priorities and limits. VP stories tend to be about how you kept product areas working together across orgs you do not run. CPO stories often involve product strategy itself, and show how you brought leaders outside product, and the CEO, along with a product direction. At each step up, influence starts earlier and lasts longer, and a wrong call becomes harder to reverse.
What if the conflict is with the CEO?
At CPO, it often is, and there is no one above you to take it to, because the CEO is both the other party and the decision maker. What interviewers tend to probe is whether you have built enough trust to own product direction. A strong story shows how you made your case, how you disagreed without relitigating the boundary every time, and how you committed once the CEO decided.
Where to start
If you are preparing for a Director, VP, CPO, (or L7-L9 at companies like Google and Meta) interviews and want help with your conflict and influence stories at the level you are aiming for, or you are already in the role and want help with the cross-org conflicts in front of you, this is the work we do together. https://nancychu.hbportal.co/public/acing_interviews
See recent client outcomes: https://www.nancychu.co/wins
About the author
Nancy Chu is a leadership coach for Director, VP, CPO level roles, which often map to L7 to L9 at companies like Google and Meta. She was a director at Roku and a manager of product managers at Meta. Since 2024, her clients have landed more than 70 offers, 24 of them at L7 and above, at companies like Anthropic, OpenAI, Meta, Google, Microsoft, Stripe, Uber, and more, with packages reaching $3.6M in annual total compensation.
More clear thinking, each week
Every week, Nancy Chu shares insights for Director, VP, and CPO-level product leaders, both for landing the role and for leading well once they are in it, like why a conflict is happening, when it needs to go to a leader above you, and how to escalate it gracefully. You can get them at nancychu.co.
Comments