Establish the specialty occupation on duties, not titles

A specialty occupation normally requires at least a bachelor's degree in a specific field. A title such as systems engineer does not show this alone. Duty descriptions with percentages explain how the person spends their working time.

Examples include network design, linking login systems, writing system setup code and planning backup capacity. The record connects those duties with knowledge from computing or engineering degrees. A description mainly about support can suggest a less specialized role.

Degree-to-duty alignment

A degree in a related field needs a clear link to the duties. Coursework, earlier specialized work and, where appropriate, a review of qualifications can explain that link. Certificates support the record but do not replace the degree connection.

The job description, labor condition application, team chart, offer letter and supporting letter need to describe the same role. The labor condition application records employment conditions. Wage levels also need to agree across documents.

Client sites, itineraries, and control

Third-party worksites are client locations where another employer's staff work. Filings covering them need records of the placement and the employer's right to control work. Records include work agreements, available client confirmation and a schedule covering the requested period.

Control records explain who assigns tasks, reviews performance and provides tools and standards. They also show who can reassign the engineer. Client managers may coordinate schedules without taking over the employer's role.

Timing and contingency

Filings subject to the annual H-1B limit follow a registration and lottery cycle with a fixed start date. Hiring timelines need to account for that cycle and uncertain selection. This is general information, not advice on a route for an individual case.

Premium processing speeds the decision on a filing, not lottery selection. Wage decisions, worksite plans and supporting records take preparation. They are separate from the lottery outcome.

Make a complex engineering role understandable

A clear description separates design, setup and ongoing operations. Design covers connections and login boundaries; setup covers platform settings and system setup files. Operations covers watching and maintaining those systems. The description needs to reflect actual work, not duties implied by a broad title.

Worksite, supervision and reporting records need to match the actual arrangement. Records can explain how client and employer teams work together. Technical records alone do not establish eligibility. General information cannot replace a review of current rules and individual facts.

Key takeaways

  • Duty descriptions show percentages of time spent on specialized work.
  • Records need to agree on the role, wage level and worksite.
  • Client-site records explain the employer's control over the work.
  • Lottery selection remains uncertain, even when preparation is complete.

Read this as an employer's overview of how we hire, not legal advice. TalentOp Systems LLC does not handle visa matters for anyone; for your own case, please speak with a qualified, licensed immigration attorney.

TalentOp Systems offers IT software services in cloud, application development and cybersecurity.

Contact us →

Related: Visa questions →