Is 'Software Engineer' Actually a TN Visa Profession?

The USMCA profession list has no line item for "software engineer" — here is the title that actually gets you across the border.

You have an offer letter that says "Software Engineer." You are Canadian or Mexican, you qualify for USMCA professional status, and someone just told you TN visas are fast, cheap, and don't require a lottery. Then you actually open the USMCA profession list and search for "software engineer." It is not there.

That is not a website error or an outdated list. As of 2026-09-12, the USMCA Appendix 2 professions annex — the successor to the original NAFTA list — has never contained a category called Software Engineer. It has also never been updated to reflect how the tech industry organizes job titles today. If you are trying to use TN status for a coding-heavy role, the category almost everyone gets routed into instead is Computer Systems Analyst, and understanding why that substitution happens, and where it can go wrong, is the whole ballgame.

The TN profession list was frozen decades ago

The TN nonimmigrant classification comes from the United States-Mexico-Canada Agreement (USMCA), which replaced NAFTA in 2020 but carried over the original professional occupation list essentially unchanged. That list, in Appendix 2 to Annex 16-A, enumerates specific job titles and their minimum credential requirements — things like Engineer, Accountant, Physician, and, relevant here, Computer Systems Analyst.

The list was drafted in the early 1990s, before "software engineer," "site reliability engineer," "machine learning engineer," or "full-stack developer" existed as common industry titles. There has been no update to add modern tech job titles. This is why the mismatch you are running into is structural, not a mistake on your employer's part.

What is actually on the list for tech-adjacent roles

Here is how the relevant categories on the USMCA list compare to how the industry actually names jobs today:

Notice what is missing entirely: Data Scientist, DevOps Engineer, Product Manager, UX Designer, and Machine Learning Engineer have no clean home on this list at all. If your title is one of those, the Computer Systems Analyst route is often the only viable path, and it depends even more heavily on how your duties are described.

Why the title on your offer letter almost doesn't matter

Here is the part that surprises most candidates: a border officer at a port of entry, or a consular officer processing your TN application, is not primarily looking at what your company calls you. They are looking at whether your day-to-day job duties match the description of a listed profession.

This means two candidates with the identical job title "Software Engineer" can have very different TN outcomes:

1. Candidate A spends their day analyzing business requirements, designing data structures, and building systems to process organizational information — duties that map cleanly onto the traditional "Computer Systems Analyst" description.
2. Candidate B spends their day writing algorithm implementations for a specific technical stack with limited business-analysis component — duties that an officer may view as further from the listed category's language.

Both have the same title. Only one may have an easy path, depending entirely on how the supporting letter and job description are written and how the officer interprets them.

Common mistakes

• Assuming the job title is what gets evaluated. Officers look at duties, not titles. A support letter that just restates "Software Engineer" without mapping duties to the Computer Systems Analyst description invites scrutiny.
• Not requesting a detailed support letter from the employer. The single most useful document in a TN application is a letter from the employer that explicitly ties the role's actual responsibilities to the language of the USMCA profession category. Employers unfamiliar with TN sometimes write a generic offer letter instead.
• Traveling without understanding the credential requirement. If the Computer Systems Analyst category in your case requires a bachelor's degree and you have a non-traditional path (bootcamp, associate degree, or self-taught background), that gap can be a real problem at the border, not a paperwork formality to smooth over later.
• Confusing TN with H-1B rules. TN has no lottery, no annual cap, and (for Canadian citizens) can often be processed directly at a land border port of entry rather than through a US consulate. But it also has no built-in bridge to permanent residency the way an H-1B petition can support through PERM and I-140 filings, and status must be renewed on a recurring basis. If you're a Canadian or Mexican candidate weighing your options, TN visa vs H-1B covers that tradeoff in depth.
• Not preparing for officer discretion. Because the underlying evaluation is judgment-based, two applicants with similar fact patterns can get different outcomes. This is not evidence the rule is being applied incorrectly — TN adjudication has always carried more officer discretion than more codified categories.
• Ignoring what happens after entry. TN status is tied to a specific employer and role. A change in job duties, a promotion into a title further from the listed profession, or a switch to a new employer can all require a new TN application. Read the complete TN visa guide for Canada and Mexico for the renewal and employer-change mechanics.

Old assumption vs. what the list actually requires

A note on the current climate for nonimmigrant workers

Separately from TN-specific mechanics, it's worth knowing that as of 2026-09-12, DHS has published a proposed rule (published 2026-09-10/11, comment period closing 2026-11-10) that would eliminate the discretionary 60-day grace period currently available to TN, H-1B, L-1, O-1, and E-visa workers after their qualifying employment ends. This is a proposal only — it is not law, and the 60-day grace period is still in effect today. TN workers should be aware this is under active public comment and could change; check the Federal Register docket (USCIS-2026-0364) directly rather than relying on secondhand summaries, and do not assume any particular outcome.

This is a separate issue from the F-1 student post-completion grace period, which is a different rule entirely (currently scheduled to shrink from 60 to 30 days effective 2026-09-15 under a Duration-of-Status rule that is itself being challenged in active litigation). If you are moving between F-1/OPT status and a work visa like TN, do not conflate the two grace periods — they have different rules, different timelines, and different legal status right now.

How to actually approach a TN application with an ambiguous title

If your offer letter says "Software Engineer" and you're evaluating a TN path, here is the general sequence most candidates and employers work through — this is a description of the process, not guidance on what to file for your specific situation:

1. Get your actual job description in writing — not the marketing title, but a real list of day-to-day duties and responsibilities.
2. Compare those duties against the Computer Systems Analyst language in USMCA Appendix 2, ideally with input from an immigration attorney who has handled tech TN cases before.
3. Have the employer draft (or revise) the support letter to describe the role using language that tracks the listed profession, where that description is accurate.
4. Confirm your degree or experience meets the category's credential requirement, and gather transcripts or a credential evaluation if your degree was earned outside the US.
5. Decide on filing method — Canadian citizens can often apply for TN classification directly at a land border port of entry or pre-clearance facility; Mexican citizens generally need to obtain a TN visa stamp at a US consulate first.
6. Consult an immigration attorney before travel if there is any ambiguity in how your duties map to the listed category — this is exactly the kind of judgment call that benefits from professional review rather than a DIY approach, especially given how much discretion the reviewing officer has.

None of these steps are a guarantee of any particular outcome. Whether your specific role, degree, and duties add up to a qualifying TN case is a legal determination that depends on facts a blog post cannot evaluate for you.

Frequently asked questions

Is Software Engineer an official TN visa profession

No. The USMCA Appendix 2 profession list, unchanged since NAFTA, does not contain a line item called "Software Engineer." The closest listed category most software roles are matched to is Computer Systems Analyst. Whether your specific role qualifies depends on your actual duties and degree, and only a licensed immigration attorney or the reviewing officer makes that determination.

Can I still get a TN visa if my job title is Software Engineer

Possibly, but the title on your offer letter is not what a border officer or consular officer evaluates. What matters is whether your actual day-to-day duties match the Computer Systems Analyst category and whether you hold a qualifying bachelor's degree or equivalent professional experience recognized under USMCA. Many candidates with a Software Engineer title do cross successfully when their employer frames the petition support letter around analyst-type duties, but this is a case-specific judgment call for your attorney.

What degree do I need for TN as a Computer Systems Analyst

USMCA generally expects a baccalaureate degree in computer science, information systems, or a closely related field for the Computer Systems Analyst category, though the category's text has historically allowed for certain combinations of postsecondary diploma plus experience in some interpretations. Because degree-equivalency evaluations vary and USCIS or CBP officers have discretion, confirm your specific credential against current requirements with an immigration attorney before you file or travel. USCIS's own Policy Manual chapter on USMCA professional eligibility lays out the credential framework officers apply.

What happens if my job title does not match a TN profession

If your title does not map cleanly to a category on the Appendix 2 list, a border officer or consular officer can deny entry or refuse to issue the TN classification even if your underlying work would otherwise qualify. This is called a title mismatch problem, and it is one of the most common reasons Canadian and Mexican TN applicants get turned away. The fix is aligning your support letter and duties description with the listed category language, not changing your resume title alone.

Is TN a better option than H-1B for a software role

TN has no annual lottery, no cap, and can often be processed at the border for Canadians, which makes it faster when it fits. But TN requires annual or up-to-three-year renewal, has no direct path to permanent residency the way H-1B petitions can support, and depends entirely on correctly matching your duties to a listed profession. Which visa fits your situation is a decision to make with a licensed immigration attorney, not from a blog post.

If you're a Canadian or Mexican software professional trying to figure out whether TN, H-1B, or another category fits your specific situation, that comparison is worth getting right before you commit to a strategy — see also how TN compares to H-1B on the broader tradeoffs between employer-sponsored categories. For personalized help building a job search and sponsorship strategy around your actual visa options, reach out to F1Jobs — we work with international candidates across TN, H-1B, and OPT pathways every day, though we're not a substitute for your own immigration counsel.