Uma candidatura completa num minuto
Currículo e carta de apresentação personalizados, prontos a enviar.
Adalat AI is hiring a Head of Data & Analytics to make numbers trustworthy and decisive. You will own end-to-end data standards, the pipeline, and reporting, working alongside Product, leadership, and government stakeholders.
You will build a defensible event taxonomy, a queryable warehouse, and a governance framework that enforces measurement integrity across teams in the US market.
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.
We are hiring a Head of Data & Analytics to make this company's numbers trustworthy, and then to make them decisive.
We are deployed in courtrooms across 10 states. Every dictation, cause list, template and error is a data point, and we have years of them. What we do not yet have is a data function.
This is the role that fixes current analytics/data "fires" and then builds the thing that should have existed from the start: a defensible event taxonomy, instrumentation that engineering cannot bypass, a warehouse that other teams can query themselves, and a reporting layer that leadership, partnership teams and our government stakeholders plan around.
You will own the function end to end — the standards, the pipeline, the people, and the answers. You will work alongside the Product function, and your numbers and their evidence are expected to be checked against each other rather than published side by side.
We have a preference, not a requirement, for people who have built a data function from nothing rather than inherited a mature one. There is no data contract here, no naming convention, no verified event and no versioned mapping table. You will write the first version of all of them.
You have cleaned up someone's analytics before and you are not romantic about it. You know the first ninety days are unglamorous — reading event definitions, finding out that two teams count the same thing differently, telling a CXO that a number in last quarter's deck was wrong. You are willing to do that work yourself rather than delegate it on day one.
You do not trust a number until you know how it was made. Your first question about a chart is what was filtered out. You have been caught by a silent join or a null-heavy property before, and it changed how you work.
You think in contracts, not dashboards. When engineering proposes a schema change, you can tell within a day which existing reports it breaks and what three properties need to ride along with it. You ask for those before the release, not after, and you ask in a way that does not block the release.
You can say no to senior people without making an enemy. Teams will want to ship events without review, pull numbers without context, and quote state-level figures you know are unsound. Holding that line politely, repeatedly, in writing, is a real part of this job.
You manage by raising the standard, not by taking the work. You review your analyst's SQL, you write the convention they follow, and you give them the visible deliverable rather than keeping it.
You write. Every number you publish arrives with a sentence saying what it means and a caveat you volunteered before anyone asked for it.
* Especially valuable