Rowe v. Google LLC

CourtDistrict Court, S.D. New York
DecidedSeptember 26, 2022
Docket1:19-cv-08655
StatusUnknown

This text of Rowe v. Google LLC (Rowe v. Google LLC) is published on Counsel Stack Legal Research, covering District Court, S.D. New York primary law. Counsel Stack provides free access to over 12 million legal documents including statutes, case law, regulations, and constitutions.

Bluebook
Rowe v. Google LLC, (S.D.N.Y. 2022).

Opinion

UNITED STATES DISTRICT COURT SOUTHERN DISTRICT OF NEW YORK -------------------------------------------------------------X : ULKU ROWE, : Plaintiff, : : 19 Civ. 8655 (LGS) -against- : : OPINION AND ORDER GOOGLE LLC, : Defendant. : : ------------------------------------------------------------ X LORNA G. SCHOFIELD, District Judge: Plaintiff Ulku Rowe brings this action against her current employer, Defendant Google LLC, alleging sex-based discrimination and retaliation in violation of the New York Equal Pay Law (“NYEPL”), the New York Labor Law (“NYLL”) §§ 194, 215 and the New York City Human Rights Law (“NYCHRL), N.Y.C. Admin. Code § 8-101.1 Google moves for summary judgment on all of Rowe’s claims. Rowe cross-moves for summary judgment on her NYEPL claim and one of Google’s affirmative defenses to that claim. For the reasons discussed below, the parties’ motions are denied. BACKGROUND The background facts below are drawn from the parties’ Rule 56.1 statements and other submissions on these motions. The facts are either undisputed or based on evidence in the record drawing all reasonable inferences in favor of the non-moving party. In 2016, Will Grannis and Brian Stevens, Chief Technology Officers (“CTO”) of Google Cloud, established the Office of the CTO (“OCTO”) within Google’s Cloud organization. OCTO was designed to be a team of employees with CTO-like qualities (“Technical Directors”)

1 On August 23, 2021, Rowe voluntarily dismissed her Title VII and Equal Pay Claims based on the understanding that the Court would retain jurisdiction over Rowe’s state and city law claims. that would represent Google Cloud externally as the technical face of the organization and be the liaison between clients and Google’s engineering teams. As the hiring managers, Grannis and Stevens determined that the newly-created OCTO role was commensurate with a Level 8 or Level 9 on Google’s salary scale. Technical Directors were expected to assume three key “pillars” of responsibility: customer advancement, engineering impact and evangelism or

thought leadership. Technical Directors initially were considered individual contributors -- although over time, some Technical Directors managed direct reports. All Technical Directors in OCTO reported to Grannis. Between March 2016 and March 2018, Google hired seventeen people to serve as Technical Directors, five of whom were hired as Level 9s. In December 2016, Google extended an offer of employment to Rowe. At the time, Rowe held a Bachelor of Science in Computer Engineering and a Master of Science in Computer Science and had more than twenty years of experience in the financial services industry, including as the Global Head and Chief Technical Officer (“CTO”) of Credit Risk Technology at JPMorgan Chase. On March 13, 2017, Rowe

started as a Technical Director in Google’s New York City office. Rowe was hired as a Level 8 and was the only woman to serve as a Technical Director when she was hired. The parties vigorously dispute how Google evaluated whether to hire candidates as a Level 8 or a Level 9. The parties do not dispute that Google used the same job description and external job posting to hire and recruit all of the Technical Directors and evaluated all Technical Director candidates using the same interview questions and rubrics. Rowe testified that she asked as part of her interview process whether she should be classified as a Level 8 or Level 9 and was told that all Technical Directors were being hired at a Level 8. At the time of Rowe’s hiring, Grannis wrote “[b]ased on the positive, consistent feedback from the panel, the criticality of financial services as a vertical for Google Cloud, and the candidate’s clear demonstration of readiness to make an immediate impact as a L[evel] 8, I enthusiastically endorse the hire recommendation.” Grannis could not recall whether he considered Rowe for hire at a Level 9. In November 2017, Rowe complained to Human Resources that she believed she was under- leveled at hire. Once employed, Rowe had the same duties as the Level 9 Technical Directors

and received favorable performance reviews. On June 25, 2018, as part of a larger reorganization, Google transferred Rowe and three other employees from OCTO to report to Tariq Shaukat as Global Client Technical Leads (“GCTLs”). Each of the transferred employees had an “industry vertical focus.” Rowe’s was the financial services industry. The transfer did not impact compensation or result in a change to Rowe’s job code or level. Rowe testified that Shaukat treated her differently than her male counterparts, including not inviting her to staff meetings in or around August 2018. On June 13, 2018, Rowe expressed interest in a role on Shaukat’s team as the head of the Financial Services Industry Vertical (the “FSVL Role”). Rowe testified that Grannis, Stevens

and Jennifer Burdis -- a recruiter -- previously told Rowe that she would be the obvious person to lead the Financial Services vertical based on her experience. Although Shaukat told Rowe he would formally interview her for the role, in June 2018, weeks into Rowe’s new role on his team, Shaukat wrote that Rowe was not “likely right . . . for the [FSVL] role.” Around the same time in June 2018, Rowe spoke with Grannis regarding her concerns that she was not being fairly considered for the promotion. In August 2018, Rowe was interviewed by four men for the FSVL Role. The parties dispute whether Rowe received favorable reviews from the August 2018 interview. Plaintiff proffers evidence that “there was no negative feedback” from Rowe’s interviewers; “[t]here was only positive feedback on the technical side,” and while one interviewer raised some questions “on the business side,” it was with the caveat that his interview with Rowe was only 30 minutes. In August 2018, Shaukat decided that Rowe “was not going to be a finalist for the role,” although he did not communicate the decision to Rowe. Around the same time, Rowe emailed the Google internal recruiters she had worked with, Melissa Lawrence and Kevin Lucas, to

inform them that she perceived that her under-leveling at hire was negatively impacting her consideration for the FSVL Role. In November 2018, Rowe emailed Shaukat and Diane Greene -- then CEO of Google Cloud -- to raise concerns regarding her treatment during the interview process for the FSVL Role, again reiterating her belief that her original under-leveling was impacting her candidacy. Shaukat and Greene escalated her complaint to HR. HR later responded that Rowe’s leveling process was not discriminatory. On November 16, 2018, Greene announced she was leaving Google. Shaukat elected not to proceed with an offer to his preferred candidate for the FSVL Role to allow him time to understand the new CEO’s plans for Google Cloud. In December

2018, Shaukat told Rowe he was pausing the search but that she was not a finalist given the feedback he received about her candidacy during the interview process. In January 2019, Shaukat selected Stuart Breslow -- someone who had not interviewed for the FSVL Role -- as the interim head of financial services. Around the same time, Stuart Vardaman, the lead recruiter for the FSVL Role, entered applicant feedback into Google’s Thrive database stating that Rowe was rejected from the FSVL Role because she lacked “Googleyness” and describing Rowe as “overly self-oriented” and recording that Rowe “was not qualified for the role in addition to ego concerns.” On or about September 17, 2019, after Rowe filed this lawsuit, Google, through its Employee Relations (“ER”) team undertook an internal investigation of Rowe’s claims, which lasted from approximately October 2019 until April 2020. On January 22 and 29, 2020, ER interviewed Vardaman, who had led the recruitment process for the VP Financial Services position. Vardaman described Rowe in his ER interview as “abrasive,” “cantankerous,” and

Free access — add to your briefcase to read the full text and ask questions with AI

Related

McDonnell Douglas Corp. v. Green
411 U.S. 792 (Supreme Court, 1973)
Anderson v. Liberty Lobby, Inc.
477 U.S. 242 (Supreme Court, 1986)
United States v. Amodeo
71 F.3d 1044 (Second Circuit, 1995)
Gorzynski v. Jetblue Airways Corp.
596 F.3d 93 (Second Circuit, 2010)
Copantitla v. Fiskardo Estiatorio, Inc.
788 F. Supp. 2d 253 (S.D. New York, 2011)
Kwan v. The Andalex Group LLC
737 F.3d 834 (Second Circuit, 2013)
Talwar v. Staten Island University Hospital
610 F. App'x 28 (Second Circuit, 2015)
Chiaramonte v. Animal Medical Center
677 F. App'x 689 (Second Circuit, 2017)
Schwebel v. Crandall
967 F.3d 96 (Second Circuit, 2020)
Electra v. 59 Murray Enterprs., Inc.
987 F.3d 233 (Second Circuit, 2021)
Albunio v. City of New York
947 N.E.2d 135 (New York Court of Appeals, 2011)
Lefort v. Kingsbrook Jewish Med. Ctr.
203 A.D.3d 708 (Appellate Division of the Supreme Court of New York, 2022)
Vega v. Hempstead Union Free School District
801 F.3d 72 (Second Circuit, 2015)

Cite This Page — Counsel Stack

Bluebook (online)
Rowe v. Google LLC, Counsel Stack Legal Research, https://law.counselstack.com/opinion/rowe-v-google-llc-nysd-2022.