The Interview
Where did your interest in law begin, and what were you studying/doing just before you chose law? I did a B.Sc. in Computer Science (CGPI 9.72). While building student-facing sites, I kept hitting policy and IP questions—terms of use, data privacy, and “who owns what” on user uploads. That curiosity pulled me into law.
What was the moment you decided to blend law with technology instead of picking just one?
Why Kishinchand Chellaram Law College first, and what drove the transfer to Government Law College, Mumbai? What did you gain/lose with that move? KC was my entry point; I transferred to GLC for stronger exposure, alumni network, and Mumbai’s core legal ecosystem. Gains: faculty depth, peer quality, brand. Losses: momentum/stability for a while and some campus familiarity.
Looking back at year 1–2 of law school, what were the two best decisions and one mistake that shaped your path?
What’s the origin story behind LegalAlphabet.com and munotes.in—what problem did you see first, and which came first? Munotes came first: students/job seekers needed clean, daily updates. LegalAlphabet followed when I saw law jobs and internships were fragmented, spammy, and hard to filter by real criteria.
What was your very first MVP for each—how long did it take, what did it do, and what did you intentionally leave out?
In one sentence each: LegalAlphabet’s core user, core job-to-be-done, and “why now.”
Core user: Indian law students and early-career lawyers who want clean, verified roles fast.
JTBD: “Show me credible, current legal jobs/internships, minus spam.”
Why now: Hiring moved online, but quality control didn’t; verification + speed is the gap.
What’s the simplest metric you track daily (the “one number that matters”) for each product—and why that number?
Most effective distribution channel vs. one that failed?
Winner: Consistent daily posting + lightweight SEO (programmatic structure + fast pages).
Failed: Heavy WordPress theme marketing pages—looked great, loaded slow, converted poorly.
Hardest technical problem you personally solved (stack, constraints, unblocked)?
Monthly operating costs & burn control (as a student-founder): Lean infra on Plesk, domains, basic tooling; no salaried headcount. I keep burn low by shipping myself, templating ops, and deferring “nice-to-haves.”
Quality control for job postings—what gets rejected, and by whom?
Preventing platform pollution & escalation path: Anything unpaid (unless clearly educational and compliant), vague/no-comp details, non-legal roles, or duplicate posts. I do first-pass; flagged items get a second look before publish.
Wedge against large incumbents (hard to copy in 6 months):
If someone cloned the UI tomorrow, why do users stay? Hyper-focused vertical (law), manual verification, fast pages, and programmatic structure tuned for India’s legal market—plus community touchpoints and transparent standards.