Lack of qualified interpreters in the military unveiled
The allegation is simple and difficult to hear. A former employee whose job was to screen interpreters for Afghan languages at Mission Essential Personnel says the company routinely sent interpreters into battle who did not speak the languages they had been hired to interpret, and that the practice was widespread rather than exceptional.
The supporting evidence is not a document. It is video. Footage broadcast by ABC News shows an interpreter working with U.S. troops in an Afghan village and failing at nearly every part of the job at once. He leaves out what was said. He renders other statements incorrectly. He invents content that nobody uttered. At one point he says, on camera, "I hate these people," referring to the villagers he is supposed to be helping the soldiers talk to.
Three failures, not one
The screening process, according to the whistleblower, was breaking down in distinct ways:
- Interpreters who speak the wrong languages. Afghanistan is not a one-language country. A speaker of one regional tongue can be deployed to a district where nobody uses it and be functionally mute.
- Interpreters who pretend to speak a language. If the person testing you cannot assess the language either, a confident bluff passes.
- Interpreters without ethical principles or standards. The man on the ABC tape was not merely incompetent. He had opinions about the people in front of him and let them into the conversation.
Each of these is a screening failure, and screening was the whistleblower's own department. That is what gives the account its weight. This is not an outsider guessing at what happens inside a contractor. It is someone describing a process he watched fail.
Why the languages get confused
Anyone treating "Afghan" as a language has already made the first mistake. Pashto translation and work in the dari language cover two different tongues spoken by different populations across different provinces, and neither exhausts the country's linguistic map. Uzbek, Turkmen, Balochi and Pashai speakers exist in numbers that matter to a patrol trying to talk to a village elder.
A recruiter hiring at speed, under a contract with headcount targets, does not necessarily know or care about that distinction. The person hired knows. So does the platoon that arrives at a compound and discovers their language interpreter is nodding along to sounds he cannot parse.
What an interpreter is actually for
The core tenets of the job are unglamorous and non-negotiable. Interpret everything that is said. Interpret it accurately. Add nothing. Take no side in the exchange. The interpreter is a conduit, and the moment he becomes a participant with views, the conversation is no longer between the two people who think they are having it.
Professional language interpretation has spent decades codifying those rules for courtrooms, hospitals and diplomatic settings. A courtroom will throw out testimony over an interpreter's embellishment. A hospital will treat a mistranslated dosage as a serious incident. The standards exist because the consequences of ignoring them are known.
In a combat zone the consequences are larger and the standards were looser. Providers of civilian interpreting services in regulated fields are typically tested, credentialed and subject to complaint procedures. War zone contracting outran all of that.
The people who do it properly
None of this is an argument against military interpreters, and it would be a disgrace to read it that way. They volunteer for the work. They walk into the same firefights as the soldiers they accompany, usually with less protection and less recourse, and many of them are identifiable to insurgents in a way no soldier rotating home ever is. Their families become targets. Plenty of them are talented, well trained and better at the job than anyone had a right to expect for the money.
Those interpreters are the ones most damaged by the bad hires. Every fabricated exchange and every hostile aside on camera degrades the trust that the competent majority need in order to work at all. A commander who has been burned once starts second-guessing every rendering he hears, which slows everything down and makes the good interpreter's job harder.
How the contract created the incentive
It helps to look at the commercial shape of the problem. A linguist supply contract pays per interpreter placed, and it comes with a deployment schedule the military expects to be met. Screening is the only part of that pipeline that can slow the numbers down, which makes it the part under permanent pressure. A screener who fails too many candidates is an obstacle to the delivery target. A screener who passes them is efficient. Nobody has to give a corrupt instruction for that arithmetic to produce unqualified people in the field, and the whistleblower's account describes exactly the outcome the incentives would predict.
Not the place to save money
Interpreters are the gatekeepers of communication that protects the lives of thousands of troops and of the civilians they are meant to be safeguarding. A misrendered answer at a checkpoint is not a customer service problem. It is how a farmer with a shovel becomes a suspect, and how a genuine warning goes unheard.
When it comes to getting value for money, this is not the place to skimp. The fix is not exotic and it is not new. Test candidates properly, in the specific language and dialect they will actually be deployed into, using assessors who speak it. Train them in the ethics of the role rather than assuming bilingualism implies neutrality. Monitor performance in the field and act when it falls short. Militaries do exactly this for every other safety-critical skill they buy.
Only by putting real testing, training and monitoring behind military interpreting can the lives that depend on it be protected. The alternative is what the ABC footage already showed: a man in the middle of a war, holding a conversation nobody else in the frame can check.