DeepL to cut about 250 jobs, acquire Mixhalo team and open San Francisco office as it pivots to 'AI‑native

DeepL announced it will lay off roughly 250 employees, CEO and founder Jarek Kutylowski said in a LinkedIn post on May 7, 2026. He described the decision as the hardest of his career and framed the reductions as part of a broad organizational reset; the company did not provide a department — by-department breakdown or a firm timetable for departures in the announcement.

The stated goal of the reorganization is to rebuild DeepL as an "AI-native" company. Leadership says that will mean replacing large functional departments with smaller teams that rely on AI to perform work previously handled by whole groups. Kutylowski added that DeepL’s existing structure “isn't built for what comes next” and that he will personally lead a task force charged with realigning products and internal processes to the new model.

As a concrete element of the shift, DeepL is doubling down on real-time voice translation. The company is acquiring the team from Mixhalo, a specialist in low-latency audio streaming technology, and plans to open a new San Francisco office tied to that effort. DeepL intends to leverage the Mixhalo engineers and streaming expertise to improve audio capture, delivery and synchronization required for live translation services.

Delivering real-time voice translation at scale involves several engineering challenges: model inference speed, latency optimization, audio codecs, and coordination between edge devices and cloud infrastructure. DeepL competes in this space with established machine translation and speech products such as Google Translate and other cloud providers; the restructure and the Mixhalo hire are presented as moves to address those technical gaps for both consumer and enterprise use cases.

The changes carry potential upside and operational risk. Smaller, AI-led teams combined with the audio — streaming acquisition could accelerate development of low-latency voice features and real-time services, but workforce reductions risk disrupting projects and eroding institutional knowledge. Kutylowski’s decision to lead the task force centralizes control over roadmap changes; developers, partners and customers should watch for forthcoming product and API announcements to see how capabilities, SLAs and deployment regions are affected.