Do not buy a full petition kit before you know the real blocker.
If the blocker is category fit, run the free checker first. If the EB1A/O-1A evidence is real but messy, use Profile Builder Pro. If NIW is cleaner, use the NIW kit.
Use this to separate a plausible EB1A evidence map from a title-only profile.
Free EB1A / O-1A evidence Profile Builder ProUse this when papers, citations, judging, critical-role evidence, or original contribution claims need a category map.
$99 NIW route EB2 NIW KitUse this when the U.S. national-importance story is stronger than the personal-acclaim story.
$89First, separate self-petition from employer sponsorship
A software engineer with a PhD may have more than one immigration route. The route changes depending on who sponsors the case and what the evidence proves.
| Route | Employer sponsor? | What it usually tests |
|---|---|---|
| EB1A | Often self-petitioned | Individual extraordinary ability, recognized work, qualifying criteria, and whole-record strength. |
| EB2 NIW | Often self-petitioned | Advanced degree or exceptional ability plus a proposed endeavor that satisfies the NIW framework. |
| EB1B | Usually employer-led | Outstanding professor or researcher logic tied to a qualifying employer and research role. |
| PERM / employer EB2 / EB3 | Employer-led | Job-offer and labor-certification path, not an independent profile claim. |
If your company will not sponsor you, do not spend energy pretending EB1B or PERM is available. Pressure-test the self-petition paths and ask counsel how your status and timing facts affect the decision.
What the PhD helps prove
The PhD matters when it created evidence. The useful pieces are usually not the diploma alone. They are the artifacts around the work:
- publications with clear author contribution, venue quality, and field context,
- citations that show independent reliance on your methods, systems, findings, or datasets,
- reviewer, conference, program-committee, editorial, or grant-review evidence,
- research translated into products, patents, standards, clinical, security, AI, infrastructure, or public-interest outcomes,
- letters that explain impact rather than only say you are talented.
That evidence can support EB1A or NIW, but it supports them in different ways.
When EB1A is the cleaner test
EB1A becomes more plausible when the individual record is strong outside the employer's internal narrative.
For a PhD software engineer, that may mean:
- cited research with field-level reliance,
- judging or peer review of other researchers' or engineers' work,
- original contribution evidence that a skeptical officer can follow,
- critical or leading technical role evidence with independent proof,
- high salary or compensation evidence with careful benchmarking,
- credible media, awards, invited talks, patents, open-source adoption, or standards work.
If the profile is mostly "I have a PhD and a strong job," EB1A may be too early. If the record shows independent recognition and contribution, EB1A may be worth a serious evidence map.
When NIW may be cleaner
NIW may be cleaner when the work has a strong U.S.-focused proposed endeavor, but the personal-acclaim record is not yet mature enough for EB1A.
Examples:
- AI safety, cybersecurity, healthcare AI, infrastructure resilience, energy, defense, public health, or other work that can be tied to U.S. national importance,
- credible evidence that you are well positioned to advance the work,
- a proposed endeavor that is more concrete than "continue working as a software engineer."
NIW is not "easier" in a lazy sense. It is a different proof job. The endeavor, national-importance argument, and well-positioned evidence need to be coherent.
How long will it take?
Do not use a generic timing estimate to choose a category. Timing depends on petition processing, premium-processing availability, visa-number availability, country of chargeability, priority date, whether adjustment of status is available, consular processing, RFEs, and personal status facts.
Use the State Department Visa Bulletin for visa-number context, then ask counsel how your facts change the practical path.
What to collect before you pay anyone
- Publication list with your role, venue, dates, and contribution.
- Citation snippets grouped by what the citing work relied on.
- Reviewer, judging, program-committee, or editorial proof.
- Independent adoption proof: users, customers, deployments, papers, standards, patents, open-source use, or outside technical reliance.
- Employer facts: whether the company will sponsor anything, and if so, which category.
- Status facts for counsel: visa, OPT/STEM OPT, H-1B, O-1A, priority dates, dependents, travel, and deadline constraints.
This is the creator-style "free sample" step for your own case: make the one-page evidence inventory before buying the full package.
Bottom line
If you are a PhD software engineer and the company will not sponsor you, do not start by asking "EB1 or EB2?" Start by asking which proof job is real.
Choose EB1A to test individual distinction. Choose NIW to test a U.S.-important proposed endeavor. Bring status and filing-timing questions to counsel. Use ChatEB1 for the evidence map and packet structure, not as legal advice.
Start with the free EB1A checker. If the EB1A/O-1A evidence is real but messy, use Profile Builder Pro. If the NIW proposed-endeavor route is cleaner, use the EB2 NIW Kit.