Product Analyst

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 and document navigation - are now deployed across 9 states, covering nearly 20% 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

Adalat AI is live in ~20% of Indian courtrooms across 9 states. The next phase of growth demands rigorous answers to two questions: what should we build next, and where should we expand? Today, nobody owns these questions full-time.

The Partnerships team—primarily lawyers—excels at judicial stakeholder management and field operations, but lacks the quant and research skills to systematically convert field observations into structured product insights. The Customer Success team captures user feedback through ticketing and Voice of Customer, but this data remains reactive: it surfaces what’s broken, not what to build. The Product team makes roadmap decisions, but doesn’t have a dedicated person feeding them structured, field-grounded research.

The Product Analyst fills this gap. Sitting within the Product team under Technology, this role serves as the connective tissue between field reality (Operations) and product direction (Technology)—turning what lawyers see in courtrooms into data-backed recommendations for what Adalat builds next.

Key Responsibilities

Map next product bets through field research

Embed with the Partnerships team during court visits. Conduct structured observations and user interviews alongside lawyers in Judicial Stakeholder Management and Field Operations.
Produce research briefs: what are courts struggling with that Adalat doesn’t address? What manual workflows could be automated? What needs beyond transcription are emerging?
Present product bet recommendations to Product Lead and CTO/CEO with supporting data, not just anecdotes.

Drive state expansion analysis

Build a data-driven framework for prioritising which states and courts to expand into next (from ~20% toward broader national coverage).
Score and rank expansion targets by court volume, infrastructure readiness, judicial receptivity, and partnership pipeline.
Work with the Growth function under Partnerships to align expansion priorities with on-the-ground capacity.

Own the strategic layer of Voice of Customer

Pull from the VoC function under Customer Success: analyse quantitative and qualitative product feedback for patterns that inform product strategy.
Distinguish systemic product gaps from one-off issues. Escalate the former to Product; help CS route the latter.
Build and maintain a feedback taxonomy that connects user input to product themes.

Build and own product analytics

Set up and maintain product analytics dashboards to track usage, adoption, feature engagement, and outcomes.
Define success metrics for new features alongside Engineering and Design.
Use quantitative data to validate (or challenge) qualitative research findings. Triangulate signals.

Bridge Operations and Product

Be the structured intermediary between what Partnerships lawyers observe in the field and what the Product team decides to build.
Translate qualitative observations into quantified, prioritised product inputs.
Support Partnerships with data for stakeholder conversations, state government pitches, and judicial academy presentations.

Shape strategic priorities

Collaborate directly with CTO and CEO on product direction. Provide the research foundation for strategic decisions.
Contribute to roadmap planning with user research summaries, competitive observations, and field-grounded opportunity sizing.
Over time, become the recognised go-to person for strategic product questions across the org.

Qualifications

Background

2–5 years in design research, user research, product strategy, or a role combining qualitative and quantitative methods.
Experience translating research into product or policy recommendations—influencing what gets built, not just writing reports.
Comfort with field work: court visits, stakeholder interviews, operating in government/institutional settings.
Familiarity with Indian judicial system, civic tech, legal tech, or government technology is a strong signal.

Strong Plus

HCI, human-centred design, or design research training.
Experience at orgs working at the intersection of tech and public systems (e.g., Digital Green, Wadhwani, Bhashini, Samagra, eGov, Dalberg, IDinsight).
Hindi or other Indian languages for field research.
Ecosystem-building or multi-stakeholder coordination experience.

What You Will Achieve in a Year

In your first year, you'll have built Adalat's first structured product analytics layer — adoption dashboards, court-level engagement tracking, and the metrics framework the pod uses to decide what to build. You'll have completed field visits across at least 3–4 states, producing product bet briefs that directly shaped the roadmap. You'll own the state expansion model that tells us where to go next. And you'll have turned a scattered stream of VoC feedback into a repeatable synthesis process that the whole product team relies on. By month 12, no major product decision gets made without your research on the table.