Distributed backend
Designed and evolved .NET services around payments, disputes, Kafka integrations, PostgreSQL and production-grade operational constraints.
1M+ workflows / year Open to product engineering roles
Fullstack engineer.
Platform mindset.
Built for production.
I build backend platforms, internal tools and distributed systems for fintech products — the kind of software that survives traffic, legacy, deadlines and people asking “can we ship it yesterday?”.
Impact
Not just coding tickets.
Moving systems.
A compact version of my engineering story: legacy into modern stack, integrations into Kafka, UI abstractions into platform pieces.
Platform refactoring
Worked on shared table/list architecture, reducing duplicated logic and preparing frontend/backend components for cleaner scaling.
less backend noiseTech leadership
Led engineering initiatives, interviews, releases, documentation and team practices without turning the process into corporate soup.
lead + hands-onSelected work
Production stories
with receipts.
The focus is not on “I participated”. The focus is on what changed after the work landed.
Dispute+
National payment dispute platform
Fintech platform for dispute management, integrations and internal workflows. Built in the real world: legacy, migrations, deadlines, compliance and production traffic included.
- Moved integrations away from direct database coupling toward Kafka messaging.
- Worked across .NET Framework 4.8, .NET 8, Angular, PostgreSQL, Redis and ClickHouse.
- Improved release/process hygiene with docs, branch guides and deployment pages.
1M+business processes handled yearly
3clients planned for operation search
microservice
.NETFramework 4.8 → .NET 8 modernization path
Kafkaevent-based integrations instead of DB
coupling
Platform UX
Table views without suffering
Refactoring shared tabular views and list abstractions so product screens become easier to evolve and less expensive to maintain.
- Kendo Grid-based architecture
- Angular + backend query composition
- Metric focus: fewer backend requests
Side product
Fivey — short talks, less cringe
Experimental matching/social product around 5-minute conversations, anti-bot mechanics and lightweight discovery. A product playground for infrastructure, UX and market thinking.
- Landing + Ubuntu/Nginx deployment
- Matching-first product idea
- International-market mindset
Stack
The tools I actually use.
Enough keywords for recruiters. Enough substance for engineers.
Backend
.NET 8.NET FrameworkASP.NET
CoreEF CoreRESTHangfire
Frontend
AngularTypeScriptNgRxKendo
UIRxJSHTML/CSS
Data
PostgreSQLClickHouseRedisSQLQuery
tuningRead models
Infra
KafkaDockerNginxUbuntuJenkinsNLog
Engineering taste
Make it boring where it must survive. Make it bright where people must care.
I like product engineering. The best architecture is not
the fanciest one — it is the one that makes product changes cheaper.
I respect legacy. Mostly because legacy has already
survived things your new service has not even seen yet.
I care about developer experience. Fewer rituals,
clearer abstractions, better docs, faster releases.
I can lead without disappearing into meetings. Still
close to code, still close to production, still useful.