Enterprise Integration Engineer

About the role

The Enterprise Integrations Engineer delivers the technical onboarding of Enterprise merchants: payment service providers, remittance companies and global brands. These are custom integrations, usually built directly on Flutterwave's APIs.

You are the merchant's technical lead from the kick-off call until their payments are stable. You own well-scoped projects yourself and work with a Senior Integration Engineer on the most complex ones. You work with Sales, Product, Engineering and Compliance to scope, test and launch each integration.

Compared with SMB integrations, you handle fewer merchants, but each one is larger, more custom and carries more risk. The role sits between Sales and Engineering and is a step on Flutterwave's Integrations career path.

Responsibilities

1. Get merchants live

• Run each integration from start to finish and own the technical side of merchant onboarding, aiming to shorten the time from contract signed to first live transaction (team target: a median of 24 days).

• Scope the work: run technical kick-off calls, check what the merchant wants against what Flutterwave's products can do, and recommend the right setup (for example a direct API integration or hosted checkout) based on the market's rules and customers' needs.

• Test before production in the test environment before live keys are issued. This includes 3DS card payments, mobile money payments (phone prompts and redirects), signature-checked webhooks that can safely arrive twice, and payments that stay pending before a final status.

• Clear go-live checks: build and testing start when the contract is signed. Only live keys wait for business verification (Know Your Business, KYB) and a daily system check that account setup and fees match the signed deal. Fix any differences posted to the Jira ticket.

• Keep the record in Jira: note what you did, the next step and any blocker, and show who must act next. Talk with merchants on Slack or email.

2. Solve technical problems

• Explain the APIs: guide merchant developers on Flutterwave's REST APIs, including card tokenisation, recurring payments and split payments.

• Find the cause of failures: read API requests and responses and check logs in internal log tools and Datadog. Separate merchant-side errors from platform problems, with evidence.

• Keep merchants secure: make sure merchants confirm each payment with a server-to-server call to the API, and do not rely on the browser redirect alone.

3. Work across teams and improve how we work

• Raise and log blockers in Jira with the person who must act. Escalations are handled by the system on a set timetable.

• Support live incidents: give Customer Reliability Engineering the evidence for P1–P4 incidents on live merchants.

• Improve payment success: track success rates for each payment rail your merchants use, and work with the Global Expansion and Payment Partnerships team on problems caused by payment partners.

• Hand over cleanly: own the merchant until the system marks them stable, then hand over to their Technical Account Manager with a complete Jira record.

• Report gaps in documentation to the Developer Experience team.

How success is measured

• Merchants live and transacting (most important): measured from first live transaction in payment records.

• Time to live: days from contract signed to first live transaction, a shared team result. Days waiting on the merchant, Sales or Product do not count against you.

• Payment success rate: share of payment value that succeeds for your merchants in their first weeks live, counting only integration-caused failures.

• Clear ticket notes: every ticket shows what happened, the next step and any blocker.

Required competencies

• A minimum of a bachelor's degree from an accredited university.

• 4–9 years' relevant experience in integration engineering, implementation engineering or similar.

• Able to read and debug REST API requests and responses in JSON, use Postman to send test requests and find errors, and read code in JavaScript, Python or PHP.

• Able to run several high-value projects at once, keep to timelines and hold people to commitments, using Jira or a similar tool.

• Writes and speaks clearly, and can explain a complex technical limit to a non-technical person, including senior leaders at a merchant.