Airwallex is the AI-native financial operating system for a real-time, intelligent economy. More than 675,000 businesses, including McLaren Racing, Qantas, SHEIN, and TikTok, use us, directly or through our platform partners, to run their financial operations or build and monetize financial products of their own.
We started in Melbourne in 2015 to build the infrastructure global commerce runs on. We're the regulated backbone behind global payments: not by accident, but by design. A decade plus, 85+ licenses, and a financial infrastructure spanning North America, Europe, the Middle East, and Asia-Pacific.
We're co-headquartered in San Francisco and Singapore, with more than 2,300 people across 27 offices. We hire builders with founder-level energy, people who move fast with good judgment, dig in with real curiosity, and make calls from first principles rather than waiting to be told what to do. Read our operating principles to see it in full.
As an Engineering Lead, Scale, you’ll lead a team building critical platform capabilities for Airwallex’s embedded finance products. You’ll manage engineers directly and be accountable for team health, execution, and long-term technical quality, while staying technically credible and involved at an architectural level.
You’ll work from our London office three days a week.
The Scale team builds the infrastructure that lets platforms embed Airwallex financial products at speed and with confidence. The team owns multi-tenant systems powering companies like Brex, Rippling, Navan, Qantas, and SHEIN. The engineering challenges are real: balancing tenant isolation with resource efficiency, low-latency performance with cross-data-center resilience, and immediate customer needs with long-term architectural extensibility. Beyond infrastructure, the team owns cross-domain product features and designs enterprise integrations by translating customer business requirements into scalable technical solutions.
You'll thrive here if: * You’re comfortable owning the roadmap yourself. * You’re comfortable with ambiguity. Give you a problem, not a prescription, and you’ll run with it. * You own the outcome and you don’t wait for permission to fix what’s broken. * You connect dots across functions and hold the big picture without losing grip on the details. * You simplify complexity rather than hiding behind it.