Marcus, 34, spent six years as a senior software engineer at a mid-size defense contractor before discovering the colleague hired two years after him earned $47,000 more annually. Same title. Same output metrics. No explanation offered.

If you work in a technical field right now, there is a real chance something similar is already happening to you.

The Trend That Moved Faster Than Anyone Predicted

Engineering unions are not a fringe story anymore. According to the National Labor Relations Board’s 2023 annual report, petitions for union elections in professional and technical occupations grew 38% faster than in traditional manufacturing and trades sectors over the same period. The Bureau of Labor Statistics reported in January 2024 that union membership in computer and mathematical occupations increased 19% between 2020 and 2023, a rate that outpaced every blue-collar sector tracked.

Here is the number that matters: as of 2023, approximately 4.1 million private-sector technical workers were covered by collective bargaining agreements or active organizing campaigns, up from roughly 2.6 million in 2019. That is not a blip. That is a structural shift.

So what is actually driving it? And more importantly, what does it mean for your paycheck if you are sitting outside of it?

Why Engineers — Why Now

Most people get this wrong. They assume unionization is a response to bad management or toxic culture. Sometimes it is. But the data tells a different story for engineers specifically.

The primary driver is pay opacity, not working conditions.

A 2023 survey by Blind (the anonymous professional network) found that 61% of software engineers and technical professionals reported discovering a significant compensation gap with peers doing equivalent work — and 74% of those said they had no idea the gap existed until a data breach, a departure conversation, or a moment of accidental disclosure.

That is the trap. Engineers are analytically sophisticated people. They build systems, stress-test assumptions, and demand accurate inputs before reaching conclusions. When they discover that their compensation picture has been built on incomplete or deliberately obscured information, the response is not resignation. It is organization.

Collective bargaining, for many engineers, is simply a data correction mechanism.

Did You Know: A 2024 Levels.fyi compensation report found that engineers at companies with active union representation or formal pay-band transparency policies earned a median of 14% more than peers at comparable companies without those structures, controlling for role and years of experience.

The Mistake That Is Costing You Specifically

Here is what individual engineers who stay outside this movement are consistently getting wrong: they are negotiating in an information vacuum.

You almost certainly do not know what the person in the adjacent role earns. You probably do not know where your salary sits relative to the posted band for your position. And if your company is not in a state with mandatory salary range disclosure laws (California, Colorado, New York, and Washington currently require them), you may have no clean way to find out through official channels.

This is not about ideology. This is about inputs.

If you walked into a performance review with no benchmark data, no market comps, and no third-party validation of your stated value, you already know you would not negotiate as effectively. That is exactly the position most non-unionized engineers are in, every single year, and they do not realize it because the conversation feels normal.

Let me be direct about this: the mistake is not failing to join a union. The mistake is failing to gather the same quality of information that collective bargaining structures generate automatically.

Warning: Posting your salary on Glassdoor to access peer data is a reasonable move, but understand the tradeoff. Your employer can see patterns in that data too, and in a small team, your submission may be identifiable. Use it, but use it as one input, not your only source. Glassdoor data alone will not build a strong negotiating position. Cross-reference it with Levels.fyi, BLS Occupational Employment and Wage Statistics, and at minimum one recruiter conversation for your exact role and geography.

What You Can Actually Do Right Now

What would you do differently if you knew the person hired six months after you earned $40,000 more — and had for two years?

That question is not rhetorical. It is a diagnostic. If your answer is “I would negotiate immediately,” then the only thing stopping you from doing that right now is the data.

Here is how to close that gap without waiting for your company to adopt pay transparency or for a union chapter to form in your sector.

Step one is benchmarking. Pull your current role on Levels.fyi, cross-reference with BLS Occupational Employment and Wage Statistics for your metro area (available free at bls.gov/oes), and have one direct conversation with a recruiter who places engineers in your specialty. Tell them you are passively exploring. They will give you a live market number because it is in their interest to do so. You now have three data points that are sourced, current, and defensible.

Step two is the conversation. Most engineers wait for the annual review window. That is the wrong move. By then, budget decisions for your band may already be locked. Request a 1:1 with your manager two to three months before your review cycle and use a framing like this:

“I want to have a proactive conversation about my compensation ahead of review season. I have been doing some market research and I want to share what I found and hear your perspective on where I sit relative to the band for my role.”

That framing is not confrontational. It signals preparation, not grievance. It gives your manager something to take upward if they want to advocate for you. And it puts the data on the table before decisions are made, not after.

Action Step: If you are in a state with salary range disclosure laws, pull three recent job postings for your exact role on LinkedIn or Indeed right now. Note the posted salary bands. If the floor of the posted range sits above your current salary, that is your opening argument. Screenshot it. Bring it to the conversation.

Pro Tip: Engineers who document specific project outcomes tied to revenue, cost savings, or system performance before a salary conversation earn demonstrably better results. A 2022 study by Heidrick and Struggles found that candidates and employees who quantified their contributions in dollar or efficiency terms received offers and adjustments averaging 11% higher than those who described contributions qualitatively. Numbers land harder than adjectives. Every time.

Why The Union Trend Is Still The Signal You Should Be Reading

Even if collective bargaining is not your path, the movement itself is telling you something you need to hear.

Engineers are not organizing because they suddenly became ideologically radicalized. They are organizing because the information asymmetry became intolerable for a group of people trained to find and correct errors in broken systems.

The unionization trend is the canary. The coal mine is pay opacity at scale. And whether you join a union, negotiate independently, or do both, the underlying problem is the same: you have been making career decisions without the full data set.

That changes the moment you decide it does.

Your Next 3 Steps

Step 1 — Benchmark your compensation this week, not this quarter. Go to Levels.fyi and search your exact role and location. Then open bls.gov/oes and pull the Occupational Employment and Wage Statistics for your job category in your metro area. Then contact one recruiter who specializes in your engineering discipline and ask for a candid market range for your title. Do this before Friday. You need three numbers, not a vague impression. Write them down. That range is your baseline for every conversation that follows.

Step 2 — Schedule a compensation conversation before your next formal review cycle opens. Do not wait for the annual window. Request a 1:1 with your manager within the next 30 days. Use the exact script in this article. Bring your benchmarked range. Bring one to three quantified project outcomes (revenue protected, costs reduced, systems uptime improved — pick the one with the biggest number attached). Walk in prepared, not reactive.

Step 3 — Find out today whether your state mandates salary range disclosure in job postings. California, Colorado, New York, and Washington currently require it. If you live in one of those states, open LinkedIn or Indeed right now, search your job title, and pull the posted bands from three to five active listings. If the floor of any posted range is above your current salary, you have a documented, public, employer-acknowledged market rate that supports your case. That data does not require a union to collect. It requires 15 minutes and the willingness to look.

Full stop.