Selling a role and setting honest expectations feel like they pull in opposite directions, but they only conflict when the honesty is vague. A hiring manager who names the hardest, most specific part of the job, and pairs it with a real reason a strong candidate would be equipped to handle it, is not scaring anyone off. They are filtering out the candidates who would have quit in month three anyway, while giving everyone else the confidence that comes from knowing exactly what they signed up for. The candidates worth keeping rarely leave over a hard job. They leave over a job that turned out to be different from the one they were sold.
Every hiring manager we work with eventually asks a version of the same question. How honest should I actually be in this interview? Say too little about the hard parts of the role and you risk a new hire who quits the first time the job gets difficult, because nobody warned them it would. Say too much, or say it the wrong way, and you risk losing a strong candidate to a competing offer that sounded easier.
Both outcomes are real. But they are not two sides of the same coin that a hiring manager has to choose between. They are two failure modes of the same underlying mistake: treating "selling the role" and "setting expectations" as if they compete for the same airtime in an interview, instead of treating them as two different jobs that both need to get done well.
When a client calls us to backfill a role that just opened up again after two or three months, the exit interview rarely says the work was too hard. It says something closer to "this was not what I thought I was signing up for." The candidate was capable of the job. They just were not told, clearly enough, what the job actually was.
Why This Feels Like a Trade-Off (And Isn't)
The instinct to treat selling and honesty as competing goals comes from a reasonable place. Every minute spent describing a role's hardest parts in an interview is a minute not spent describing why the role is a great opportunity, and hiring managers are right to worry that a candidate hearing mostly downsides will walk away unimpressed. But that worry assumes the two things are zero-sum, and in practice they are not. A candidate does not experience "here is the exciting part" and "here is the hard part" as competing messages. They experience the combination as one coherent, credible picture of a real job, which is exactly what makes them trust the person describing it.
The candidates most likely to accept and stay are the ones who leave the interview able to picture both the best week and the worst week in the role. Candidates who only heard the best week tend to accept quickly and leave quickly. Candidates who only heard the worst week tend not to accept at all.
The Case for Selling the Role Hard
Strong Candidates Have Options
A hiring manager who assumes a strong eCommerce or DTC candidate has no other conversations happening is usually wrong. Candidates worth hiring are almost always weighing this role against at least one other opportunity, and an interview that undersells what is genuinely exciting about the work, the team, or the growth trajectory will lose to a competing process that does a better job telling that story.
Enthusiasm Is Part of the Evaluation, Not Just the Pitch
Candidates are reading a hiring manager's energy as a signal about what the team culture actually feels like day to day. A manager who cannot articulate why they are excited about this role, right now, is inadvertently telling the candidate that the job might not be that exciting either. Selling the role is not a separate marketing exercise bolted onto the interview. It is part of how a candidate judges whether this is a team worth joining.
A Job Description Alone Undersells Almost Every Role
Bullet points about responsibilities rarely capture what actually makes a role compelling: the specific problem the team is trying to solve, the resources a new hire will actually have, or the kind of decisions they will get to make within the first six months. That context only comes through in conversation, and skipping it leaves candidates to fill in the gaps themselves, usually with a less interesting version of the job than the one that is real.
The Case for Setting Real Expectations
This Is What a Realistic Job Preview Does
Industrial psychologists have a name for this practice: a realistic job preview, a deliberate, honest picture of what a role actually involves, hard parts included, delivered before a candidate accepts. It works because it lets candidates self-select. Someone who hears an accurate description of the job's hardest recurring challenge and still wants in has already done the mental work of deciding they can handle it, which is exactly the decision you want a new hire to have made before their first difficult week, not during it.
Surprise Is What Actually Drives Early Turnover
New hires rarely quit because a job turned out to be hard. They quit because a job turned out to be different from what they were told, and the gap between expectation and reality erodes trust fast. A candidate who was warned that a role involves frequent late-quarter fire drills, for example, experiences the first fire drill as confirmation. A candidate who was never told experiences it as a red flag about whether they were misled about the rest of the job too.
Clear Expectations Make the Eventual Offer More Trustworthy
A candidate who has heard a hiring manager be specific and honest about a role's real challenges tends to trust that same person's excitement about the role's upside more, not less. Credibility on the hard parts of a story is what makes the good parts of the story believable. A pitch with no rough edges reads as a pitch, and candidates who have been through a few interview processes can usually tell the difference.
How to Do Both in the Same Conversation
Lead With the Real Win, Not Just the Perks
Open with what is genuinely compelling about the specific problem this person would be solving, not a generic list of benefits and culture claims that could describe any company. Specificity here does more selling than enthusiasm alone, and it sets up the honest parts that follow as part of the same real story rather than a separate disclaimer.
Name the Hard Part Before They Ask
Every role has one or two recurring challenges that experienced people in that seat would recognize immediately: a demanding stakeholder, a seasonal crunch, a system that is not fully built out yet. Naming it directly, before the candidate has to ask a probing question to find it, signals confidence rather than concern.
Use Specific Scenarios, Not Vague Warnings
"This role can be stressful" tells a candidate almost nothing and invites them to imagine the worst version of stressful. "During Black Friday week, you will likely be fielding escalations from three departments at once" tells them exactly what to expect and lets them honestly assess whether that is something they want to do.
Give Them a Day in the Life, Not a Highlight Reel
Walk through an actual recent week, the good parts and the frustrating parts both, rather than a curated list of exciting projects. A candidate who has mentally rehearsed a normal Tuesday in the role is far less likely to be blindsided by one three weeks into the job.
Let a Future Teammate Say the Hard Part Out Loud
A challenge that sounds like a warning coming from the hiring manager often sounds like useful, trusted information coming from someone who currently does the job. A short conversation with a future peer during the process does more to make honest expectations land as credible rather than discouraging.
Treat Expectations as a Filter, Not a Deterrent
The goal of naming a role's hard parts is not to talk anyone out of the job. It is to make sure the people who do accept have already decided, on their own, that the hard part is one they are equipped for. Framed that way internally, a hiring manager stops experiencing honesty as a risk to the close and starts experiencing it as part of what makes the close durable.
Watch the Ratio, Not Just the Content
It is possible to say all the right honest things and still get the balance wrong if the hard parts dominate the conversation's tone and airtime. A good rule of thumb: for every specific challenge named, spend at least as much time on the specific reason a strong candidate would find that challenge worth taking on.
A useful test for any hiring manager: if a candidate could not describe, in their own words, both the best part and the hardest part of the role by the end of the process, the interview did one job and skipped the other.
Signs an Interview Has Tipped Too Far One Way
The All Sunshine Pitch
Every answer to a question about challenges gets redirected back to perks, growth potential, or culture. Candidates who accept after this kind of process are the ones most likely to feel misled the first time the job gets genuinely difficult.
The All Warnings Pitch
The interview turns into a list of everything that is hard about the role with little energy spent on why the role is worth doing anyway. Strong candidates with other options tend to quietly opt out of this process rather than push back on it.
The Bait and Switch
The interview describes one version of the role and the actual first month reveals a meaningfully different one. Even if nothing was technically dishonest, an incomplete picture erodes trust exactly as fast as an inaccurate one does.
The Vague Disclaimer Close
A hiring manager senses they should mention the job is "demanding" or "fast-paced" and does, without ever getting specific. This satisfies the instinct to be honest without actually giving the candidate anything real to evaluate, which means it fails at the one job it was supposed to do.
A Note on This Framework
The patterns above come from what we see repeatedly across the eCommerce and DTC hiring processes we run, not from a formal study. Every role and every hiring manager's natural style will land this balance a little differently. The underlying principle does not change: selling a role and being honest about it are not competing goals, and a hiring manager who treats them as two parts of the same job, rather than a trade-off to be managed, ends up with candidates who accept with open eyes and stay because of it.
Frequently Asked Questions
How do you sell a role to a candidate without overselling it?
Lead with what is genuinely compelling about the role, then name the hardest part of the job before the candidate has to ask about it. Selling and honesty are not opposites when the honesty is specific and framed as a real challenge the candidate would be equipped to handle, rather than a vague warning. Candidates read confidence in a hiring manager who can describe both the upside and the difficulty of a role in the same breath.
What is a realistic job preview and why does it matter in hiring?
A realistic job preview is a deliberate, honest picture of what a role actually involves, including its hardest parts, given to a candidate before they accept. It matters because new hires who quit in the first few months rarely leave over a skill gap. They leave because the job did not match what they were told to expect, and a realistic preview closes that gap before it ever becomes a resignation.
Does being honest about a job's challenges scare off good candidates?
It scares off the candidates who were never going to succeed in the role, which is the point. Strong candidates are generally reassured by specific, well-framed honesty because it signals the hiring manager respects them enough to tell the truth and trusts them to handle a real challenge. What actually dissuades good candidates is vague, unstructured negativity that reads as a warning rather than a description of the job.
How much should a hiring manager reveal about a role's downsides during an interview?
Enough that the candidate could describe the hardest part of the job back to you in their own words by the end of the process. That usually means naming one or two specific, recurring challenges tied to real scenarios, not a running list of every possible frustration. The goal is a candidate who walks in on day one having already pictured the hard days, not just the good ones.
Does setting clear expectations during interviews actually improve employee retention?
Yes, because most early attrition is a mismatch problem rather than a capability problem. When a candidate accepts a role with an accurate picture of its demands, the first difficult month confirms what they were already told instead of contradicting it, which is a very different experience for a new hire than feeling misled. Expectations set at the interview stage do more for 90 day retention than almost anything a company does after the start date.