I work as a backend-focused engineer who builds reliable, maintainable systems from the ground up. I approach every project with the same structure: understand the data flow, identify failure points, and construct a design that holds under real conditions. My work spans service development, cloud migration, automation, and performance tuning. I use Java, Spring Boot, AWS, Docker, and CI/CD pipelines as core tools because they enable predictable deployment, controlled scaling, and clean separation of responsibilities across components.
At EPAM, I worked as a backend developer where I built Spring Boot services and migrated them to AWS, ensuring stable deployment pipelines and consistent runtime behavior across environments. I handled API development, authentication flows, database interactions, and containerized workloads. The shift to AWS required refactoring modules for cloud compatibility, implementing IAM-based security, and integrating services with monitoring and logging systems. I pushed the services through automated CI/CD pipelines, ensuring each build met quality gates and could be deployed without manual steps. My exit was driven by the freeze on backend conversion roles.
Across my independent work, I focus on projects that require clear logic and strong engineering discipline. I built an estrus detection system for cattle using signal patterns, transforming raw inputs into actionable insights. I developed a ship routing algorithm for the Indian Ocean region that optimizes fuel, safety, and time under dynamic weather conditions. I also worked on a dynamic rule engine using Flask, SQLAlchemy, and a Tkinter interface, enabling real-time rule creation and evaluation. In other projects, I created automated bus scheduling systems, e-commerce customization tools, and routing engines, each centered on reliable algorithmic behavior.
My priority in any engagement is predictable delivery. I keep communication minimal and focused on technical requirements. I structure work so that each component is testable, traceable, and easy to extend. I do not rely on assumptions; I depend on clear system logic, measurable outcomes, and verifiable performance. My objective is to deliver solutions that continue functioning long after handover.