Bounce

What Do Employment Background Checks Actually Verify?

August 22, 2026 · Bounce

The offer letter says "contingent on successful completion of a background check," and suddenly you are lying awake inventorying your entire history. That title that was sort of informal. The job that ended three weeks earlier than you remembered when you wrote the resume. The degree you finished, but at a school that has since merged with another one. What are they actually going to look at?

Here is the calming, practical truth: background checks verify a short, predictable list of hard facts, and almost nothing else. Once you know the list, the anxiety gets replaced by a simple rule: keep the verifiable facts exact, and put your persuasion into the parts only you can describe. Let's go item by item.

How the check actually works

First, the mechanics, because they explain everything else. Employers rarely investigate you themselves. They hire a background screening company, which is a records-and-phone-calls operation, not a detective agency. In the US, these checks are regulated by federal law (the Fair Credit Reporting Act), which requires your written consent, and gives you the right to see the report and dispute errors before an employer acts on it.

The screening company checks what can be confirmed against records: databases, institutions, and calls to past employers' HR departments or their verification services. That single fact defines the whole landscape: if it lives in a record, it can be checked; if it lives only in your description, it cannot.

Employment dates and titles: usually verified

This is the core of every employment verification. The screener contacts your past employers (or the payroll-based verification services many large companies use) and confirms two things: when you worked there and what your title was.

Practical move: before your next application, write down your exact start month, end month, and official title for each job, from offer letters or pay records if you have them. Those exact facts go on the resume, every time, forever.

Education: often verified, and easily

Degree verification is fast and cheap because most institutions report to central clearinghouses. The check confirms the institution, the degree earned, and sometimes the dates and field of study.

Criminal records, licenses, and the role-specific extras

Depending on the role and jurisdiction, checks may include:

The theme holds: these are all record lookups. Exactness is the entire game.

Salary: rarely verified, and increasingly unaskable

People fear this one far out of proportion to reality. Many employers confirm only dates and titles as a matter of policy and decline to discuss pay. On top of that, a growing list of US states and cities ban employers from asking candidates about salary history at all.

So a check probably will not expose your old salary. That is not a license to inflate it; a lie that probably will not be caught is still a lie you have to maintain, and it can surface through offer letters or W-2s if a company requests documentation. The cleaner path is to move the conversation from history to expectations, which is better negotiation anyway; see what to say when asked about your current salary.

What almost never gets verified: everything that makes you good

Now the part that should change how you write your resume. No background check verifies:

None of that lives in a database. Reference calls can touch it, but structured background checks do not, and many companies limit references to the same dates-and-titles script anyway.

Read that list again, because it is the strategic heart of this whole topic. The verifiable layer of your resume (dates, titles, degrees, licenses) is pure compliance: it must be exact, and it earns you nothing extra by being exact. The descriptive layer (what you did, what changed because of you, what you can do) is where the entire persuasive weight of your candidacy lives, it cannot be verified by any service, and most people write it badly while obsessing over the layer that just needs to be correct.

The standard for the descriptive layer is not "will a database confirm this" but "can I defend this out loud when an interviewer asks how, three times." That standard, applied line by line, produces a resume that is both safe and strong. And if you are tempted to test what happens when the factual layer is not exact, read what happens if you lie on your resume first; the pipeline is unforgiving in a very specific place, and this is the place.

Getting through your check without drama

Make sure the machines read your facts right

Here is the quiet failure mode nobody warns you about: your dates and titles can be perfectly honest and still arrive wrong, because the applicant tracking system misparsed them. Creative date formats, columns, and unusual headings can scramble a work history so the "resume" a company records for you (and later compares against your check) never matched what you wrote. How that parsing works is covered in how ATS parses your work history.

The fix takes two minutes: run the free scan at careerbounce.io and look at the machine-readable version of your resume. You will see exactly how your employment history, dates, and titles parse, and whether the airtight facts you wrote are the airtight facts the system received. The scan runs entirely on your device, your resume never leaves your computer, and there is nothing to sign up for. No promises about offers, because nobody honest makes those. Just certainty that the layer of your resume that must be exact is exact everywhere it counts.

See what the hiring bots see

Free, private, and instant. Your resume never leaves your browser.

Scan my resume free

Frequently asked questions

What do employment background checks actually check?

Most commonly: employment dates and job titles with past employers, education (degrees and institutions), criminal records within legal limits, and identity. Depending on the role, they may add professional licenses, credit history, or driving records. They almost never verify your job duties, accomplishments, or the quality of your work.

Do background checks verify salary?

Rarely. Many past employers only confirm dates and titles, and a growing number of US states and cities ban employers from asking about salary history at all. Do not count on a check exposing a past salary, but do not lie about it either; the safer and increasingly standard move is to discuss expectations, not history.

Can a background check see my job duties and accomplishments?

Almost never. Verification services confirm that you worked somewhere, when, and with what title. What you actually did there, your projects, results, and skills, is not in any database. That is why the descriptive parts of your resume are where your persuasion belongs, and why the factual parts must be exact.

Will a small date discrepancy fail my background check?

Minor mismatches of a few weeks are common and usually resolved by explanation, since HR records themselves can be imprecise. Gaps of months presented as employment are a different matter and read as misrepresentation. Use months and years exactly as your former employer's records would show them.

How do I make sure my resume matches what a background check will find?

List dates and titles exactly as your former employers recorded them, and verify your degree name matches your transcript. Then confirm hiring software reads those facts correctly: the free Bounce scan at careerbounce.io shows how your work history parses, on your device, so the verifiable facts arrive exactly as you wrote them.

Keep reading

what happens if you lie on your resumehow ats parses your work historycan you change your job title on your resume