Suppose an accomplished applicant tells me, “My field is technology.” That may be true in ordinary conversation. It is rarely useful as an EB-1A case theory.
Technology includes semiconductor design, cybersecurity, machine learning, industrial automation, e-commerce, data infrastructure, product management, and thousands of other areas. A person can be outstanding in one of those areas without being nationally or internationally recognized across all of “technology.”
The field is not a label added to the petition. It is the lens through which the entire record will be judged.
Why “Technology Professional” Is Not an EB-1A Field of Endeavor
Suppose an accomplished applicant tells me, “My field is technology.” That may be true in ordinary conversation. It is rarely useful as an EB-1A case theory.
Technology includes semiconductor design, cybersecurity, machine learning, industrial automation, e-commerce, data infrastructure, product management, and thousands of other areas. A person can be outstanding in one of those areas without being nationally or internationally recognized across all of “technology.”
The field is not a label added to the petition. It is the lens through which the entire record will be judged.
Defining the EB-1A Field of Endeavor Under the Regulation
Under 8 CFR § 204.5(h)(2), extraordinary ability means a level of expertise indicating that the individual is “one of that small percentage who have risen to the very top of the field of endeavor.” That phrase — field of endeavor — is not decorative language. It reappears throughout the ten evidentiary criteria at 8 CFR § 204.5(h)(3): prizes “for excellence in the field,” membership requiring outstanding achievement “in the field,” judging experience in “the same or an allied field,” and contributions “of major significance in the field,” among others.
Every one of those criteria depends on how the field is defined. Define it too broadly, and the comparison group becomes so large that “top of the field” starts to mean almost nothing. Define it too narrowly, and there may be no field left to be recognized in at all.
When Your EB-1A Field of Endeavor Is Too Broad
A field that is too broad makes almost every part of the case less precise.
It becomes difficult to explain who the applicant’s peers are, which achievements are relevant, what compensation comparison makes sense, why a contribution is original, or whether recognition is meaningful. Projects that appear connected on a resume may look unrelated when measured against an undefined global category.
An applicant may have spent fifteen years developing specialized systems for one industry, yet the petition describes the person merely as an “IT professional.” That language erases the very specialization that makes the record compelling.
When Your EB-1A Field of Endeavor Is Too Narrow
The solution is not to define a field so narrowly that only the applicant occupies it.
A field such as “the development of one named product for one employer” is not a meaningful field of endeavor. It may simply restate the applicant’s job assignment. The field must be honest, externally recognizable, and broad enough to include other professionals whose work can be compared.
The goal is precision, not artificial exclusivity.
A Fictional Composite Technology Example
Consider a fictional composite: a senior engineer whose strongest achievements involve designing predictive-maintenance systems for industrial equipment.
Calling the person a “technology professional” is too broad. Calling the field “one proprietary monitoring tool” is too narrow.
A more coherent formulation might focus on the design and deployment of machine-learning systems for industrial predictive maintenance. That formulation connects the person’s technical expertise, business function, industry context, and body of work without reducing the field to a single employer or product.
The language is not magic. It must be supported by the career itself. But once the field is accurately defined, the rest of the record becomes easier to understand.
Three Tests for a Strong EB-1A Field of Endeavor
A useful field definition should satisfy three basic tests.
It should be honest. The definition must reflect what the applicant has actually done and intends to continue doing.
It should be coherent. The applicant’s principal achievements, recognition, and expertise should make sense within the same professional area.
It should be externally recognizable. Other professionals, organizations, publications, compensation sources, and industry actors should exist within the field.
If a proposed field fails one of those tests, the petition may be forcing the evidence into a narrative that the record does not support.
How Your EB-1A Field of Endeavor Affects Every Criterion
The field of endeavor is not confined to one paragraph near the beginning of the brief.
It affects whether judging occurred in the same or an allied field. It affects whether published material relates to the applicant’s work. It affects who counts as a meaningful comparator for salary. It affects whether a contribution was major within the relevant professional community. It affects whether the applicant’s recognition appears sustained and coherent.
This is why the field must be defined before the petition becomes a pile of exhibits.
A Field Should Reveal the Career, Not Rewrite It
Good EB-1A strategy does not invent a field around the evidence. It identifies the field that the career already reveals.
For many industry professionals, that requires a deeper discussion than job titles and keywords. A senior engineer may actually be an expert in a specialized commercial or technical problem. A product leader may have built a record around transforming one type of system across multiple organizations. An industrial technologist may occupy a narrow intersection of software, engineering, and operational reliability.
The right definition allows the adjudicator to see that trajectory.
A vague field hides the applicant’s expertise. An artificial field undermines credibility. The right field makes the record make sense.
Frequently Asked Questions
How narrow should an EB-1A field of endeavor be?
Narrow enough to reflect real specialization, but broad enough that other professionals, publications, and organizations exist within it for comparison. A field defined around a single product or a single employer usually fails that second test.
Can a software engineer define a specialized EB-1A field?
Often, yes — but “software engineer” or “technology professional” alone is rarely sufficient on its own. The field typically needs to reflect the specific technical problem, industry, or system that the engineer’s strongest achievements center on.
Does the intended future work need to relate to the field?
Yes. Adjudicators look at whether the applicant intends to continue working in the field of extraordinary ability, so the field definition should connect the applicant’s past record to their stated future plans.
Choosing the Right EB-1A Field of Endeavor
“Technology professional” describes a career. It rarely defines an EB-1A field. The same is true of “healthcare,” “finance,” or “media” — broad industry labels that feel accurate but dissolve the specificity a strong petition needs.
Silmi Law conducts strategy evaluations for professionals whose strongest achievements may not fit a generic academic or checklist model. The analysis begins with the applicant’s real field, work, and impact — not with a label borrowed from a job title.
Schedule a Strategy Evaluation with Attorney Sharif Silmi = Video Call
Legal Disclaimer
This blog post is provided for informational purposes only and does not constitute legal advice. Reading this content does not create an attorney-client relationship with Silmi Law Firm.
This article uses a fictional, composite scenario for illustrative purposes only. It does not describe any actual client, case, employer, compensation figure, or filing, and no identifying details of any real person are included or implied. Certain facts and details have been changed or omitted.
Immigration law, including EB-1A eligibility standards, is highly fact-specific and subject to change. The information above reflects general principles under 8 CFR § 204.5(h) as of the publication date and should not be relied upon as advice for any specific case. No outcome is represented or guaranteed.
Before taking any action related to an EB-1A petition or any other immigration matter, you should:
- Consult with a qualified immigration attorney
- Provide complete and accurate information about your specific circumstances
- Obtain written legal advice tailored to your situation
Silmi Law makes no guarantee of approval, outcome, or the completeness or accuracy of any information contained in this post.
For legal representation, contact Silmi Law at:
- Phone: +1 (443) 329-2929
- Email: info@silmilaw.com
- Website: silmilaw.com
