Given
* We are seeing highly publicized layoffs across many companies in many industries. * These companies are not uniformly underperforming relative to the market. Some are even doing well in absolute terms. * These add weeks of runway to their existing years. * Executive and shareholder compensation is not being cut in correspondence.
How do we, as tech-labor, coordinate in the same way for the conditions we want? Knowing the distaste for union labor in the West, especially in the tech industry, what are the next steps.
* Can we coordinate secretly, without letting management know? * Can we avoid preventative firings of organizers? * Can we do this while providing meaningful material improvement in outcomes for all tech workers without being suborned by leftist-style factionism?
I hope everyone laid off comes back ready to acqui-unionize.
You have have a plan to offer something else- job security by pulling up the ladder on new programmers is probably the easiest lift. It worked for the doctors and lawyers.
That way, the association / members can offer something to employers - they will operate professionally, use approved and best practice tools and processes, and achieve outcomes on company time instead of arguing about tabs vs spaces, emacs vs vim, the need to rewrite everything in rust or clojure, etc., and in exchange they expect better conditions and terms.
The best examples of this kind of thing are the National Association of Realtors, bar associations, FINRA, FASB, etc. Although they don't look and feel like unions, they do function effectively to protect the interests of their members, and to a lesser extent the public and industry.
2. Find enough likeminded coworkers who are onboard with organizing.
3. Contact the NLRB to hold a vote. You’ll need a majority. You don’t need unanimous buy in, and likely won’t get it; optimize accordingly.
Organizing is federally protected. If you have suspicion or evidence your employer is retaliating against your organizing efforts, report them to the NLRB.
Unions, like companies, are only as good as the people in charge. Good luck.
https://uniontrack.com/blog/roadmap-for-unionizing-first-ste...
https://www.nlrb.gov/about-nlrb/what-we-do/conduct-elections
https://www.nlrb.gov/about-nlrb/rights-we-protect/the-law/em...
https://www.dol.gov/sites/dolgov/files/olms/regs/compliance/...
When I worked at a UAW shop (GM) in the 1980s, there were salaried engineers and union hourly people building the cars. When the union made a gain by way of a strike, it was automatically applied to the salaried folks. We understood that their work benefitted the rest. This started to break down when GM bought EDS in 1985 and transferred all their IT people over to it and they lost all of those benefits. People who were able to get themselves classed as "engineers" rather than data processing were able to avoid the big transfer.
I have worked for less than $25/hr at various web shop LLCs, less than what some tech internships pay. I'm also going through one of my longest unemployment periods ever. Yet, even I don't think unionizing tech jobs is going to prevent these sorts of situations for developers.
Start a union. Ask people to join. Don't tell the companies who joins. Wait until you have a critical mass. Then do stuff.
I prefer being a tech mercenary than joining a union.