I'm a Staff Backend Engineer open to Staff, Principal, or Founding-Engineer roles where I can own a backend or data infrastructure system with the same scope and have real influence on how a team scales.
I own backend and data platforms from system design through migration, production operation, and recovery. Scaled a platform team from 4 → 7 engineers, served 200+ merchants across five commerce platforms, and reduced infrastructure cost 66% along the way.
“I worked with Udhay for the past four years, and calling him just a 'team lead' wouldn't do justice to the role he played in my journey. He has been an exceptional mentor and guide, always approachable, patient, and supportive.”
“Udhaya is an exceptional engineer with strong technical depth and the curiosity to solve complex client challenges. He combines a high ownership mindset with excellent communication, translating technical concepts clearly for non-technical stakeholders.”
“Udhaya has demonstrated an impressive ability to manage complex product development projects while leading a diverse team. His leadership style fosters a supportive environment where team members can thrive.”
“Udhaya is an exceptional leader who sets high standards for his team and inspires them to reach their full potential. His technical expertise has been invaluable to the success of our projects.”
Staff, Principal, or Founding-Engineer roles where I can own a backend or data infrastructure system with real influence on how a team scales.
Deep expertise across CDC pipelines, warehouse consolidation, and building for reversibility so mistakes stay cheap to fix.
Match storage to question. Operational simplicity beats sophisticated abstractions. Ship in trust order, not sophistication order.
Every new consumer had to implement backpressure monitoring and memory high-water marks before deployment. This pattern prevented OOM crashes across 15+ services company-wide.
Led hiring for 3 backend engineers. Focused questions on tradeoffs and reversibility, not algorithm complexity — raised the bar for architectural thinking across the company.
Platform, Recommendations, and Segmentation teams aligned on shared systems. This is where we caught the stale recommendation churn driver before it spiraled.
Goutham Kishore and Piyush Jaiswal both reported to me. Focused on helping them own systems end-to-end and communicate architecture to non-technical stakeholders. Both now lead sub-systems independently.
Whether you're refactoring a legacy pipeline, diagnosing CDC lag, or designing a zero-downtime migration, let's unpack the architecture.