1 2 3 4 UNITED STATES DISTRICT COURT 5 NORTHERN DISTRICT OF CALIFORNIA 6 7 ERIC RAHMAN, Case No. 25-cv-05171-PCP
8 Plaintiff, ORDER GRANTING DEFENDANT'S 9 v. MOTION TO DISMISS
10 GOOGLE LLC, Re: Dkt. No. 18 Defendant. 11
12 13 Eric Rahman brings this lawsuit against Google, LLC arising from Google’s March 2023 14 termination of Rahman’s employment. Google now moves to dismiss all of Rahman’s claims 15 except for those arising under the Uniformed Services Employment and Reemployment Rights 16 Act (USERRA). For the following reasons, the Court grants Google’s motion. 17 BACKGROUND 18 Rahman was employed by Google from June 2020 through March 2023.1 At the same 19 time, he was an enlisted reservist in the Army. Rahman was hired during the pandemic and 20 worked remotely from his home in Florida. He visited California in connection with his job but 21 was never formally assigned to an office. In his complaint, Rahman alleges that he traveled to 22 Google’s Mountain View headquarters “on multiple occasions” but specifically identifies only two 23 meetings in June and December 2021. 24 Rahman worked as a “Field Sales Representative.” In that role, he helped Google secure a 25 software sale to the US Army worth nearly $19 million. Rahman alleges that, at some point during 26 the deal, he was “sidelined” by his direct supervisor and was ordered to “stop focusing on” the 27 1 software sale. Rahman claims this was because his supervisor wanted to “remove [him] from the 2 DoD team altogether, thereby avoiding very large commissions that were coming due for 3 Plaintiff.” Rahman alleges that he was fired while “away on military duty.” 4 Rahman filed suit on June 18, 2025, asserting the following causes of action against 5 Google: (1) wrongful termination in violation of public policy under California’s Fair 6 Employment and Housing Act (FEHA); (2) discrimination based on military status in violation of 7 FEHA; (3) failure to prevent discrimination in violation of FEHA; (4) retaliation in violation of 8 FEHA; (5) discrimination in violation of USERRA; (6) breach of contract; (7) violation of 9 California Business and Professions Code § 17200; (8) intentional infliction of emotional distress; 10 and (9) negligent infliction of emotional distress. 11 LEGAL STANDARDS 12 The Federal Rules require a complaint to include a “short and plain statement of the claim 13 showing that the pleader is entitled to relief.” Fed. R. Civ. P. 8(a)(2). If the complaint does not do 14 so, the defendant may move to dismiss the complaint. Fed. R. Civ. P. 12(b)(6). Dismissal is 15 required if the plaintiff fails to allege facts allowing the court to “draw the reasonable inference 16 that the defendant is liable for the misconduct alleged.” Ashcroft v. Iqbal, 556 U.S. 662, 678 17 (2009). “Dismissal under Rule 12(b)(6) is appropriate only where the complaint lacks a cognizable 18 legal theory or sufficient facts to support a cognizable legal theory.” Mendiondo v. Centinela 19 Hosp. Med. Ctr., 521 F.3d 1097, 1104 (9th Cir. 2008). To survive a Rule 12(b)(6) motion, a 20 plaintiff need only plead “enough facts to state a claim to relief that is plausible on its face.” Bell 21 Atl. Corp. v. Twombly, 550 U.S. 544, 570 (2007). 22 In considering a Rule 12(b)(6) motion, the Court must “accept all factual allegations in the 23 complaint as true and construe the pleadings in the light most favorable” to the non-moving party. 24 Rowe v. Educ. Credit Mgmt. Corp., 559 F.3d 1028, 1029–30 (9th Cir. 2009). While legal 25 conclusions “can provide the [complaint’s] framework,” the Court will not assume they are correct 26 unless adequately “supported by factual allegations.” Iqbal, 556 U.S. at 679. Courts do not “accept 27 as true allegations that are merely conclusory, unwarranted deductions of fact, or unreasonable 1 v. Golden State Warriors, 266 F.3d 979, 988 (9th Cir. 2001)). 2 ANALYSIS 3 I. Rahman fails to establish a basis for applying FEHA extraterritorially. 4 Google moves to dismiss Rahman’s FEHA claims on the ground that he has not pleaded 5 facts sufficient to support applying that California statute to work that he performed primarily in 6 Florida, where he resided throughout his employment by Google. 7 The “extraterritorial application of FEHA is determined by the situs of both [(1)] 8 employment and [(2)] the material elements of the cause of action, as opposed to residence of the 9 employee or the employer.” Russo v. APL Marine Servs., Ltd., 135 F. Supp. 3d 1089, 1094 (C.D. 10 Cal. 2015), aff’d, 694 F. App’x 585 (9th Cir. 2017). Rahman’s allegations regarding the situs of 11 his employment and the underlying elements are sparse. He alleges that the only Google office he 12 visited was its Mountain View, California location, and that he traveled to the Mountain View 13 location “on multiple occasions” to “meet with and brief Google executives” regarding the Army 14 Workspace deal. Dkt 15, 16. He names only one executive who attended those meetings. In 15 addition, Rahman alleges that he was “specifically hired due to his network and reputation within 16 the United States Army Reserve,” and that the main projects he worked on—Project Maven and 17 Army Workspace—benefitted from that network. Id. at 6, 7. Although Rahman names several 18 executives with whom he met and offers specific tasks he completed for them (for example, “Mr. 19 Rahman was tasked with drafting congratulatory correspondence to senior defense officials on 20 behalf of Mr. Sundar Pichai, CEO of Alphabet”), he fails to allege that any of these tasks were 21 performed in a particular geographic location. 22 These sparse allegations are insufficient to establish a basis for applying FEHA to 23 Rahman’s employment. The situs of employment is generally the employee’s principal place of 24 work. Hill v. Workday, Inc., 773 F. Supp. 3d 779, 793 (N.D. Cal. 2025). Here, Rahman pleads few 25 facts to place his principal place of employment anywhere, let alone in California, and the limited 26 facts he does provide suggest he was principally working in Florida. The only allegations 27 potentially relevant to California are those involving two meetings at the Google offices in 1 meetings is enough to establish a situs of employment. See Hill, 773 F. Supp. 3d at 795 (finding 2 that a week of meetings in California was not enough to establish a situs there). While the 3 Mountain View office may have been the only Google office Rahman “set foot in” during the 4 entirety of his tenure, he does not allege any additional facts that help the Court place those 5 meetings in context, such as whether those were the only two in-person meetings of his entire 6 tenure or where the major stakeholders in his projects were located. As a result, Rahman fails to 7 plead facts sufficient to meet the first Russo prong. 8 To evaluate the second prong of the Russo test, courts typically look to “the location of 9 where the core of the alleged wrongful conduct occurred.” Id. at 794 (collecting cases). Rahman 10 once again fails to allege any facts identifying the location of actions by the alleged tortfeasors.
Free access — add to your briefcase to read the full text and ask questions with AI
1 2 3 4 UNITED STATES DISTRICT COURT 5 NORTHERN DISTRICT OF CALIFORNIA 6 7 ERIC RAHMAN, Case No. 25-cv-05171-PCP
8 Plaintiff, ORDER GRANTING DEFENDANT'S 9 v. MOTION TO DISMISS
10 GOOGLE LLC, Re: Dkt. No. 18 Defendant. 11
12 13 Eric Rahman brings this lawsuit against Google, LLC arising from Google’s March 2023 14 termination of Rahman’s employment. Google now moves to dismiss all of Rahman’s claims 15 except for those arising under the Uniformed Services Employment and Reemployment Rights 16 Act (USERRA). For the following reasons, the Court grants Google’s motion. 17 BACKGROUND 18 Rahman was employed by Google from June 2020 through March 2023.1 At the same 19 time, he was an enlisted reservist in the Army. Rahman was hired during the pandemic and 20 worked remotely from his home in Florida. He visited California in connection with his job but 21 was never formally assigned to an office. In his complaint, Rahman alleges that he traveled to 22 Google’s Mountain View headquarters “on multiple occasions” but specifically identifies only two 23 meetings in June and December 2021. 24 Rahman worked as a “Field Sales Representative.” In that role, he helped Google secure a 25 software sale to the US Army worth nearly $19 million. Rahman alleges that, at some point during 26 the deal, he was “sidelined” by his direct supervisor and was ordered to “stop focusing on” the 27 1 software sale. Rahman claims this was because his supervisor wanted to “remove [him] from the 2 DoD team altogether, thereby avoiding very large commissions that were coming due for 3 Plaintiff.” Rahman alleges that he was fired while “away on military duty.” 4 Rahman filed suit on June 18, 2025, asserting the following causes of action against 5 Google: (1) wrongful termination in violation of public policy under California’s Fair 6 Employment and Housing Act (FEHA); (2) discrimination based on military status in violation of 7 FEHA; (3) failure to prevent discrimination in violation of FEHA; (4) retaliation in violation of 8 FEHA; (5) discrimination in violation of USERRA; (6) breach of contract; (7) violation of 9 California Business and Professions Code § 17200; (8) intentional infliction of emotional distress; 10 and (9) negligent infliction of emotional distress. 11 LEGAL STANDARDS 12 The Federal Rules require a complaint to include a “short and plain statement of the claim 13 showing that the pleader is entitled to relief.” Fed. R. Civ. P. 8(a)(2). If the complaint does not do 14 so, the defendant may move to dismiss the complaint. Fed. R. Civ. P. 12(b)(6). Dismissal is 15 required if the plaintiff fails to allege facts allowing the court to “draw the reasonable inference 16 that the defendant is liable for the misconduct alleged.” Ashcroft v. Iqbal, 556 U.S. 662, 678 17 (2009). “Dismissal under Rule 12(b)(6) is appropriate only where the complaint lacks a cognizable 18 legal theory or sufficient facts to support a cognizable legal theory.” Mendiondo v. Centinela 19 Hosp. Med. Ctr., 521 F.3d 1097, 1104 (9th Cir. 2008). To survive a Rule 12(b)(6) motion, a 20 plaintiff need only plead “enough facts to state a claim to relief that is plausible on its face.” Bell 21 Atl. Corp. v. Twombly, 550 U.S. 544, 570 (2007). 22 In considering a Rule 12(b)(6) motion, the Court must “accept all factual allegations in the 23 complaint as true and construe the pleadings in the light most favorable” to the non-moving party. 24 Rowe v. Educ. Credit Mgmt. Corp., 559 F.3d 1028, 1029–30 (9th Cir. 2009). While legal 25 conclusions “can provide the [complaint’s] framework,” the Court will not assume they are correct 26 unless adequately “supported by factual allegations.” Iqbal, 556 U.S. at 679. Courts do not “accept 27 as true allegations that are merely conclusory, unwarranted deductions of fact, or unreasonable 1 v. Golden State Warriors, 266 F.3d 979, 988 (9th Cir. 2001)). 2 ANALYSIS 3 I. Rahman fails to establish a basis for applying FEHA extraterritorially. 4 Google moves to dismiss Rahman’s FEHA claims on the ground that he has not pleaded 5 facts sufficient to support applying that California statute to work that he performed primarily in 6 Florida, where he resided throughout his employment by Google. 7 The “extraterritorial application of FEHA is determined by the situs of both [(1)] 8 employment and [(2)] the material elements of the cause of action, as opposed to residence of the 9 employee or the employer.” Russo v. APL Marine Servs., Ltd., 135 F. Supp. 3d 1089, 1094 (C.D. 10 Cal. 2015), aff’d, 694 F. App’x 585 (9th Cir. 2017). Rahman’s allegations regarding the situs of 11 his employment and the underlying elements are sparse. He alleges that the only Google office he 12 visited was its Mountain View, California location, and that he traveled to the Mountain View 13 location “on multiple occasions” to “meet with and brief Google executives” regarding the Army 14 Workspace deal. Dkt 15, 16. He names only one executive who attended those meetings. In 15 addition, Rahman alleges that he was “specifically hired due to his network and reputation within 16 the United States Army Reserve,” and that the main projects he worked on—Project Maven and 17 Army Workspace—benefitted from that network. Id. at 6, 7. Although Rahman names several 18 executives with whom he met and offers specific tasks he completed for them (for example, “Mr. 19 Rahman was tasked with drafting congratulatory correspondence to senior defense officials on 20 behalf of Mr. Sundar Pichai, CEO of Alphabet”), he fails to allege that any of these tasks were 21 performed in a particular geographic location. 22 These sparse allegations are insufficient to establish a basis for applying FEHA to 23 Rahman’s employment. The situs of employment is generally the employee’s principal place of 24 work. Hill v. Workday, Inc., 773 F. Supp. 3d 779, 793 (N.D. Cal. 2025). Here, Rahman pleads few 25 facts to place his principal place of employment anywhere, let alone in California, and the limited 26 facts he does provide suggest he was principally working in Florida. The only allegations 27 potentially relevant to California are those involving two meetings at the Google offices in 1 meetings is enough to establish a situs of employment. See Hill, 773 F. Supp. 3d at 795 (finding 2 that a week of meetings in California was not enough to establish a situs there). While the 3 Mountain View office may have been the only Google office Rahman “set foot in” during the 4 entirety of his tenure, he does not allege any additional facts that help the Court place those 5 meetings in context, such as whether those were the only two in-person meetings of his entire 6 tenure or where the major stakeholders in his projects were located. As a result, Rahman fails to 7 plead facts sufficient to meet the first Russo prong. 8 To evaluate the second prong of the Russo test, courts typically look to “the location of 9 where the core of the alleged wrongful conduct occurred.” Id. at 794 (collecting cases). Rahman 10 once again fails to allege any facts identifying the location of actions by the alleged tortfeasors. 11 Even assuming that the bulk of Rahman’s work—the Workspace deal—involved matters of 12 significant concern to Google’s leadership in California, that work is only peripherally related to 13 the wrongful conduct underlying Rahman’s claims: his purportedly wrongful termination after 14 completing that work. The facts relevant to that conduct are not pleaded with any specificity as to 15 their location. Rahman does not specify, for example, where the individuals who made the 16 decision to terminate his employment were located. 17 Because Rahman fails to allege the facts necessary to support the extraterritorial 18 application of FEHA, his FEHA claim is dismissed with leave to amend. And because Rahman’s 19 seventh cause of action under California’s Unfair Competition Law depends upon an underlying 20 FEHA violation, that claim is also dismissed with leave to amend. 21 II. Rahman fails to allege a breach of contract. 22 Google moves to dismiss Rahman’s breach of contract claim on the ground that he has not 23 alleged the terms of the contract at issue with sufficient specificity. 24 To plead a proper breach of contract claim, a plaintiff must “allege in the complaint the 25 terms of the contract or attach a copy of the contract to the complaint.” Langan v. United Servs. 26 Auto. Ass’n, 69 F. Supp. 3d 965, 979 (N.D. Cal. 2014) (citing Twaite v. Allstate Ins. Co., 216 Cal. 27 App. 3d 239, 252 (1989)). These terms need not be “precis[e]” but should be clear enough to 1 In support of his breach of contract claim, Rahman alleged that he was denied a 2 “commission” for the “Army Workspace” deal that was promised under his employment contract. 3 As evidence, he submits a “Sale Bonus Plan” that was included in his offer letter. The portion of 4 the bonus plan submitted by Rahman contains a condition precedent (“to receive your quarterly 5 bonus, you must be employed on the last day of the performance period aligned to the end of the 6 quarter”) and an eligibility clause (“you’ll be told if you’re on a sales bonus plan”). 7 Rahman relies on the plan to establish his contract clam, but the allegations within that 8 claim fail to meet the pleading requirements of Fed. R. Civ. P. 8(a). Rahman’s complaint does not 9 establish either the existence of a contract or a breach of its terms. Although he distinguishes 10 between commissions and bonuses in his complaint, he alleges only that he was “deprived of 11 significant commissions to which he was otherwise entitled” and never describes the relationship 12 between the Sale Bonus Plan and the allegedly denied commissions. He also fails to allege how 13 any “quarterly bonus” due under the Plan would be calculated. And even if the Court were to 14 accept that the Sale Bonus Plan constituted a contract for commissions, Rahman does not allege 15 that he met either contingency in the plan. He fails to plead any facts specifying what quarter the 16 deal was completed in, the dates of that quarter, and whether he was “employed” on the last day of 17 that quarter. He also never alleges that he was “told” that he was on the Sale Bonus Plan, only that 18 he was “eligible to participate in [it].” 19 Because Rahman’s existing complaint fails to plead a valid breach of contract claim, the 20 claim is dismissed with leave to amend. 21 III. Rahman’s claims for wrongful termination, intentional infliction of emotional distress, and negligent infliction of emotional distress are time-barred. 22 23 Rahman’s common law claims are subject to a two-year statute of limitations. Cal. Civ. 24 Proc. Code § 335.1. Rahman’s last day of employment with Google was March 31, 2023. He filed 25 this suit on May 12, 2025, more than two years later. As a result, his common law claims are 26 untimely on their face unless he is entitled to relief from the statute of limitations. Rahman argues 27 that his filing of a USERRA administrative claim with the U.S. Department of Labor, Veterans’ 1 limitations on his common law claims. 2 “California’s equitable tolling of a limitations period ‘is a judicially created, nonstatutory 3 doctrine ... designed to prevent unjust and technical forfeitures of the right to a trial on the merits 4 when the purpose of the statute of limitation—timely notice to the defendant of the plaintiff's 5 claims—has been satisfied.’” Darnaa, LLC v. Google Inc., 236 F. Supp. 3d 1116, 1121 (N.D. Cal. 6 2017) (citing McDonald v. Antelope Valley Community College Dist., 194 P.3d 1026, 1031 (Cal. 7 2008)). Two of Rahman’s common law claims—wrongful termination and negligent infliction of 8 emotional distress—are rooted in Google’s decision to terminate him. That decision, however, 9 occurred nearly a year after Rahman filed his VETS complaint. As a result, the complaint did not 10 provide Google with notice of any claims arising out of Rahman’s allegedly wrongful termination. 11 Because the conduct at issue in the administrative complaint was distinct from the conduct that 12 forms the basis for his wrongful termination and negligent infliction of emotion distress claims, 13 the filing of the VETS complaint could not have tolled the statute of limitations on those claims. 14 See Cheeney v. Highland Cmty. Coll., 15 F.3d 79, 82 (7th Cir. 1994) (“[P]ursuit of an 15 administrative remedy unrelated to a later filed [] claim does not toll the statute of limitations for 16 the [later filed] claim.”) (citing Johnson v. Railway Express Agency, Inc., 421 U.S. 454 (1975)). 17 Rahman’s claim for intentional infliction of emotional distress is rooted more generally in 18 Google’s “conduct,” rather than solely in his allegedly wrongful termination. As a result, there is 19 at least a possibility that the VETS complaint provided Google with notice of Rahman’s 20 intentional infliction of emotional distress claim. The problem for Rahman, however, is that the 21 VETS complaint process Rahman pursued involved procedures and remedies wholly distinct from 22 his common law intentional infliction of emotional distress claim. 23 Tolling is a matter of state law, and California courts have yet to decide whether common 24 law claims may be tolled during VETS proceedings. The Court must therefore predict how the 25 California Supreme Court would resolve the issue, “using intermediate appellate court decisions 26 … as guidance.” Strother v. S. Cal. Permanente Med. Group, 79 F.3d 859, 865 (9th Cir. 1996). 27 In considering whether California would toll the statute of limitations while Rahman’s 1 Norrell Corp., 115 Cal. App. 4th 1174 (2004). Mathieu concluded that the plaintiff’s filing of a 2 FEHA claim with the California Department of Fair Employment and Housing (“DFEH”) (now 3 the California Civil Rights Department) did not toll the statute of limitations on the plaintiff’s 4 common law claim of wrongful termination in violation of the public policy. Id. at 1189. The court 5 noted that California Supreme Court has declined to find tolling where a common law cause of 6 action provides an independent alternative to pursuing an administrative claim and there is no 7 requirement to exhaust any administrative remedies before pursuing the common law claim. Id. 8 That analysis applies with equal force to Rahman’s common law claim for intentional 9 infliction of emotional distress. Rahman was not required to pursue his USERRA claim through 10 the VETS administrative process before he could file suit alleging intentional infliction of 11 emotional distress, and that common law claim provided him with an entirely independent 12 alternative to pursuing any administrative remedy. Mathieu thus counsels that the statute of 13 limitations on Rahman’s common law claims was not tolled while his VETS claim was pending, 14 and Rahman has not identified any contrary California caselaw suggesting that the California 15 Supreme Court would not adopt Mathieu’s analysis. 16 Rather than contending that Mathieu was wrongly decided, Rahman argues that equitable 17 tolling should be treated differently under FEHA and USERRA. He notes that administrative 18 exhaustion of a FEHA claim before the DFEH only requires obtaining a right to sue letter, while 19 the administrative processing of his VETS administrative claim “ultimately proved to be a two- 20 year process.” But if anything, the differences between the DFEH and VETS processes strengthen 21 the Court’s conclusion that the VETS claim did not toll Rahman’s statute of limitations for his 22 common law claims. Unlike a FEHA claim, Rahman was not required to pursue an administrative 23 remedy with VETS before he could assert his USERRA claim in federal court. 38 U.S.C. §§ 4322, 24 4323. He therefore did not need to “await the outcome of the [agency] processing his claims in 25 order to receive the full benefit of an investigation.” Salgado v. Atlantic Richfield Co., 823 F.2d 26 1322, 1326 (9th Cir. 1987). And when an administrative remedy is unrelated to the plaintiff’s 27 ability to file a common law tort claim, the length of time involved in pursuing the administrative 1 proceeding and a common law claim provide two entirely separate remedies, one cannot toll the 2 other). 3 Rahman fails to provide any reason why he might be entitled to equitable tolling of the 4 || statute of limitations with respect to his common law claims. Because his claims for wrongful 5 || termination, intentional infliction of emotional distress, and negligent infliction of emotional 6 distress are time-barred on their face, those claims are dismissed without leave to amend. 7 CONCLUSION 8 For the foregoing reasons, Google’s motion to dismiss is granted. Dismissal is with leave 9 to amend except as to the common law claims. Any amended complaint must be filed within 35 10 || days of the date of this Order. If no amended complaint is filed, Rahman’s non-USERRA claims 11 against Google will be dismissed with prejudice.
IT IS SO ORDERED. 14 Dated: November 5, 2025
16 Ag □□ P. Casey Mts 17 United States District Judge 18 19 20 21 22 23 24 25 26 27 28