Why your noncompete agreement could become "Exhibit A" in a discrimination lawsuit.

For years, employers have treated noncompete agreements as just another item in the onboarding paperwork. Hand over the offer letter, the handbook acknowledgment, the tax forms, and somewhere in the stack sits a restrictive covenant that employees sign without much thought.

The recently settled lawsuit against Boston Beer Company serves as a reminder that noncompetes rarely stay confined to contract disputes. They can become Exhibit A in a much larger employment-law battle.

The case was brought by several former sales employees who alleged gender discrimination, retaliation, hostile work environment, and unlawful noncompete practices. According to the complaint, Boston Beer required broad noncompete agreements for sales employees and aggressively enforced them against departing workers. The plaintiffs claimed those restrictions trapped employees in jobs they wanted to leave, prevented them from pursuing opportunities with competitors, and amplified the effects of alleged discrimination and retaliation.

Boston Beer denied the allegations. The parties have now settled.

The settlement itself doesn't establish liability. But the allegations offer several important lessons for employers.

The DOL's World Cup warning is really an overtime compliance warning

The Department of Labor has a message for employers in cities hosting the 2026 World Cup: We're here to help you comply with federal wage and hour laws.

Translation: We're watching.

The DOL's Wage and Hour Division recently announced compliance-assistance resources for employers in the 11 U.S. host cities preparing for the flood of soccer fans, tourists, hotel guests, restaurant patrons, bar tabs, rideshare trips, security needs, cleaning shifts, temporary staffing, and event work that will come with the tournament. The agency specifically pointed employers to resources for industries expecting World Cup-driven spikes, including restaurants, hotels, and other businesses serving fans.

That sounds friendly enough.

It's also a warning.

WIRTW #801: the 'dads' edition

Sunday is Father's Day. Which makes this lawsuit especially worth paying attention to.

Emilio Arellano claims that Golden State Cider fired him after he took leave and sought additional flexibility to help care for his prematurely born son.

According to the lawsuit, his employer didn't respond with support. It responded with retaliation. The company denies wrongdoing. The case remains pending.

But the allegations highlight an issue many employers still fail to recognize:
Workplace discrimination against fathers is real.

Not because employers think fathers are caregivers. Because they think they aren't.

When employers assume fathers should prioritize work over family, they're relying on the same unlawful sex stereotypes that protect mothers when employers assume they should shoulder caregiving responsibilities.

The EEOC has been saying this for decades. Denying leave, flexibility, or opportunities to fathers that would be afforded to mothers can violate Title VII.

And the legal risk is increasing.

Last year, the Supreme Court held in Ames v. Department of Youth Services that Title VII protects "any individual" and that courts cannot impose higher burdens on so-called majority-group plaintiffs.

The EEOC has embraced that principle, making clear that discrimination is discrimination, regardless of who brings the claim.

That matters for fathers.

A dad who is treated differently because he doesn't conform to traditional expectations about gender and caregiving isn't bringing a novel claim. He's bringing a sex discrimination claim.

Which brings us to a question every employer should ask: If this employee were a mother instead of a father, would we have responded the same way?

If the answer is no, you've identified a legal risk. And perhaps a cultural one, too.

---

Here's what I read this week that you should read, too.

Pride Night, Bible Verses, and When Title VII Protections Collide

Three San Francisco Giants pitchers are facing backlash after writing a Bible passage on their Pride Night caps during a team-sponsored LGBTQ+ celebration. The players cited Genesis 9:12-16, the biblical passage describing the rainbow as God's covenant with humanity. Critics viewed the gesture as a deliberate rebuke of Pride Month and the LGBTQ+ community. The Giants apologized for the pain caused. Major League Baseball warned the players for violating uniform rules.

Predictably, the story has become another front in America's never-ending culture war.

But strip away the politics and outrage for a moment, and what's left is a workplace issue every employer should understand.

While the setting is a Major League Baseball clubhouse, the legal and practical issues are no different from those employers confront every day.

The Giants wanted to send a message of inclusion. The players wanted to express their religious beliefs. Those objectives collided in public.

Welcome to the modern workplace.

Regrets, I've had a few.

My life's biggest regret is that I never studied abroad.

The opportunity was there. I just didn't take it. At the time, it felt like too much of a risk. It felt expensive. It felt complicated. And it just felt easier to stay where I was comfortable.

I've regretted it ever since.

And even though I've spent decades making up for lost time, I've never stopped wondering how different my life might have been had I gotten on that plane when I was 20 instead of staying home. The travel bug has since bit me hard. I just wish I had started sooner.

So years ago, I made a promise to myself that if I ever had kids, I would encourage them not to make the same mistake.

Sometimes the merits don't matter. And that's exactly the point.

Imagine you walk into court with what appears to be a strong case. The law is on your side. The facts are on your side. Even the judge seems troubled by what the government is doing. And then you lose anyway. Not because you're wrong. Because the court says it lacks the power to decide whether you're right.

That's essentially what happened last week in FreeState Justice v. EEOC.

DOJ's attack on disparate impact gets Title VII exactly backwards

The Department of Justice just issued a legal opinion claiming that disparate impact liability is unconstitutional because it supposedly "incent[s] — and even coerce[s] — employers to make race-based decisions to avoid liability."

That's a remarkable claim.

It's also a fundamental misunderstanding of how disparate impact law actually works.

Disparate impact claims exist precisely because they target facially neutral policies. No one is alleging intentional discrimination. No one is claiming that an employer adopted a policy because of race, sex, or some other protected characteristic.

The entire point of disparate impact is that a neutral rule can nonetheless operate as an unnecessary barrier to employment opportunities.