Home / Blog / H-1B not selected
H-1B lottery, software engineers, O-1A, EB1A, and evidence mapping

H1B not selected in 2026: can EB1A be a plan B for software engineers?

Maybe. But H-1B disappointment is not EB1A evidence. The right first move is to separate immigration timing from the proof map: what can be tied to you, what is independent, and what survives outside employer brand.

Published Jun 23, 2026 ยท Educational only, not legal advice

Short answer: if your H-1B was not selected, EB1A and O-1A may be worth pressure-testing only if the evidence already points beyond ordinary employment success. Talk to counsel about status, timing, travel, filing strategy, and legal eligibility. Use this page only to organize the evidence question.
Free first pass

Do not buy a filing product just because the lottery failed.

Use the free checker to route the profile. Buy only when the evidence map points to a real next step.

First pass Free EB1A checker

Answer five no-upload questions and route profile mapping, self-filing, RFE, bundle, or counsel-first timing.

Free Evidence map Profile Builder Pro

Use this when the profile may be real but the criteria, proof gaps, and attorney handoff are still messy.

$99 Full stack Complete EB1A Bundle

Use this only when profile mapping, self-filing structure, and RFE planning all need to work together.

$199

H-1B lottery loss is a timing problem. EB1A is an evidence problem.

When the lottery fails, the pressure is real. But that pressure does not make EB1A easier. It only makes the decision more urgent.

Before treating EB1A as a plan B, separate three questions:

  1. Status and timing: What are your legal options, deadlines, travel constraints, employer options, and fallback statuses?
  2. Evidence strength: Is there proof of distinction that travels outside a resume?
  3. Packet strategy: Can the evidence be mapped into a coherent case without exaggeration?

The first question belongs with counsel. The second and third are where ChatEB1 can help you organize your thinking before you spend more.

The mistake: chasing "3 criteria" too mechanically

People often hear that EB1A requires meeting at least three regulatory criteria and then start collecting items like a scavenger hunt. That can backfire.

A software engineer can sometimes build evidence around high salary, judging, authorship, original contributions, critical roles, awards, media, or other categories. But the final question is not whether three boxes can be named. It is whether the whole record reads as extraordinary and credible.

Practical test: if the case sounds strong only while you narrate it, but the documents do not independently carry the story, it is not ready.

A cleaner evidence map for software engineers

Start with four buckets:

Bucket Question Good proof looks like
Independent proof What is visible outside your employer? Citations, patents, public talks, judging, peer review, press, open-source adoption, standards, external users, or outside expert context.
Individual traceability What can be tied to you, not just your team? Specific ownership, commit history, architecture docs, named author role, reviewer proof, technical leadership evidence, or letters with concrete facts.
Field comparison Who is the right peer set? A narrow enough field definition that your evidence can be compared honestly.
Final merits Does the story hold without company-brand halo? A record that still reads unusually strong after removing employer prestige and adjectives.

What evidence often works for technical profiles

  • Original contribution: a technical system, model, infrastructure, paper, dataset, patent, framework, or open-source project others relied on.
  • Judging or review: conference review, hackathon judging, grant review, technical award judging, code review in a recognized project, or editorial/reviewer proof.
  • Critical role: not just a title, but proof that the organization or product depended on your work.
  • High salary: useful only with careful benchmarking and context. It does not replace the case story.
  • Authorship and visibility: papers, technical blogs, invited talks, serious engineering posts, or media that is about the work, not fake PR.

When O-1A may be part of the conversation

O-1A and EB1A often draw from overlapping evidence, but they are not the same filing decision. O-1A is temporary. EB1A is a green-card category. Legal strategy, employer facts, timing, and status details matter.

Use the evidence map to decide whether the profile deserves a serious counsel conversation. Do not use an article to choose the filing route.

When it is probably too early

  • Your strongest evidence is mostly internal performance feedback.
  • You have no independent proof yet.
  • Your "field" is just "AI" or "software engineering" with no narrower comparison set.
  • Your salary evidence is the only strong category.
  • You are relying on future speaking, future press, future reviews, or hoped-for adoption.

What to do this week

  1. Ask counsel what status and timing options must be protected after the H-1B result.
  2. Make a one-page evidence inventory across independent proof, traceability, field comparison, and final merits.
  3. Run the free checker before buying anything.
  4. If the profile is real but messy, use Profile Builder Pro to build the evidence map.
  5. If the evidence is already strong and the next job is packet structure, look at Self-Filer or the Complete Bundle.

Bottom line

EB1A can be a serious path for some software engineers. It is not a consolation prize for losing the H-1B lottery.

Start with the evidence. Then choose the smallest useful next step. Use the free EB1A checker first. If the evidence is real but disorganized, use Profile Builder Pro. If the whole EB1A stack needs rebuilding, use the Complete EB1A Bundle.