The employer must be enrolled in E-Verify
The single most common blocker is employer eligibility. A STEM OPT extension requires the employer of record to be enrolled in E-Verify and to have a valid EIN used for payroll. Staffing arrangements complicate this because the employer of record and the day-to-day worksite are frequently different organizations. DevGrid Staffing operates as the employer of record for pod engineers, which keeps E-Verify enrollment, wage records, and the training plan under a single accountable entity rather than spreading them across a chain of vendors.
Third-party placement is not automatically disqualifying, but it must include a bona fide employer-employee relationship. That means the employer of record controls the engineer's assignment, evaluates performance, and can demonstrate real oversight — not merely invoice for hours.
Form I-983 has to describe real infrastructure work
The I-983 training plan is a learning document, not a job description. For a cloud or DevOps engineer it should name concrete skills to be acquired: Terraform module authoring, Kubernetes workload scheduling, incident response rotations, CI/CD pipeline hardening, or cost governance in a multi-account AWS organization. Each objective needs an explanation of how the skill will be taught, who will teach it, and how progress will be measured.
Generic plans copied between candidates are the fastest route to a denial or an unfavorable site visit outcome. Tie each objective to the actual systems the engineer touches — the pipeline they maintain, the clusters they observe, the runbooks they write.
Supervision, evaluations, and reporting cadence
STEM OPT requires a named supervisor who can attest to the engineer's work, plus self-evaluations at the twelve-month mark and at the end of the extension, each signed by that supervisor. In a pod model, the pod lead is usually the correct supervisor of record because they review pull requests, run retrospectives, and own the delivery outcome.
Separately, the engineer must report changes of address, employer, or supervisor to their Designated School Official within ten days, and validate their information every six months. A missed validation window is treated as a status problem even when the underlying work is entirely legitimate. We build these dates into the pod's operating calendar so they are never dependent on individual memory.
Wages, hours, and material changes
Compensation must be commensurate with similarly situated U.S. workers, and the role must be a paid position of at least twenty hours per week that is directly related to the engineer's STEM degree. A platform engineer with a computer science or information systems degree clears the relatedness test comfortably; the documentation should still make the connection explicit.
Material changes — a move from pipeline automation to a purely managerial role, a significant reduction in hours, or a change of worksite — require an amended I-983. Treat scope changes as compliance events, not just staffing events.
Key takeaways
- The employer of record must be E-Verify enrolled and exercise genuine oversight.
- Write the I-983 around the specific infrastructure the engineer will actually operate.
- Assign a technical pod lead as supervisor of record so evaluations reflect real work.
- Track the six-month validations and ten-day change reports on a shared calendar.
- Amend the training plan whenever role, hours, or worksite change materially.
Need a pod that already works this way?
DevGrid Staffing assembles managed DevOps, platform, and SRE pods with the compliance and delivery practices described here built in from week one.