Capi is building the financial infrastructure for emerging markets trade.

Backed by $18M+ from top-tier investors like Creandum, Y Combinator, General Catalyst, and angels from Revolut, Checkout, Stripe, and Remitly, we’re building the financial infrastructure that emerging markets deserve.

Our mission is to grow GDP in emerging markets by making the global financial system fairer and more accessible. We’re tackling global trade, making it easier for importers to pay their international suppliers. Our platform enables businesses to expand rapidly, create jobs, and be engines of prosperity for their countries.

Our team is made up of approx 100 people across 10 countries; we are a group of a highly-ambitious, get-it-done people, who like to work hard on something that has a tangible impact in the world. And we’re looking for more people to join our team!

Take a look through Capi’s mission & values.

Role Overview

You'll join a small, high-performing team of engineers and product leaders shaping how we scale our platform and our impact.

From your first day, you will have the opportunity to work closely with the founding team based across London & Paris to shape the product vision and all parts of our technical architecture. As we scale our products and deepen our presence across emerging markets, this is a role that builds technology to solve customer problems.

To do that, you must have empathy and curiosity to get to the root cause of the issue and the creativity to build a solution that balances impact, effort, and delight.

Key Responsibilities

Leadership Excellence

Lead by technical example — your influence comes from the quality of your work, your judgment and your ability to bring others along with you, not from authority.

Own technical direction within your team and workstream, collaborating closely with principal engineers and the Head of Engineering to align with broader architectural strategy.

Mentor senior engineers through pairing, code reviews and design discussions — raising the technical floor of the people around you.

Champion engineering best practices across the team, introducing standards and patterns that improve consistency, reliability and developer experience.

Act as a subject matter expert in your core technical domain, and be the person others turn to when the problem is hard.

Delivery Excellence

Lead the end-to-end delivery of complex, multi-stakeholder projects — from scoping and design through to deployment, feedback and iteration.

Translate ambiguous problem spaces into clear technical plans, breaking down large initiatives into well-defined milestones that the team can execute against.

Manage delivery dependencies across teams and communicate progress clearly to both technical and non-technical stakeholders.

Drive a culture of outcome-oriented delivery within your workstream — focused on impact shipped, not activity completed.

Proactively identify and remove blockers before they slow the team down.

Operational Excellence

Take ownership of the reliability and observability of systems within your domain — ensuring they are monitored, well-understood and resilient to failure.

Handle production incidents with confidence, leading postmortems that result in genuine process improvements rather than just documentation.

Set the standard for what good operational practice looks like within your team — monitoring, alerting, runbooks and on-call hygiene.

Contribute to company-wide reliability initiatives led by principal engineers and the Head of Engineering.

Technical Excellence

Make and defend strong architectural decisions within your workstream, balancing pragmatism with long-term technical health.

Write production-quality code consistently — this is a fully IC role and hands-on technical contribution is expected at all times.

Drive scalability, modularity and performance improvements in the areas of the codebase you own.

Champion code quality through rigorous testing, thoughtful documentation and constructive code reviews that develop the engineers around you.

Proactively identify technical debt and lead initiatives to address it before it compounds.

Culture Communicate internally and externally about new features, be it collecting feedback pre-implementation or explaining them on launch.