Architecture & system design
Boundaries your team can explain in a stand-up — so “one more feature” doesn’t quietly become a six-month rewrite.
Loading…
Java · Spring · Cloud · Senegal & worldwide
Launch week is only the beginning. I partner with product and engineering teams on Java and cloud-native systems — from architecture through production — so roadmap pressure doesn’t undo what already works.
Dakar, Senegal — on-site or hybrid locally; remote or hybrid internationally. Overlap-friendly across Francophone Africa, Europe, and US time zones when it matters.
Intro call → written scope, risks & constraints → proposal or kickoff. Clear steps, no endless email tennis.
Go to contact — email, CV, and full booking options.
Teams that needed shipping in production — not another roadmap deck
Partner brands: BOA Group, ENG Technologie, Mafalia, SarayaTech Senegal.
What I bring to consulting and long-term collaboration: clear ownership, delivery you can plan around, and fewer surprises when load or regulation tighten the screws.
Boundaries your team can explain in a stand-up — so “one more feature” doesn’t quietly become a six-month rewrite.
Multi-tenant reality: integrations, billing, and ops you’ll still recognize after the next funding round.
Money, latency, audits — the flows where “we’ll patch it later” isn’t an option. Built deliberately, not improvised.
Tests, CI/CD, and signals you can trust — so Friday deploys are boring for the right reasons.
From vague brief to something running in production — with only the process your risk level actually needs.
Who decides, what’s non-negotiable, what “good” means — before we pick a framework logo.
Boundaries, interfaces, and a plausible next year so your team isn’t hostage to my first diagram.
Tests, CI, and alerts aligned with how you’ll really run it — not how the demo looked.
Measure and fix where users and revenue hurt — not where the Grafana chart is prettiest.
Operating model
Architecture is a product: written decisions when they reduce risk, measurable outcomes, and room for your team to own the system — consulting should leave you stronger, not dependent.
References you can verify — public names when NDAs allow. Each card mirrors a type of engagement: similar constraints, delivery pressure, and outcomes you can discuss before we scope yours.
What if stock, sales, and the messy day-to-day lived in one product instead of five tabs and a spreadsheet? SaaS for retail SMEs — built to retire the accidental tool stack.
Merchants productive in days, not quarters — onboarding that sidesteps the “big bang” IT programme while still caring about traceability.
Who owns the gym’s truth — the front desk laptop or the member’s phone? Staff on the web, members on mobile; the product is still baking, but the story is already public.
One spine for operations, members, and multi-site expansion — fewer handoffs, fewer “we’ll fix it in the next tool”.
Greenfield B2B: tenants, roles, usage-based billing — and a domain you can split before the merge queue becomes your roadmap. The interesting question is how modular the first cut is.
~40% faster feature cadence once boundaries landed — releases that didn’t need a committee merge every time.
Planning a build, refactor, or scale-up?
Share the goal and hard constraints — I’ll outline options, risks, and a realistic first step so you can decide on fit before any formal commitment.
Banking, fintech, high-traffic products — contexts where releases, compliance, and incidents all show up in the same week. Java/Spring, Angular, React.
What you get in a collaboration
Hands-on experience on regulated stacks, mobile-money integrations, and real delivery pipelines — so our work together starts from practice, not theory. Useful when you need judgment under pressure, not another generic blueprint.
BANK OF AFRICA — BOA Services International
Feb 2025 — Present
Almadies, Dakar, Senegal
ENG Technologie Group
Oct 2023 — Feb 2025
Dakar-Plateau, Senegal
Mafalia — Ecom & Fintech apps
Nov 2023 — Nov 2024
Dakar Region, Senegal
SarayaTech Senegal
Dec 2022 — Feb 2023
Senegal
Tools and practices I use in advisory and delivery — chosen for outcomes your team can measure, not for buzzwords.
Product intent only matters if the software can still move a year later — explicit trade-offs, boundaries your team can name, and architectures that don’t calcify on day one.
Beyond code, I contribute to architecture decisions, system design, junior engineers mentoring and engineering practicesthat keep delivery calm when complexity and traffic grow.
Strong Java & Spring background, modern cloud-native stacks, and JavaScript frameworks when the product needs them — for SaaS, enterprise platforms, mobile applications and web applications.
Focus: FinTech, SaaS, e-commerce, digital platforms, and large-scale enterprise. Based in Dakar — engagements in Senegal and internationally. Formats: architecture advisory, embedded delivery with your team, or phased work — scoped to your risk, budget, and timeline. Async-first with clear written specs; live overlap when decisions need it.
Software Engineer
From intent to shipped software
4+
Years
20+
Systems
∞
Curiosity
Notes on trade-offs, failure modes, and delivery — background reading if you’re evaluating a collaboration or a technical direction.
Use them as a lens — then we can test them against your real constraints in a conversation.
Get in touchSenegal or international: product, constraints, timeline. You’ll get a direct answer — whether there’s a fit, a concrete next step for an engagement, or an honest no so neither side wastes time.
What happens next
I usually acknowledge messages within two business days (often faster).