IN THIS GUIDE · TN review for a systems analyst offered a role weighted toward hands-on programming
Start with the TN eligibility and application overview
Map the role's actual task split
Ask for a breakdown of time spent on systems analysis tasks, such as requirements gathering, system design, and evaluating technology solutions, versus hands-on programming tasks like writing and maintaining code. Job postings often use 'systems analyst' loosely for roles that are mostly development work. Get specifics: what percentage of the week involves design and evaluation work versus writing code, and who else on the team handles the analysis side if the applicant is doing mostly programming.
Compare the split against the analyst profession's scope
The systems analyst category is built around analysis, design, and evaluation duties, not primarily around hands-on software development. Where the offered role is substantially weighted toward writing and maintaining code, that shift matters and should not be minimized by keeping the title unchanged. Compare the applicant's actual responsibilities against what the analyst category is understood to cover, and treat a heavily programming-focused role as a separate classification question rather than a variation within the same category.
Consider whether the credential still fits
Confirm the applicant's education and experience support the analyst duties specifically, not just general IT competence. If the role is genuinely programming-heavy, the applicant's background may fit a different category better, or the offer letter itself may need revising to reflect analysis work more accurately if that is truly the core of the job. Do not assume that strong technical skills in general automatically resolve a mismatch between the profession claimed and the duties actually performed.
Resolve the boundary before documenting the case
Ask the employer to state plainly what proportion of the role is analysis versus programming and get that in writing. Where the split is close, discuss with the applicant and employer whether adjusting responsibilities toward more analysis work is realistic, or whether a different approach to the case makes more sense. Build family and relocation timelines around resolving this boundary question first, since a case built on an inaccurate duty description creates more risk than a short delay to get the description right.
Decide what happens if the answer is that it does not fit
A boundary review has two possible outcomes, and a plan that only contemplates one of them will handle the other badly. So agree in advance what the parties do if the honest answer is that the role has moved outside the profession being relied upon. Three responses are legitimate and one is not. The employer can change the job, genuinely reallocating the work so that the position matches the profession — which is a real business decision with consequences for the team and should be treated as one. The parties can consider whether a different listed profession fits the work as it actually is, remembering that each has its own requirements and that the credential must match the profession claimed rather than the general field. Or they can accept that this route does not fit and examine what else the facts might support. What is not legitimate is rewriting the description while leaving the job unchanged, because the authorization relates to the position described and a description the business will not follow creates a durable problem rather than solving a temporary one. Deciding this in advance also removes the pressure that produces the fourth option, which usually arrives late, under deadline, and framed as a small clarification. Hypothetical example: a building-envelope engineer's role turns out to be substantially site supervision, and the employer redefines the vacancy rather than the paperwork.
Sources reviewed 2026-09-07. This guide covers a preparation focus; it is not an individual eligibility assessment.