Loading
Move money correctly, every time, under the regulator's eye.
Fintech engineers build the systems that move money — payment rails, mobile wallets, lending platforms, and the ledgers that record every cent. The job exists at the intersection of distributed systems, financial regulation, and adversarial security: a single off-by-one in a ledger is a refund storm; a missed KYC check is a regulator fine. The role is large and growing in mobile-money markets (M-Pesa, MTN MoMo in Africa) and Latin American neobanks (Nubank, Mercado Pago), where billions of users transact daily through APIs that didn't exist a decade ago. SFIA 9 maps this cluster across BURM (business risk management), DESN (systems design), and SCTY (information security).
“You start the morning triaging an overnight reconciliation break — a card processor's webhook missed a refund event, and the ledger now disagrees with the acquirer's report by $1,432. You write a replay script, fix the drift, and add a guardrail. After standup, you scope a KYC pipeline upgrade so the compliance team can onboard SMEs in three more countries. Afternoon is split between reviewing a teammate's idempotency change to the payouts API, debugging why a fraud model is flagging legitimate Nigerian transactions, and writing the RFC for migrating internal messages to ISO 20022.”
11 required
18 required
26 required
When you complete this track, you'll have built:
PCI Security Standards Council
Security standard for any system that stores, processes, or transmits cardholder data.
ISO / SWIFT
Global messaging standard for financial transactions — payments, securities, FX, trade.
Financial Action Task Force
International standard for anti-money-laundering (AML) and counter-terrorist-financing controls.
European Banking Authority
EU regulatory framework for payment services, strong customer authentication, and open APIs.
Roles you can grow into from here.