Founding Infrastructure Engineer

Rebuild Matter haul's infrastructure and core systems from zero — AWS, Kubernetes, Golang, and the data and pipeline choices that the rest of engineering will build on for years. Founding infra seat with the architectural calls in your hands.

Full-time

Matter haul is building the AI-native operating system for the physical goods supply chain.

Distributors and manufacturers run on disconnected systems, manual re-entry, and tribal knowledge that never gets captured. The software that was supposed to fix that never did. We're changing that.

Matter haul sits above the systems these businesses already run — unifying their data, capturing the operational context legacy software misses, and deploying AI agents across quoting, order entry, procurement, dispatch, and customer updates. No rip and replace. Teams go live fast, and Matter haul expands until it becomes the system the business runs on.

That's the wedge. The vision is bigger: a purpose-built, AI-native platform that doesn't just automate what ERPs do today — it does what they were never capable of.

We're a small team with deep roots in this space. Our founders grew up in the trades and spent careers building products for the physical world at Stripe, Verkada, and Cisco Meraki. We're based in San Francisco's SOMA/Transbay neighborhood, in-office four days a week, and we spend real time with the distributors and operators we build for.

We move fast, ship often, and build for the people who actually do the work.

Three things are true at once and rarely line up:

• AI has stopped being an experiment. A year ago this was a pilot conversation. Today, executives are being asked why they aren't deploying AI in operations.
• Legacy ERPs are no longer defensible. The customers know it. Their leadership teams are openly looking for a way out.
• The supply‑chain trauma of the last five years is fresh. The companies that move physical goods lived through it in a way software companies didn't. They want visibility and automation, and they aren't going back.

The window is open. Windows like this don't stay open.

Today we deploy to Railway:
Docker‑per‑service, health checks, no Kubernetes, no IaC, shared Supabase Postgres, no data warehouse, no managed queue. It got us here. It will not get us into a distributor's critical workflow at scale, and it will not carry us through a Series A.

The next phase of the company is the platform — one cohesive system, not five tools that share a login. AI that shines. Workloads that customers can't operate without. That requires infrastructure built for it.

We're hiring a founding infrastructure engineer to rebuild our infra and core systems from zero: AWS + Kubernetes, clean service boundaries, Golang for core systems, and a deliberate set of choices around databases, data warehousing, and processing pipelines. You'll set the platform direction the rest of engineering builds on for years.

This is a high‑leverage seat. You will not be re‑skinning a Helm chart someone else wrote.

Year one, concretely:

• AWS landing zone — accounts, networking, IAM, KMS, secrets, CI/CD, cost controls. Codified in IaC (Terraform / Pulumi / CDK — your call, with rationale).
• Kubernetes platform — EKS or equivalent, with the supporting bits (ingress, service mesh if warranted, autoscaling, image pipeline, Git Ops). Make boring choices that work.
• Service architecture — Carve crisp boundaries across what is today a mixed Golang + Node/Effect.ts service fleet (API gateway, GraphQL, workflow cluster, public catalog, durable streams, OpenFGA, telemetry, Electric SQL proxy, health check sidecar). Decide what stays, what merges, what gets rewritten. Push Golang as the language for core systems where it pays off — proxies, gateways,…