Basketball
UConn, specifically, and to a degree that mildly concerns the people around me. I know more about the program’s history than is strictly useful.
Tristan Couvares
I’ve helped take companies from a dozen people to a few hundred, been close enough to a billion-dollar IPO to feel it, and I still write code most weeks to fix things that annoy me.
A recurring operating question, made testable.
An interactive, synthetic model for exploring hiring demand, recruiting throughput, and backlog assumptions.
A weekend project before the feature was everywhere.
Wired a language model into iMessage, back when that was a weekend project rather than a product in everything.
Boring. Finicky. Used constantly.
Reshapes messy CSV exports into the exact form a finicky destination will actually accept.
Because backtracking is quietly satisfying.
A backtracking solver, written mostly because backtracking is quietly satisfying to watch work.
The receipts
Close enough to watch an early bet grow into a billion-dollar public company.
Helped the organization grow from around a dozen people to roughly 250.
Ran a small operation connecting people with companies most had not heard of yet.
Working on the people and operating systems behind a company building AI products.
The titles vary. The job is always the same: be right about people early.
In public
A practical boundary for take-homes, one-way interviews, and other hiring assessments.
Read →On interdependence, venture funding, and what happens when the music stops.
Read →A contemporaneous argument against the loudest version of the 2016 bubble chorus.
Read →About
I’ve spent fifteen-odd years doing essentially one thing under a rotating set of titles: being early on people and companies, when the evidence is thin and the price is low. The seat changes — the instinct is older than any of the jobs. I was a kid taking machines apart, a teenager posting code to forums, a sysadmin before I could legally drink.
I think about the world in terms of edges and asymmetries: where is something mispriced, what’s the downside if I’m wrong, what’s the upside if I’m right. That frame works on hiring, on markets, on code, on nearly everything I find interesting. I’d rather be dangerous across a few domains than narrow in exactly one.
Currently
I’m working on the people and operating systems behind AI products, taking algorithms coursework for fun, and turning recurring recruiting problems into small tools that can be tested in public.
Updated August 2026
Otherwise
UConn, specifically, and to a degree that mildly concerns the people around me. I know more about the program’s history than is strictly useful.
How scarcity gets priced when almost nobody is trading. I collect a few things, mostly as an excuse to keep thinking about why they’re worth what they’re worth.
Priors, base rates, and the gap between a good decision and a good outcome. Most people confuse the two; I try not to.
I take real CS coursework for fun — an algorithms sequence out of Stanford, a Python specialization — because I’d rather understand the machine than rent it.
Your move
I’m easy to find and I read everything, even when I’m slow to reply. I’m especially interested in AI operating problems, talent systems, and unusually early bets — though arguments about basketball are always welcome.
hello@tristancouvares.com