Zhuzh Finance
[Client]
Zhuzh Finance
[Year]
2026
[Project Focus]
- Design secure account and transaction workflows for a fintech product.
- Build backend infrastructure that stays correct as volume and complexity rise.
Scroll to explore
[Overview]
Zhuzh Finance is an independent product. The engineering brief is financial workflows that remain correct as volume and complexity rise.
[What I did]
- Designed backend architecture for secure transaction and account workflows
- Implemented API services focused on reliability, observability, and maintainability
- Led product and technical decisions across engineering and delivery execution
[The role]
Backend Engineer and Co-Founder
Njay
Project Info
Zhuzh Finance is a fintech product I co-founded. The work is the account and transaction layer that must remain correct as volume rises and the product operates as a financial service.
I own backend architecture: how accounts are opened, how funds move, how those movements are recorded, and how the services around them can be observed when something looks wrong. That layer has to be predictable, inspectable, and resistant to corruption.
Overview
2026
Zhuzh Finance is a fintech product I co-founded. The work is the account and transaction layer that must remain correct as volume rises and the product operates as a financial service.
I own backend architecture: how accounts are opened, how funds move, how those movements are recorded, and how the services around them can be observed when something looks wrong. That layer has to be predictable, inspectable, and resistant to corruption.
The Process
We started from the models, not the screens. Account state, transaction intent, and settlement status were designed so a later feature could not introduce a second meaning for “paid.” GraphQL and REST services sit on those models with the same language operators use when they investigate a case.
Reliability and observability were part of the first services, not a later cleanup. Logging, deployment shape, and failure paths were treated as product requirements. A financial workflow that cannot be explained after the fact is incomplete.
As co-founder I also held the product decisions that keep engineering disciplined: what must be true on day one, what can wait, and which shortcuts would cost more than they save once real money is in the system.
The Outcome
Zhuzh has a backend foundation for secure accounts and transaction orchestration — services designed to be operated and extended, not replaced when the first serious load arrives.
The architecture remains inspectable as the product grows. That is the requirement of a fintech backend: correctness that can still be reasoned about months later.