About This Episode
Two finalists: one spent three years at a household-name company after the IPO, the other lived through a layoff, a near-collapse and growth with no playbook. Leadership wants the logo; the hiring manager wants proof. Heather Krueger, Chief People Officer at Engine, and Rebecca Taylor cover the "how" questions that cut through AI-polished answers, onboarding built around a new hire's gaps, a 30-to-60-day incubation period, and why a panel where everyone agrees may have a blind spot.
About The Guest
Heather Krueger is Chief People Officer at Engine, the business and group travel platform. She joined Engine in August 2025 as Senior Vice President of People, after leading people strategy and operations as Head of Talent Density at Coinbase. She has led people teams through more than one high-growth company and runs her function like a product org: if employees don't feel the value, it's just a tax. She is skeptical of resumes and a fan of hiring HR people who didn't start in HR.
Episode Breakdown

Two finalists are left for a role at a fast-scaling company. One spent three years at a marquee name but joined after the IPO, once the work was smooth and well-resourced. The other spent three years inside a layoff, a near collapse, and breakneck growth with no playbook, and has the weaker resume to show for it. Leadership wants the recognizable name. On HR Voices, host Rebecca Taylor put the scenario to Heather Krueger, Chief People Officer at Engine.

Heather called it one of the most common hiring debates she has seen in recent years. She reduced it to one choice: whether the company is hiring the logo or the person. Those are two different decisions, with two different processes. Her first concern was not which finalist wins. It was that leadership had anchored to a logo without knowing what either candidate did or how they solved problems.

Why the Logo Is the Wrong Thing to Debate

Heather read the leadership framing as a “concerning signal” about how senior leaders reason, and as a warning that the hiring manager has a hard conversation ahead. The candidate risk comes second. Companies hire someone who performed in a stable environment and expect the same results in the chaos of fast growth. Because the mistake is so common, it rarely carries much accountability.

The resume works in both directions. Time at a company in hypergrowth does not make someone a builder, Heather argued, and time at a marquee company does not make someone less scrappy. Then there is the question few interviewers ask: whether the candidate is willing and able to do it again. Plenty of people enjoyed the trenches, have good stories from them, and do not want another round.

The gap Heather wanted closed was what year one will feel like. In the high-growth companies she has worked in, the first six months were “particularly hellish,” and a new hire who does not know that going in is unlikely to last. In her words, a realistic job preview “is the biggest gift we can give to candidates,” and Engine has gone as far as documenting who tends to succeed there and who does not. No surprises is the goal for both sides.

What a Wrong Hire Costs the Team

Heather’s biggest takeaway for listeners was to think past the role to the team and its dynamic. A wrong hire made on something as shallow as a logo wastes a hiring cycle, along with time and resources. The team loses momentum while the person is there. When the person leaves, everyone else fills the gap. Gallup estimates that replacing an employee costs one-half to two times the employee’s annual salary. Heather adds lost momentum and a gap the team has to cover to the full cost of turnover.

That is why Heather holds the hiring manager to both halves of the decision. The manager owns the choice to hire, and owns making that person successful. A manager bold enough to take a bet, on a logo or on anything else, also takes on the work that follows.

When a new hire struggles, the manager and the employee usually tell different stories, and the truth tends to sit in the middle. Heather starts by asking the manager whether the person knows what good looks like at 60 days and at six months. Only after that is settled, with coaching and modeled behavior behind it, does she treat the problem as performance.

What Actually Works

Ask How Questions, Not What Questions

Big outcome statements are easy to make now, and AI makes polished answers easier still. Heather probes the input behind the outcome. A candidate who claims a big growth number should explain whether a 50-person team helped or whether the work was done alone while wearing two other hats. Her questions ask how the candidate handled a roadmap that changed three times in a quarter, built something with no team and no tools, or prioritized when everything was an emergency. These are behavioral-based interview questions aimed at the job as it will actually run. A case study or a 45-minute working session, run inside a structured interview process, gets closer still.

Map the Interview Record to the Job Description

No candidate is a perfect match. Heather takes a transcript of everything the panel learned about the hire, maps it against the written job description with AI, and treats the gaps as the design brief for onboarding the new hire. The interview stops being a pass or fail gate; it becomes the first draft of a development plan. Gallup finds that only 12 percent of employees strongly agree their organization does a great job onboarding new employees.

Set an Operating Rhythm for the First 60 Days

Heather treats the first 30 days as an incubation period. Leaders model the communication style, the documentation, and the problem-solving that work at the company, then ease off after the first 30 to 60 days, before support turns into babying. An operating rhythm makes the expectations spoken rather than assumed. At Engine, leaders talk about being shock absorbers, not shock amplifiers.

Her own rhythm is specific. She speaks to the whole people team twice a month, and weekly one-on-ones are “non-negotiable” for a new hire and a three-year veteran alike. A weekly team meeting lets people watch how others ask hard questions.

Where Employee Relations Fits

Rebecca noted that employee relations tends to see performance only once there is tension, and that most of those cases start as communication failures. Heather’s view of HR’s role there is a neutral one: get to the root of the integration problem, whether it is communication, operating norms, or missing rhythms. Exit and engagement data belong in the decision too. Patterns from exit interviews show which backgrounds have struggled in the culture a company already has, and Heather is cautious about repeating a values mismatch.

Frequently Asked Questions About Hiring for a Fast-Scaling Role

Should You Hire the Candidate With the Big-Name Resume?

Not on the logo alone. Heather Krueger points out that a logo does not show what the candidate did or how they solved problems. Evidence from the interview process should decide the hire, not the brand on the resume.

What Interview Questions Reveal Whether a Candidate Can Handle Chaos?

Questions about the how do. Heather asks how candidates handled a roadmap that changed three times in a quarter, built something with no team or tools, and chose priorities when everything was an emergency.

How Can AI Help Plan a New Hire’s Onboarding?

It can map the interview record to the role. Heather maps a transcript of what every interviewer learned against the job description, then builds the onboarding plan around the gaps that analysis finds.

Why Does Heather Krueger Look at LinkedIn More Than Resumes?

LinkedIn shows more of the person. Heather looks for promotions and multiple tours of duty within one company, and for what candidates post and respond to, which can show what they care about.

What Does It Mean When an Interview Panel Agrees on Everything?

It can mean a blind spot. Heather warns against consensus culture: when every interviewer says the same thing, the panel may be relying on shortcuts, such as a logo, and you should dig into what actually happened.

The Bottom Line for HR Leaders

Heather’s advice for the hiring manager is to stop debating a logo on logic and bring evidence instead. “Proof over prestige” is the line she likes to hammer home. She also urges People leaders to challenge their own assumptions, follow the recruiting process even when the answer feels obvious, and stay skeptical when everyone agrees.

The hires Heather still keeps in touch with from about five years ago did not have the best story or the prettiest resume. They were the people who “held things together when it got hard and kept going.” Resumes rarely show who that is. Heather Krueger’s point is that the interview process can, if HR keeps the bar high.

See how AllVoices helps People teams resolve employee relations issues when a new hire and a manager describe the same problem two different ways.

Our next webinar
Frequently asked questions

Got more questions? Email us at support@allvoices.co and we'll respond ASAP.

No items found.
Frequently asked questions

Got more questions? Email us at support@allvoices.co and we'll respond ASAP.

No items found.

Big-Name Resume or Proven Operator: Making the Hiring Call

About the guest

Heather Krueger is Chief People Officer at Engine, the business and group travel platform. She joined Engine in August 2025 as Senior Vice President of People, after leading people strategy and operations as Head of Talent Density at Coinbase. She has led people teams through more than one high-growth company and runs her function like a product org: if employees don't feel the value, it's just a tax. She is skeptical of resumes and a fan of hiring HR people who didn't start in HR.

Episode Breakdown

Two finalists are left for a role at a fast-scaling company. One spent three years at a marquee name but joined after the IPO, once the work was smooth and well-resourced. The other spent three years inside a layoff, a near collapse, and breakneck growth with no playbook, and has the weaker resume to show for it. Leadership wants the recognizable name. On HR Voices, host Rebecca Taylor put the scenario to Heather Krueger, Chief People Officer at Engine.

Heather called it one of the most common hiring debates she has seen in recent years. She reduced it to one choice: whether the company is hiring the logo or the person. Those are two different decisions, with two different processes. Her first concern was not which finalist wins. It was that leadership had anchored to a logo without knowing what either candidate did or how they solved problems.

Why the Logo Is the Wrong Thing to Debate

Heather read the leadership framing as a “concerning signal” about how senior leaders reason, and as a warning that the hiring manager has a hard conversation ahead. The candidate risk comes second. Companies hire someone who performed in a stable environment and expect the same results in the chaos of fast growth. Because the mistake is so common, it rarely carries much accountability.

The resume works in both directions. Time at a company in hypergrowth does not make someone a builder, Heather argued, and time at a marquee company does not make someone less scrappy. Then there is the question few interviewers ask: whether the candidate is willing and able to do it again. Plenty of people enjoyed the trenches, have good stories from them, and do not want another round.

The gap Heather wanted closed was what year one will feel like. In the high-growth companies she has worked in, the first six months were “particularly hellish,” and a new hire who does not know that going in is unlikely to last. In her words, a realistic job preview “is the biggest gift we can give to candidates,” and Engine has gone as far as documenting who tends to succeed there and who does not. No surprises is the goal for both sides.

What a Wrong Hire Costs the Team

Heather’s biggest takeaway for listeners was to think past the role to the team and its dynamic. A wrong hire made on something as shallow as a logo wastes a hiring cycle, along with time and resources. The team loses momentum while the person is there. When the person leaves, everyone else fills the gap. Gallup estimates that replacing an employee costs one-half to two times the employee’s annual salary. Heather adds lost momentum and a gap the team has to cover to the full cost of turnover.

That is why Heather holds the hiring manager to both halves of the decision. The manager owns the choice to hire, and owns making that person successful. A manager bold enough to take a bet, on a logo or on anything else, also takes on the work that follows.

When a new hire struggles, the manager and the employee usually tell different stories, and the truth tends to sit in the middle. Heather starts by asking the manager whether the person knows what good looks like at 60 days and at six months. Only after that is settled, with coaching and modeled behavior behind it, does she treat the problem as performance.

What Actually Works

Ask How Questions, Not What Questions

Big outcome statements are easy to make now, and AI makes polished answers easier still. Heather probes the input behind the outcome. A candidate who claims a big growth number should explain whether a 50-person team helped or whether the work was done alone while wearing two other hats. Her questions ask how the candidate handled a roadmap that changed three times in a quarter, built something with no team and no tools, or prioritized when everything was an emergency. These are behavioral-based interview questions aimed at the job as it will actually run. A case study or a 45-minute working session, run inside a structured interview process, gets closer still.

Map the Interview Record to the Job Description

No candidate is a perfect match. Heather takes a transcript of everything the panel learned about the hire, maps it against the written job description with AI, and treats the gaps as the design brief for onboarding the new hire. The interview stops being a pass or fail gate; it becomes the first draft of a development plan. Gallup finds that only 12 percent of employees strongly agree their organization does a great job onboarding new employees.

Set an Operating Rhythm for the First 60 Days

Heather treats the first 30 days as an incubation period. Leaders model the communication style, the documentation, and the problem-solving that work at the company, then ease off after the first 30 to 60 days, before support turns into babying. An operating rhythm makes the expectations spoken rather than assumed. At Engine, leaders talk about being shock absorbers, not shock amplifiers.

Her own rhythm is specific. She speaks to the whole people team twice a month, and weekly one-on-ones are “non-negotiable” for a new hire and a three-year veteran alike. A weekly team meeting lets people watch how others ask hard questions.

Where Employee Relations Fits

Rebecca noted that employee relations tends to see performance only once there is tension, and that most of those cases start as communication failures. Heather’s view of HR’s role there is a neutral one: get to the root of the integration problem, whether it is communication, operating norms, or missing rhythms. Exit and engagement data belong in the decision too. Patterns from exit interviews show which backgrounds have struggled in the culture a company already has, and Heather is cautious about repeating a values mismatch.

Frequently Asked Questions About Hiring for a Fast-Scaling Role

Should You Hire the Candidate With the Big-Name Resume?

Not on the logo alone. Heather Krueger points out that a logo does not show what the candidate did or how they solved problems. Evidence from the interview process should decide the hire, not the brand on the resume.

What Interview Questions Reveal Whether a Candidate Can Handle Chaos?

Questions about the how do. Heather asks how candidates handled a roadmap that changed three times in a quarter, built something with no team or tools, and chose priorities when everything was an emergency.

How Can AI Help Plan a New Hire’s Onboarding?

It can map the interview record to the role. Heather maps a transcript of what every interviewer learned against the job description, then builds the onboarding plan around the gaps that analysis finds.

Why Does Heather Krueger Look at LinkedIn More Than Resumes?

LinkedIn shows more of the person. Heather looks for promotions and multiple tours of duty within one company, and for what candidates post and respond to, which can show what they care about.

What Does It Mean When an Interview Panel Agrees on Everything?

It can mean a blind spot. Heather warns against consensus culture: when every interviewer says the same thing, the panel may be relying on shortcuts, such as a logo, and you should dig into what actually happened.

The Bottom Line for HR Leaders

Heather’s advice for the hiring manager is to stop debating a logo on logic and bring evidence instead. “Proof over prestige” is the line she likes to hammer home. She also urges People leaders to challenge their own assumptions, follow the recruiting process even when the answer feels obvious, and stay skeptical when everyone agrees.

The hires Heather still keeps in touch with from about five years ago did not have the best story or the prettiest resume. They were the people who “held things together when it got hard and kept going.” Resumes rarely show who that is. Heather Krueger’s point is that the interview process can, if HR keeps the bar high.

See how AllVoices helps People teams resolve employee relations issues when a new hire and a manager describe the same problem two different ways.