We see this situation all the time: a startup spends 5 weeks interviewing a Senior Engineer.

The candidate meets the hiring manager, completes the system design round, meets future teammates, and gets strong feedback across the board. Everyone internally assumes the process is going great.

Then the offer goes out and the candidate suddenly becomes less responsive.

A few days later, they decline.

Sometimes the reason is compensation. Sometimes it’s the commute, relocation reality, or another competing offer. Sometimes the candidate says they “weren’t fully sure yet” or “didn’t have enough information to make the decision confidently.”

At first glance these look like offer stage problems, but we actually categorize them as interview process problems, or information collection problems. We see most offers go south for one of 2 reasons:

• Employers lacking visibility into candidates’ compensation expectations, competing opportunities, location preferences, timeline constraints, and overall decision-making process.

• Candidates lacking enough information about job security, company trajectory, manager quality, team dynamics, engineering culture, growth opportunities, compensation structure, benefits, working norms, and whether the role actually aligns with what they want next in their career.

Below is our list of common ways offers go south, and our ideas for how to get ahead of them. Plus we’ve included a bunch of ways to make your interview process more engaging and higher converting. 

Example #1: No Compensation Check In

A candidate tells the recruiter early on they’re targeting ~$220K base.  Three weeks later they’re interviewing at three other companies and now expecting closer to $260K plus stronger equity.

Nobody checks in again before the offer.

The hiring team spends days getting approvals, writes the package, sends it over, and the candidate immediately hesitates.

Now everyone is frustrated:

• the recruiter thinks the candidate moved the goalposts

• the hiring manager thinks compensation expectations were already aligned

• the candidate feels like the company isn’t competitive

The issue wasn’t the offer itself. The issue was assuming information collected in week 1 was still accurate in week 5.

Example #2: Timing & Location Issues

A candidate gets all the way to the offer stage before mentioning:

• They need a later start date because of equity vesting

• They’re considering a stock buyout from their current company and want to see that out before leaving 

• They booked a 3 week trip during the summer and would prefer to start after 

• They need to stay in New York for family reasons

• They are open to in-person 5 days

This can be because there should've been a pulse check, or should've been checked on the intro call. Don't worry, we have tips for both!

Example #3: The Candidate Never Got Sold on the Company

A startup runs a very rigorous interview process:

• coding round

• architecture round

• behavioral round

• founder round

• references

Every conversation is evaluative. Nobody spends meaningful time explaining:

• why the company matters

• what’s exciting internally

• why engineers stay

• where the product is headed

• what makes this team different

Meanwhile another company:

• Offers calls with cross functional team members to learn more about the business

• invites the candidate to an offer dinner with other team members

• introduces future teammates into the process to share their experience working there 

• shares a product demo

Even if both companies are equally strong, one process feels warm and personalized, and one feels transactional.

At the end, the company extends an offer. But the candidate chooses another startup with weaker compensation but a manager who spent multiple conversations actively helping them picture themselves there.

Ideas To Prevent These Scenarios

Here are our tips for improving your interview process by stage: 

During the Interview Process

• Actively sell & build excitement-building at every stage. For example, a hiring manager can explain why they personally joined, what problems the team is solving, and why this is a meaningful growth opportunity for the candidate.

• Share traction, roadmap, and product updates during the interviews. For example, sending candidates a recent funding announcement, customer growth milestone, or major product launch can help candidates feel momentum and understand where the company is headed. 

• Help candidates understand the team dynamic. For example, candidates should leave interviews understanding how engineers collaborate, how decisions get made, how feedback is handled, and what day-to-day communication actually looks like.

• Create opportunities for peer connection. For example, companies can host casual coffee chats, engineering AMAs, team lunches, or virtual hangouts where candidates can ask unfiltered questions to future teammates. These can feel small but really help candidates picture themselves on the team beyond formal interviews. 

• Ask directly about a candidate’s competing opportunities. For example, a candidate may tell you they’re deciding between your startup and a larger public company with fully remote flexibility.

• Loop Leopard in as soon as a candidate becomes a serious finalist. This way  we can help pressure test excitement, competing opportunities, and potential risks before the offer stage. For example, a candidate may tell Leopard privately that they are worried about relocation, manager fit, or equity structure even if they have not shared those concerns directly with the company yet. We may recommend adding an extra conversation with a founder, organizing a casual dinner with future teammates, or moving faster because another offer is likely coming within days.

Before Final Interviews

Run a short “temperature check” call before preparing the offer so you can catch hesitation while there is still time to address it. Make it warm and open ended, so the candidate can lightly surface their questions & concerns, things like:

• What are the company financials? 

• What is the culture really like here? 

• Is this company actually doing well?

• “I’m actually leaning toward another company because it’s bigger”

• “I’m worried about stability.”

• “I still want to understand the roadmap.”

Or asks, like: 

• “I’d love more time with the engineering manager.”

• “I’d love to meet other women/nb folks on the team to learn about their experiences”

• “I’d love to walk through the financials with the finance team to make sure I really understand them”

• I’d love to get full access to the benefits info to see if my current therapist is covered” 

A few key best practices we recommend to cover on that call: 

• Ask candidates what they still want to learn before finals. For example, a Staff engineer may want more clarity on engineering culture, roadmap stability, or how technical disagreements are handled internally.

• Pulse-check location and timeline alignment. For example, a candidate may be open to San Francisco initially but later realize they need to stay in New York for family or partner reasons.

• Reconfirm compensation expectations. For example, a candidate who originally said “I’m targeting around $220K” may now be interviewing at companies offering $260K plus larger equity packages. Or a senior engineer may care less about base salary and more about equity refresh structure, level scope, signing bonus, or start date flexibility.

• Confirm excitement level directly. For example, a candidate may keep progressing through interviews while still feeling unsure about the company’s product direction or long-term growth potential.

• Make sure the candidate understands the role and company deeply. For example, a candidate should already understand the engineering challenges, leadership style, product roadmap, and why current employees are excited to work there before they are asked to make a decision.

After the Offer

• Host dinners or onsite visits for in person connection. These types of IRL celebrations really help candidates feel stronger emotional conviction around the team and environment. 

• Connect candidates with future teammates outside the formal interview process These types of calls create a safe space for candid questions about day-to-day life at the company.  For example, a senior engineer may want to understand how technical disagreements are handled or what the actual work pace feels like week to week.

• Have Leopard help the candidate assess the offer. Sometimes there’s information candidates still feel they are missing before making a decision, but the candidate can’t articulate what those open questions are or how to get them answered. For example, a candidate may want deeper context on engineering leadership stability, roadmap clarity, or how performance reviews actually work internally, but isn’t sure how to ask. The Leopard team can help you all by helping the candidate figure out what they care about!