Engineer sues HubSpot, says parental leave triggered PIP and firing

A 14-day gap between an HR complaint and a PIP sits at the center of the lawsuit

Engineer sues HubSpot, says parental leave triggered PIP and firing

A former HubSpot engineering lead says the company punished him for taking parental leave, then fired him days after he outed himself as a whistleblower. 

The engineering lead filed the complaint on May 7, 2026, in the US District Court for the Western District of New York. He is suing HubSpot, Inc. and his former manager under Title VII, the New York State Human Rights Law, and New York's whistleblower statute, Labor Law § 740. 

For HR leaders, the case is a study in how routine workforce decisions - a performance review, a PIP, an investigation timeline - can be reframed as a retaliation pattern when they cluster around protected activity. 

The complainant joined HubSpot as an Engineering Lead in June 2024 at a base salary of $245,000, with total compensation of about $395,000 including stock. According to the complaint, he told his manager early on that his wife was pregnant. The role, he says, was framed as a management job. The filing points to a September 9, 2024 Slack message from his manager setting "Global Home planning and execution" as Priority Zero and describing coding as work that "run in parallel always" and could be delegated. 

The engineering lead's  son was born in late November 2024. He took parental leave under HubSpot's company policy. 

According to the filing, the trouble started after he returned in February 2025. Within twelve days, the complaint says, the manager rolled out a new "Engineering Values" framework telling people in his role they were "engineers first, managers second" - a reversal, the complaint argues, of what had been agreed in writing seven months earlier. 

The gender stereotyping claim turns on a single line. The engineering lead says he told his manager he was sleep-deprived from caring for his newborn. According to the complaint, the manager asked: "What does your wife do?" The engineering lead says he read the question as a sex-based assumption that overnight infant care belonged to his wife. 

A few weeks later, his performance assessment flipped. His February 25 six-month review was a 3 out of 5 - what the manager reportedly called the rating "the vast majority of employees receive" - and came with a 6% raise. On March 11, 2025, after the engineering lead confirmed his remaining parental leave dates for August and early September, the complaint says, his manager told him he was "absolutely not meeting expectations" on code output. The filing argues the "almost a year" timeframe the manager used for the review mathematically included the leave period. 

The HR sequencing is the part employment professionals will want to study. 

On March 20, 2025, the engineering lead filed a formal HR complaint. He met with Jasmine Daniels, an Employee Relations Partner, on April 3. According to the filing, HR offered no investigation and no mediation, and told him his only option was to take it up with the manager directly - and that Daniels would be discussing it with him herself. 

Fourteen days after that meeting, on April 18, the manager put him on a PIP citing insufficient code contributions. The complaint says the basis directly contradicted the September 2024 written priority framework. It also says the PIP email itself acknowledged nine pull requests in March, while HubSpot's later EEOC position statement claimed he "failed to ship any Pull Requests" that month. 

The PIP was extended three times. After the second extension, the complaint says, an Employee Relations Partner who had taken over the case described the extension as "highly non-standard." 

Then the whistleblower thread. The engineering lead says he learned in May 2025 of a HubSpot bug that recorded user consent to data sharing when none had been given. The filing puts the affected scope at more than 67,000 business accounts across North America and the European Union, active for roughly nine months. He filed an external whistleblower report on May 16, 2025, and identified himself internally on May 28. 

On June 3, 2025, the complaint says, HubSpot closed both investigations the same day - the discrimination case at 2:36 P.M., the data privacy case at 7:15 P.M., closed as "unsubstantiated." Three days later, the manager terminated him. The filing says the manger had told him four days earlier he was "doing well." 

The complaint seeks reinstatement or front pay, back pay, lost stock vesting estimated at approximately $82,087 for 2025 events, compensatory and punitive damages, attorneys' fees, and the civil penalty available under § 740. 

The allegations have not been tested in court. HubSpot has not yet filed a response, and no court has ruled on any of the claims. 

LATEST NEWS