Can a job require U.S. citizenship? When a citizenship requirement is lawful and how to word it

Usually not: under 8 U.S.C. 1324b, a private employer with four or more employees may limit a job to U.S. citizens only when a law, regulation, executive order or federal, state or local government contract requires it, or when the Attorney General determines it is essential to do business with a government agency. Jobs that need a security clearance generally qualify, because the Defense Department's rules for contractors restrict classified access to U.S. citizens. Export control rules (ITAR and EAR) do not: they allow "U.S. persons," a group that includes lawful permanent residents, refugees and asylees. As of November 2026, the Justice Department's Immigrant and Employee Rights Section (IER) keeps resolving cases over citizenship requirements that had no legal basis.

For the wording of ordinary sponsorship lines, see visa sponsorship language in job postings; for the law and penalties, see citizenship status discrimination in hiring; for other federal contractor posting duties, see job posting requirements for federal contractors. This page is about the exception: when citizenship can be a real requirement, and how to state it without overreaching.

When can a job lawfully require U.S. citizenship?

IER's FAQ states the rule plainly: employers may not limit applicants or hires to U.S. citizens unless required to do so by federal, state or local law or federal contracts. Its fiscal 2026 letters of resolution show what happens otherwise: a utility (February 6, 2026) and an IT services company (February 9, 2026) each committed to stop "limiting positions based on citizenship status without proper justification" after IER investigations (IER, FY 2026).

Do security clearance jobs require U.S. citizenship?

For contractor work under the National Industrial Security Program, yes in practice. The rule at 32 CFR 117.10 says:

• the contractor must determine that access to classified information is essential to the tasks on a classified contract (117.10(a));
• a contractor "will require each applicant for determination of eligibility for access to classified information who claims U.S. citizenship to provide evidence of citizenship" to the facility security officer, using original or certified documents (117.10(c));
• contractors "must make every effort to ensure that non-U.S. citizens are not employed in duties that may require access to classified information" (117.10(k)). A limited access authorization is possible only in rare cases where a non-citizen has unique skills urgently needed and no cleared or clearable citizen is readily available, and it is not valid for TOP SECRET information; and
• non-U.S. citizens are not eligible for temporary (interim) eligibility (117.10(l)).

Two cautions. The requirement attaches to positions that need classified access, not to every job at a company that holds a facility clearance; a role that never needs classified access does not carry it. And the citizenship evidence the security officer collects is a clearance step, separate from Form I-9, where the employee still chooses which acceptable documents to show.

Do ITAR or EAR jobs require U.S. citizenship?

No, and this is the most common mistake IER sees. Its FAQ says "Nothing under the ITAR or the EAR requires or allows an employer to limit jobs to U.S. citizens," and its fact sheet explains that U.S. persons, meaning U.S. citizens, U.S. nationals, lawful permanent residents and people granted refugee status or asylum, can access export-controlled items without government authorization. For other workers, the employer may need a license from the State Department (ITAR) or the Commerce Department (EAR). IER's best practices for these jobs:

• do not state in job ads that export rules require a specific citizenship, immigration status or national origin, and do not use the ITAR or EAR as a reason to limit jobs to citizens;
• when you discuss export rules with candidates, make clear that U.S. persons include more than citizens;
• assess U.S.-person status only for workers whose positions involve controlled items, and tell them why you are asking;
• keep the export assessment separate from Form I-9, store its documents apart from I-9s, and never mark the I-9 with export notes.

IER's fiscal 2026 letters include a manufacturer and distributor (March 23, 2026) that agreed to correct "incomplete descriptions of U.S. persons" and train its staff, and a staffing company (January 13, 2026) that agreed to train document reviewers using IER's export control fact sheet.

What about government contracts and public employers?

A contract clause counts only if it actually requires citizenship for the position. Ask for the clause, copy its citation into the job order, and match the posting to it: if the clause covers people working on one contract, the requirement covers those roles. Federal agencies hiring directly follow their own rule, 5 CFR 338.101, which allows appointment in the competitive service only of people who are citizens of, or owe permanent allegiance to, the United States, with rare exceptions. State and local public employers should check the specific statute or charter provision for the job.

How do you word a lawful citizenship requirement?

Security clearance role:
This position requires access to classified information and
eligibility for a U.S. government security clearance. Under the
Department of Defense's rules for contractors, that generally
requires U.S. citizenship.

Contract-based requirement:
This position is subject to [contract name and clause], which
requires U.S. citizenship for personnel performing this work.

Export-controlled role (no citizenship requirement):
This position involves technology controlled under U.S. export
regulations. The company may need government authorization before
some candidates can access it.

Avoid "U.S. citizens only" with no reason, "citizens or green card holders only," "ITAR requires U.S. citizens," "must have a U.S. passport," and "active clearance required" for roles that will never touch classified work. IER's best practices page lists the first, second and fourth of those among phrases to avoid unless legally required, and its export control fact sheet covers the third.

Can you ask candidates to prove citizenship before hiring?

For ordinary roles, no. The EEOC's citizenship page says most employers should not ask whether an applicant is a U.S. citizen before an offer, and that Form I-9 and E-Verify come after an offer is accepted. Ask only the two questions IER calls appropriate, covered in work authorization questions in interviews. For a cleared role, the facility security officer's citizenship check under 117.10(c) is the place for proof, and it should stay separate from the I-9.

What should a staffing agency do when a client asks for "citizens only"?

1. Ask what requires it: a clearance, a named contract clause or a regulation. Write the answer on the job order.
2. If it is export control, explain the U.S. person rule and change the requirement to match it.
3. If nothing requires it, decline the restriction in writing and recruit on the job's actual requirements.
4. Limit any lawful requirement to the roles it covers, and word the posting to match the source.
5. Train recruiters: IER's fiscal 2026 letters include a staffing company where a naturalized citizen was told a job was "only open to U.S. citizens" without legal justification, asked for proof, and lost the offer; she received $5,600 in back pay (December 11, 2025).

The agency's own exposure does not depend on who wrote the request, because recruitment and referral for a fee are covered activities under 1324b. For the related interview rules, see illegal interview questions; for other phrases to keep out of ads, see discriminatory job ad language.