Verifying a C-Suite Candidate's Background Before You Hire
Executive background checks get skipped more often than they should, usually because founders assume seniority implies the claims on a resume have already been vetted somewhere along the way. They haven't, and the cost of finding out after someone starts, rather than before an offer goes out, is far higher for a C-suite hire than for almost any other role in the company.
This checklist covers the specific things worth verifying, and how to do it without the process itself becoming a reason a strong candidate walks.
How do you verify a C-suite candidate's degrees and credentials?
Confirm claimed degrees directly with the issuing institution's registrar office, or through a reputable verification service, rather than accepting a resume claim or even a professional networking site listing at face value. Degree misrepresentation is more common at the executive level than most founders expect, partly because nobody checks as rigorously once someone has enough other credibility markers, like a well-known past employer, to seem beyond question.
Verify past exits and outcomes, not just past titles
A candidate's resume might accurately list that they were CFO of a company that was acquired, without clarifying whether the acquisition was a strong outcome or a distressed sale, or whether they were still in the role at the time. Ask directly, and separately try to verify through your own network or public records, what the actual outcome and the candidate's actual role in it looked like, since resume language around past exits is often technically true and substantively misleading.
Check litigation history relevant to the role
A public records search can surface civil litigation involving a candidate, including disputes with former employers, non-compete violations, or fiduciary duty claims from a past board role. Not every past lawsuit is disqualifying; people get sued for reasons unrelated to their own conduct. But an unexplained pattern, or a candidate who fails to mention litigation you find independently, is worth a direct conversation before moving forward.
For example, suppose a search turns up a civil dispute between a candidate and a former employer over a non-compete. Raise it as a neutral question: ask what happened, how it ended, and whether it relates to the role you are filling. A candidate who explains it plainly and offers documents is showing you something useful. A candidate who is surprised you found it, or who left it out when asked about past disputes, gives you a different signal. Either way, note the answer in your hiring file and confirm it with one independent source before deciding. This keeps the process fair and makes the decision defensible if it is questioned later.
How do you reach references the candidate didn't provide?
Candidate-supplied references are selected because they'll speak favorably, which limits how much they actually tell you. Use your own network to find someone who worked with the candidate but wasn't on their provided list, ideally someone who reported to them directly rather than only peers or superiors, since direct reports often have the most honest read on how someone actually operates day to day.
Balancing thoroughness against candidate experience
A background check process that takes too long or feels invasive can cost you a strong candidate who has other offers moving faster. Run credential and litigation checks early, in parallel with later interview rounds rather than sequentially after an offer is drafted, and be transparent with the candidate that this is standard practice for the role rather than something specific to them, which reduces the chance it reads as distrust.
Verify these items before an offer goes out:
- Confirm degrees with the issuing registrar or a reputable verification service, not the resume or a networking profile.
- Verify past exits, including how the acquisition actually turned out and whether the candidate was still in the role.
- Search public records for litigation, and discuss anything unexplained directly with the candidate.
- Speak with references the candidate did not provide, ideally a former direct report.
- Run credential and litigation checks in parallel with later interviews, and tell the candidate this is standard practice.
A short example of what direct verification actually catches
Say a candidate's resume states they earned an MBA from a specific university and served as CFO through a company's acquisition by a well-known acquirer. A direct call to the university's registrar might reveal the degree was never completed, only attended, and a conversation with someone from the acquired company might reveal the acquisition was actually a distressed asset sale at a fraction of the company's earlier valuation, with the candidate having left several months before it closed. Neither fact would have surfaced from the resume, the candidate's own references, or a generic background check that only confirms identity and criminal history. Both details would likely have changed how the hiring decision was made, or at minimum prompted a direct, informed conversation with the candidate before an offer went out rather than after problems surfaced on the job. Building this kind of direct verification into a standard checklist, rather than leaving it to whoever happens to be running a given search, is what makes it reliable across every senior hire instead of only the ones where someone happened to be especially diligent.
What Good Looks Like
Good practice means degrees, past outcomes, and litigation history are independently verified before an offer is finalized, using sources beyond the candidate's own resume and supplied references.
Building The Capability (5-Stage Skill Ladder)
How to Get Started
Frequently Asked Questions
Is it legal to run a background check on an executive candidate?
Generally yes, but requirements vary by jurisdiction, and most places require the candidate's written consent before running a formal background check, along with specific disclosures if the check affects a hiring decision. Confirm your specific state and local requirements with counsel before running checks, since rules around what can be checked and how results can be used vary meaningfully.
Should background checks happen before or after an offer?
Many companies run at least a preliminary check before extending an offer, then a more thorough one as a condition of the offer being finalized. Running checks entirely after someone has already started is the riskiest sequencing, since it puts you in the position of having to unwind a hire that's already begun rather than catching an issue beforehand.
What's a reasonable way to bring up a litigation finding with a candidate?
Ask directly and neutrally, giving the candidate a real chance to explain context before drawing any conclusion. Many litigation records reflect disputes that say little about a candidate's fitness for the role, and a defensive or dismissive reaction to a fair, direct question often tells you more than the litigation record itself.
About the numbers
This guide doesn't quote a sourced benchmark. Figures in it are estimates or general guidance, so check them against your own numbers.
Related Guides
What a Fractional Executive Bench Actually Costs
A worked example of what it costs to assemble a fractional CFO, CMO, and COO bench instead of hiring three full-time executives, and where savings vanish.
Running a Weekly Cadence for a Fractional C-Suite
How to run a weekly cadence across several fractional executives so cross-functional decisions don't stall between their limited overlapping hours.
Fractional CFO vs COO: Which Should You Hire First?
A decision framework for founders choosing between a fractional CFO and a fractional COO first, based on which function is actually breaking down.
A 14-Day Onboarding Plan for Fractional Executives
A day-by-day plan for onboarding a fractional executive in their first two weeks, so context transfers fast without turning into a documentation project.
Running an Executive Team Split Across Time Zones
The specific habits that stop a distributed leadership team from letting whoever shares a time zone with headquarters make every real decision.
A Fractional CRO's First 90 Days Rebuilding Pipeline
What a fractional CRO actually does in the first 90 days to restructure a B2B pipeline, from diagnosing the stall to rebuilding stage definitions.