Turning Equal Access Into a Working Recruitment System
In the OpenAI and Statsig settlement, equal access is not left as a general promise to avoid discrimination. The agreement turns the reported PERM recruitment problem into a set of connected operating requirements: a job must have a stable identity, be findable on the company’s career sites, accept an electronic application through the ordinary route, and remain visible to the recruiting team afterward. The practical question here is how those pieces work together—and why an accessible application path is still different from a promise of selection.
Give every PERM-related opportunity an ordinary way in
The settlement requires each Respondent to draft a policy governing its PERM recruitment process and to prohibit citizenship-status discrimination in that process. The policy must be submitted to IER for review and approval within 120 calendar days of the agreement’s Effective Date, and the Respondent must implement it within 30 days after receiving approval. Those timing requirements matter to the agreement’s governance, but the more revealing part of the remedy is its design of the candidate’s route.
Each PERM-related position must have its own unique identifier. The agreement gives examples such as a unique URL, requisition number, or posting ID. The identifier must allow the position to be searchable from the Respondent’s internal, if any, and external career websites, and it must allow individuals to apply electronically through those pages. All PERM-related positions must be posted on the internal, if any, and external career websites. Electronic applications for those positions must be accepted through those sites in the same manner as applications for non-PERM recruitment.
A unique identifier can sound like a small administrative detail, but it solves a larger problem. A recruitment opportunity needs to remain the same opportunity as it moves between a posting, an application page, and the employer’s internal records. Without a stable reference, a position can be advertised in one place, described differently in another, and later become difficult to locate. The agreement does not prescribe one software product or data format. It does require an identity that supports searchability and electronic application, so the job is not merely present in a compliance file but usable through the career system where applicants normally begin.
The requirement also limits a common form of procedural separation. An employer might maintain one process for ordinary jobs and another process for PERM-related positions, with each process appearing defensible in isolation. The settlement’s language instead asks whether the PERM-related opportunity can be found and applied for through the same kind of internal or external career website. “Same manner” is best understood as a parity test at the application interface. The jobs need not have identical duties or qualifications, and the agreement does not say that every posting must use identical wording. The relevant question is whether a U.S. worker is sent through a different application channel because the position is PERM-related.
This is why the identifier and the application route belong together.