SOFTWARE ENGINEER AT EPAM / FULL-STACK

Making complex systems feel simple.

I'm Kevin, a Software Engineer at EPAM working on the Philips client engagement. My background connects enterprise service-management workflows with full-stack product and commerce engineering.

KV / SYSTEMSFIG. 01—26
HOW I THINK ABOUT SOFTWARE
INTERFACEClear experiences
→
APPLICATIONClean contracts
→
DATAReliable models
DESIGNBUILDREFINE
const principle = "clarity";const outcome = usefulSoftware(principle);// thoughtful engineering, end to end.
AVAILABLE FOR CONVERSATIONSBASED IN INDIA · WORKING GLOBALLY
SCROLL TO EXPLOREEST. 2022 · 4 yrs 10 mo EXPERIENCE
01 / EXPERIENCE4 yrs 10 moSince January 2022
02 / FOCUSFull stackEnterprise + product engineering
03 / APPROACHSystems-firstMaintainable by design
04 / LOCATIONIndia ↗Working with global teams
02CAPABILITIES

The stack is a tool. The system is the work.

I use the technologies that suit the constraints, rather than designing around a list of buzzwords.

From pixel to persistence.

Good engineering connects interface decisions to domain logic, databases, delivery, and long-term maintenance.

Explore the full tech stack
01 /

Frontend engineering

Responsive applications and accessible, well-structured interfaces.

JavaScript (ES6+)TypeScriptReactNext.js App RouterHTML5
02 /

Backend & databases

Contracts, business logic, integrations and relational data.

Node.jsExpressHonoREST APIsGraphQL
03 /

Commerce & content

Headless product and editorial delivery at scale.

BigCommerceContentstackBloomreach CDXPApollo ClientGraphQL
04 /

Service & enterprise

Enterprise operations and production service workflows.

ServiceNow exposureOdoo ERP (v12–v18)Enterprise service managementIncident / request workflowsApplication troubleshooting
03HOW I WORK

A product mindset. An engineering backbone.

My experience spans production commerce, full-stack systems and enterprise service management.

01

Understand the domain.

Start with the user's real workflow, failure cases, and the business rules underneath.

02

Design for change.

Keep boundaries clear, components reusable, and assumptions visible.

03

Make it dependable.

Consider data integrity, performance, accessibility, and operational realities early.

WHAT'S NEXT

Interesting problems deserve thoughtful solutions.

Start a conversation