INDmoney

Overview

INDmoney is an Indian investing and personal-finance platform. In July 2026 I joined its web team as an onsite SDE Intern in Gurugram, working on indmoney.com: a large, live production frontend where the code I write is deployed directly to real users.

My work sits where product and performance meet: shipping new pages that bring people to the site, and making existing pages faster and more responsive once they arrive.

Recent work: creator indicators on charts

INDmoney runs a creator (affiliate) program. Creators who have their own audience can publish their own chart indicators, and their followers can then use those indicators on INDmoney’s charts.

I’ve been working on two parts of this:

• The indicator saving flow: the flow that saves indicators so they’re stored and available when users come back to their charts.
• Integrating indicators on charts: wiring indicators into the charting experience so they show up and work on the charts users trade from.

It’s product work where reliability matters: an indicator that doesn’t save, or doesn’t render correctly on a chart, directly breaks the experience for both the creator and their audience.

What I work on

• Complete pages, end to end. I’ve built and shipped complete pages on indmoney.com, from layout and components through to performance. These pages have contributed to growth in the site’s overall web traffic.
• INP optimization. I optimize existing production components to reduce Interaction to Next Paint (INP), so taps and clicks respond faster for users on the live site.
• Page revamps. I revamp existing pages to improve the user experience and make them easier to maintain.
• Reusable components. I build performance-first UI components designed to be reused across the product, so new pages start fast by default.

Why INP matters

Interaction to Next Paint is one of Google’s Core Web Vitals. It measures how quickly a page visually responds after a user interacts with it. On a finance product, where people tap through data-heavy screens, a sluggish response feels broken even when nothing has failed. Improving INP directly improves how the product feels, and Core Web Vitals also feed into how pages perform in search.

Working in a production codebase

This is my first time working inside a codebase of this scale with a team, rather than on products I own end to end. Day to day that means:

• Reading before writing: understanding existing patterns and conventions before extending them.
• Shipping to live users: my changes go straight to production, so correctness and performance are part of the definition of done.
• Building for the team: reusable components that other engineers can pick up, not one-off code.

A note on details

Much of this work is internal to INDmoney, so this case study focuses on the kind of work I do rather than internal numbers or screens.