He says the system then fired him for shifts he was never allowed to work
An Arizona man says Amazon's own hiring software became the tool it used to punish him for speaking up.
In a complaint filed July 13, 2026, in federal court in Arizona, the man alleges that Amazon and its benefits recordkeeper, Fidelity Workplace Services LLC, turned a routine seasonal hire into what the filing calls a "ghost employee" loop - keeping him active on the backend while blocking him from working, then firing him for missing shifts he says he was never allowed to take.
The case should get the attention of any HR leader running high-volume, automated hiring. It goes straight at the systems most large employers now depend on: automated background checks, automated shift assignment and automated attendance tracking.
According to the complaint, Amazon offered him a Seasonal Delivery Station Warehouse Associate role on October 18, 2025, with a November 9 start date, contingent on a background check and other pre-hire steps. The filing says that on October 29, he emailed Amazon's legal department a formal notice about protected legal filings. Human resources acknowledged it on November 3. Less than a day later, at 2:39 AM on November 4, the complaint alleges Amazon manually reset his background check.
On November 7 - the same day he says he filed an EEOC inquiry - Amazon pulled his confirmed shift, citing "incomplete pre-hire requirements," according to the complaint. Three days later, his report reportedly came back clean, marked "No Record Found."
The sharpest lesson for HR sits in the complaint's FCRA claim. It alleges Amazon acted on an unfinished background report without first handing over a copy of the report and a summary of his rights, and without waiting a reasonable period for him to respond. Those pre-adverse-action steps are what the federal Fair Credit Reporting Act requires before an employer moves on a report.
The filing also alleges Amazon recorded a backend "Hire Start Date" of November 8, 2025, flipping him from applicant to active employee on its systems and using his Social Security number for 92 days to maintain what the complaint calls a "phantom" profile - which, it says, triggered 401(k) and benefits notices through Fidelity.
The complaint alleges that on November 11, Amazon confirmed a shift its system had "selected" for him and warned that taking no action "may negatively impact future applications." It ties this to the Federal Trade Commission's September 2025 Stipulated Final Order against Amazon.com, Inc. over "dark patterns," arguing the same coercive design was used on him. The filing alleges Amazon then ran automated attendance points against the phantom profile and executed a "Termination for Cause" on March 10, 2026.
Against Fidelity, the complaint brings an ERISA claim, alleging the recordkeeper built a retirement account tied to his SSN and later carried out a "purge and termination" of that data on February 15, 2026 - after a litigation hold. When he called to report the problem, the filing says a Fidelity customer response manager refused to route the matter to fraud or compliance staff, telling him, "I will not be doing that."
Amazon disputes the claims. In a pre-suit letter quoted in the complaint, Amazon's outside counsel wrote that there was "no merit" to his claims and declined to make a settlement offer.
According to the complaint, the EEOC dismissed the charge and issued a right-to-sue notice on July 2, 2026, clearing the way for this lawsuit. The suit asserts retaliation under Title VII, FCRA violations, breach of contract, deceptive interface design, ERISA fiduciary breach and negligence, and seeks compensatory and punitive damages plus injunctive relief.
The allegations have not been tested in court, and no judge has ruled on the claims.
