I build full-stack applications that combine thoughtful user experiences with strong backend engineering. Focused on performance, architecture, and product-driven problem solving, with growing depth in security and intelligent systems.
A curated selection of shipped work, systems projects, and security-focused practice.
Contributed to a scalable investment-oriented backend platform focused on modular architecture, data-driven workflows and production-grade API engineering.
Developed an e-commerce management system exploring distributed architecture, service decomposition and scalable commerce workflows.
Designed and developed a rental management system centered around reservation workflows, business rules and practical domain modeling.
Hands-on offensive security practice focused on web vulnerabilities, attack surfaces and secure engineering principles.
Developed a full-stack news/content platform with structured content management and user interaction flows.
Built a structured library management system focusing on OOP principles and backend logic design.
Built a backend service integrating external weather APIs with clean service abstraction.
Developed a transactional order management system focusing on business logic and customer workflows.
Industry experience across backend systems, distributed workflows, and product-focused engineering.
I’m a software engineer focused on building reliable software end-to-end — from polished frontend experiences to scalable backend systems. I enjoy solving engineering problems where architecture, performance and usability intersect, and I’m especially interested in backend systems, cybersecurity, and intelligent software.
Selected notes and short reads.
Most tutorials show how to use Kafka. Very few show how to use it in a real system. This article builds a practical event-driven architecture using Spring Boot, Kafka and Docker—based on an Event & Ticketing System scenario.
Backend looks clean from the outside, but the real lessons come after production issues. This post shares five mistakes I made—and what they taught me about building reliable systems.
Microservices can look “senior”, but they’re often unnecessary. This post explains why overusing microservices makes systems harder to build, debug and scale—and when you should keep things simple.
AI systems are evolving from “answering models” to systems that can decide and act. This article compares RAG with Agentic RAG and clarifies how the architectures differ in practice.