The U.S. Department of Government Efficiency, or DOGE, is reportedly planning to rewrite the software that the U.S. Social Security Administration (SSA) uses to make payments. According to a report from Wired on March 28, 2025, the initiative will focus on switching code written in COBOL to a different programming language. DOGE intends to complete the upgrade in a matter of months, raising concerns among experts about the potential for technical issues during such a rapid transition.
The SSA's software systems contain over 60 million lines of COBOL code, a programming language that has been around since 1960 and is known for its use in financial applications due to its robust features for processing transaction data. The core logic of the SSA's software, which handles critical functions such as issuing social security numbers and managing payments, is largely written in COBOL.
A former senior SSA technologist expressed concern about DOGE's plan, stating that a hasty rewrite could lead to miscalculations or failures in issuing payments. The last significant upgrade to the SSA's code base occurred in the 1980s with the rollout of the MADAM database, which was also written in COBOL and assembly language.
Experts emphasize that before deploying new applications, thorough testing is essential to identify bugs and ensure functionality. The former SSA technologist noted that the testing phase of DOGE's proposed rewrite would likely take several years, and rushing the process could skip vital quality assurance steps, increasing the risk of errors.
Interestingly, an internal document from the SSA outlining the agency's priorities for May does not mention the planned code revamp, raising questions about the timeline and feasibility of the project. The push to transition the SSA away from COBOL is reportedly being led by Steve Davis, a former employee of SpaceX, who has been identified as the de facto head of DOGE. Currently, at least ten DOGE staffers are working within the SSA, and since their arrival, the agency has faced frequent website outages and other technical issues.
This report comes just weeks after DOGE shut down 18F, a technology unit within the U.S. General Services Administration that had around 90 employees dedicated to improving federal websites and streamlining technology procurement.
In a related development, during a Senate Finance Committee confirmation hearing on March 25, 2025, Fiserv CEO Frank Bisignano, who has been nominated by President Donald Trump to lead the SSA, stated he has “never thought about privatizing” the agency. This comment came in response to concerns about DOGE's cost-cutting efforts targeting the SSA, an agency that has become a focal point for Musk's administration.
At the hearing, Bisignano emphasized the importance of ensuring that the SSA operates correctly, asserting, “I want to provide all the information required by the Senate, and by anyone else, in order to make these decisions, but I don’t believe I’m a decision maker.” His remarks indicate a commitment to transparency and accountability amidst the ongoing scrutiny of the SSA.
Meanwhile, the push to migrate the SSA's computer systems off COBOL is being organized by Davis and aims to transition all systems to a more modern programming language like Java. However, this expedited deadline raises alarms about the potential disruption to payments for the more than 65 million people currently receiving Social Security benefits.
Experts have warned that in addition to the risk of underpayment or overpayment, there is a significant danger of not paying beneficiaries at all, which could result in invisible errors and omissions. The SSA has faced increasing pressure from the Trump administration, particularly after Musk made allegations of fraud within the agency, claiming that individuals as old as 150 were receiving benefits, a statement that is not supported by factual evidence.
As reported by The Washington Post, the SSA has experienced frequent website crashes and extended wait times for phone assistance, coinciding with significant budget cuts imposed by DOGE. This proposed migration away from COBOL is not the first attempt by the SSA to modernize its systems; in 2017, the agency announced plans to secure hundreds of millions in funding to replace its core systems, predicting a five-year timeline for modernization. However, due to the COVID-19 pandemic, the SSA shifted its focus to other public-facing projects.
COBOL is a programming language that was developed in part by computing pioneer Grace Hopper in the 1950s. Following its inception, the Defense Department effectively pressured the private sector to adopt COBOL, leading to its widespread use in mainframe systems by the 1970s. As of 2016, the SSA's infrastructure still contained more than 60 million lines of COBOL code, with millions more written in other legacy languages.
The SSA's core logic, which is crucial for issuing social security numbers and managing payments, is predominantly written in COBOL. Experts warn that even minor changes to this code could lead to cascading failures across multiple programs. Dan Hon, a principal at a technology strategy consultancy, remarked, “If you weren't worried about a whole bunch of people not getting benefits or getting the wrong benefits... then sure go ahead,” highlighting the potential consequences of the proposed migration.
It remains unclear when exactly the code migration will commence. A recent document circulated among SSA staff outlining priorities through May does not reference the migration, instead focusing on other initiatives like terminating non-essential contracts and adopting artificial intelligence for administrative tasks. Earlier this month, Wired reported that at least ten DOGE operatives are currently embedded within the SSA, including some relatively inexperienced engineers.
As the SSA navigates these challenges, it faces a critical juncture in its efforts to modernize its systems while ensuring that the benefits and services provided to millions of Americans remain intact. The potential implications of a rushed migration away from COBOL could have far-reaching effects on the agency's ability to serve its beneficiaries, making it imperative for decision-makers to proceed with caution.
