01
Senior IC engineering, broadly defined.
I'm comfortable across product, systems, and AI work, and happy to keep widening that range. If the role asks for engineering judgement and care, I'd like to hear about it.
I'm open to inbound and curious about a wide range of engineering work. If you think there's a fit, I'd be glad to hear about the role. This page is here to make the first exchange a useful one.
I'm happy to explore widely and would rather expand my range than narrow it. Treat the list below as a few directions that have felt like a good fit so far, not as a fence.
I'm comfortable across product, systems, and AI work, and happy to keep widening that range. If the role asks for engineering judgement and care, I'd like to hear about it.
Smaller teams where decisions aren't already cemented and where shipping carefully is valued. I enjoy being close to the problem and to the people the product is for.
I'm interested in the parts that don't fit on a demo reel: retrieval, schemas, evaluation, the recovery paths around the model. I'd be glad to learn from teams further along on those problems.
Domain matters less to me than whether someone outside the building actually depends on the work. Consumer or B2B, established or early stage, all good.
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, AI products, and the parts of the work that don't show up in commits.