AI / ML professionals

Organize technical impact before comparing U.S. pathways.

A profile hub for AI engineers, machine learning researchers, applied scientists, and technical founders preparing O-1, EB-2 NIW, or EB-1A research questions.

Official-source trail visibleNo route scoringCounsel-ready questions
Review O-1 evidence themesBuild an evidence inventoryEvidence organization only
Research preparation boundary

Use this page to organize public criteria, evidence categories, timing questions, and official sources before a professional consultation.

Route dossier

Keep profile, evidence, sources, and questions in view.

Each page keeps context, evidence categories, source status, and professional questions as separate working surfaces before the detailed notes take over.

01

Profile context

Use the reader's facts as the first lens before comparing route mechanics.

02

Document questions

Keep evidence questions separate from timing, source checks, and any professional interpretation.

03

Source trail

Use official-source status and update timing as part of the page, not as a hidden footnote.

04

Counsel brief

Move the page into prepared questions, packet structure, and next-source checks.

Preparation loop

Move from research notes to a cleaner first conversation.

PathwayMatch keeps the public flow practical: organize evidence, prepare professional questions, and only share details when the user explicitly chooses a handoff.

01

Inventory evidence

Group broad evidence categories before interpreting strength or route implications.

Open inventory
02

Prepare questions

Turn route names, timing pressure, and source gaps into a short consultation agenda.

Open checklist
03

Consent-based handoff

Keep private details and legal advice inside the professional relationship the user chooses.

Review boundary

Profile signals

Technical impact can appear in more than one format.

AI and machine learning profiles often include a mix of academic, commercial, open-source, and company-internal signals.

  • Published research, citations, conference work, patents, or standards contributions.
  • Open-source libraries, model releases, package usage, GitHub adoption, or technical community impact.
  • Production systems, platform influence, infrastructure ownership, or business-critical technical leadership.
  • Founder evidence such as product traction, funding, customer adoption, or market relevance.

Route questions

The same evidence may raise different O-1, NIW, and EB-1A questions.

This profile page helps users avoid flattening every achievement into one generic evidence pile.

  • O-1 research may focus on extraordinary ability, role, recognition, and petitioner structure.
  • EB-2 NIW research may focus on proposed endeavor, national importance, positioning, and benefit questions.
  • EB-1A research may focus on sustained acclaim, recognition, and evidence categories with a higher bar.
  • Employer-internal impact often needs special care before it is treated as field-level evidence.

Preparation

Build a clean inventory before interpreting strength.

The first useful output is a structured evidence map and a short list of questions for counsel.

  • Separate public evidence from company-confidential or personal facts.
  • Group evidence by source, audience, and field impact.
  • Mark what is independently verifiable and what needs context.
  • Bring route-specific questions to a lawyer or authorized professional before drawing conclusions.

Deeper research notes

Turn the page into a stronger preparation packet.

These notes add context, source checks, and counsel-prep prompts without turning the page into a route decision.

Profile framing

Start with the person’s work pattern and timing pressure.

Profile pages are strongest when they describe why a reader is researching, what facts they should organize, and which assumptions should stay open.

  • Separate current status, work authorization dates, employer dependence, and company role before comparing route names.
  • List public career signals separately from confidential employer, client, funding, or ownership details.
  • Keep evidence examples broad until a lawyer or authorized representative can review personal facts.
  • Use the profile to choose the next research page, not to make a route decision.

Evidence planning

Turn achievements into reviewable categories.

Many high-skill users arrive with scattered proof. The useful product job is to make that material easier to discuss without judging its legal weight.

  • Group recognition, authorship, product adoption, leadership, company traction, and field-impact examples by source type.
  • Flag which examples are public, independently verifiable, employer-internal, confidential, or likely to need context.
  • Write down what changed recently, such as new funding, publication, role scope, open-source adoption, or timing pressure.
  • Bring gaps and source questions into the first professional conversation instead of filling them with guesses.

Continue researching

Use these connected pages to move from timing pressure to comparison, evidence preparation, and tool output.

O-1 evidence categoriesOrganize recognition, authorship, judging, role, and comparable evidence themes.O-1 vs EB-2 NIWCompare temporary work mechanics with immigrant-route framing.AI engineer research fileSee how an anonymous research scenario can be structured before legal review.Evidence inventory builderCreate a research-prep outline without uploading sensitive documents.EB-1A evidence categoriesCompare higher-bar recognition and sustained-acclaim evidence themes.

Source review

Official references stay visible.

This page keeps the public-source trail near the research workflow so dynamic facts can be rechecked before a professional conversation.

CurrentChecked 2026-05-07Monthly review

Questions for counsel

Prepare the professional conversation.

These prompts are meant to organize discussion topics, not to answer them automatically.

  • Which technical-impact signals are useful to organize before deeper legal review?
  • Which items are public and independently verifiable?
  • Which evidence themes may be route-specific rather than generally useful?
  • Which company-internal facts should be handled carefully or kept out of lightweight tools?

Important boundary: PathwayMatch provides research preparation, not legal advice. It does not make legal judgments, choose a strategy, predict results, or rank lawyers.