Loading…
Senior Software Engineer — backend, distributed systems, APIs, and architecture. Mainly Java and Spring Boot. I start from the problem, make trade-offs explicit, and ship systems that stay reliable.
Track record across enterprise platforms, banking, and FinTech — including Bank of Africa Group (via Synapse) and ENG Technologie.
Trusted where reliability matters
Employers
Employers: Synapse Groupe, ENG Technologie, Mafalia, SarayaTech Senegal.
Delivery for Bank of Africa Group platforms via Synapse — not a commercial partnership.
Start here
Experience, case studies, and About — then the CV.
See shipped systems, ways to work, then book a short call.
Selected work
Live products and production systems — problem, architecture, and what had to be correct.
Live
10+ Merchants live
African retailers ran day-to-day operations on notebooks, spreadsheets, and improvised tills — cash errors, blind stock, forgotten customer credits, and end-of-day totals rebuilt by hand.
Outcome — 10+ merchants live across Senegal and West Africa; hours saved weekly on closing; Wave & Orange Money on every sale with accountant-ready exports.
Lab · P0–P2 shipped
0 Double capture on timeout
Happy-path payment APIs are easy. The hard cases start when a PSP times out (captured or not?), the client retries after an HTTP timeout, a webhook arrives three times, a Kafka consumer dies while events pile up, or a deploy breaks 20% of traffic — perceived availability and financial correctness diverge.
Outcome — P0–P2 delivered: Compose stack, payment-service with idempotency and outbox, dual PSP + safe failover vs IN_RECONCILIATION, SRE control center. Disaster scenarios D1–D10 documented.
Reference · Modular monolith
Append-only Journal
Wallet and payment products need auditable money movement — balanced journals, safe retries, provider webhooks, and ops controls. A balances table plus ad-hoc updates fails compliance, idempotency, and reconciliation under load.
Outcome — Runnable Compose stack with seeded roles, live demo UI (transfer, merchant pay, withdraw, journal expand, trial balance, approvals), Swagger, Prometheus, and Grafana — reference platform for wallet and ledger delivery.
Experience
Consultant Backend Engineer — Banking Systems
Client: Bank of Africa — Groupe Bank of Africa
Drove backend modernization of enterprise banking platforms — Java / Spring Boot, multi-tenancy, clean architecture — serving 11+ Bank of Africa Group subsidiaries.
Software Engineer — FinTech & Payments
Owned backend microservices for digital lending, customer onboarding, and payment workflows on a FinTech platform.
Software Engineer — SaaS Platform
Built backend services and REST APIs supporting inventory management, order processing, sales, and financial workflows for a SaaS platform helping SMEs manage operations.
Ways to work
Every path starts the same: a short discovery call, then a written proposal with scope, milestones, and ownership.
01
Founders and product teams that need a reliable backend without hiring a full platform squad yet.
From fuzzy idea to a system you can demo, operate, and hand off — with explicit trade-offs along the way.
See Ecom 360 case studyBest when: Scope is unclear, stakes are rising, and you need the shortest path to a launchable design.
Lock goals, risks, integrations, and architecture before you burn budget on the wrong build.
Best when: You know what to ship and need a named senior engineer to own delivery through production.
End-to-end delivery of APIs, workflows, or integrations — milestones, tests, and runbooks included.
Best when: You need a fundable, demo-ready product on real integrations — built to extend, not throw away.
Core domain APIs and critical flows shaped for launch, security baseline, and the next iteration.
02
Banks, fintechs, and platform teams modernizing under constraints — or adding senior backend depth.
Ownership where correctness and reliability are non-negotiable — regulated contexts, clear governance, lasting architecture.
Best when: Before a big bet — you want ranked risks, reference designs, and a plan your team can execute.
Independent look at a backend, API, or integration surface before you commit to build or migrate.
Best when: Legacy or fragmented systems need a phased move to something operable, observable, and partner-ready.
Migration waves, partner API contracts, and resilience work with enterprise-grade delivery discipline.
Best when: Your squad needs senior capacity inside the team — roadmap delivery, quality bar, production ownership.
A named Senior Software Engineer embedded in your ceremonies and tools through release and stabilization.
Not sure which fits? Start with discovery — I will recommend the right engagement.
Insights
Backends, distributed systems, and architecture.
Thursday 16:47. A merchant payout. The client timed out, then fired again. Then again. Ninety seconds from paying the same person three times.
Friday, the app said Paid. Monday, 15,000 XOF was missing. The callback was named SUCCESS. That was the whole problem.
Most payment bugs are vocabulary bugs. Accepted is not confirmed. Confirmed is not settled. The three-state model this blog starts from — and why your boolean is lying to finance.
FAQ
With a short discovery call. You get a written proposal covering scope, milestones, effort range, and a recommended way of working — no vague retainers.
Yes. Delivery is remote worldwide from Dakar, with async-friendly rituals and overlap that fits your timezone for critical workshops.
Product teams usually start with an Architecture sprint, Scoped build, or MVP acceleration. Banks and platform teams lean toward Architecture review, Platform modernization, or a Contract embed.
Yes. Experience includes Synapse delivery for Bank of Africa Group platforms, payment integrations, audit-friendly trails, and production ownership where compliance and reliability matter.
I do. You work with a named Senior Software Engineer — not a rotating bench. Scope, architecture, and delivery stay with me through production-ready ownership.
Download the CV, review Experience and case studies, then book a short call or send a brief. I reply within two business days.
Contact
Hiring or a project — share context, and I reply with a clear next step.
01
Say whether you are hiring or scoping a project.
02
I reply within two business days with questions — or a written proposal.
03
Next step is explicit: CV and hiring path, or a scoped engagement.
