Watch the Full Interview
How This Senior Manager Overcame Resistance to Slash $45 Million in Costs
Earns TrustExpert Roundtable
4 experts discuss this interview
Sarah Chen
VP of Engineering
Jordan Taylor
Senior Client Success Manager
Marcus Johnson
Director of Product
Priya Sharma
Head of Growth
Discussing:
Panel review of Earns Trust response
The candidate demonstrated solid ownership by partnering with a more senior colleague to hit those work goals, which hints at influencing without direct authority - a green flag for senior levels. But they completely sidestepped the root conflict with the junior employee who wasn't asking for the right things, missing a chance to show systems thinking across org levels. I'd push on whether this scales to leading broader technical strategy.
Building trust with the senior colleague to accomplish goals feels genuine and proactive, especially for a BD role where relationships drive outcomes. That said, dodging the conflict with the junior - who clearly didn't understand the right asks - comes off as reactive rather than addressing risks head-on. In client-facing work, we'd expect them to navigate those tough conversations with empathy to strengthen the whole team.
I appreciate how they framed collaboration with the senior as a way to deliver on goals, showing some cross-functional influence without starting from a customer or stakeholder problem explicitly. The real miss is not tackling the junior's misunderstanding directly - that's a classic stakeholder trade-off they avoided, which questions their ability to prioritize and influence in conflicting scenarios. Curious if this holds up when real business trade-offs are at play.
Teaming up with the senior colleague to achieve goals shows they can align on outcomes, which ties nicely to business impact like funnel progression in BD. However, ignoring the junior's gap in understanding the right asks skips any hypothesis on how to experiment with clarifying or upskilling them. For growth roles, we'd want to see that structured approach to turn conflicts into revenue levers.
Jordan, you're right that dodging the junior's misunderstanding comes off as reactive, but I see it differently because true technical leadership requires owning the systems gap across levels, not just partnering with seniors. Marcus, pushing on prioritization is spot on, yet they missed articulating how bypassing the conflict impacts broader org design. Priya, your hypothesis angle is good - we'd need to see if they scale that ownership to technical strategy.
Sarah, exactly, and from a relationship perspective, addressing the junior's gap in asking for the right things would've built multi-threaded trust across the team. Building on Marcus's point about stakeholder trade-offs, their senior partnership shows influence, but avoiding tough convos risks long-term outcomes. Priya, tying it to revenue levers makes sense for BD, where proactive empathy drives adoption.
Jordan, I wonder if we're assuming too much about customer-side empathy here - the junior was an internal stakeholder whose misunderstanding they ignored, missing a chance to frame it as a customer problem. Sarah, your push on systems thinking aligns perfectly; bypassing the conflict questions their cross-functional prioritization. Priya, I'd test if experimenting with clarification would've led to better business trade-offs.
Marcus, exactly, and we tested similar upskilling hypotheses in growth to fix funnel bottlenecks like this junior's wrong asks. Sarah, owning the full conflict would've shown stronger outcome alignment, beyond just senior collab. Jordan, from BD's lens, proactively turning that risk into a team strength directly lowers CAC through better internal conversions.
We've converged on the candidate's strong ownership in partnering with the senior colleague to hit goals, as Jordan and Priya noted for influence and outcomes. But across our discussion, the consistent miss is sidestepping the junior's misunderstanding of the right asks, which Marcus and I see as a systems-level gap that doesn't scale to org design. Ultimately, it shows accountability with peers but lacks the full leadership breadth for senior BD.
Sarah's point on scalability ties perfectly to our shared view that the senior partnership built genuine trust, yet avoiding the tough convo with the junior - who wasn't grasping the right needs - feels reactive, as Priya and Marcus highlighted for team risks. The panel agrees this dodges proactive empathy essential for BD relationships. In wrapping up, it's a solid start on outcomes but misses deepening multi-threaded trust across levels.
Building on Sarah and Jordan, we all see the senior collaboration as a green flag for cross-functional influence, but the junior conflict avoidance questions prioritization, as Priya's hypothesis angle and my trade-off concerns emphasized. It's telling they framed goals without addressing that internal stakeholder gap head-on. Overall, the response hints at potential but skips the customer-centric depth needed for real BD trade-offs.
Marcus and Sarah nailed the prioritization and systems gaps, while Jordan's relationship lens aligns with how the senior team-up drove outcomes - yet ignoring the junior's wrong asks skips any experiment to fix it, turning a funnel risk into a missed lever. The group consensus is clear: good alignment on goals, but no structured path through conflict. This leaves the response strong on execution but light on growth mindset for BD.
Panel Consensus
The panel unanimously agrees that the candidate showed strong ownership and influence by partnering with a senior colleague to achieve goals, viewing it as a green flag for trust, relationships, and outcomes across their lenses. They also converge on a shared concern that the candidate sidestepped the conflict with the junior employee who misunderstood the right asks, interpreting this miss through systems gaps, reactive behavior, prioritization avoidance, and lack of experimentation. No significant disagreements emerge, with panelists building on each other to emphasize how this limits scalability for senior BD.
Hiring Signals from the Loop
Sarah Chen
VP of Engineering
Reason to Hire
Demonstrated solid ownership by partnering with a more senior colleague to hit goals, hinting at influencing without direct authority - a green flag for senior levels.
Concern
Completely sidestepped the root conflict with the junior employee, missing systems thinking across org levels and scalability to broader technical strategy and org design.
Jordan Taylor
Senior Client Success Manager
Reason to Hire
Building trust with the senior colleague to accomplish goals feels genuine and proactive, essential for BD where relationships drive outcomes.
Concern
Dodging the conflict with the junior - who didn't understand the right asks - comes off as reactive rather than addressing risks head-on with empathy in tough conversations.
Marcus Johnson
Director of Product
Reason to Hire
Framed collaboration with the senior as a way to deliver on goals, showing cross-functional influence.
Concern
Did not tackle the junior's misunderstanding directly, avoiding a classic stakeholder trade-off and questioning ability to prioritize in conflicting scenarios.
Priya Sharma
Head of Growth
Reason to Hire
Teaming up with the senior colleague to achieve goals shows alignment on outcomes, tying to business impact like funnel progression in BD.
Concern
Ignoring the junior's gap in understanding skips any hypothesis or experiment for clarifying or upskilling, missing a structured approach to turn conflicts into revenue levers.