Hiring for a role
The internship and the two businesses behind it, plus a resume you can take with you.
See the experienceHello, I'm
I track what users do in a product, find the behaviour behind the drop-off, and turn it into the change worth shipping.
Start here
Three different people read this page for three different reasons. Pick whichever one is you and jump to it.
The internship and the two businesses behind it, plus a resume you can take with you.
See the experienceHow an engagement runs, and a record of things already built and running end to end.
How I workA live analytics dashboard, a data-engineering course, and the repositories behind them.
See the projectsGet to know
I work at the intersection of product analytics and data analytics. That means tracking what users actually do inside a product, defining the metric that explains why, and running the SQL and Python behind it to find out what changed — then reporting it in a form a product team will act on.
My stack is SQL, Python, Power BI and Excel for the analysis, and Google Analytics, Microsoft Clarity, Mixpanel and Optimizely for the product side: funnels, retention, session behaviour and experiment readouts. I clean and validate data first, because a metric built on bad rows is worse than no metric at all.
Beyond the tooling I run two businesses end to end — an app studio and an e-commerce supply venture. That is where I learned pricing, inventory and demand forecasting as numbers that have to work in a real month, rather than as a case study. I am a B.Tech Data Science student at Abhyuday University and was a Data Analyst Intern at Stuffmatic.
Track record
One internship and two businesses, run hands-on rather than advised on. The businesses are here deliberately: owning pricing and inventory is where the judgement behind a recommendation comes from, and no course teaches it.
Eight months inside a working data team, on the unglamorous part of analytics that decides whether anything downstream is trustworthy.
A one-person product studio. Each engagement runs scope, design, build, verify and support — which is the same loop a product team runs, at one-person scale.
An e-commerce supply business moving fresh, thornless Opuntia pads directly to farming, research, skincare and vegan-leather buyers across India.
What I do
Four areas, each with the tools that produce it and something you can go and check. The links are the point — a list of technologies tells you nothing about whether the person will be useful.
Answers to what users did and why they stopped — funnels, retention, drop-off points and experiment readouts, not a dashboard nobody opens.
Most product teams have the events and no read on them. I define the event and the funnel that actually answers the question being asked, instrument it, and come back with where the loss is and what is worth testing next. The output is a recommendation with a number attached, not a chart handed over for someone else to interpret.
Dashboards and reports a manager reads in ten seconds — not a table of numbers they have to interpret themselves.
Most reporting answers a question nobody asked. I start from the decision that has to be made, define the metric that actually settles it, and build only what that decision needs — so the answer stays visible instead of being buried in a chart nobody opens twice.
Cleaned, validated analysis that runs exactly the same way again without anyone rebuilding it by hand.
A raw export nobody else can read is the normal starting point, not the exception. I clean and validate it, write the query behind the number so it is reproducible, and hand it over documented — because an analysis that only ever existed in one laptop has not really been delivered.
Working applications — designed, built, tested and shipped — not scripts, notebooks and slideware.
An analysis nobody can act on is just a spreadsheet. I build the thing that does the job: a signed Android app, a live dashboard, or an automated pipeline, taken through to something that runs and is still running a year later.
Two toolchains, used for different jobs. The product analytics platforms answer what users actually did; the data stack is what turns that into a number you can defend. The rest is the delivery and communication work that turns either one into a change somebody ships.
Product Analytics
Data & Reporting
Tools & Technology
Product & Delivery
The work
Six things built rather than a list of things half-built: a data-engineering course you can start right now, an analytics dashboard, three shipping products, and a competition entry taken from research to pitch.
Operational insight from a 50,000-record ride-booking dataset. Booking volume, fare, distance, ratings and cancellations, broken down by vehicle type, pickup and drop zone, payment method and cancellation cause. Delivered as a dashboard you can open, plus a written insight layer that quantifies what each finding is worth rather than only describing it.
An interactive data-engineering course that teaches the stack in the order a data team uses it: Python, SQL, pandas, APIs, ETL/ELT, Git/Linux/Docker, Airflow, PySpark, cloud warehousing, dbt and Kafka. Sixteen modules and 240 questions, with each module gated behind a 10/15 pass mark and progress saved in the browser.
Smart expiry and inventory tracker built for kirana stores. Tracks stock and expiry dates, calculates sales velocity to recommend reorder quantities, and surfaces margin leaks and slow-moving stock — turning a shop's own sales data into restocking, billing and insight screens.
A focus timer and weekly timetable that keeps an honest study record — including the days you meant to study and did not, and the reason each one was missed. Built as an Android app with a live lock-screen countdown, subject-level insights, a 26-week heatmap and entirely local storage.
A tactile to-do list and reminder app built around the moment a task is due: a live countdown, a chosen lead time, stacked nudges and a snooze that keeps the task in play. Tasks carry custom categories with their own icon and tone, times are always shown with AM/PM, and a monthly feedback prompt and studio update feed keep the app improving without an account or a subscription.
A consumer-brand and youth-focused product challenge, taking an idea from research through to a presented solution. Applied the same discipline as the analytics work: understand the user, define what would have to be true, and present it in a way a panel can act on.
Process
Fixed order, and the verify step is the one most people skip. On a CV full of similar candidates, this is usually what decides between them.
Before anything is built, the question gets pinned down: what decision does this need to support, and who is the one making it. A vague brief is the usual reason a dashboard ends up unused.
The metric is agreed in writing before any work starts, because a number that was never defined cannot be checked afterwards — and an undefined number is exactly where projects quietly go wrong.
For product work, the events and funnels get built before the analysis does. A funnel defined after the fact is a funnel that agrees with whatever the answer already was.
The result is checked against the question it was meant to answer and the edge cases are tested. What the analysis does *not* cover gets said out loud, rather than left for someone to discover later.
You get the work, the code behind it, and documentation written so it can be re-run or extended without me. The point is that it keeps working after this ends.
Evidence
The checkable part. Certifications are linked to their real verification pages — anyone can confirm them, and so can you.
Abhyuday University, Khargone — Pursuing
First-year topper.
Rumas, Latur — 76.60%
Government ITI, Latur — 79.90%
Yashwant Vidyalaya, Latur — 78.90%
External training, kept separate from the degree so the two are not read as the same claim.
MX
Each one links to its real verification page, so the claim is checkable rather than asserted.
Academic and co-curricular record during the engineering degree.
Academic performance
Recognised for consistent excellence across the full first-year B.Tech coursework.
Represented the department in sports activities, building teamwork and discipline alongside the degree.
Tools only go so far. The rest is whether the person handing you the number will also tell you what it does not cover.
Turning analysis into something people actually act on — clear updates, shared context, and expectations set before they are missed.
Coming at a vague business question with structure, and checking the edge cases that would make a wrong number look right.
Asking the better question when the first answer is too easy, and treating feedback as the cheapest input available.
Reach out
If you have a role, a project, or a product whose data needs making sense of, I would like to hear about it.
Product analytics, data analytics, and the dashboards that turn both into a decision. The quickest route for a role is the resume; the form below gets you a typed answer rather than a PDF read later.