Job search
ITAR and U.S. Person Requirements in Tech Jobs: What to Verify Before Self-Rejecting
Current eCFR and DOJ guidance, plus a real Rocket Lab posting, separate export access from citizenship-only program requirements and employment authorization.
Do not reject an ITAR-related technology job solely because you are not a U.S. citizen. The ITAR definition of U.S. person is broader. Also do not assume that permission to work, a broad export-control footer, or a possible authorization route satisfies every condition of a particular role. Read export access, citizenship, clearance and employment authorization separately.
This guide uses current eCFR text, DOJ guidance and a public Rocket Lab posting reviewed on October 12, 2026. It provides a wording-check process, not an individual legal opinion. LandOffer publishes the guide and offers a place to browse recent technology roles; the employer's complete current requirements remain essential.

Read the current definition before interpreting shorthand
22 CFR 120.62 defines a natural person as a U.S. person through lawful permanent residence or the protected-individual definition in 8 U.S.C. 1324b(a)(3). It separately addresses organizations. For an individual applicant, the existence of a U.S.-incorporated employer does not answer the individual's status question.
DOJ's export-control fact sheet, revised March 2024, identifies U.S. citizens, U.S. nationals, lawful permanent residents, and people granted refugee status or asylum among U.S. persons. It explains that ITAR and EAR do not themselves impose citizen-only hiring requirements. An employer may need government authorization to release covered items to someone outside those categories.
Use the full current definition when a status question is technical. Pending an application for a status is different from having been granted that status. The phrase international applicant is also too broad to resolve a person's circumstances. Seek qualified advice when your own classification is uncertain.
This prevents two errors. Citizen-only shorthand can unnecessarily narrow a search, while treating every work-authorized person as a U.S. person can create an inaccurate answer. Read the relevant definition before choosing an application answer.
Separate four questions that often share a paragraph
Start with the job's country and actual duties. Then identify which sentence concerns each requirement. A role in a U.S. office may have different conditions from another role at the same company abroad.
Employment authorization: Can you perform this employment in the stated country and circumstances? Does the employer ask separately about present or future visa sponsorship? DOJ's current IER FAQs explain that employers generally may ask about the legal right to work and the need for employment visa sponsorship.
Export access: Does the work involve covered technology or technical data, and what access or authorization is required? This is the question raised by the ITAR wording. An employment visa and an export authorization are different processes.
An independent citizenship condition: Does the posting identify a separate program requirement? The statute referenced by ITAR includes exceptions to its nondiscrimination rule for citizenship restrictions required by specified laws, regulations, executive orders or government contracts. Whether a particular restriction qualifies requires facts this article cannot adjudicate.
Security clearance: Does the role require an existing clearance or the ability to obtain and maintain one? Read the required qualifications for that separate timing condition. Do not substitute a favorable answer about export access for the clearance condition.
Record an answer for each of the four requirements, leaving an unresolved condition marked unknown.
A completed wording-check card
The following phrases are illustrative wording, not quotations from one employer. The completed readings show what a phrase establishes and what it leaves unresolved. They are search instructions rather than findings about a person's eligibility.
| Illustrative phrase | Completed reading | Question still to resolve |
|---|---|---|
| U.S. person required under ITAR | Export-access classification is material; citizen-only shorthand is insufficient | Which current definition and assessment apply to this role? |
| Eligible to obtain export authorization | An authorization route is mentioned | Will this employer pursue it for this requisition, and what must happen before access? |
| U.S. citizenship required for the program | A separate narrower condition is stated | What specific program condition applies, especially if another paragraph is broader? |
| Authorized to work without sponsorship | Employment authorization and sponsorship are being addressed | Is export access or clearance separately required? |
| Must meet export-control requirements | The description does not explain the actual route | What requirement, access, authorization and responsible office does the employer mean? |
The second row matters when a listing looks welcoming. A possible route is not an approval, an undertaking to file, or a start date. Ask about the employer's actual process instead of recording “sponsorship available” without specifying which kind.
The third row matters in the opposite direction. Recognizing the broad U.S. person definition does not erase a separately stated citizenship condition. Preserve both passages and clarify their relationship. If you believe a restriction is improper, get appropriate assistance rather than changing your answer to work around it.
The card identifies the fact you need before spending time on an uncertain application. Keep the posting unresolved until that material fact is known, rather than classifying it from one phrase.
Read a real Rocket Lab posting from body to form
The Rocket Lab Senior Machine Learning Engineer II posting, employer-linked Greenhouse destination 8025567003, was publicly readable during this review. It identifies Long Beach, California and work on electro-optical and infrared image analysis. The technical duties include model development and ML pipelines.
Its required-qualification list contains a program citizenship sentence displayed as “S. citizenship is required, due to program requirements.” The initial appears incomplete on both the corporate page and its linked Greenhouse posting; this review does not infer the missing character. The same list requires the ability to obtain and maintain a government security clearance. A later preference names TS/SCI.
Farther down, the U.S.-office export paragraph lists citizens, lawful permanent residents, people admitted as refugees or granted asylum, and a route involving required government authorizations. That broad paragraph does not explain how it relates to the narrower program sentence.
The linked form separately asks about citizenship status and active clearances. It also asks whether the applicant meets the required qualifications. Seeing those fields does not resolve the incomplete program wording. This review read the public page without entering information or submitting an application.
There is another identity detail worth preserving: the corporate detail page displayed a different Job Ref from the Greenhouse destination number. Include the Long Beach title and Greenhouse URL ending 8025567003 in a clarification, and mention the differing corporate reference if identification is uncertain.
Here is the completed annotation:
| Part of the actual posting | What it contributes | What the applicant should avoid assuming |
|---|---|---|
| Required program sentence | A citizenship condition is presented, with an incomplete initial | That a writer may silently repair or waive the sentence |
| Required clearance sentence | A process to obtain and maintain clearance is a separate condition | That export classification satisfies this condition |
| U.S.-office export footer | Several status categories and a possible authorization route are described | That the general footer overrides every program-specific condition |
| Application questions | Citizenship, active clearance and qualification responses are separate | That a form option proves the employer considers that category for this role |
The completed result is clarification needed about the program condition. It is not a declaration that the position accepts every U.S. person, nor a finding that Rocket Lab violated employment law.

Two fictional candidates need different answers
Fictional teaching examples: Lina is a lawful permanent resident evaluating U.S.-office software roles. Dev has a work-authorization arrangement confirmed for the employment under consideration but has not established the applicable export-access route. These are invented circumstances; neither example decides a real person's legal status.
Lina reads a fictional role whose only relevant export sentence requires a U.S. person under ITAR. She does not discard it simply because she is not a citizen. Her next action is to review the actual definition, the remaining requirements and the employer's appropriate assessment process.
When Lina reads the actual Rocket Lab example, her next action changes. The role also presents the program citizenship condition. She holds that requisition for clarification rather than relying on the generic export footer. A different technical role at the company could have different conditions.
Dev reads a fictional posting explicitly mentioning possible export authorization. He records the employer's willingness to pursue that route as unknown. His confirmed employment authorization does not answer that question, and the advertisement does not establish an approval.
Dev's question is operational: does this requisition support the applicable authorization process, who handles it, and what access or start conditions depend on it? He also keeps any employment-visa sponsorship question separate.
These cases produce three distinct next steps: continue reviewing a clearly stated U.S. person condition, clarify an additional program restriction, or investigate an explicitly mentioned authorization route. They do not produce a generalized permission to apply to every aerospace job.
A finished inquiry about the ambiguous program sentence
Lina prepares the following fictional, unsent message about the real posting. No employer reply is assumed:
Subject: Program and export requirements — ML Engineer II, Long Beach
Hello Recruiting Team,
I am reviewing the Senior Machine Learning Engineer II posting at the Greenhouse link ending 8025567003. The required qualifications include a program citizenship sentence whose initial appears incomplete, while the U.S.-office export paragraph lists broader categories and a possible authorization route.
Could you clarify the exact citizenship requirement for this Long Beach role and whether it is separate from the export-control assessment? Does the broader paragraph describe an available route for this requisition, or do the specific program conditions restrict it?
Please also identify the appropriate contact for any export-compliance questions.
Thank you.
The message asks about published requirements before transmitting personal documents. It gives the employer enough context to locate the issue without sending a passport, immigration record or sensitive technical material.
If a reply describes a company-wide policy, ask whether it answers the specific program condition. If it confirms a narrower requirement, record that condition without claiming the general U.S. person definition changed. If it says authorization may be pursued, distinguish willingness, submission and approval.
If no useful answer arrives, preserve the unresolved issue. Do not answer a required all-qualifications question Yes merely because the broader paragraph is more favorable. Use truthful responses and the employer's stated instructions when making the application decision.
Know the purpose of a document request
DOJ's export-control fact sheet distinguishes an export-compliance assessment from Form I-9. It recommends keeping them separate and preserving employees' choice of acceptable I-9 documents. An employer may need citizenship or immigration-status information for an applicable export assessment, but that is a different purpose from verifying permission to work.
For a real request, establish the verified recipient, purpose, stage and secure submission method. Ask whether the request concerns export compliance, onboarding or another identified process. That question helps you follow the correct instructions without guessing from a file-upload label.
Do not use a broadly shared application tracker to store document numbers. A note can record the confirmed requirement, responsible office and next action without copying identity records. If the confusion concerns onboarding stages, ask the verified onboarding contact which process and instructions apply.
The current IER FAQs direct people with possible citizenship-status discrimination concerns to IER. Its guidance is an appropriate starting point for assistance; a job-search article cannot decide whether a particular employer's restriction is lawful.
Finish with the requirement that changes your decision
Keep the exact export wording, any independent program condition, clearance requirement and employment-authorization question together. Reopen the employer source before acting because a saved excerpt can omit the narrower condition that matters.
An existing document is enough for this comparison. LandOffer has an interest in job-search tools, but no listing filter can determine your legal classification, grant export authorization or waive a program condition.
To use the method, choose one recent role on LandOffer.ai, complete the four-question annotation and identify the single unresolved requirement that could change your decision. Continue the technical review when all four conditions are clear; otherwise, prepare a requisition-specific clarification before answering the affected field.


