NASA is restructuring its workforce management strategy to improve efficiency.

Under Administrator Jared Isaacman’s workforce initiative, thousands of contractor positions are being converted into federal civil service jobs. The effort is intended to rebuild technical expertise within the agency and strengthen control over mission-critical operations.

For decades, NASA has relied on its old workforce model. The shift, however, has already sparked debate over costs, flexibility, contractor relationships, and the agency’s ability to manage its most important technical functions.

Former NASA flight director Gerry Griffin supports the move. Drawing from his experience during the Apollo program, he believes NASA performs best when its core mission responsibilities remain within the agency.

Gerry Griffin’s Apollo Experience Shows Why Trust Matters

According to Ars Technica, Griffin served as a flight director during NASA’s Apollo missions and later became director of Johnson Space Center in Houston. His experience included several lunar landings and the dramatic effort to bring the Apollo 13 crew safely home.

For Griffin, one of the most important lessons from those missions was the value of trust between people working in Mission Control.

The Apollo 12 mission provided a striking example. In 1969, the Saturn V rocket triggered lightning while passing through electrically charged clouds during its ascent. The strike disrupted electrical systems aboard the spacecraft, creating a situation that required immediate action from both flight controllers and astronauts.

Griffin recalled that members of his Mission Control team, including John Aaron and Jerry Carr, were able to respond because they trusted one another and communicated effectively. The spacecraft recovered from the electrical problems and went on to complete the second crewed lunar landing.

How NASA Became More Dependent on Contractors

Contractors have long played an important role in NASA operations. During the Apollo era, outside companies supplemented the agency’s workforce and provided expertise for specialized systems and equipment.

However, Griffin noted that the people working directly in Mission Control remained NASA employees. The agency retained direct responsibility for the mission, including its ultimate success or failure.

That arrangement gradually changed. Griffin said he was surprised during the middle of the Space Shuttle era to see more Mission Control positions transferred to contractors.

Contractors continued to provide valuable technical knowledge, but an increasing number of critical positions were outsourced. In some cases, the approach allowed NASA to increase its workforce without expanding the number of civil service positions.

Isaacman’s workforce initiative is intended to reverse part of that trend.

NASA Plans to Bring 7,500 Positions In-House

As part of the initiative, NASA is bringing approximately 7,500 contract positions into the agency as civil service roles. The goal is to rebuild what Isaacman describes as NASA’s “core competencies.”

Per Ars Technica, the change affects technical positions connected to areas such as launch operations, engineering, and other mission-critical functions.

Griffin has welcomed the initiative, arguing that rebuilding NASA’s internal capabilities could benefit the agency over the long term.

NASA previously had a much larger contractor workforce than civil service workforce. Before the latest changes, the agency had roughly 40,000 contractors and about 14,000 civil servants.

The balance had also been affected by federal workforce reductions and employee departures earlier in 2025.

The current initiative, however, is not simply an effort to restore positions lost through those earlier reductions. Its stated focus is on strengthening NASA’s technical knowledge and ensuring that essential functions remain under direct agency control.

The Cost Debate Behind NASA’s Workforce Initiative

Cost savings are another major argument supporting the workforce transition.

Isaacman has said early pilot programs identified more than $100 million in potential savings by converting contractor positions to civil service jobs. He has suggested that the savings could eventually exceed $1 billion.

The reasoning is partly based on the administrative structure surrounding government contracts. Contractor arrangements can involve layers of management, third-party systems, and contractual restrictions that may add costs or slow access to information.

Contracting companies dispute this argument. They have said the overhead associated with their employees can be relatively small, reportedly around 2 to 3 percent of employee compensation.

The disagreement reflects a larger question about whether NASA’s traditional contractor model remains the most efficient way to support an increasingly complex space program.

Why Some Industry Groups Oppose the Change

The workforce transition has not been universally welcomed. Major NASA contractors, including Amentum, Jacobs Engineering Group, and KBR, have expressed concerns about the disruption caused by such a significant change.

The companies have historically supplied thousands of workers to NASA field centers across the country. Their position is that the existing contractor ecosystem provides flexibility that could be difficult for a government workforce to replicate.

Under a contractor model, NASA can change its requirements or choose not to renew a contract when priorities shift. Civil servants, by comparison, have stronger employment protections.

That difference can give NASA more flexibility when using contractors, particularly during periods when programs expand, contract, or change direction.

Some industry representatives also argue that the contractor ecosystem has supported NASA’s broader relationships with Congress and other government stakeholders.

Why NASA Says Greater In-House Expertise Is Necessary

Supporters of the workforce initiative argue that flexibility is not the only consideration. They point to situations where contractors’ control over technical information can create barriers for NASA personnel.

One example involved preparations for the Artemis II launch. According to an engineer involved in the process, NASA controllers dealing with a ground-system issue reportedly did not have direct access to certain technical schematics because of intellectual property and contractual restrictions.

Instead, information had to be shared through a Microsoft Teams screen-sharing session.

For supporters of the workforce conversion, situations like this demonstrate the problem with placing critical technical knowledge outside the agency. Bringing key personnel into NASA could allow engineers and controllers to access essential information more directly.

The goal is not necessarily to eliminate contractors from NASA’s operations. Rather, the initiative seeks to ensure that the agency itself maintains sufficient expertise to understand, oversee, and make decisions about its most important systems.

Could the Workforce Shift Affect Artemis?

The timing of the initiative has raised concerns because NASA is pursuing the ambitious Artemis program, including plans to return astronauts to the Moon and establish a longer-term lunar presence.

Critics have argued that changing NASA’s workforce structure so quickly could create disruption and potentially affect schedules or safety.

The Aerospace Safety Advisory Panel, however, offered a more positive assessment. During an August meeting, panel chair Lieutenant General Susan J. Helms said the initiative had made substantial progress.

Helms acknowledged that the speed and scope of the workforce changes had created challenges and that organizational changes can be unsettling. However, the panel had not identified critical safety concerns related to the initiative.

The panel ultimately described the administrator’s workforce directive as a coherent and necessary vision for NASA’s future.

Frequently Asked Questions

Why is NASA converting contractor jobs into civil service positions?

NASA is converting thousands of contractor positions to civil service roles to strengthen the agency’s internal technical expertise and maintain greater control over mission-critical functions. Cost savings and fewer contractual barriers are also cited as reasons for the change.

How many NASA contractor positions are being brought in-house?

The workforce initiative aims to bring approximately 7,500 contract positions into NASA as civil service jobs.

Why does Gerry Griffin support NASA’s workforce changes?

Former flight director Gerry Griffin believes NASA benefits when critical mission responsibilities and expertise remain within the agency. His view is shaped by his Apollo-era experience, particularly the importance of trust and communication during emergencies.

Does NASA plan to eliminate contractors?

The workforce initiative does not mean that all contractors will disappear from NASA. Contractors continue to provide specialized expertise and support for many agency programs. The focus is on ensuring that NASA retains core technical capabilities internally.

What are the main criticisms of NASA’s workforce initiative?

Critics argue that the transition could reduce NASA’s workforce flexibility, disrupt established contractor relationships, and create uncertainty during an important period for the Artemis program. Some also question whether the expected cost savings will materialize.

Could the changes affect the Artemis program?

Critics have raised concerns about potential disruption to Artemis missions, but NASA’s Aerospace Safety Advisory Panel reported substantial progress and said it had not identified critical safety concerns related to the workforce transition.

Why are civil servants considered different from contractors?

Civil servants generally have stronger employment protections and remain directly within the federal agency. Contractors work through private companies under specific agreements, giving agencies greater flexibility to change or end contracted services when requirements shift.