01
Product and backend, not one or the other.
I've built pipelines and the interfaces that sit on top of them. I'd like to keep doing both instead of picking one.
I'm curious about a wide range of engineering work, including roles that don't map exactly onto what I've done before. This page exists to make the first exchange a useful one.
Four things I've noticed about the work I've enjoyed. They aren't requirements. If a role matches some of this, that's reason enough to write.
I've built pipelines and the interfaces that sit on top of them. I'd like to keep doing both instead of picking one.
I work best when I can follow a feature from the backend through to the UI. Small teams make that easier, but plenty of larger ones do it too.
Tool calling, retrieval, structured output, evaluation. Making it reliable takes more than passing a prompt through, and that's the part I enjoy.
I care more that someone outside the company depends on the work than what the domain is. Consumer or B2B, early or established.
A snapshot, not a fence. I pick up what a project needs and try to keep opinions about tools secondary to opinions about problems.
A few production systems shipped at Tessact and elsewhere, written up in a bit more depth than a bullet list.
Tools and experiments built outside of work, often where I prototype an idea before it finds a home in production.
How I think about systems and AI products, including the parts of the work that don't show up in commits.