This week’s conversation is with Emily Pritzkow, executive director for the Wisconsin Building Trades, which represents over 40,000 workers at 15 unions, including the International Brotherhood of Electrical Workers, the International Union of Operating Engineers, and the Wisconsin Pipe Trades Association. I wanted to speak with her about the kinds of jobs needed to build and maintain data centers and whether they have a big impact on how communities view a project. Our conversation was edited for length and clarity.
So first of all, how do data centers actually drive employment for your members?
From an infrastructure perspective, these are massive hyperscale projects. They require extensive electrical infrastructure and really sophisticated cooling systems, work that will sustain our building trades workforce for years – and beyond, because as you probably see, these facilities often expand. Within the building trades, we see the most work on these projects. Our electricians and almost every other skilled trade you can think of, they’re on site not only building facilities but maintaining them after the fact.
We also view it through the lens of requiring our skilled trades to be there for ongoing maintenance, system upgrades, and emergency repairs.
What’s the access level for these jobs?
If you have a union signatory employer and you work for them, you will need to complete an apprenticeship to get the skills you need, or it can be through the union directly. It’s folks from all ranges of life, whether they’re just graduating from high school or, well, I was recently talking to an office manager who had a 50-year-old apprentice.
These apprenticeship programs are done at our training centers. They’re funded through contributions from our journey workers and from our signatory contractors. We have programs without taxpayer dollars and use our existing workforce to bring on the next generation.
Where’s the interest in these jobs at the moment? I’m trying to understand the extent to which potential employment benefits are welcomed by communities with data center development.
This is a hot topic right now. And it’s a complicated topic and an issue that’s evolving – technology is evolving. But what we do find is engagement from the trades is a huge benefit to these projects when they come to a community because we are the community. We have operated in Wisconsin for 130 years. Our partnership with our building trades unions is often viewed by local stakeholders as the first step of building trust, frankly; they know that when we’re on a project, it’s their neighbors getting good jobs and their kids being able to perhaps train in their own backyard. And local officials know our track record. We’re accountable to stakeholders.
We are a valuable player when we are engaged and involved in these sting decisions.
When do you get engaged and to what extent?
Everyone operates differently but we often get engaged pretty early on because, obviously, our workforce is necessary to build the project. They need the manpower, they need to talk to us early on about what pipeline we have for the work. We need to talk about build-out expectations and timelines and apprenticeship recruitment, so we’re involved early on. We’ve had notable partnerships, like Microsoft in southeast Wisconsin. They’re now the single largest taxpayer in Racine County. That project is now looking to expand.
When we are involved early on, it really shows what can happen. And there are incredible stories coming out of that job site every day about what that work has meant for our union members.
To what extent are some of these communities taking in the labor piece when it comes to data centers?
I think that’s a challenging question to answer because it varies on the individual person, on what their priority is as a member of a community. What they know, what they prioritize.
Across the board, again, we’re a known entity. We are not an external player; we live in these communities and often have training centers in them. They know the value that comes from our workers and the careers we provide.
I don’t think I’ve seen anyone who says that is a bad thing. But I do think there are other factors people are weighing when they’re considering these projects and they’re incredibly personal.
How do you reckon with the personal nature of this issue, given the employment of your members is also at stake? How do you grapple with that?
Well, look, we respect, over anything else, local decision-making. That’s how this should work.
We’re not here to push through something that is not embraced by communities. We are there to answer questions and good actors and provide information about our workforce, what it can mean. But these are decisions individual communities need to make together.
What sorts of communities are welcoming these projects, from your perspective?
That’s another challenging question because I think we only have a few to go off of here.
I would say more information earlier on the better. That’s true in any case, but especially with this. For us, when we go about our day-to-day activities, that is how our most successful projects work. Good communication. Time to think things through. It is very early days, so we have some great success stories we can point to but definitely more to come.
