Elango Ponnusamy
Full Stack Engineer & Software Architect based in Tamil Nadu, India
Over the past five years I have designed, built, and shipped production web applications for startups and established teams — from customer-facing React interfaces to Node.js APIs, Supabase-backed data layers, and cloud deployments on AWS and Vercel.
What I build
My work centers on three principles: write code that is easy to maintain, ship features that perform under real traffic, and design interfaces that feel fast and intentional. I specialize in the React and Next.js ecosystem, TypeScript, REST and GraphQL APIs, PostgreSQL, and modern CSS.
Whether the task is a greenfield SaaS product, a legacy migration, or a performance audit, I focus on measurable outcomes — shorter load times, cleaner architecture, and fewer production incidents.
This site
On elangodev.com this is my professional profile: work history and education live on this About page and the author profile. I also publish open-source packages on NPM and keep a few learning pages — articles, the React roadmap, Node.js roadmap, and testing guides. See the editorial standards for how those resources are written.
Engineering principles
1. Maintainable architecture
I favor clear module boundaries, typed contracts, and patterns teams can extend without tribal knowledge. Simpler systems stay reliable as requirements change.
2. Measured performance
Core Web Vitals, server timing, and real user signals guide optimization — not guesswork. Improvements target LCP, INP, and TTFB with before/after evidence.
3. Accessible by default
Semantic HTML, keyboard paths, and contrast are part of the build checklist. Accessibility is a requirement for shipping, not a later polish pass.
Professional focus
Available for full-time roles, contract work, and technical consulting. Day-to-day work spans product UIs, API design, data layers, and cloud deploys — with an emphasis on systems teams can keep shipping after the first release.
Education & growth
Continuous learning through production projects. Stack trade-offs, performance fixes, and architecture decisions from client work feed the next engagement.
Technical expertise
Open source
Beyond client work, I publish small NPM packages built from problems I hit in production—focused utilities other developers can install and use immediately.
Editorial standards
Ads, when shown, are clearly separated from editorial content and never interrupt reading flow. User privacy and page performance come first. See the editorial policy and privacy policy.
Get in touch
For project inquiries, roles, or corrections to published material, use the contact page.