Pick the occupational classification honestly
Choose the job type from the main duties, not the lowest pay available. Network design, systems administration and software development have different minimum wage levels. A title alone does not decide which category fits.
Write the duties first, then choose the category they support. An engineer mainly designing cloud and office networks is not a systems administrator just because of the title. Reversing this order can make records disagree.
Wage levels track requirements, not seniority feelings
Wage levels depend on required experience, education, supervision and special skills. Five years of cloud design experience and independent design decisions do not fit the lowest (Level I) wage tier. A job posting can reveal that mismatch.
Hiring materials, internal role descriptions and the wage decision must agree. Adding requirements to attract candidates can change the required wage level. Check that all teams describe the same requirements.
Worksite geography in multi-site deployments
Prevailing wage depends on where work happens. Months at a factory in another area may bring different wage and notice duties. Record planned worksites when filing and review duties when placements grow longer.
Apply the same checks to remote work and mixed office and home work. The actual work location matters. Do not rely only on the employer's office address.
Keep payroll and the record in sync
Pay the required wage as soon as the duty begins. This includes gaps between project stages when the employed engineer has no billable work. A reviewer can readily find gaps in pay records.
Keep the public access file, wage decision, job description and pay records together. The public access file holds employment records available for public review. Assign an owner to check these records quarterly, like records of system changes.
Keep role architecture aligned across teams
Keep one current role description shared by hiring, engineering and project teams. Include main duties, education, experience, locations and supervision. Actual work can change even when the title does not. Matching records support accurate job and pay reviews.
Do not reshape a job description to fit the lowest wage category. Base the review on actual requirements and work locations, including remote work. A qualified immigration attorney should assess applicable duties and changes. Technical records add context but do not replace wage or legal decisions.
Key takeaways
- Choose the job category from a written list of main duties.
- Keep hiring requirements consistent with the wage level.
- Review wage duties when the work location changes.
- Do not stop required pay during gaps in billable work.
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 →