Watch the Full Interview
How This Business Development Manager Turned Peer Resistance into Winning Government Tenders
Earns TurstExpert Roundtable
4 experts discuss this interview
Michael Park
VP of Sales
Sarah Chen
VP of Engineering
Jordan Taylor
Senior Client Success Manager
Marcus Johnson
Director of Product
Discussing:
Panel review of Earns Turst response
Right off the bat, the candidate's story about turning around a stalled deal by qualifying the champion early stands out - that's solid process discipline and a green flag for me. They hit 115% quota consistently, which shows results orientation. But they blamed market conditions a bit for one miss, and I'd push back on that; I want to hear more about personal ownership there.
From a systems perspective, I like how they described influencing cross-functional teams without authority to unblock a BD deal, tying it to org-wide impact. That's ownership we look for. However, they didn't quantify the technical or scalability ripple effects of that trust-building - I'd push back if it was just surface-level without deeper business-tech linkage.
The candidate's example of having a tough conversation with a key stakeholder to rebuild trust after a product delay feels genuine and proactive - great for relationship building. They emphasized multi-threading contacts, which is key for outcomes in BD. That said, it seemed a tad reactive; I'm interested if they spot risks earlier from the customer's side.
Starting with the customer's problem in their hypothesis-driven approach to earning trust is spot on, especially the anecdote about validating pain points before pushing a solution. It shows customer empathy and prioritization smarts. I wonder though if they truly balanced stakeholder trade-offs, as they didn't dive into data-backed decisions there.
Sarah, I see your point on quantifying the scalability ripple from that cross-functional unblock, and it ties to my concern about their market blame for the quota miss - we need full ownership there. Jordan, exactly on the tough stakeholder conversation rebuilding trust; that's how you qualify a champion early like in their stalled deal turnaround. But Marcus, I'd push back - hitting 115% quota shows that hypothesis approach closes deals, not just validates pain points.
Michael, you're right that quota attainment reflects ownership, but I want to push back on assuming the cross-functional influence scaled without those quantified ripple effects they skipped. Jordan, from an org design angle, that multi-threading in the product delay recovery is a green flag for influencing without authority. Building on Marcus, their hypothesis on pain points needs deeper technical strategy linkage to truly earn trust at our scale.
Sarah, I agree - the multi-threading after the product delay builds outcomes beyond just BD unblocks, spotting risks proactively from the customer side. Michael, that stalled deal qualification via champion is spot-on for relationships, but it felt reactive like my concern, not ahead of the curve. Marcus, exactly, validating pain points first fosters trust, though I'd love to see more empathy in those trade-offs for enterprise risks.
Jordan, building on your customer-side risks, their pain point validation before solutions shows empathy that prevents reactive fixes like the product delay talk. Sarah, I wonder if we're assuming too much systems depth without data on trade-offs, as they didn't tie hypothesis to quantified stakeholder impact. Michael, that 115% quota is compelling, but does qualifying the champion truly balance cross-functional trade-offs, or just sales wins?
We've converged on the candidate's 115% quota attainment and stalled deal turnaround via early champion qualification as clear green flags for results and process, which Jordan nailed on relationship-building and I pushed back on with Marcus's trade-off concerns. Sarah, your point on unquantified scalability from cross-functional unblocks aligns with my red flag on their market blame dodging full ownership. In sales, that repeatable process is a win, but owning misses completely would make this response a home run.
Michael, spot on tying quota to ownership, and Jordan, your multi-threading in the product delay recovery shows org-level influence we all value alongside Marcus's customer hypothesis. But we've consistently pushed back on lacking quantified ripple effects from those unblocks and deeper technical strategy links to business impact. Their cross-functional wins demonstrate potential systems thinking, yet scaling trust needs those metrics to fully convince.
Sarah and Marcus, I fully agree the hypothesis-driven pain point validation and multi-threading post-product delay foster genuine trust and proactive risk spotting from the customer side. Michael, that champion qualification in the stalled deal aligns perfectly with relationship outcomes, though we all noted the reactive tint and market blame as gaps. Overall, their tough conversations show empathy for outcomes, but earlier risk identification would elevate it.
Jordan, exactly - pain point validation prevents reactive fixes like the product delay, and Michael, the 115% quota proves hypothesis turns into stakeholder wins, building on our shared green flags for customer empathy. Sarah, we agree on needing data-backed trade-offs to avoid assumptions in cross-functional influence, as their examples hint but don't fully quantify. This response shines in starting with the customer problem, balancing vision with pragmatism we'd probe further.
Panel Consensus
The panel converges on key green flags like the candidate's 115% quota attainment, stalled deal turnaround via early champion qualification, hypothesis-driven customer pain validation, multi-threading relationships, and tough stakeholder conversations demonstrating trust-building and process discipline. They agree these show potential for results, ownership, empathy, and influence, but consistently push back on gaps including incomplete personal ownership (e.g., market blame for misses), lack of quantified ripple effects or scalability impacts, reactive rather than proactive risk spotting, and insufficient data-backed trade-offs in cross-functional decisions. While sales and relationship strengths are broadly endorsed, technical and product panelists emphasize deeper systems linkage and prioritization rigor as unresolved concerns.
Hiring Signals from the Loop
Michael Park
VP of Sales
Reason to Hire
Consistent 115% quota attainment and turning around a stalled deal by qualifying the champion early, demonstrating results orientation and solid process discipline.
Concern
Blaming market conditions for a quota miss without full personal ownership.
Sarah Chen
VP of Engineering
Reason to Hire
Influencing cross-functional teams without authority to unblock a BD deal, tying it to org-wide impact and showing ownership.
Concern
Lack of quantification on technical or scalability ripple effects from trust-building efforts, missing deeper business-tech linkage.
Jordan Taylor
Senior Client Success Manager
Reason to Hire
Having a tough conversation with a key stakeholder to rebuild trust after a product delay and emphasizing multi-threading contacts for outcomes.
Concern
Approach seemed reactive rather than proactively spotting risks earlier from the customer's side.
Marcus Johnson
Director of Product
Reason to Hire
Hypothesis-driven approach starting with customer's problem and validating pain points before solutions, showing customer empathy.
Concern
Did not dive into data-backed decisions or truly balancing stakeholder trade-offs.