Integration Engineer

About the role

You will connect systems that were never designed to talk to each other: a core banking platform, an ERP, eight clinical systems, a warehouse management system twenty years old. The constraint is usually organisational as much as technical.

We start with data contracts and event boundaries rather than with connectors, and you will help hold that discipline.

About OneCluster

OneCluster is a product and engineering company that embeds inside regulated institutions across Africa: banks, telcos, health systems, logistics operators and energy companies. We were founded in 2026 by practitioners who spent their careers inside those organisations.

We work embedded in our customers’ own teams rather than alongside them. That means their repository, their CI, their on-call rotation, and their constraints: regulatory scrutiny, legacy integration, and a business that cannot absorb a bad release. Every piece of work has a partner on it, in the standup rather than on the proposal.

The measure of our work is that the customer keeps running the practice after we leave. That shapes how we hire: we look for people who can raise the standard of the team around them, not only ship their own work.

The team you join

You will work between systems and between organisations, often with vendors and third parties who have their own priorities.

What you will do

• Design event-driven integration between legacy and modern systems.
• Define API and data contracts, and the governance that keeps them stable.
• Build and operate the integration layer, including its failure handling and replay.
• Work with vendor teams and client architects to agree boundaries.
• Document decisions so the client can extend the pattern without us.

Minimum qualifications

• Five or more years in integration or backend engineering.
• Deep experience with messaging and event streaming platforms.
• Practical knowledge of API design, versioning and contract testing.
• Patience for vendor documentation and protocols that predate you.
• Ability to negotiate technical boundaries across organisations.

Preferred qualifications

• Experience with core banking, FHIR, ISO 20022 or telco OSS/BSS.
• Background in platform or reliability engineering.
• Exposure to zero-trust or regulated network environments.

Your first three months

1. Get one integration into production in your first month.
2. Document the contracts that exist only in someone's head.
3. Own the reliability of a set of interfaces by month two.
4. By month three, be the person consulted before a new integration is agreed.

Compensation and benefits

Rates are agreed per engagement and depend on scope and seniority. We discuss numbers openly on the first call, before you spend time on a practical.

• Rates are agreed per engagement and discussed openly on the first call, before you spend time on a practical.
• Remote across Africa, with on-site weeks where the engagement calls for them.
• Work embedded inside regulated institutions, on systems with real consequences, alongside senior engineers who review your work and expect you to review theirs.
• Small crews and direct access to partners, with no layers between you and the decisions.
• Long relationships. We would rather work with the same capable people across engagements than hire for a single project.
• Straight answers. We tell you what we can and cannot offer before you commit, and we do not promise what we cannot deliver.

How we interview

The whole process is normally two to three weeks, and we work around your current job.

1. Application review. A partner reads every application. You hear back either way, usually within two working days.
2. Intro call, 45 minutes. Your background, what you want next, and honest answers about the work, the rate and the constraints.
3. Practical session, 2 hours. A realistic problem close to what the role actually involves, scheduled around you and sized to respect your time. We tell you the shape it takes when we book it.
4. Practical review, 60 minutes. We walk through what you built, why, and what you would change with more time.
5. Partner conversation, 45 minutes. Scope, expectations, terms, and your questions.
6. Decision, normally within two working days of the last conversation.

How to apply

Send an application through the form. A partner reads every one, and you will hear back either way. If you are unsure whether you qualify, apply anyway and say what you are unsure about.

We will tell you what we can and cannot offer before you commit to anything.

Apply for this role →