Careers

Join the team that signs the audit row.

Tallywyrm is hiring across engineering, GTM and design. The roles below are the same ones the founder mission operates by — every change ties to a PR, a deploy timestamp, and a post-deploy measurement window.

Founding team
Remote-first
Engineer / GTM / Design
How we hire
A note, a reply, a one-hour trial project, a hire.
Every inbound reads in one inbox — a real FinOps analyst, no SDR, no marketing nurture. The trial project is the same audit-row contract the production agent ships: one PR, one deploy timestamp, one post-deploy measurement. Same wording /methodology and /security publish.
01 · Culture

A small team operating by a single principle.

The same mission /about publishes restated for the hiring reader. Hiring without the principle is hiring without the company.

The founder mission
One audit row the invoice, the carbon report and the PR travel together on.
Same paragraph the JSON-LD WebPage.description carries — referenced once, surfaced into every surface that quotes the mission.

We started Tallywyrm because the multi-cloud bill had become the one invoice engineering, finance and sustainability could not reconcile against. The platform team shipped rightsizing numbers finance refused to sign off on. The FinOps analyst produced reports nobody knew how to action. The sustainability lead attributed cloud carbon to a factor nobody could trace back to a spend delta. We built Tallywyrm to close that loop: every verified saving ties to a single audit row — a PR, a deploy timestamp, a post-deploy measurement — and that row is the same artifact the invoice is computed against, the same artifact finance signs off on, and the same artifact the Scope 3 category 1 carbon report uses. The principle the company operates by is simple: a forecast is not a saving, a saving is not a verified saving, and a verified saving is not a saving finance can pay for until it has survived the post-deploy measurement window. Everything else on the site — /methodology, /security, /pricing, /customers — is a public-facing mapping of that principle.

A forecast is not a saving.

We do not publish an upside number finance has not signed off on. Every reported dollar is post-deploy.

Read-only by default.

The agent connects with read-only credentials brokered via the customer's existing OIDC trust. No write surface against the customer account.

One audit row, three consumers.

Finance signs off on it. The sustainability team reads it. The platform team merges its PR. Same row, same timestamp, same sha256.

Replies within one business day.

A real FinOps analyst reads every inbound — candidate, customer or procurement. No SDR, no marketing nurture behind the inbox.

02 · Open roles

Hiring across engineering, GTM and design.

One recruiting slate at a time. The role tile below is example copy — same shape a candidate would see when the company is hiring into the position for real.

The slate
One role, one inbox, one replies-within-one-business-day SLA.
A real FinOps analyst reads every inbound. Send a note via the role tile below; the same inbox the /about hiring tile and the /contact CTA both post to.
Founding Engineer — Verified-Savings Core

Owns the audit row end to end: the IaC PR loop, the post-deploy measurement window, and the read-only credential broker. Stack is TypeScript + Terraform on AWS / GCP / Azure.

Apply →
No open roles right now

Check back soon — the recruiting slate opens when the audit row contract calls for it. Send a speculative note through the “Apply →” tile above and we’ll keep it on file for the next slate.

Next step

Read the mission, then send a note.

The same mission /about publishes is the mission the role would be hired into — no separate recruiting narrative. Pricing is the same /pricing every other page on the site links to.