“I have no idea how they got my contact information,” says the engineer. Unlike other interviews for government jobs, the engineer says, there was no recruiter present—only Coristine was on the interview call. “Normally initial screenings are done over the phone, rather than video, to reduce bias in the process,” they say.

During the engineer’s NDS interview, they say, Coristine didn’t seem to know the skill set he was looking for. “I generally don’t know if this person is capable of evaluating a full-stack engineer,” they say, “because they themselves aren’t aware of the skill sets, tools, and things needed in this profession.” Coristine did not reply to a request for comment. (In January 2025, Coristine was one of several DOGE members who interviewed workers at the General Services Administration’s Technology Transformation Services, who were required to defend their jobs and justify their projects. At the time, employees who spoke to WIRED described meetings in which the DOGE members were not familiar with their work.)

Coristine told the engineer that the role was geared toward supporting what would become Rampart, a tool released in late June to prevent personally identifiable information (PII) from leaving a user’s browser, particularly if they’re using something like a chatbot. In an interview with the Technology Business Programming Network (TBPN) podcast, Coristine described the project as a “side quest ” and told the engineer that the NDS team of about 30 people did not include a machine-learning engineer.

The tool is similar to OpenAI’s browser-based “privacy filter,” which can detect things like a personal email, address, or account number, and mask them automatically. But exactly how this tool is meant to be used in the context of government services is unclear. In the interview with TBPN, Coristine did not offer any particular examples, though he noted the tool is significantly smaller than OpenAI’s, making it potentially more accessible in lower-bandwidth environments.

“It feels very counterintuitive because in most instances, when you are asking for PII, you want PII,” says the engineer, noting that in government work, a user might need to provide PII like their social security number or address in order to access government benefits. “You don’t want that information redacted.”

In many cases, developers can choose to encrypt certain fields that an API sends to the backend of a website, and websites that use HTTPS connections to communicate with their backends also encrypt their requests.

This is not the first time the Trump administration has tried to reinvent the wheel of government technology. Last year, as DOGE promised government efficiency through technology, its members fired technologists who were already working on exactly the kinds of projects it purported to want, even killing a flagship product in the Internal Revenue Service’s free tax filing tool. An OPM memo published last week instructed agencies to prioritize hiring technical talent.

“This does feel superfluous. My most optimistic speculation is that this is indicative of an organization that has no goals,” the engineer says, noting that the National Institute of Standards and Technology (NIST) regularly supports the creation of tools to solve complex technical problems around issues like privacy. “Why are these guys who are so closely associated with the White House wasting tax money on this little hacker project?”