Web Lead

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 Web Lead to own our web presence end to end.

Our website runs on Framer today. It is the first thing a judge, a journalist, a funder or a prospective hire sees, and right now nobody owns it. Every web question — a new page, a broken redirect, a blog post that needs a proper template, a visual that needs making, a tracking request — becomes a negotiation between comms and engineering and usually lands on whoever is least busy that week. Pages go up when someone finds an afternoon. Nothing is measured.

This role ends that. You are the point of contact for everything website: what gets built, what it gets built in, what it looks like, what it says, when it ships, and whether it works once it is live.

This is a builder's job, and it is genuinely three jobs in one pair of hands. You will be hands-on in Framer from week one. You will design in Figma and produce the visual assets that go on the page, because there is no designer waiting to hand you anything. You will write and rewrite the words, because a site is mostly words and ours could be sharper. You will make the call on when a page should stop being no-code and become a properly coded stack, and you will defend that call. And you will direct any outside help we bring in rather than take direction from it.

We have a preference, not a requirement, for people who have run a web presence well with no team behind them, rather than people who have been one specialist inside a large web org.

You will report into Communications, with a dotted line to Platform Engineering for anything touching infrastructure, security, or user data.

Key Responsibilities

Own our web properties end to end — from brief to information architecture to design to build to launch, and then the maintenance nobody volunteers for
Build and ship in Framer, and decide when Framer stops being the right answer for a given surface; you own the tooling call and defend it with reasons, not preference
Design what you build — page layouts, components and responsive behaviour in Figma, working from our brand direction, to a standard that does not need a designer's rescue
Produce the visual assets the pages need — hero and section graphics, icons, diagrams, data visuals, social and OG cards, image treatment and selection, and light motion where it earns its place; you make these, you do not commission them by default
Build and maintain a reusable asset and component library so that visual work compounds instead of being remade from scratch each time, and so anything new we put on the web is recognisably ours
Write and edit what goes on the page — landing copy, product pages, blog structure and headlines; you will be handed rough source material and expected to turn it into something publishable, not just pour text into a template
Own the blog as a publishing surface — templates, content model, SEO structure, editorial workflow, and a handoff path that lets non-technical colleagues publish without filing a ticket
Be the single intake point for web requests — a visible queue, a published turnaround expectation, and the ability to say no to a senior person with a reason and an alternative rather than a silent delay
Direct any external web or design help we engage — write the briefs, set scope, review output, hold the timeline; outside partners work to your specification, not the other way round
Own web analytics and the tracking layer — instrumentation on the site, conversion measurement, and keeping third-party scripts and trackers under control; you consume the analytics stack, you do not own it
Own the unglamorous operational layer — DNS, domains, SSL, redirects, uptime monitoring, backups, and the things that are invisible until the day they are not
Work inside platform's standards without being chased — anything touching authentication, user data, or the product runtime goes through platform review before it ships, including for urgent launches

About You

You ship. A good page live this month beats a perfect one live next quarter, and you have made that trade knowingly and can name a time it cost you something.

You are a three-in-one. You can design a page and the assets on it, write the copy, and build it. None of the three is your weak leg by a wide margin. If you need a designer to start and a writer to finish, this is not the job.

You are not precious about the tool. You can build a beautiful thing in Framer and you know exactly where Framer runs out — dynamic content at scale, complex SEO, anything with real data behind it. You have hit that wall before and know what moving past it costs.

You design systems, not one-offs. Your instinct after making a thing twice is to make it once and reuse it.

You write. On the page and off it — briefs, documentation, handover notes. When you are on leave, the org is not stuck.

You are comfortable being the only person who does this job — and you know when to buy freelance capacity instead of quietly absorbing the work and becoming the bottleneck.

Qualifications

5+ years building and running websites, with at least two properties you can point to and say "I owned that end to end"
Fluent in a visual builder — Framer strongly preferred, Webflow or equivalent acceptable — and able to work at the limits of the tool rather than inside its templates
Strong design capability in Figma — page layouts, components, and the visual assets that sit on them, produced from a brand direction without a designer's involvement; show us work where the design and the build were both yours
Demonstrated content writing and editing for the web — you can write a landing page, sharpen someone else's draft, and structure long-form content for readability and search; send us something you wrote that shipped
Real front-end capability beyond no-code — HTML, CSS and JavaScript to a working standard, and comfort with a modern framework or static site generator (Next.js, Astro or similar) plus a headless CMS
Working knowledge of Git, deployment pipelines, DNS and hosting — you can debug a failed build or a bad redirect yourself
Demonstrated technical SEO and site performance work with measurable before-and-after, not assertions
Experience directing external web or design help — a freelancer, a studio or an agency — including scoping, reviewing, and holding a timeline
Track record with non-technical stakeholders across functions, including protecting scope without damaging the relationship
Genuine interest in the mission and in how public institutions adopt technology

Especially valuable

Having built or maintained a design system or asset library that other people used
Illustration, iconography, diagramming, or data visualisation as a real skill rather than a passing one
Light motion and animation work — Framer motion, Lottie, After Effects
Accessibility work, ideally audited
Nonprofit, social impact or mission-driven organisation experience, including donor and partnership-facing pages
Having migrated a site off a no-code builder onto a coded stack, and being honest about what it cost
Building for low-bandwidth and mobile-first users
Experience writing for a technical or policy audience
Familiarity with product analytics tooling (Mixpanel, PostHog, GA4 or similar)

What You Will Achieve in a Year

Our web presence has a named owner, a known stack, and a maintenance path — and the things that were quietly broken or unmonitored have been found and fixed
The site says something clear and current, in language we are proud of, rather than whatever was written eighteen months ago
Anything we put on the web looks like it came from the same organisation, because there is an asset and component library behind it rather than a folder of one-off files
Putting something new on the web takes days rather than months
Nobody in comms or programs is waiting on engineering to change a web page, and nobody in engineering is being pulled into web work
Web numbers — traffic, performance, accessibility, conversion — are measured, published, and improving from a stated baseline