Nithin Peter

I work with the founders. The main thing I built is an interviewer that runs a research call by itself. It records, transcribes and translates as the call goes. Around it there are agents that ask follow-ups, write the insight report, and let you query a pile of transcripts in ordinary language. Studies run to a few hundred interviews, often 20 to 45 minutes each, so the report has to shrink that a lot. I wired the agents into the rest of the product with MCP. Much of how the team builds this now started there.

Core team on a meeting product. Volume is the thing: millions of meetings a month. I built insight generation over the transcripts, and a chat that can look across several meetings rather than one. Spaces is the organising layer, also mine. So is the desktop app that sits in the meeting and transcribes it, which I wrote in Swift. I tended to own a feature the whole way: React and TypeScript on the front, Node, GraphQL and Temporal behind it, then whatever broke once it was live.

Product engineering in Sydney for four years. React, TypeScript, a shared design system, and a release process with a lot of checkpoints. I spent a lot of time on tests, on performance, and on how the frontend talked to APIs. Day to day I was with designers, PMs, and backend and platform engineers.

Financial software, on the frontend. I built a UI toolkit that a few IRESS products shared. I worked on the redesign of Xplan. A fair amount of the job was accessibility, tests, and the structure of the frontend.

Founding engineer. Small team. I built the admin app customer support used to review accounts, approve people, and watch signups and payments. I also worked on the main web app and the mobile site.

Propatrol

Property research for Australian buyers, from the listing link through to the contract

propatrol.co

Courtab

An app for planning an event, collecting RSVPs, and splitting the cost

courtab.app

Jest Run-It

A VS Code extension for running one Jest test instead of the whole suite

Source