SECURITY / SAASLive · Independent product
DealForte
Secure document sharing with granular access, verification, revocation and engagement visibility.
SENIOR SOFTWARE ENGINEER / LAGOS, NIGERIA
Backend systems for finance, AI & secure SaaS.
I'm Muhammed, a Python-first software engineer building financial data platforms, real-time AI and secure SaaS. I own the work from architecture and APIs to integrations and deployment.
Python-first · Secure by design · End-to-end ownership✳ Python-first · Architecture-minded · End-to-end ownership
SELECTED BUILDS2021 — NOW ●
Financial data/Conversational AI/Secure SaaS
06+Years building
software systems
software systems
1,000Concurrent conversations in conversational-engine load tests
<70msDataBrew API response time in load tests
MY PHILOSOPHY / 001
Make it correct.
Make it resilient.
Make it useful.
Performance figures are load-test results, not production guarantees. Results depend on workload and test conditions.
01 / SELECTED WORKA LOOK UNDER THE HOOD ↓
The work speaks.
Real products, hard engineering problems, and the decisions behind them. Select a project to explore my contribution.
SECURITY / SAASBUSINESS INTELLIGENCE / ANALYTICSLive · Business intelligence suite
Leveler ↗
Led Leveler’s backend architecture and technical direction, making the key design decisions and building the services and APIs behind its intelligence products.
DATA INGESTION / INTEGRATIONLive · Part of Leveler
DataBrew
Bringing fragmented Nigerian market, government and financial data into reliable, consistent datasets.
REAL-TIME AI / VOICEIn alpha testing
Murya
A multi-tenant AI voice platform for inbound assistants and outbound campaigns, designed to work with documents and contact lists before integrations.
FINTECH / PAYMENTSPayments backend
Cudify
A multi-currency wallet and payments backend, shown alongside its public product site.
IDENTITY / AUTHORIZATIONOpen source
Hexalgon IAM
Multi-tenant identity and authorization with fine-grained permissions and Bloom-filter-accelerated token revocation.
↗ Want to see how a system works? The case studies unpack architecture decisions, not just screenshots.
02 / THE ENGINEERINGBEYOND THE INTERFACE ↓
The things I build for.
Technology changes. The engineering fundamentals don't: predictable behavior, clean boundaries, clear failure modes and software that people can rely on.
01 /
Backend architecture
Service boundaries, API contracts, data models and systems designed to evolve without becoming fragile.
02 /
Real-time & async systems
Low-latency processing, message queues, concurrency and integrations where timing and reliability matter.
03 /
Financial & data systems
Ingestion, reconciliation, transactional integrity, and clean APIs over complex upstream data.
04 /
Security by design
Tenant isolation, authentication, authorization, auditable events and revocable access.
TOOLS OF THE TRADE
03 / THE PATHWHERE I'VE BUILT ↓
Experience built by doing.
From operational systems to financial data platforms and AI infrastructure, my work has centered on shipping useful software and owning the engineering behind it.
Full résuméMango Zest Labs
2024 — PRESENTBackend Systems Engineer
Designed the conversational AI and telephony backend powering virtual call-center capabilities. Built asynchronous orchestration and separated latency-sensitive call flows from queued work.
Full-time Jun–Dec 2024 · Part-time Jan 2025–presentData Quotient
2025 — 2026Lead Backend Engineer
Led backend architecture and key technical decisions for Leveler, building the services and APIs across its intelligence suite. Also led DataBrew’s data pipelines and developer-facing APIs.
Part-time · Jan 2025–Feb 2026Fagmaz Hydra Ventures
2021 — 2024Backend Developer
Built inventory and operational tools with Flask, MySQL and Django, replacing manual reporting and stock-tracking workflows.
Jan 2021–May 202404 / ABOUT ME
Curious about the hard parts.
I'm a Lagos-based software engineer with six years of experience working across backend systems, data products, financial software and applied AI.
I like the problems that aren't obvious in a screenshot: race conditions, inconsistent data, authorization boundaries, operational reliability, and making a complex product feel simple to use.
I've worked across teams and built independent products from the ground up. What connects them is a willingness to own the problem, not just the ticket.
05 / WHAT'S NEXTHAVE A PROBLEM WORTH SOLVING?
Let's build something worth relying on.
muhammedyusufoa@gmail.com ↗
Open to thoughtful conversations about backend engineering, architecture, real-time systems and ambitious products.