Jeet Makwana

Working on an Insurtech platform, backend systems and data infrastructure. Most of my time goes into Scala services and data pipelines built with Temporal and Dagster. Data ingestion, transformation, replays, and the kind of architecture decisions that decide whether things scale cleanly or quietly fall apart six months later. Also led a large PDF migration project turning messy, unstructured insurance documents into clean. For analysis and internal tooling I work across Postgres, MySQL, Hex, and Retool, building the kind of dashboards that save the team hours instead of pinging an engineer every time someone needs a number. What I like here: the problems are deeper than "ship a feature." You start thinking in terms of correctness, replays, and what breaks when data volume goes 100x.

Spent a year and a half building a livestreaming product end-to-end. My work spanned the stack APIs, AWS infrastructure, frontend features, and the plumbing that makes a stream actually start when someone hits play. A lot of it was solving problems that only show up under real load: race conditions, network flakiness, and edge cases that pass every test until they don't. If startup life taught me how to ship fast, livestreaming taught me how to ship things that don't break in front of people.

Co-founded an HR-tech startup at 22. Two products, a lot to prove, and very little adult supervision. Emplitrack: GPS-based attendance and field tracking, plus a full Core HR suite (leave, expenses, CRM). The product solved a very real headache: companies couldn't actually trust whether their salespeople visited the clients on their reports. We made tracking accurate enough that businesses used it for payroll. (emplitrack.com) Emplicheck: real-time KYC verification, e-signatures for offer letters, and document checks at a fraction of what incumbents charged. Built for HR teams that wanted onboarding to take minutes, not days. (emplicheck.com) As the technical co-founder, I owned everything that touched code: architecture, infrastructure, deployments, the database, sometimes the customer support inbox. You learn fast when there's no one above you to escalate to. Two years of this taught me more than any job could — about systems design, yes, but also about why features ship, why customers leave, and why most technical decisions are business decisions wearing a costume.