Bilingual receptionists and technicians can matter a great deal where many clients book, check in and settle bills in Spanish — and hiring for the language is lawful when the job actually needs it.
The lines that matter: require a language only where effective job performance requires it, test fluency against real duties rather than accents, keep the posting free of any national-origin preference, and know that Title VII does not require extra pay for work done in another language, as long as no one is required to work extra hours unpaid.
This guide walks through them.
Rules vary by state and change
This guide explains federal rules and the state rules it names, as of the date above.
Employment law and veterinary practice rules differ by state and are revised often, so confirm current requirements with your state veterinary board, labor agency or employment counsel before you act on them.
It is general information, not legal advice.
When a language requirement is lawful
The test comes from EEOC enforcement guidance: requiring fluency in a language other than English is permissible only if it is required for the effective performance of the position.
A language you need because of the work is a job qualification.
A language you prefer because of who you picture in the role is national-origin territory, and that is where hiring decisions get expensive.
EEOC's own example maps cleanly onto a practice: a business that provides services to numerous Spanish-speaking customers may have a sound business reason for requiring that some of its employees speak Spanish.
A front desk in a practice where many clients book, check in and settle estimates in Spanish sits exactly in that picture — the receptionist cannot do the core job without the language.
The same logic sets the line between require and prefer.
If the role answers the phones, takes histories and walks clients through costs in both languages every shift, require it.
If the need is occasional — a Spanish-speaking client now and then, a colleague who can cover — prefer it instead, and hire the strongest overall candidate.
A requirement shrinks your applicant pool to the people who clear the bar, so reserve it for duties the job cannot survive without.
The role this comes up for most is the front desk; our guide to how to hire a receptionist covers the rest of that hire end to end.
English requirements run through the same test.
EEOC guidance says an English fluency requirement is generally permissible only if required for effective performance of the position, and it tells employers to assess the level needed job by job rather than applying uniform requirements to dissimilar positions.
The front desk and the kennel do not need the same English — and neither needs more than the job actually uses.
Accents are the trap inside this.
An employment decision may rest on a person's accent only if the accent materially interferes with job performance, and EEOC says employers may not rely on client or coworker preference to justify accent-based decisions.
A client-preference argument — that some clients would be more comfortable with someone who sounds native — is not a reason you can act on.
Whether a candidate is understandable on the phone while quoting an estimate is.
The reverse rule applies too — what your staff may be told to speak.
Under EEOC rules (29 CFR 1606.7), a workplace rule requiring employees to speak only English at all times is presumed to violate Title VII; a rule limited to certain times must be justified by business necessity, and employees must be told when it applies and what the consequences are.
29 CFR 1606.7(b) allows the time-limited version where the employer can show that necessity.
If you restrict conversation to English while a procedure is underway, be ready to articulate why for the times you name — and write the policy down.
Testing fluency
Test the language the way the job uses it.
For a receptionist that is a role-play: a client calls in Spanish about a bill, and the candidate has to greet them, find the account, explain the balance and book the visit.
For a technician it might be reading a discharge instruction aloud and summarizing a treatment plan for the client.
A free-form chat with a fluent interviewer is weaker evidence — it has no bill in it.
Build the exercise from your actual workflow, and score it against a short written rubric: did the candidate convey the estimate, capture the history, ask the right follow-up?
Run the same exercise for every candidate for the role, because an inconsistent test also makes your comparisons worthless.
The bar itself matters as much as the exercise.
EEOC lists fluency-in-English requirements — such as denying opportunities because of a foreign accent or an inability to communicate well in English — among the selection procedures that may discriminate on the basis of national origin.
What keeps a fluency screen defensible is that the level you demand matches the level the job needs, you decide that level before interviews start, and you apply it to everyone who interviews.
Then judge performance inside the exercise, not by ear.
The accent question has a specific shape: a decision may rest on accent only where it materially interferes with job performance — so the question your rubric answers is whether the client on the role-play call got the right information, not whether the candidate sounds like a native speaker.
Have a fluent staff member run the exercise, and keep the rubric sheets with your interview notes so you have a consistent record of why each hiring decision happened.
Pay differentials
Start with what the law does not say.
EEOC is explicit that Title VII does not require employers to provide additional compensation for work performed in a language other than English, provided employees are not required to work extra hours without compensation.
We could not find a government figure or a primary industry survey that publishes a typical bilingual pay differential — no hourly add-on and no percentage of base — and we will not invent one.
If you have seen a specific figure quoted, treat it with caution: we could not verify any differential against a government or primary-survey source, so do not build a pay decision on one.
Treat the differential as a pay-design decision, made before you interview.
Start from the role's market rate, then decide whether the language skill is part of the base rate or a premium on top.
Where bilingual is a genuine requirement of the role, folding it into the posted range keeps one clear number for candidates to react to.
Where it is preferred rather than required, a stated premium on top of base prices the skill visibly without moving the whole band.
Whatever you decide, anchor the base in real numbers.
BLS OEWS data for May 2025 puts receptionists and information clerks in veterinary services at a median of $18.23 an hour (25th percentile $17.11, 75th $21.16), against a median of $18.27 across all industries.
Our guide to what to pay a receptionist covers the full picture for that role.
Two design cautions.
First, apply whatever you choose consistently across the people doing the same bilingual work — one-off, informal side payments are how pay disputes start.
Second, if the premium goes to non-exempt hourly staff, check how it interacts with overtime before you roll it out; overtime and the regular rate covers the mechanics.
Writing the posting
The posting is where language hiring becomes visible, and federal rules reach it directly.
EEOC states it is illegal for an employer to publish a job advertisement that shows a preference for, or discourages someone from applying because of, race, color, religion, sex, national origin, age (40 or older), disability or genetic information.
Title VII's advertising provision (42 U.S.C. § 2000e-3(b)) says the same thing in statutory form: no notice or advertisement indicating a preference, limitation, specification or discrimination based on race, color, religion, sex or national origin — with an exception where religion, sex or national origin is a bona fide occupational qualification for the job.
The practical translation: require the language, never the origin.
“Bilingual — Spanish/English required” describes a skill your first-section analysis says the job needs.
An ad that signals who you want the person to be, rather than what you need them to do, is what the national-origin rule is written against.
Coverage has a threshold.
Title VII applies to employers with 15 or more employees for each working day in 20 or more calendar weeks in the current or preceding year — but many state anti-discrimination laws reach smaller employers, so a small practice should not treat the federal number as a safe harbor.
Then the part state pay-transparency laws require: pay in the ad.
VeterinaryHires counted 14 states plus the District of Columbia with a law requiring a pay range in job postings as of October 6, 2026 — Colorado, California, Washington, New York, Hawaii, Maryland, Illinois, Minnesota, New Jersey, Vermont, Massachusetts, Virginia, Maine and Connecticut.
The employer-size thresholds differ: California's posting rule applies at 15 or more employees, New York's at four or more, Colorado's at one or more employee in Colorado.
Check your state before you publish — our pay transparency laws page keeps the full table.
Write the duties that use the second language into the posting itself — which calls, which conversations, which documents — so candidates can judge their own fluency against real work before they apply, and you have the job-related record of why the requirement exists.
For structure, length and the rest of the ad, our guide to writing a job posting takes over from here.
Using interpreters vs staff for consent
The conversations where language does the most damage are the ones about money and risk: the estimate before a dentistry, the consent conversation before a spay, the discharge instructions, the euthanasia discussion.
A client who signs something they did not understand becomes a complaint, a bad review or an unpaid invoice — whatever the law requires.
So design the interpretation before the moment arrives.
Start by deciding which conversations get handled in the client's language as a matter of practice policy: estimates and consent at minimum, plus treatment changes and discharge instructions.
Then name who does it.
If interpreting is part of a receptionist's or technician's job, that belongs in the role's duties and in the hiring analysis from the first section — not as an informal expectation bolted onto whoever happens to be bilingual.
The staffing reality is the trade-off.
One bilingual employee becomes a single point of failure: every Spanish call, estimate and consent conversation routes through them, pulling them off their own work and concentrating risk in one person's availability.
Whether the volume justifies coverage across shifts — not necessarily a second full-time hire — is a design question to answer before your busiest month proves the bottleneck for you.
For long or high-stakes conversations when no fluent staffer is free, a professional interpreter service is the fallback; we make no claim about what these services cost, so get quotes.
And document the language: a line in the record noting that the estimate was reviewed in Spanish and the client's questions answered is the cheapest protection available the day a client disputes what they agreed to.
What we could not find: any federal rule or veterinary-board guidance that sets requirements for interpreting veterinary client consent or estimates.
Treat this section as practice design rather than a compliance checklist, and confirm anything state-specific with your attorney.
Language rules also reach your own documents
Serving bilingual clients is not the only place language obligations appear — they reach employee-facing paperwork too.
In California, an employer whose workforce at a facility is 10 percent or more speakers of a non-English language must translate the harassment-prevention policy into every such language (2 CCR 11023(e)).
In New York, the wage notice must be given in English and in the employee's primary language when the state Department of Labor offers a translation — Spanish, Chinese, Haitian Creole, Korean, Polish and Russian as of October 7, 2026.
If part of your team is Spanish-primary, check what your own state requires before you hand over the standard English-only paperwork.
Before you post the bilingual role
- Decide require vs prefer for each role, from the duties the job actually performs.
- Set the fluency bar at the level the job needs, and build the test from real workflow before interviews start.
- Decide the pay treatment — folded into base or a stated premium — before the first interview.
- Check whether your state requires a pay range in the posting, and at what employer size.
- Require the language in the ad, never a national origin.
- Name which client conversations happen in the client's language, and who covers them on each shift.
- If you limit conversation to English at certain times, write down when it applies and why it is necessary.