Dhruv Singhal · Product Manager & Builder

I own the problem, the spec, the trade-offs and the evidence. Where I also built it, I say so.

Product Intern, Growth · The Sleep Company (Jul to Oct 2026)

E-commerce and AI products: stakeholder input, user research, and product specs turned into decisions teams can build.

See the workEmail me

Looking for full-time PM / APM roles

Four case studies below. Each states the decision, the trade-off, what was tested, and what is still unproven.

Four stories, one PM decision each

AI trust and evaluation · focused scope · D2C retention definitions and privacy · rider-to-rider matching and fare fairness.

Product

Local build · not deployedEvidence: Built

ExperimentHub

Self-hosted A/B testing whose statistics engine is allowed to say keep running: a sequential verdict instead of a bare p-value, and assignment that puts the same user in the same variant every time. Built solo; evidence so far is a synthetic demo tenant, not production use.

Solo · product and architecture

ContinueSequential verdict at p = 0.0337 (synthetic demo)

Technical

PrivateEvidence: Built

KiteEdge

A personal analytics desk for my own Zerodha account, running on my own laptop: technical indicators, Monte Carlo VaR, ensemble forecasting, a NIFTY 500 screener and a FIFO trade journal. Private by design; the tests run on synthetic data only.

Solo · personal tool, product and architecture

Analytics onlyNever places an order · synthetic data in tests

Technical

LiveEvidence: Built

TCS NQT Prep Hub

Built so a candidate can prepare for the TCS NQT without a paid prep course: 404 practice questions and 10 previous papers (counts per the repo README), quizzes, flashcards and progress tracking. Installable as a PWA and usable offline.

Built the web app · question bank started by three other contributors

404Practice questions (repo README)

Product

ArchivedEvidence: Self-reported

Hackmate

Designed to help solo founders find a co-founder they would actually build with: swipe-based matching shaped around founder-discovery pain points. A two-person build; usage was never instrumented, so there is no user number to report.

Two-person build · I owned product

2Person build · usage not instrumented

Product

PrivateEvidence: Tested

Better-Half

Helps a long-distance couple stay in sync when they can't read the room in person. Cycle phase, mood and stress drive daily guidance for her, him and us. Private, used by two people. Privacy is enforced at the database rather than the UI: 575 RLS policy checks, offline-first, hosted on free tiers ($0 a month, self-recorded).

Solo · product and engineering

575RLS policy checks (test suite)

Technical

LiveEvidence: Tested

This Portfolio

Treated my own portfolio as a product: spec and success criteria before code, then versioned iterations from v1 (Jan 2026) to v6 (Sept 2026), with the decision trail written up as its own case study.

Solo · product, content and build

6Versions, Jan to Sept 2026

What the evidence supports

Each number says where it stops. Case-study and article counts are coverage, not outcomes.

SourcedA source link required on every recommendation · offline eval result withheld; field accuracy not measured
0Failures · release gate run, 15 Sep 2026
57E2E tests passing (19 Sep 2026) · local pilot ready
897Tests passing · local build, not deployed
10Case studies (4 flagship) · coverage
14Articles · coverage
Dhruv Singhal

Still reading?

Then we should probably talk. Email is the fastest way to reach me; LinkedIn works too. More on how I work is on the about page.