John Milito v. Infosys Limited

• Court: District Court, W.D. Washington
• Decided: December 18, 2025
• Docket: 2:25-cv-01204
• Status: Unknown

Opinion

1 2

3 4 5 UNITED STATES DISTRICT COURT 6 WESTERN DISTRICT OF WASHINGTON AT SEATTLE 7 JOHN MILITO, CASE NO. 2:25-cv-1204-JNW 8 Plaintiff, REMAND ORDER 9 v. 10 INFOSYS LIMITED, 11 Defendant. 12 13

14 1. INTRODUCTION 15 This matter comes before the Court on Plaintiff’s Motion to Remand. Dkt. No. 16 19. Having reviewed the motion, Defendant’s opposition, Dkt. No. 22, the reply, Dkt. 17 No. 24, and all supporting materials, the Court GRANTS the motion. 18 2. BACKGROUND 19 Plaintiff John Milito filed this class action in King County Superior Court 20 against Infosys Limited and various Doe Defendants, claiming Defendants violated 21 the pay transparency requirements of Washington’s Equal Pay and Opportunities 22 Act (EPOA), RCW 49.58.110. Infosys removed the action to this Court, and Milito 23 1 asserts that the matter was improperly removed. The Court reviews the statutory 2 and factual background.

3 2.1 Statutory background: the EPOA mandates wage disclosure in job postings. 4 Washington State passed its first equal pay legislation, the Equal Pay Act, in 5 1943, and amended it for the first time in 2018, at which time it became known as 6 the EPOA. See RCW 49.12.175; 49.58.005. The Washington Legislature found that 7 “despite existing equal pay laws, there continue[d] to be a gap in wages and 8 advancement opportunities among workers in Washington, especially women.” 9 RCW 49.58.005. The law was updated “to address income disparities, employer 10 discrimination, and retaliation practices, and to reflect the equal status of all 11 workers in Washington state.” Id. 12 In 2019, the EPOA was further updated to address discriminatory hiring 13 practices by prohibiting employers “from seeking the wage or salary history of an 14 applicant for employment in certain circumstances,” and by requiring “an employer 15 to provide wage and salary information to applicants and employees” upon request, 16 although only “after offering the applicant the position.” RCW 49.58.005; see also 17 RCW 49.58.100, -.110. 18 In 2022, the Legislature again amended the EPOA by modifying RCW 19 49.58.110 to require employers to proactively disclose compensation information 20 when a position is posted as available. This “allows a discussion at the start of the 21 process instead of after an offer has been made, which will increase the ability to 22 negotiate pay.” Dkt. No. 1-2 (Compl.) ¶ 5 (quoting H.B. Rep. ESSB 5761, at 2 (Wash. 23 1 2022)).) The Legislature was also concerned that “‘[m]any candidates spend hours 2 going through rounds of interviews only to find out they can’t live on the offered

3 pay.’” Id. (quoting S.B. Rep. ESSB 5761, at 3 (Wash. 2022)). 4 The EPOA now states, in relevant part, that an employer must “disclose in 5 each posting for each job opening the wage scale or salary range, and a general 6 description of all of the benefits and other compensation to be offered to the hired 7 applicant.” RCW 49.58.110(1). It is this provision that Milito claims Defendants 8 violated.

9 2.2 Factual background. 10 Milito lives in Washington and applied for a job opening Infosys offered in 11 Washington. Compl. ¶¶ 15, 25. Milito alleges “[t]he posting for the job opening 12 Plaintiff applied to did not disclose the wage scale or salary range” being offered. Id. 13 ¶ 26. He alleges that he and the members of a proposed class of similarly-situated 14 individuals “lost valuable time applying to a position for which the wage scale or 15 salary range was not disclosed.” Id. ¶¶ 33, 37. But Milito alleges only that he 16 applied for the job, not that he was qualified for the position, that he received any 17 specific response, or that he received an interview offer. 18 Milito’s complaint is virtually identical to numerous other putative class- 19 action lawsuits filed by plaintiffs represented by the same counsel and subsequently 20 removed to and remanded by courts in this district. And according to Defendant, 21 Milito has filed 37 similar EPOA actions in King County Superior Court since 2024. 22 Dkt. No. 22 at 11 n.1 (listing cases). 23 1 3. DISCUSSION 2 3.1 Plaintiff lacks Article III standing. The Court finds that it lacks subject matter jurisdiction over this matter 3 because Milito does not have Article III standing, having failed to identify a 4 concrete injury from Defendant’s failure to provide statutorily required salary 5 information. 6 “Under Article III, the Federal Judiciary is vested with the ‘Power’ to resolve 7 not questions and issues but ‘Cases’ or ‘Controversies.’” Ariz. Christian Sch. Tuition 8 Org. v. Winn, 563 U.S. 125, 132 (2011). “Among other things, that limitation 9 requires a plaintiff to have standing.” Fed. Election Comm’n v. Cruz, 596 U.S. 289, 10 295–96 (2022). If a plaintiff lacks Article III standing, the Court does not have 11 subject matter jurisdiction. See Warth v. Seldin, 422 U.S. 490, 498 (1975). 12 The standing inquiry begins with a simple principle: “No concrete harm, no 13 standing.” TransUnion LLC v. Ramirez, 594 U.S. 413, 417 (2021). “[T]o establish 14 standing, a plaintiff must show (i) that he suffered an injury in fact that is concrete, 15 particularized, and actual or imminent; (ii) that the injury was likely caused by the 16 defendant; and (iii) that the injury would likely be redressed by judicial relief.” Id. 17 at 423 (citing Lujan v. Defenders of Wildlife, 504 U.S. 555, 560–61 (1992)). Plaintiff 18 bears the burden of establishing each of these elements “with the manner and 19 degree of evidence required at the successive stages of the litigation.” Lujan, 504 20 U.S. at 561. “At the pleading stage, general factual allegations of injury resulting 21 from the defendant’s conduct may suffice[.]” Id.; accord Tingley v. Ferguson, 47 22 F.4th 1055, 1066 (9th Cir. 2022). 23 1 This case falls into a category of lawsuits where standing hinges on the 2 violation of a statutory right. “[T]he Supreme Court made clear that a plaintiff does

3 not ‘automatically satisf[y] the injury-in-fact requirement whenever a statute 4 grants a person a statutory right and purports to authorize that person to sue to 5 vindicate that right.’” Robins v. Spokeo, Inc. (Spokeo II), 867 F.3d 1108, 1112 (9th 6 Cir. 2017) (quoting Spokeo, Inc. v. Robins (Spokeo I), 578 U.S. 330, 341 (2016) as 7 revised (May 24, 2016)). To establish a concrete injury, “the plaintiff must allege a 8 statutory violation that caused him to suffer some harm that ‘actually exist[s]’ in

9 the world; there must be an injury that is ‘real’ and not ‘abstract’ or merely 10 ‘procedural.’” Id. (quoting Spokeo I, 578 U.S. at 340). 11 “Although we often think of ‘tangible’ injuries as the basis of this 12 jurisdictional requirement, the Supreme Court has confirmed that ‘intangible 13 injuries can nevertheless be concrete.’” Magadia v. Wal-Mart Assocs., Inc., 999 F.3d 14 668, 679 (9th Cir. 2021) (quoting Spokeo I, 578 U.S. at 340). While “[t]he omission of 15 statutorily required information can constitute a distinct, concrete injury,” “not

16 ‘every minor inaccuracy reported in violation of [a statute] will cause real harm or 17 present any material risk of real harm.’” Id. (quoting Spokeo II, 867 F.3d at 1116). 18 “[A]n intangible injury may be concrete if it presents a material risk of tangible 19 harm or ‘has a close relationship to a harm that has traditionally been regarded as 20 providing a basis for a lawsuit in English or American courts,’ like common law 21 torts or certain constitutional violations.” Phillips v. United States Customs &

22 Border Prot., 74 F.4th 986, 991 (9th Cir. 2023) (quoting Spokeo I, 578 U.S. at 340- 23 41). 1 “To determine whether the violation of a statute constitutes a concrete harm, 2 we engage in a two-part inquiry.” Magadia, 999 F.3d at 679. “We first consider

3 ‘whether the statutory provisions at issue were established to protect . . . concrete 4 interests (as opposed to purely procedural rights).’” Id. (quoting Spokeo II, 867 F.3d 5 at 1113). “If so, we then assess ‘whether the specific procedural violations alleged in 6 this case actually harm, or present a material risk of harm to, such interests.’” Id. 7 (quoting Spokeo II, 867 F.3d at 1113). 8 Although the EPOA protects concrete interests of job applicants, Milito has

9 failed to show that the alleged violation caused actual harm or presented a material 10 risk of harm to those interests. The Court reviews its two-part analysis, below. 11 First, the salary disclosure requirement in the EPOA was established to 12 protect concrete, non-procedural rights for job applicants and employees. As 13 discussed above, Legislature amended the EPOA to address the wage gap and 14 income disparities that exist affecting workers in Washington. RCW 49.58.005. The 15 EPOA expressly states that “the legislature intends to require an employer to

16 provide wage and salary information to applicants and employees.” RCW 17 49.58.005(4). To promote this goal, the 2019 Amendments to the EPOA required 18 employers to provide wage and salary information to applicants upon request, but 19 only “after offering the applicant the position.” RCW 49.58.005, -.100-.110. Then in 20 2022, the Legislature amended the EPOA to increase transparency by requiring 21 proactive disclosure of wage and salary information to “allow[] a discussion at the

22 start of the process instead of after an offer has been made, which will increase the 23 ability to negotiate pay.” H.B. Rep. ESSB 5761, at 2. This change was designed to 1 avoid harm to those who “spend hours going through rounds of interviews only to 2 find out they can’t live on the offered pay.” S.B. Rep. ESSB 5761, at 3. Read

3 together, this legislative history confirms that the EPOA’s procedural requirement 4 of disclosure was established to protect applicants by arming them with sufficient 5 information to ensure fair and equitable pay negotiations, and to avoid wasting time 6 interviewing for positions whose pay would never be adequate. 7 Second, Milito has failed to show how Defendant’s nondisclosure caused him 8 actual harm or material risk of harm. Milito alleges that as a result of the missing

9 pay scale and wage range information, he “lost valuable time,” was unable to 10 negotiate, and was “unable to evaluate the pay for the position and compare [it] to 11 other available positions in the marketplace[.]” Compl. ¶¶ 30–35. But these 12 allegations fail to show any actual harm against which the EPOA intends to protect. 13 Nowhere has Milito alleged that he was offered an interview or that he engaged in 14 any pay negotiations. All Milito alleges is that he applied to the job. And Milito does 15 not even allege he was qualified for the position. His only identified injury is the

16 time he “lost” in submitting the application, but this is not an injury that the EPOA 17 was designed to prevent. As Judge Rothstein concluded in Floyd v. Insight Glob. 18 LLC, “[a] job posting that does not contain compensation information is a technical 19 violation, but it does not harm or create a material risk of harm to any individual’s 20 concrete interest” because “[a] nominal applicant with no interest in the position 21 will neither receive a benefit from early pay disclosure nor be harmed by the lack

22 thereof.” No. 23-CV-1680-BJR, 2024 WL 2133370, at *7 (W.D. Wash. May 10, 2024), 23 amended on reconsideration, No. 23-CV-1680-BJR, 2024 WL 3199858 (W.D. Wash. 1 June 26, 2024). Defendant’s invocation of Milito’s conclusory phrase “economic and 2 non-economic harm” changes nothing. Labels do not create concrete injury where

3 the underlying facts do not support one. 4 As was the case in Floyd, Milito has failed to identify a concrete and 5 particularized injury sufficient to satisfy Article III standing. Because the Court 6 lacks subject matter jurisdiction, the Court GRANTS the Motion to Remand. 7 The Washington Supreme Court’s recent decision in Branson v. Washington 8 Fine Wine & Spirits, LLC, 574 P.3d 1031 (Wash. 2025), does not affect the Court’s

9 decision. There, the Washington Supreme Court addressed the question of what a 10 plaintiff must prove to be considered a “job applicant” under RCW 49.58.110(4)— 11 and specifically, whether the applicant must prove they are a bona fide applicant. 12 Branson, 574 P.3d at 1034. The Washington Supreme Court held: 13 A job applicant need not prove they are a ‘bona fide’ applicant to be deemed a ‘job applicant.’ Rather, in accordance with the plain language 14 of RCW 49.58.110(4), a person must apply to any solicitation intended to recruit job applicants for a specific available position to be considered 15 a ‘job applicant,’ regardless of the person's subjective intent in applying for the specific position. 16 Id. at 1040. 17 The Branson court did not address standing—neither federal nor statutory— 18 and therefore does not change this Court’s Article III standing analysis. The 19 Branson decision clarifies that a plaintiff does not have to prove they are a “bona 20 fide” or “good faith” applicant to qualify as a “job applicant” that can sue to obtain 21 remedies under the statute. Id. But a plaintiff must still show an injury-in-fact for 22 Article III purposes. Spokeo II, 867 F.3d at 1112. Milito has failed to plead such an 23 1 injury. Because a lack of Article III standing implicates the Court’s subject matter 2 jurisdiction, see Warth, 422 U.S. at 498, this case will be remanded to King County

3 Superior Court pursuant to 28 U.S.C. § 1447(c). And because Milito lacks standing, 4 this Court does not have subject matter jurisdiction to address the parties’ 5 additional arguments. 6 This Court’s conclusion is consistent with the uniform approach of every 7 judge in this district to have considered the issue. In multiple cases involving nearly 8 identical EPOA claims, courts in this district have held that plaintiffs who do not

9 allege bona fide applicant status, an interview offer, or engagement in pay 10 negotiations lack Article III standing. See, e.g., Floyd v. Photon Infotech Inc., No. 11 C24-01372-KKE, 2025 WL 3442736 (W.D. Wash. Dec. 1, 2025); Eggleston v. 12 Bruckner Truck Sales Inc., No. C25-1467-JLR, 2025 WL 3153503 (W.D. Wash. Nov. 13 12, 2025); Hill v. Les Schwab Tire Centers of Washington LLC, No. 24-CV-425-BJR, 14 2025 WL 3062646, at *3 (W.D. Wash. Oct. 31, 2025). This Court knows of no case in 15 this district reaching a contrary result.

16 3.2 The futility exception does not apply. 17 Because Milito lacks Article III standing, the proper remedy is remand, but 18 Defendant argues in the alternative that the Court should apply the futility 19 exception and dismiss instead. Dkt. No. 22 at 17–21. The Court declines. The 20 futility exception is difficult to reconcile with 28 U.S.C. § 1447(c)’s plain language, 21 and it is questionable whether it remains good law. See Polo v. Innoventions Int’l, 22 LLC, 833 F.3d 1193, 1197–98 (9th Cir. 2016). Even assuming it remains valid, the 23 1 exception is “narrow” and applies only where there is “absolute certainty” that a 2 state court would dismiss the action following remand. Sauk-Suiattle Indian Tribe

3 v. City of Seattle, 56 F.4th 1179, 1189–90 (9th Cir. 2022). Defendant has not made 4 that showing. Washington courts are not bound by Article III, Polo, 833 F.3d at 5 1196, and under Branson, Milito need not prove bona fide applicant status to seek 6 remedies under the EPOA. 574 P.3d at 1040. Dismissal in state court is not an 7 absolute certainty, and thus the futility exception does not apply. 8 4. CONCLUSION 9 The Court finds that Milito has failed to allege an injury to a concrete 10 interest sufficient to satisfy Article III standing. The Court therefore lacks subject 11 matter jurisdiction, and GRANTS the Motion to Remand. The Court REMANDS 12 this matter to the King County Superior Court, effective fourteen (14) days from the 13 date of this Order. See LCR 3(i). Defendant’s Motion for Jurisdictional Discovery, 14 Dkt. No. 20, is DENIED as MOOT. 15

16 Dated this 18th day of December, 2025. 17 A 18 Jamal N. Whitehead United States District Judge 19

20 21 22 23