Pangea Money Transfer Innovation & Technology Culture

What’s your rule for fast, safe releases — and what KPI proves it works?

We ship small, easily reversible changes that are simple to attribute issues to, with active and passive monitoring in place.

We validate releases by monitoring system health and customer signals — including latency, server utilization, support volume and business metrics like cancellation and conversion rates. By comparing trends and outcomes between test and control groups, we can measure real business impact while keeping production risk low.

What standard or metric defines “quality” in your stack?

Our primary quality metric is “customers impacted.” While signals like a latency spike from 75ms to 150ms are worth investigating, our true focus is ensuring reliability for customers. We post-mortem every production incident and quantify customer impact, using that data to identify and eliminate problematic trends over time.

Name one AI/automation that shipped recently and its impact on your team or the business.

We recently developed a suite of internal tools and AI-agent-focused documentation to help transition our teams toward AI-first development. The shift has required rethinking how we work and we’re increasingly acting as orchestrators of these tools while remaining accountable for outcomes.

The result has been measurable gains in developer productivity and faster iteration on internal tooling, allowing teams to spend more time on higher-impact engineering problems.