You’re out of free articles.
Log in
To continue reading, log in to your account.
Create a Free Account
To unlock more free articles, please create a free account.
Sign In or Create an Account.
By continuing, you agree to the Terms of Service and acknowledge our Privacy Policy
Welcome to Heatmap
Thank you for registering with Heatmap. Climate change is one of the greatest challenges of our lives, a force reshaping our economy, our politics, and our culture. We hope to be your trusted, friendly, and insightful guide to that transformation. Please enjoy your free articles. You can check your profile here .
subscribe to get Unlimited access
Offer for a Heatmap News Unlimited Access subscription; please note that your subscription will renew automatically unless you cancel prior to renewal. Cancellation takes effect at the end of your current billing period. We will let you know in advance of any price changes. Taxes may apply. Offer terms are subject to change.
Subscribe to get unlimited Access
Hey, you are out of free articles but you are only a few clicks away from full access. Subscribe below and take advantage of our introductory offer.
subscribe to get Unlimited access
Offer for a Heatmap News Unlimited Access subscription; please note that your subscription will renew automatically unless you cancel prior to renewal. Cancellation takes effect at the end of your current billing period. We will let you know in advance of any price changes. Taxes may apply. Offer terms are subject to change.
Create Your Account
Please Enter Your Password
Forgot your password?
Please enter the email address you use for your account so we can send you a link to reset your password:
It will take years, at least, to reconstitute the federal workforce — and that’s if it can be managed at all.

By anyone’s best guess, there are — or soon will be — 284,186 fewer federal employees and contractors than there were on January 19, 2025. While Voice of America and the U.S. Agency for International Development have had it the worst, the Trump administration’s ongoing reductions have spared few government agencies. Over 10% of the staff at the National Oceanic and Atmospheric Administration, including at critical weather stations and tsunami monitoring centers, have left or been pushed out. Layoffs, buyouts, and early retirements have reduced the Department of Energy’s workforce by another 13%.
The best-case scenario for the civil service at this point would be if the administration has an abrupt change of heart and pivots from the approach of government “efficiency” guru Elon Musk and Office of Management and Budget Director Russell Vought, who has said he wants government bureaucrats to be “traumatically affected” by the funding cuts and staff reductions. Short of that unlikelihood, its membership will have to wait out the three-and-a-half remaining years of President Trump’s term in the hopes that his successor will have a kinder opinion of the federal workforce.
But even that wouldn’t mean a simple fix. In my effort to learn how long it would take the federal workforce to recover from just the four-plus months of Trump administration cuts so far, no one I spoke to seemed to believe a future president could reverse the damage in a single four-year term. “It will be very difficult, if not impossible, to restore the kind of institutional knowledge that’s being lost,” Jacqueline Simon, policy director of the American Federation of Government Employees, the largest union of federal government workers, told me.
There are three main reasons why restaffing the government will be trickier than implementing a simple policy change. The first is that the government had already been struggling to fill empty posts before Trump’s layoffs began. “For a considerable period of time, the biggest challenge for the federal government, in personnel terms, has been getting talented people into government quickly,” Don Moynihan, a professor at the Ford School of Public Policy at the University of Michigan, told me. “That was already a problem preceding the Trump administration, and they just made it a lot worse.”
Before Trump’s second term, an estimated 83% of “major federal departments and agencies” struggled with staff shortages, while 63% reported “gaps in the knowledge and skills of their employees,” according to research by the Partnership for Public Service, a nonprofit supporting the civil service. Even President Joe Biden, who’d promised to restore a “hollowed out” federal workforce after Trump 1.0, struggled at the task, ultimately growing the number of permanent employees by just 0.9% by March 2023. (He eventually saw 6% growth over his entire term; a bright spot was hiring for roles necessary for carrying out the Infrastructure Investment and Jobs Act.)
Still, as I’ve previously reported, many hard-to-fill roles in remote locations or that required specialized skills were empty when Trump came into office and ordered a hiring freeze.
The second challenge to rebuilding the federal workforce is that many employees who have left the government may not be able to — or may not want to — return to their previous roles. Staff who have taken early retirements will be permanently lost or have to return as rehired annuitants, which Simon of the American Federation of Government Employees noted has “a lot of disadvantages,” including, in some cases, earning less than the minimum wage. Other former employees, particularly in the sciences, may have been enticed abroad as part of the U.S. brain drain. Still others may have found enjoyable and fulfilling work at the state level, in nonprofits, or in the private sector, and have no interest in returning to government.
It certainly doesn’t help that the Trump administration has made the federal government a less competitive employer. Abigail Haddad, a data scientist for the Department of the Army and, until recently, the Department of Homeland Security’s AI Corps, wrote for Moynihan’s Substack, Can We Still Govern?, that she’d been hired for a fully remote job, only to be told “we would be fired if we did not immediately return to office 9 to 5, five days a week.” Rather than make a two-and-a-half-hour round-trip commute to “an office that was never mentioned when I took the job,” Haddad quit. “It was clear to me that the people making these decisions about my work conditions were not only unconcerned about my ability to be productive, but were actively hostile toward it,” she wrote.
The last obstacle to reversing the Trump administration’s cuts echoes Haddad’s experience — and is, in my view, the most worrisome of all. That is, the current landscape will almost certainly dissuade future generations from pursuing jobs in the government. “There will be some opportunities in states and nonprofits,” Simon noted. “But as far as an opportunity for public service in the federal government — they’ve made that an impossibility, at least for the next many years.”
Moynihan, the public policy professor, added that while it’s still early to predict what students will do, he’s heard worries in his classrooms about “what future job prospects look like, given the instability around the federal government.” But the crisis goes beyond just hiring concerns.
“There’s a whole generation of public servants who would say they were inspired to go into government because they heard John F. Kennedy say, ‘Ask not what your country can do for you — ask what you can do for your country,’” he said. “There is a genuine value in elected leaders calling on people to serve and presenting that service in noble terms.” Most people don’t join the public sector for the paycheck, after all — it’s for the “opportunity to do meaningful work, and for job stability and security,” Moynihan went on. The Trump administration has gutted the promises of both.
So then, how long would it take to restaff the government? Simon told me that since it was an executive order that directed the cuts, they could be functionally undone by another executive order, though the rehiring process itself “could take years.” Moynihan used the metaphor of a muscle, rather than a switch that gets turned on and off, to answer the same question. “The Trump administration is cutting a lot of muscle right now, and so the next president will not be able to simply, on day one, bring that back,” he told me. “They’ll have to be able to persuade people that the workspace is no longer going to be toxic, is going to be more secure, and will allow them to do meaningful work — and they’re going to face a fairly skeptical audience, given everything that’s going on.”
But that’s if things hold as they are. They could still get worse.
As the administration continues its attack on the civil service, it seems all but sure to be cueing up an eventual Supreme Court case over the legality of reclassifying federal employees so that they can be easily fired if they’re perceived as not loyal enough to the president. And if the court rules that the president can do so, “any sort of law that Congress might put in the future that constrains those powers is unconstitutional,” Moynihan said. In that scenario, the government would no longer be able to provide “any sort of long-term credible commitments to potential employees that four years down the line or eight years down the line, any new president could just rip up their workplace” or lay them off for arbitrary reasons.
The answer to how long it would take to restaff the federal government after Trump, then, takes on an entirely different tenor — it may never be the same again.
Log in
To continue reading, log in to your account.
Create a Free Account
To unlock more free articles, please create a free account.
It’s aware of the problem. That doesn’t make it easier to solve.
The data center backlash has metastasized into a full-blown PR crisis, one the tech sector is trying to get out in front of. But it is unclear whether companies are responding effectively enough to avoid a cascading series of local bans and restrictions nationwide.
Our numbers don’t lie: At least 25 data center projects were canceled last year, and nearly 100 projects faced at least some form of opposition, according to Heatmap Pro data. We’ve also recorded more than 60 towns, cities and counties that have enacted some form of moratorium or restrictive ordinance against data center development. We expect these numbers to rise throughout the year, and it won’t be long before the data on data center opposition is rivaling the figures on total wind or solar projects fought in the United States.
I spent this week reviewing the primary motivations for conflict in these numerous data center fights and speaking with representatives of the data center sector and relevant connected enterprises, like electrical manufacturing. I am now convinced that the industry knows it has a profound challenge on its hands. Folks are doing a lot to address it, from good-neighbor promises to lobbying efforts at the state and federal level. But much more work will need to be done to avoid repeating mistakes that have bedeviled other industries that face similar land use backlash cycles, such as fossil fuel extraction, mining, and renewable energy infrastructure development.
Two primary issues undergird the data center mega-backlash we’re seeing today: energy use fears and water consumption confusion.
Starting with energy, it’s important to say that data center development currently correlates with higher electricity rates in areas where projects are being built, but the industry challenges the presumption that it is solely responsible for that phenomenon. In the eyes of opponents, utilities are scrambling to construct new power supplies to meet projected increases in energy demand, and this in turn is sending bills higher.
That’s because, as I’ve previously explained, data centers are getting power in two ways: off the existing regional electric grid or from on-site generation, either from larger new facilities (like new gas plants or solar farms) or diesel generators for baseload, backup purposes. But building new power infrastructure on site takes time, and speed is the name of the game right now in the AI race, so many simply attach to the existing grid.
Areas with rising electricity bills are more likely to ban or restrict data center development. Let’s just take one example: Aurora, Illinois, a suburb of Chicago and the second most-populous city in the state. Aurora instituted a 180-day moratorium on data center development last fall after receiving numerous complaints about data centers from residents, including a litany related to electricity bills. More than 1.5 gigawatts of data center capacity already operate in the surrounding Kane County, where residential electricity rates are at a three-year high and expected to increase over the near term – contributing to a high risk of opposition against new projects.
The second trouble spot is water, which data centers need to cool down their servers. Project developers have face a huge hurdle in the form of viral stories of households near data centers who suddenly lack a drop to drink. Prominent examples activists bring up include this tale of a family living next to a Meta facility in Newton County, Georgia, and this narrative of people living around an Amazon Web Services center in St. Joseph County, Indiana. Unsurprisingly, the St. Joseph County Council rejected a new data center in response to, among other things, very vocal water concerns. (It’s worth noting that the actual harm caused to water systems by data centers is at times both over- and under-stated, depending on the facility and location.)
“I think it’s very important for the industry as a whole to be honest that living next to [a data center] is not an ideal situation,” said Caleb Max, CEO of the National Artificial Intelligence Association, a new D.C.-based trade group launched last year that represents Oracle and myriad AI companies.
Polling shows that data centers are less popular than the use of artificial intelligence overall, Max told me, so more needs to be done to communicate the benefits that come from their development – including empowering AI. “The best thing the industry could start to do is, for the people in these zip codes with the data centers, those people need to more tangibly feel the benefits of it.”
Many in the data center development space are responding quickly to these concerns. Companies are clearly trying to get out ahead on energy, with the biggest example arriving this week from Microsoft, which pledged to pay more for the electricity it uses to power its data centers. “It’s about balancing that demand and market with these concerns. That’s why you're seeing the industry lean in on these issues and more proactively communicating with communities,” said Dan Diorio, state policy director for the Data Center Coalition.
There’s also an effort underway to develop national guidance for data centers led by the National Electrical Manufacturers Association, the American Society of Heating, Refrigerating, and Air-Conditioning Engineers, and the Pacific Northwest National Laboratory, expected to surface publicly by this summer. Some of the guidance has already been published, such as this document on energy storage best practices, which is intended to help data centers know how to properly use solutions that can avoid diesel generators, an environmental concern in communities. But the guidance will ultimately include discussions of cooling, too, which can be a water-intensive practice.
“It’s a great example of an instance where industry is coming together and realizing there’s a need for guidance. There’s a very rapidly developing sector here that uses electricity in a fundamentally different way, that’s almost unprecedented,” Patrick Hughes, senior vice president of strategy, technical, and industry affairs for NEMA, told me in an interview Monday.
Personally, I’m unsure whether these voluntary efforts will be enough to assuage the concerns of local officials. It certainly isn’t convincing folks like Jon Green, a member of the Board of Supervisors in Johnson County, Iowa. Johnson County is a populous area, home to the University of Iowa campus, and Green told me that to date it hasn’t really gotten any interest from data center developers. But that didn’t stop the county from instituting a one-year moratorium in 2025 to block projects and give time for them to develop regulations.
I asked Green if there’s a form of responsible data center development. “I don’t know if there is, at least where they’re going to be economically feasible,” he told me. “If we say they’ve got to erect 40 wind turbines and 160 acres of solar in order to power a data center, I don’t know if when they do their cost analysis that it’ll pencil out.”
Plus a storage success near Springfield, Massachusetts, and more of the week’s biggest renewables fights.
1. Sacramento County, California – A large solar farm might go belly-up thanks to a fickle utility and fears of damage to old growth trees.
2. Hampden County, Massachusetts – The small Commonwealth city of Agawam, just outside of Springfield, is the latest site of a Massachusetts uproar over battery storage…
3. Washtenaw County, Michigan – The city of Saline southwest of Detroit is now banning data centers for at least a year – and also drafting regulations around renewable energy.
4. Dane County, Wisconsin – Another city with a fresh data center moratorium this week: Madison, home of the Wisconsin Badgers.
5. Hood County, Texas – Last but not least, I bring you one final stop on the apparent data center damnation tour: Hood County, south of the Texas city of Fort Worth.
A conversation with San Jose State University researcher Ivano Aiello, who’s been studying the aftermath of the catastrophe at Moss Landing.
This week’s conversation is with Ivano Aiello, a geoscientist at San Jose State University in California. I interviewed Aiello a year ago, when I began investigating the potential harm caused by the battery fire at Vistra’s Moss Landing facility, perhaps the largest battery storage fire of all time. The now-closed battery plant is located near the university, and Aiello happened to be studying a nearby estuary and wildlife habitat when the fire took place. He was therefore able to closely track metals contamination from the site. When we last spoke, he told me that he was working on a comprehensive, peer-reviewed study of the impacts of the fire.
That research was recently published and has a crucial lesson: We might not be tracking the environmental impacts of battery storage fires properly.
The following conversation was lightly edited for clarity.
Alright let’s start from the top – please tell my readers what your study ultimately found.
The bottom line is that we detected deposition of fine airborne particles, cathode material – nickel, manganese, and cobalt – in the area surrounding the battery storage facility. We found those particles right after the fire, immediately detected them in the field, sampled the soils, and found visible presence of those particles using different techniques. We kept measuring the location in the field over several months after the fire.
The critical thing is, we had baseline data. We had been surveying those areas for much longer before the fire. Those metals were in much higher concentration than they were before, and they were clearly related to the batteries. You can see that. And we were able to see changes in surface concentrations in the soils over time, including from weather – once the rains started, there was a significant decrease in concentrations of the metals, potentially related to runoff. Some of them migrated to the soil.
What we also noticed is that the protocols that have been used to look at soil contamination call for a surface sample of 3 inches. If your sample thickness is that and the layer of metal deposit is 1 millimeter or 5 millimeter, you’re not going to see anything. If you use standard protocols, you’re not going to find anything.
What does that mean for testing areas around big battery storage fires?
That’s exactly what I hope this work helps with. Procedures designed in the past are for different types of disasters and incidents which are more like landslides than ash fallout from a fire. These metal particles are a few microns thick, so they slide easily away.
It means we have to rethink how we go about measuring contamination after industrial fires and, yes, battery fires. Because otherwise it’s just completely useless – you’re diluting everything.
The other thing we learned is that ashfall deposits are very patchy. You can get different samples between a few feet and find huge differences. You can’t just go out there and take three samples in three places, you have to sample at a much higher resolution because otherwise you’ll miss the whole story.
When it comes to the takeaways from this study, what exactly do you think the lessons should be for the battery companies and regulators involved?
There are a lot of lessons we learned from this fire. The first is that having baseline data around a potential fire site is important because then you can better understand the after.
Then, the main way to assess the potential hazards during the fire and after the fire are air quality measurements. That doesn’t tell you what’s in the air. You could have a high concentration of pollen, and then you know the quality of the air, but if you replace that with metal it is different. It’s not just how much you’re breathing, but what you are breathing.
Also, fast response. [Vistra] just released a report on soil saying there was nothing … but the sampling was done eight months after the fire. Our study shows after the fire you have this pulse of dust, and then it moves. Stuff moves to soil, across habitat. So if you don’t go out there right away, you might miss the whole thing.
Finally, what we found was that the fallout from the fire was not a bullseye pattern centered at the facility but rather offset kilometers away because of the wind.
We didn’t know much about this before because we didn’t have a real case study. This is the first real live event in which we can actually see the effects of a large battery burning.