Open to remote opportunities

Ayodeji Idowu / Software Engineer & Technical Lead

I build the systems behind
modern financial products.

Eight years building fintech, banking, FX, payments, and AI-assisted workflows across Africa and global markets. I lead architecture, execution, and engineering quality where trust, money, and scale are on the line.

FIG.00 — SYSTEM IN MOTIONproduct · money · compliance · ai · scale
8+ YEARSFINTECH & BANKING SYSTEMSFLUTTERWAVEGUARANTY TRUSTBAZARA TECHSKALETEKFX PLATFORMSCORE BANKINGMERCHANT PAYMENTSAI-ASSISTED WORKFLOWS
01 About

Not just a coder. A product engineer who can own the hard parts.

I build software that has to work when trust, money, and scale are involved. Over the last eight years I have worked across banking, payments, FX, merchant tools, onboarding, internal platforms, and AI-assisted workflows.

My strength is turning complex systems into products that are clear, reliable, and useful. I bring engineering depth, product judgment, execution discipline, and design taste to the same table, and I lead teams that ship.

8+
years building systems
5
serious product environments
3
leadership roles
02 What I bring

Range across the things that make a product real.

01

Product Engineering

I think beyond screens: flows, edge cases, data, operations, and whether the product actually works in the real world.

02

Fintech & Banking Systems

Payments, FX, KYC, onboarding, merchant tools, and core banking workflows built for regulated environments.

03

Technical Leadership

I shape architecture, set quality standards, mentor engineers, and keep delivery moving with clarity.

04

Frontend Architecture

Micro-frontends, design systems, and interfaces that stay fast and maintainable as they scale.

05

Backend & API Thinking

I design across the boundary: data models, API contracts, and the workflows behind the interface.

06

AI-assisted Workflows

Practical AI inside products: triage, recommendations, and automation that earn their place.

03 Selected systems

Work where trust, money, and scale were on the line.

My role

Frontend architecture lead

Problem

Loan, credit, and trade finance workflows are dense, regulated, and unforgiving. The interfaces had to stay clear under real operational pressure.

What I owned

Frontend architecture for the Loan Credit Factory, Loan Management, and Trade Finance modules, plus the shared UI system and delivery standards across teams.

Why it mattered

Institutions need software they can trust with credit decisions and trade finance. Clarity and reliability here are the product.

ReactTypeScriptSingle-SPAMicro-frontends
My role

Frontend engineering lead

Problem

Cross-border FX is sensitive: rates move, compliance is strict, and people need to feel safe at the exact moment of exchange.

What I owned

End-to-end frontend engineering for a secure, compliant exchange experience, built in partnership with Kadavra BDC and Wema Bank.

Why it mattered

Users trust the product with real money across borders. The experience had to be fast, clear, and verifiably safe.

Nuxt.jsVue.jsTypeScript
My role

Software engineering lead

Problem

High-volume merchants need to onboard fast, pass KYC, and operate across currencies without friction or fraud exposure.

What I owned

Merchant onboarding, account management, and multi-country KYC and AML flows, alongside payments, transfers, and invoicing surfaces.

Why it mattered

Serving high-volume commerce means every flow has to hold up under load and under scrutiny.

Nuxt.jsVue.jsTypeScript
My role

Frontend architecture lead

Problem

Operations teams drown in duplicate tickets and slow triage, and the context they need lives in too many places.

What I owned

The frontend system and UI architecture, with AI-assisted triage, duplicate detection, and contextual recommendations.

Why it mattered

Faster, better-informed resolution is the difference between a calm operation and a growing backlog.

Next.jsReactTypeScript
My role

Builder, solo

Problem

Candidates need structured, repeatable practice with a clear sense of where they stand.

What I owned

The full product: a large question pool, quizzes, attempt tracking, and a topic-based performance dashboard.

Why it mattered

Learning sticks when practice is structured and progress is visible.

Next.jsPrismaNextAuth
View on GitHub
04 Experience

A leadership track across serious product environments.

2024 → Now
Bazara Tech
Frontend Engineering Lead
ArchitectureDeliveryMentorship
  • Lead engineering delivery for SeaBaas core banking, owning architecture for the Loan Credit Factory, Loan Management, and Trade Finance modules.
  • Shape the shared UI system and quality standards used across financial-institution clients.
  • Direct architecture and delivery for Manovar, including its AI-assisted service operations workflows.
  • Mentor engineers and partner closely with product and design on regulated, high-stakes flows.
2021 → 2025
Flutterwave
Software Engineering Lead
LeadershipFX & paymentsRegulated flows
  • Owned product architecture and delivery for Swap, a licensed multi-currency exchange for cross-border FX.
  • Led the Whitelabel engineering team building customizable fintech infrastructure for enterprise partners.
  • Built merchant onboarding and multi-country KYC and AML flows for Flutterwave for Business, reducing fraud exposure.
  • Set quality standards and delivery timelines across teams, and grew engineers into stronger operators.
2017 → 2021
Guaranty Trust
Software Engineer
BankingAutomationReliability
  • Built web applications and business-process automation for one of Africa's largest banks.
  • Delivered internal tools and customer-facing platforms, progressing from trainee to software engineer.
  • Learned to ship inside a regulated banking environment where reliability is non-negotiable.
05 Operating principles

How I work when the stakes are real.

01

Build for trust

If people hand you their money, the product earns that trust in every detail.

02

Make complexity feel simple

The system can be intricate. The experience should never feel that way.

03

Move fast without being careless

Speed and quality stop being a trade-off once the fundamentals are right.

04

Design systems that scale

Build the second version into the first, so growth does not mean a rewrite.

05

Lead with clarity

Teams move faster when the goal, the constraints, and the standard are obvious.

06

Ship with taste

Knowing what to build, and what to leave out, is part of the craft.

07

Think in products, not tickets

A closed ticket is not the goal. A product that works is.

06 Tools I use to ship
Languages
JavaScriptTypeScriptPHPSQL
Frontend
ReactNext.jsVueNuxtTailwind CSSSCSS
Backend & APIs
Node.jsExpressNestJS
Data
PostgreSQLMongoDB
Cloud & delivery
AWSVercelFirebaseDockerCI/CD
Quality
TestingPerformanceAccessibilityCode review
Architecture
Micro-frontendsDesign systemsScalable architecture
AI
AI-assisted workflowsProduct automationRecommendations
Available now

Need someone who can build, lead, and ship?

I am open to remote roles, consulting, collaborations, and ambitious product conversations.