Product Analyst - Data & Analytics

About the Company

Adalat AI is building an end-to-end justice tech stack that automates manual and clerical pain points in courtrooms, giving judges back time to focus on what matters most: decision-making and delivering justice. Our solutions — from AI-powered transcription in Indian languages to case-flow management, document navigation, and the Paperless Courts platform — are now deployed across 10 states, covering nearly 25% of India's judiciary. Backed by leading technology companies and funders, and incubated at MIT and Oxford, Adalat AI is working to eliminate judicial delays and expand access to timely justice. Founded by a team with backgrounds in law, technology, and economics from Harvard, Oxford, MIT, and IIIT Hyderabad, we are scaling rapidly across India and the Global South.

Role Overview

We are hiring a Product Analyst to own the truth of what happens inside our products.

Every dictation, template, and error in a courtroom is a data point. Today those data points are not trustworthy enough to decide with. Teams add instrumentation without telling anyone. The result is that the company is making decisions on numbers nobody has verified.

You will fix that, and then build on top of it. You own the data going in — the taxonomy, the review gate, and the migration off Mixpanel onto analytics infrastructure we run ourselves. You also own the answers coming out — feature-level usage across states, the recurring report leadership plans around, and the analysis that settles arguments.

One thing to be upfront about: we are not moving from one SaaS analytics tool to another. Because we work with judicial data, our replacement for Mixpanel has to run on our own infrastructure, under our own control. That means this role sits closer to the metal than a typical product analyst job. You will help shape the event schema the new platform is built around, run the dual-send validation, migrate two and a half years of history, and reconcile the numbers on the other side. You do not need to be an infrastructure engineer, and you will not be on call. You do need to be the kind of person who is curious rather than alarmed when the answer lives one layer below the dashboard.

We have a preference (not a requirement) for people who have been the first analytics hire somewhere, with no standards to inherit. Our analytics function is young. We are not looking for someone to maintain a mature stack; we are looking for someone to build the thing that everyone else will later take for granted.

Key Responsibilities

Own data correctness — rebuild and document the event taxonomy, kill duplicates, and be the review gate through which every new event any team adds must pass Catch drift before it ships — build alerting that detects new or changed events at the point of development, so we are never relying on teams to self-report Own the migration off Mixpanel — design the target event schema, run dual-send validation, export and dedupe two and a half years of history, load it into the warehouse, and reconcile the numbers until we can retire the old system with confidence Be the product voice on the platform build — we are standing up self-hosted analytics infrastructure alongside this hire. You will not own the servers, but you will own what goes into them: the schema, the PII handling, the data model the rest of the company queries Build feature-level visibility — which feature, which state, which user type, trending which way, at a granularity that survives a CXO's follow-up question Own the recurring reporting — the bi-weekly feature analytics report for leadership, and the state-level and feature-level reporting inside the partnership portal Answer the questions that matter — correlation work against partnership OKRs across states, and one-off investigations where the answer changes a decision Make the company self-serve — open up warehouse querying to other teams so routine questions stop routing through you Treat p