If You're Here for Products
Start with Job Data Pool if you want the canonical data layer. Then use the project archive for downstream products, experiments, and interfaces built on top of it.
Personal Website • Job Data Infrastructure • Developer Tooling
This is the most current picture of my work: the infrastructure layer, the products built on top of it, the research behind it, and the way I like to think through systems. If you want the shortest path into what I care about building, start here.
Start with Job Data Pool if you want the canonical data layer. Then use the project archive for downstream products, experiments, and interfaces built on top of it.
The research section is where I explain the systems underneath the product surfaces, especially around AI and job data.
Use the About page for how I work and the Resume page for the quick professional snapshot.
If you only open a handful of pages on this site, make it these. They are the clearest representation of what I am actively building and how the different pieces fit together.
Canonical job data infrastructure for the Job Pool ecosystem: public API, JSON Schemas, versioned datasets, and RFCs.
CIDR visualization tooling built to make large network spaces easier to inspect and explain.
Long-form writing on AI systems, scraping, responsible collection, and the infrastructure behind search.
Current products first, earlier experiments second, and a cleaner view of what still matters.
How I work, what I optimize for, and the kinds of systems I care most about building.
The core story is on this site. These are the supporting links people usually want after they have the main picture.
Some of my favorite work is the part users never see directly: the data layer, interfaces between systems, and the decisions that make products feel stable.
My undergraduate background in Mathematics-Computer Science at UC San Diego left me especially interested in functional programming, abstraction, and category theory as ways of reasoning about software.
That is why research lives here too. Writing is part of the work when the system deserves more than a demo, especially when the underlying ideas are as interesting as the product itself.