Technical Debt: Design, risk and beyond
We talk to experienced architects and technology leaders about the architectural choices they’ve made — the good, the bad, and the costly. From scaling systems to integrating legacy platforms, from misaligned domains to governance gaps, we discuss how architecture impacts technical debt.
You’ll hear honest stories of architectural missteps, what teams learned from them, and how they built systems designed not just to work, but to last.
Technical Debt: Design, risk and beyond
Technical debt under real constraints: fintech leadership in emerging markets with Erioluwa Asiru
Use Left/Right to seek, Home/End to jump to start or end. Hold shift to jump forward or backward.
In this episode of Technical Debt: Design, Risk and Beyond, Maxim Silaev speaks with Erioluwa Asiru, CTO at CircleFunds, about what technical debt really looks like inside a fast-growing fintech operating in an emerging market.
CircleFunds is digitising traditional thrift savings in Nigeria: a problem that turns out to be far more complex than “building an app.” Erioluwa shares how early architectural decisions were shaped by human behavior, cultural practices, and the reality that some processes are initially "technically impossible" to digitise without breaking trust.
The conversation explores how technical debt rarely appears in one place. Instead, it emerges as a blend of architectural shortcuts, shifting product logic, regulatory pressure, and team dynamics in an environment that changes faster than most systems can adapt. Erioluwa explains the early warning signs, such as constant firefighting, repeated fixes, and system instability, that signal debt accumulation long before failure is visible from the outside.
We also dive into leadership tradeoffs: how to balance speed with system health, how to ask engineers for compromises without losing trust, and why many long-term technical problems are rooted in product and leadership decisions rather than code. Erioluwa shares her perspective on intentional debt, architectural simplicity, documentation as a first-class artifact, and why infrastructure debt is the one category she would never knowingly accept.
The episode closes with a practical discussion on AI in fintech engineering: where it accelerates delivery, where it becomes dangerous, and why critical financial systems still demand human judgment, strong standards, and rigorous testing.
This conversation is a grounded look at technical debt as a leadership and risk problem, shaped by pressure, ambiguity, and real-world constraints.
Reach us @ LinkedIn:
https://www.linkedin.com/in/maxim-silaev
https://www.linkedin.com/in/dr-nikita-golovko
