No open roles.
FinOps LLM is early. We are not hiring against a standing headcount plan right now.
If you have shipped LLM gateways, cost attribution systems, billing reconciliation, or AI FinOps workflows, you can still send a short note and one thing you built.
What we'd want to see
There is no role to apply to, so a note is worth sending only if you have done the specific work. Concretely: an LLM gateway or proxy that survived production traffic, a cost attribution system that reconciled to an actual invoice, billing or usage pipelines where the numbers had to be defensible to finance, or FinOps practice built for teams rather than for a dashboard. One paragraph on what you built, what it cost you to learn, and what you would do differently is more useful than a resume.
How the work is shaped
The problems here are mostly data-correctness problems dressed as cost problems. Provider exports disagree with invoices at the edges, retries and agent runs make per-call accounting misleading, and a tagging scheme that nobody enforces decays into an unallocated bucket within a quarter. Enjoying that kind of reconciliation work — the part where you find out why two numbers that should match don't — matters more than familiarity with any particular provider's API.
What to expect if you write
A reply either way, usually within a week. If there is something to discuss, it starts with a conversation about a system you have already built rather than a take-home exercise. If there isn't, we will say so plainly instead of leaving the note open; keeping a pipeline warm for a headcount plan that does not exist wastes your time more than ours.
Contract and advisory arrangements are also possible where a defined piece of work exists — attribution instrumentation, invoice reconciliation, or a gateway migration — even when there is no permanent role.