Inside Meltwater Engineering.

Our team used AI-assisted development to rewrite two legacy applications: a decade-old CRUD app and an orphaned web service. Here is what worked, what didn't, and what we learned about the role of engineering judgment when AI is in the loop.

There's a particular kind of energy early in an engineering career. A quiet obsession. AI has brought that feeling back, not by replacing judgment, but by removing the friction that buried it.

How we overhauled Meltwater's speech-to-text pipeline with speech activity detection and dual-provider routing, cutting monthly model costs by 87% and making processing 1.5x faster.

We moved 1.23 TB of sentence embeddings out of our database cluster and into Amazon S3 Vectors, cutting the workload's run cost by roughly 90% and extending semantic search from 30 days to 24 months.

We rebuilt our journalist research pipeline from the ground up, splitting one generalist agent into focused specialist components. The result was 40% lower costs, around 10% higher prediction accuracy, and a system we can finally improve one piece at a time.

Keeping nearly 1,000,000 journalist profiles accurate used to be a fully manual job. We built an AI agent, Admiral, that cut research cost per profile by 85% and time per profile by 90%. Two lessons did most of the work: the value of a self-review step, and keeping the agent's toolset as...

The Meltwater Paris AI team attended the inaugural PyTorch Conference Europe at Station F. Here are our key takeaways on inference maturity, GPU kernel tooling, hardware co-evolution, and what it means for our AI platform.

How we reduced inference costs by 45.5% while improving accuracy by 3.02% by rethinking how our entity-level sentiment system processes documents.

How we tracked down and fixed a memory leak in a Kubernetes-hosted Node.js service after upgrading from Node 18 to 22, uncovering issues with closure retention, caching logic, and V8 engine changes along the way.