◆M-CommerceNDA
Enterprise M-Commerce Platform
Backend at scale for mobile commerce
Role
Engineering Lead
Industry
Retail / M-Commerce
Timeline
EPAM engagement
Type
M-Commerce
An enterprise m-commerce platform handling high transaction volumes. The client is under NDA, so this stays high-level — but it's where much of the modernization story played out: migrating Java services from blocking JDBC to reactive R2DBC, cutting startup times, and leading an international backend team to keep a high-throughput commerce platform fast and reliable.
What I owned
- Promoted from Senior Java Engineer to Lead Software Engineer, leading backend for one engineering stream across multiple international product releases.
- Managed a backend team of up to 10 engineers — providing technical direction, mentoring, and running technical interviews and onboarding.
- Kept delivery commitments on track even when roughly half the engineering team transitioned away.
- Led delivery of 6 major product launches across international markets, holding a high, predictable quality bar.
- Designed scalable backend solutions and contributed to microservices architecture decisions, applying SOLID and clean-architecture principles.
- Coordinated large cross-team integrations to reduce delivery risk and collaborated with architects on long-term technical strategy.
- Introduced stronger engineering practices — formal code reviews, technical documentation standards, architecture discussions and SonarQube — and drove proactive technical-debt reduction.
- Built on Java and the Spring ecosystem (Spring Boot, Spring Cloud), Hibernate/JPA, Azure, Kubernetes and Azure DevOps CI/CD.