About me
Backend Engineer & Solution Architect with 4+ years of experience building secure, scalable systems for banking, fintech and enterprise AI platforms.
My journey
My journey into software architecture began during my computer science studies, where I was fascinated by the complexity of building distributed and scalable backend systems. What started as curiosity about how large-scale platforms serve millions of users grew into a deep passion for designing secure, efficient and maintainable backend solutions.
Over the past four years I've worked across banking, insurance and customer service, collaborating with cross-functional teams to build enterprise-grade applications. Those experiences shaped my belief that great systems are not only functional but also scalable, reliable and adaptable to change.
What I love: distributed systems and streams
Distributed systems are what I enjoy most. I like the problems that only appear at scale: partial failures, ordering, retries, idempotency, backpressure and consistency trade-offs. Designing a system so it keeps behaving correctly when parts of it don't is the kind of challenge I look for.
That's why I'm drawn to event-driven architecture and stream processing. Treating data as a continuous flow of events, instead of something you query after the fact, changes what a system can do. It reacts as things happen, decouples services cleanly, and makes the state of the business visible in real time.
Exploring AI on top of streams
I'm actively exploring how AI capabilities can strengthen stream processing and real-time decision making. Classical streaming pipelines are very good at moving and transforming events fast. Adding AI means those pipelines can also interpret, classify and enrich events as they arrive, and trigger the right action without waiting for a human or a batch job.
I'm particularly interested in AI agents, retrieval-augmented generation (RAG) and autonomous workflows that blend classical software architecture with machine intelligence. The goal is not AI for its own sake, but systems that make better decisions, faster, with guardrails, observability and a clear fallback when the model is wrong.
What motivates me
Hard problems in systems that matter: platforms where reliability, security and scale are real requirements. I'm happiest when I can take a messy business problem and turn it into an architecture people can trust and keep evolving.
I also stay motivated by continuous learning. The field moves quickly, and I like bridging solid theoretical foundations with hands-on experience, then proving ideas in production rather than just on slides.
How I work with people
I'm a team player. Good software is built by teams, so I share context, review openly, and help teammates and other disciplines move forward. I'd rather the whole team ship something solid than be the only one who understands it.
I advocate for clean architecture, domain-driven design and choosing the right technology for each problem, always focused on delivering real value to both the business and the end user.