Do not frame the endeavor as a job title
“I work in automotive software” describes an occupation. A proposed endeavor should describe the concrete work you plan to advance and the problem it addresses.
Depending on the actual record, the work might concern safety-critical software, vehicle cybersecurity, resilient manufacturing systems, advanced driver-assistance validation, or a standards problem. Pick the lane the evidence can support. Do not borrow a nationally important label that the work history cannot prove.
Use a five-column evidence map
| Column | Question to answer | Useful proof |
|---|---|---|
| Endeavor | What specific work will continue in the United States? | Work plan, technical scope, project roadmap, role portability |
| Wider importance | Why does the problem matter beyond one employer? | Government priorities, standards, industry data, documented adoption |
| Past record | What shows the applicant can advance this work? | Patents, deployments, conference work, technical ownership, measured outcomes |
| Independent proof | Who can verify the work without repeating the resume? | External users, collaborators, standards participants, independent experts |
| Forward path | How will the work continue? | Planned projects, partner interest, implementation milestones, resource access |
Make patents prove impact, not merely existence
An accepted patent establishes that an invention exists. The petition still needs to explain what problem it addresses, how it relates to the proposed endeavor, and whether anyone used, licensed, implemented, cited, evaluated, or built on it.
For each patent, write one row with the technical problem, the applicant's contribution, the independent corroboration, the practical effect, and the proposed-endeavor connection. If a patent has no adoption evidence yet, say so and use it for the narrower claim it can actually support.
Turn ten years of work into verifiable outcomes
Years of experience are background. The useful evidence is what changed because of the work.
- What system, component, process, or standard did you influence?
- What improved: safety, reliability, validation time, defect rate, cost, throughput, or security?
- Who can corroborate the result, and which artifact makes it auditable?
- How does that result make the future endeavor more credible?
Replace broad claims such as “led critical projects” with a result, scope, baseline, and source.
Use consultations to compare case theories
Ask every firm the same five questions:
- What exact proposed endeavor would you use?
- What is the national-importance theory?
- Which facts support each NIW prong?
- What evidence gap creates the most risk?
- Who drafts the petition, and how will I review the argument and exhibit map?
A confident yes without a case theory is not much more informative than a no based on citation count alone.
Bottom line
Automotive software can be a credible NIW field, but the field name does not carry the case. The petition needs a specific endeavor, a wider-importance argument grounded in reliable sources, a record of relevant outcomes, and a believable forward plan.
If you need to organize those pieces before a lawyer call, the ChatEB1 EB2 NIW Kit provides a proposed-endeavor, Dhanasar-prong, evidence-gap, and attorney-handoff structure.