I am currently focused on designing backend systems that behave correctly under load, failure, and scale. My work emphasizes system design fundamentals—caching strategies, async processing, access control, and deployment reliability

At present, I am building KeyVaultX, a secure secret management backend, treating it as a production-style system with strict security boundaries, scoped access, and clear trust models rather than a simple CRUD application

Over the past year, I transitioned from writing basic APIs to architecting backend systems with real infrastructure concerns. Through hands-on projects, I worked on load balancing, Redis-based caching, message queues, and database performance under high read/write pressure

Projects like Opus Polling App reflect this phase, where I deliberately simulated real-world problems such as traffic spikes, database contention, and eventual consistency, and solved them using asynchronous processing and caching instead of brute-force scaling

Completed an intensive summer training program focused on frontend development and team-based software workflows. This experience strengthened my understanding of how frontend applications interact with backend APIs, authentication flows, and deployment pipelines

While my long-term focus shifted toward backend systems, this training helped me build a full-stack perspective, enabling me to design backend APIs that are practical, predictable, and frontend-friendly

Coursework: Data Structures and Algorithms, Operating Systems, Database Management Systems, Computer Networks, Object Oriented Programming

Alongside academics, I consistently applied these concepts outside coursework by building independent backend projects, prioritizing practical system behavior over theoretical implementations