Employee Survival Guide® - Rigged Performance Reviews: Molosky v. Amazon Web Services

Episode Date: September 28, 2026

Send us Fan MailMaking your employer hundreds of millions in revenue should buy you security, right? We walk through allegations that flip that assumption on its head, using the federal lawsuit Molowski v. Amazon Web Services (AWS) as a real-world case study in gender bias, bro culture, and how performance systems can be bent to serve a manager’s preferred hierarchy. We start with the business context because it matters: the complaint describes a high-achieving leader with deep technical and financial credentials, credited with initiatives tied to enormous revenue impact, while also alleging pay disparities and level misclassification. From there, we dig into the day-to-day culture claims, including gendered remarks like “lean back” and “leading lady,” pressure to move toward stereotypically “softer” work, and the alleged stripping of high-value projects and visibility. If you’ve ever wondered how discrimination can hide behind “feedback” and “fit,” this is the mechanics laid bare. Then we get specific about the process that should worry every employee: the pivot plan, the timeline after an HR complaint, the volume of required goals, and the allegation that the standards changed midstream. We also break down a confusing but crucial legal reality: federal discrimination claims can be dismissed over EEOC timing technicalities and pleading requirements, while New York State and New York City Human Rights Law claims may survive because they’re designed to capture modern, coded discrimination and subjective, weaponized performance reviews. If you want clearer insight into workplace discrimination, retaliation risk, PIPs, hostile work environment standards, and the legal differences between Title VII and NYCHRL, hit play. Subscribe, share this with someone navigating a performance review, and leave a review to help more workers find the show. What’s the most subtle “professional” line you’ve heard that was really bias? If you enjoyed this episode of the Employee Survival Guide please like us on Facebook, X and LinkedIn.  We would really appreciate if you could leave a review of this podcast on your favorite podcast player such as Apple Podcasts and Spotify. Leaving a review will help other employees find the Employee Survival Guide.  For more information, please contact our employment attorneys at Carey & Associates, P.C. at 203-255-4150, www.capclaw.com.Disclaimer:  For educational use only, not intended to be legal advice. 

Hey, it's Mark here. Welcome to the next edition of the Employee Survival Guide, where I tell you, as always, what your employer does definitely not want you to know about. And a lot more. Welcome to the Employee Survival Guide, produced by Employment Attorney Mark Carey. I want you to just imagine something for a second. Okay, I'm with you. So imagine you are at the absolute top of your game in your career. Like, you are generating hundreds of millions of dollars in revenue for your employer.

Right. You are actively unlocking. billions in future value just through sheer technical brilliance. By every objective metric, you are a star performer. The kind of employee every company says they want. Exactly. And your reward for all of this, you're pulled into a room by your male bosses, told to, quote, lean back, act like the leading lady.

And then you're forced to hand over your highly successful projects to men who have a fraction of your experience. Gosh, I mean, it sounds like a script for like an overly dramatic. corporate thriller, you know? It really does. But it is actually the reality laid out in a recent highly explosive legal complaint. Yeah. So today, we are looking at the 2025 and 26 federal lawsuit, Anna E. Molossky v. Amazon Web Services, or AWS. And we're going to look at this strictly from the employee's perspective, walking through her specific allegations against, you know, one of the most powerful tech giants on the planet. Right. That's our mission today. We are unpacking this intense legal battle to explore these dramatic allegation.

of a pervasive bro culture and a very thick glass ceiling at AWS. But more importantly, we're going to examine the actual mechanics of how subjective performance reviews are allegedly weaponized to just push out top performing female executives, all based on illegal gender stereotypes. Okay, let's unpack this. Because before we can even talk about the discrimination allegations, we have to establish exactly how valuable Anna Molloski was to AWS. Oh, absolutely.

You really need to understand her track record. She wasn't just an average employee. She had over 15 years of high-level experience, including serious strategic roles at Goldman Sachs and the massive hedge fund, 2-Sigma. Right. And it's so crucial to understand what that background actually means in the tech world. Bringing experience from Goldman Sachs and 2-Sigma means she had a highly lucrative, really rare set of skills that blends deep technical acumen with high-level financial strategy. Right. So AWS hires her in 2021 as a senior UX designer, but her strategic mind just makes it immediately apparent that she's management material. So by 2022, she transfers to a senior product manager tech role, which is often abbreviated as PMT. And this is where she just starts delivering these undeniable wins. I mean, the numbers here are just staggering. They really are.

She spearheaded an initiative called the unbilled usage initiative. And just to put a clear number on that, under her leadership, This one project generated $580 million in additional annual recurring revenue. Which is just profound. We aren't talking about like theoretical value here. That is $580 million of real money hitting the bottom line. Every single year, just because she found a way to capture revenue that the company was previously letting slip through the cracks. But then the second project is the one that really blows my mind.

She led something called the prod strat initiative. Yeah, that's the big one. Right. From what I understand, this was a highly complex end-to-end digital platform designed to automate pricing for really lucrative government contracts. And the projected value of the revenue had unlocked was a potential $55 billion over 10 years. I mean, top executives were actively praising her for this. Yes, and let's break down why a project like ProdStrat is so technically demanding. Because building a pricing engine for government contracts, it isn't just about, you know, setting up a spreadsheet.

Right. It's way more than that. Exactly. You are dealing with strict federal compliance rules. Incredible scale. Shifting security protocols, immense data sets. To architect a system that can automate all of that flawlessly, well, it requires someone who understands both the micro-level code and the macro-level business strategy. She was building the very engines driving the company's future wealth. But despite doing the heavy lifting of what AWS classifies as a level seven manager, AWS kept her classified and paid at a level six. So she's doing the work, generating literally billions, but not getting the title or the compensation. Right. And she actually found out just how bad this pay disparity was through a crowdsourced salary website called Levels.FY. Yeah, and for those who might not be familiar with it, Levels.FY is this platform where tech workers anonymously share their exact compensation packages, and it's broken down by company, level, and location.

It's super helpful. It really is. It has brought a lot of transparency to an industry that, you know, notoriously hides its pay bans. So when Molloski checked the data for her specific role, location, and experience, she discovered she was making roughly $50,000 less than her male peers at that exact same level six designation. This is like being the star quarterback who just won the Super Bowl, but the coach still makes you sit on the bench and polish the helmets just because you don't fit the traditional look of the team. That is an excellent way to visualize the disparity.

The structural inequality was just baked in from the very start. And what's fascinating here is the social dynamic. Upon her transfer to the senior PMT role, Molofsky was the only female PMT in her entire group. Oh, wow. Yeah, she was completely isolated. Which really sets the stage for the culture she was walking into. It wasn't just like a quiet underlying bias. Because in July 2022, there's an HR workshop in Berlin.

It was a new leader assimilation meeting focused on Belotsky's manager, a man named Christoph Helmiss. Right. In these assimilation meetings, they're supposed to be safe spaces. An HR facilitator usually stands at a whiteboard, and the team provides anonymous, candid feedback about their new leader to help build trust. Makes sense. But what is incredible about this specific meeting is that the male colleagues themselves spoke up. Really? Yes. They openly complained to HR that Helmiss had zero female leaders. and that he promoted a heavy bro culture.

So they are literally writing this on a whiteboard. HR is documenting it in the room? What happened next? Well, before any productive conversation could even happen, Helmiss himself suddenly walked right into the room. You're kidding. Nope. The supposedly safe meeting abruptly ended. The complaints were visually documented on the wall,

but the conversation was instantly shut down by the very manager they were critiquing. That is chilling. So the bro culture isn't just a, feeling Miloski has. It is a documented concern raised by the men in the room directly to HR. Exactly. But knowing about a toxic culture and living it every day, those are two very different things. How did this broculture actually manifest in her day-to-day job? We see exactly how it manifests when we fast forward to April 2023. This is during her formal performance review with Helmiss. Okay. Keep in mind, she has already unlocked billions in revenue by this point. You would expect,

a conversation charting a fast track to the C-suite. Obviously. Instead, Helmiss actively discourages her. He explicitly tells her to, quote, lean back. Lean back. I mean, the irony there is just thick. You have Cheryl Sandberg's famous corporate mantra for women to lean in and take a seat at the table. And this manager is using the exact opposite phrase to tell a top female executive to stand down.

It is a profound choice of words. And he even warned her that she wouldn't enjoy the burden of a higher level. The burden? Yeah. Meanwhile, according to the complaint, he was actively encouraging her male counterparts to aggressively pursue promotions. Wow. The situation then escalates in May 2023 when she gets a new direct manager, Poonit Jindal. And Jindal wastes no time, right?

None at all. Before he even officially takes over, he holds a one-on-one with Miloski and actually belittles her 55. billion dollar prod strat success. He looks at this highly complex financial and technical engine she built and calls it mere beginner's luck. Beginners luck. After 15 years in the industry at Goldman Sachs and 2 Sigma, that's insulting. That's insulting. And then both Helmiss and Gindle start pushing her to stick to user interface and design work. Now, I want to pause here for a second because I think a lot of people outside the tech industry might not understand the subtext of that request. Why is pushing her to UI such a red flag?

It is a deeply ingrained gender stereotype in software development. In tech, back end work, so the complex databases, the pricing engines, the invisible architecture, that's culturally coded as hard, highly technical and masculine. Right. But front end work, like user interface and design, you know, making things look pretty and easy to click, that is stereotypically coded as soft, less technical and feminine. Wait, so they took a female executive who unlocked $5.5 billion with a complex back-end pricing engine and essentially told her she'd be better suited picking out the digital drapes. That is exactly what the complaint alleges. They were telling her that her brain just wasn't suited for the hard technical work, completely ignoring the fact that she held multiple AWS technical certifications and had this massive proven track record. It's just wild. And Gindal's comments were incredibly overt about this.

During a meeting about the prod strat initiative, he told Maloski to project herself as the, quote, leading lady because there were a lot of cooks in the kitchen. Leading lady. It is so dismissive. It literally reduces a technical powerhouse to a casting call for a supporting role. It really does. And this is where the allegations shift from just verbal stereotyping to tangible career-destroying sabotage. Because Gindal begins actively stripping Miloski of the two highly lucrative initiatives, built, prodstratt and unbuilt usage.

Unbelievable. And he reassigns them to two male PMTs, Machik Bill, and Nidic Jaw. Let me guess. Neither of these men had the background for this. Precisely. Both men had less experience and fewer qualifications than Miloski. Okay. I have to ask a blunt question here.

If the ultimate goal of a tech giant is to generate profit, why on earth would managers sabotage their absolute best moneymaker just to uphold a boys club? It completely defies business logic. Well, it does defy pure economic logic, but it makes perfect sense when you understand the psychology of structural bias. Really? How so? In highly toxic corporate cultures, maintaining the social hierarchy, the bro culture in this case, often supersedes short-term profit. Oh, I see. Historically, when women display the exact same ambition, assertiveness, and technical brilliance that is heavily praised in men,

it makes a certain type of manager deeply uncomfortable. The discomfort of having a powerful woman in the room outweighs the joy of the revenue she brings in. So they neutralize the threat to the hierarchy. And how did that neutralization play out practically? Because you can't just hand a highly complex technical project to someone who doesn't understand it and expect it to run smoothly. It certainly didn't run smoothly. Macek Beal, a man with less tenure, immediately begins treating Miloski like she is his subordinate. He starts assigning her menial tasks, having her run basic tests and, you know, write his customer emails. So she builds a multi-million dollar revenue stream.

It is given to a guy with less experience. And then he tells her to do his secretarial work. And it gets significantly worse. When Bill inevitably struggles to understand the complex technical architecture of the project he was handed, Gendell doesn't give the project back to Molloski. Of course not. Instead, he orders Molloski to ghostwrite the technical documents for Bill. Wait, ghost right.

How does that even work in a corporate setting? Well, she was forced to do the high-level intellectual labor, writing the strategic code documentation, outlining the pricing models, and sent it to Bill in the shadows. He would then take her work, put his name on it, presented in meetings, and take all the credit. Are you kidding me? I wish I was.

Furthermore, Gindle starts excluding Miloski from all expenses paid strategic meetings in Berlin. She had spent 42 days in Berlin the previous, year building these exact strategies, but suddenly she is grounded and Jindal is sending her male colleagues in her place. Okay, that is infuriating. And when she finally calls them out on it, she formally complains to Jindal about the workload, the ghostwriting, and the incompetence of the male colleagues who took her projects. And according to the complaint, Jindal responds by launching into a sexist diatribe. Oh, great. He blames a completely different female manager for some of the project delays, claiming that other woman wasn't strong enough to shepherd the troops.

And then he looks at Miloski and suggests that, as a female manager, she too is weak and unfit to lead. It's just staggering. So Molloski is clearly had enough. She formally submits a complaint to HR and to Helmiss about the psychological toll this chauvinism is taking on her. Yes, she does. And this brings us to a crucial part of the story.

If you're listening to this right now and you've ever been put on a sudden performance plan out of nowhere, this next part is going to sound chillingly familiar to you. Because when a star employee raises a red flag about discrimination, you would think HR would swoop in to protect the asset. Instead, HR and management allegedly engineered a swift calculated exit strategy massed as a standard performance review. Exactly four days after she filed that formal complaint, AWS placed Moloski on what they call a pivot plan. A pivot plan. A pivot plan. That is just corporate jargon for a performance improvement plan, right?

Correct. And according to the lawsuit, this pip was a complete sham. designed to guarantee her failure and create a paper trail for termination. How so? The mechanics of how they weaponize this plan are important. She was given 22 mandatory, highly labor-intensive goals to complete in just one month. 22 goals. Yes.

In one month. But she actually completed them, right? She is a high performer. She put her head down and did the work. As she did. And during their weekly check-ins, Jindel even confirmed she was on track. But when the evaluation period ended, Jindal informed her she had failed. Wait, how can she fail if she completed the goals and he confirmed she was on track?

Because he secretly changed the goalposts midway through without telling her. You have got to be joking. No, he evaluated her on work that had been completed months before the plan even started. He even penalized her for not getting a specific sign-off from a leader, a formal approval process that didn't even exist in the AWS operational guidelines. Unbelievable. They essentially invented invisible hurdles that she couldn't possibly jump over. and then fired her for tripping. Despite submitting voluminous written proof from colleagues that she passed the requirements, she was terminated in December 2023.

Which leads her to file this federal lawsuit. And the legal fallout here is something I really wanted to dig into because it is confusing. The defendants, Amazon, moved to dismiss the case. Right. And the judges actually dismissed several of Miloski's claims, including her federal Title VII claims, her retaliation claims, and her equal pay claims. Hold on. If she has all these proof, all these emails, the levels.FYI data, how can a federal judge just toss out the main discrimination claims? That makes no sense to me. It is incredibly frustrating for employees, but it comes down to strict procedural technicalities, not the believability of her story. Let's look at the federal Title VII claims first. Okay. The Equal Employment Opportunity Commission or EEOC is the federal gatekeeper for workplace discrimination. Before you can sue in federal court, you have to file. a charge with them. But the law has a strict 300-day window to file that charge. Okay, so she missed the deadline. Well, it depends on how you count. Malaski filed her charge based on her last day of work in December, but under federal law, the 300-day clock

actually starts taking the exact moment an employee is given notice of their termination, which for her was in November. That is such a harsh technicality. It's like arriving at the airport gate one minute after the door closes. It doesn't matter if you have, a first-class ticket and a fantastic reason for being there. The plane is gone and nobody cares. That is the perfect analogy. Because of that slight miscalculation in dates, measuring from her last day in the office instead of the day she was told she would be fired, the federal claim was tossed. Wow. And for the equal pay claim, the court said the complaint didn't provide enough specific granular details about the exact daily duties of her male comparators. Just providing their

titles and levels.FY data wasn't enough to legally prove. their day-to-day jobs were identical to hers. So a technicality on a calendar and a strict pleading standard erase the federal claims. But her case isn't dead. Her core claims survived. Right. This raises an important question about the layers of legal protection employees actually have. Because while the federal claims fell away, her state and city gender discrimination claims

survived the motion to dismiss. Okay. And this is vital for listeners to understand. The New York State and New York City human rights laws. the NYS-HRL and NYCHRL are intentionally written to be much broader and highly remedial compared to federal law. Here's where it's really interesting, because the local courts looked at this and completely bypassed the federal rigidity. Why did New York lower the bar? New York lawmakers recognize that federal standards had become too difficult for everyday employees to meet.

Under older federal law, discrimination or harassment had to be proven as severe or pervasive. We're just tough to prove. That is a very high bar. It meant isolated comments or subtle sabotage often weren't enough to win a lawsuit. But the city and state laws only require you to prove you were treated less well because of your gender. Treated less well. That sounds so much more grounded in reality. It is. The federal judges, Judge John G. Coultle and magistrate judge Sarah Netburn, they rule that in the right context, a single comment from a supervisor, like telling a female executive to lean back, is absolutely enough to legally prove a hostile work environment and discriminatory intent under these local laws. So the court recognized that lean back wasn't just casual career advice. It was a direct negative counter to the empowerment of women in the workplace. and pushing her into stereotypically feminine design roles while ignoring her complex technical expertise.

The judges saw that for the illegal gender animus it clearly represents. It is a significant ruling because it validates the reality of the modern workplace. Today, discrimination isn't always a screaming match or an overt slur. It is often coded language. It is subjective weaponized performance reviews. It's being told you are the leading lady while your actual brilliant architecture. is handed to the less experienced men in the room. The court said, essentially, we understand the subtext, and it is legally actionable. So what does this all mean for you, the listener?

We've just walked through an incredible contrast today. On one side, you have Annamovsky's raw, undeniable performance. She was architecting the infrastructure to bring tens of billions of dollars in revenue into her company. And on the other side, you have these highly subjective, heavily biased, shifting hurdles her employer allegedly used to force her out simply because she didn't fit into a manager's preferred boys club. It really leaves us with a provocative thought to mull over. If a highly credentialed multi-million dollar revenue generator can be systematically forced out of a powerful tech company through a rigged performance plan, all because she didn't fit a manager's bro culture? How safe is anyone's career?

Seriously. What happens to the modern workbook? place when a company's HR processes become nothing more than a rubber stamp to legitimize a manager's personal illegal biases. It is a chilling question. Because if they can do it to the star quarterback, they can do it to absolutely anyone. Thank you for joining us for this exploration of the employee's survival guide. Next time you are generating a few hundred million for your boss, just remember to keep an eye on who is being asked to polish the helmets. Take care, everyone.

If you like the Employees Survival Guide, I'd really encourage you to leave a review. We try really hard to produce information to you that's informative, that's timely that you can actually use and solve problems on your own and at your employment. So if you like to leave a review anywhere you listen to our podcast, please do so. And leave five stars because anything less than five is really not as good, right? I'll keep it up. I'll keep up the standards up. I'll keep the information flowing at you. If you'd like to send me an email and ask me a question, I'll actually. actually review it and post it on there. You can send it to M-C-A-R-U-Y at C-A-P-C-Law.com. That's capclaw.com.