> Markdown version of [/jobs/ext/4625500-founding-infrastructure-engineer](https://www.wearedevelopers.com/jobs/ext/4625500-founding-infrastructure-engineer). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md). --- # Founding Infrastructure Engineer - **Company:** MATTERHAUL INC. - **Location:** San Francisco, CA, United States - **Experience:** Expert - **Contract:** Permanent contract - **Skills:** Artificial Intelligence, Airflow, Amazon Web Services, Amazon S3, Backup Devices, BigQuery, Software as a Service, Databases, Continuous Integration, Data Infrastructure, Extract Transform Load (ETL), Data Warehousing, Identity and Access Management, PostgreSQL, Node.Js, Online Transaction Processing, Redis, Service-Oriented Architecture, Data Streaming, TypeScript, Datadog, Pulumi, Amazon ElastiCache, Istio, Snowflake, Grafana, Amazon Virtual Private Cloud (VPC), Backend, Data Layers, Amazon Relational Database Service, Pgvector, Debezium, Kubernetes, Low Latency, Apache Flink, Sentry, Apache Kafka, Graphql, Statsig, Machine Learning Operations, Vertica, Cloudwatch, Api Gateway, Terraform, Data Pipelines, Amazon Redshift, Golang - **Published:** November 7, 2026 - **Apply:** https://www.juju.com/job/28_25197_6f600d85d96917409e48a578fd6c4dc7 ## About the Role Must have: * 7+ years building backend and infrastructure systems in production, including meaningful 0*1 platform work (not just operating someone else's platform). * Production Golang - not just side-project Golang. You've shipped, debugged, and operated Golang services that real customers depend on. * AWS at depth - VPC, IAM, RDS, S3, EKS/ECS, ALB/NLB, CloudWatch, Secrets Manager, KMS. You can make IaC (Terraform / Pulumi / CDK) decisions and live with them. * Kubernetes in production - not just kubectl apply. You've built, broken, and fixed clusters; you know when to reach for a service mesh and when not to. * Distributed-systems judgment - consistency models, idempotency, retries, backpressure, queueing, the failure modes of multi-region. You've debugged at least one outage that taught you something you still cite. * Data infrastructure experience - picked and run an OLTP database at scale, built or operated an ETL/ELT pipeline, and stood up a warehouse (Snowflake / BigQuery / Redshift / ClickHouse / Iceberg-on-S3 / equivalent). * Pragmatism about build-vs-buy. You've replaced custom orchestration with managed services and the other way around, and can explain why each was right. * Clear writing. This role makes durable decisions; we want them legible. Nice to have: * Multi-tenant SaaS at scale, including noisy-neighbor and per-tenant isolation work. * Familiarity with Effect.ts (we are heavy users) - or willingness to learn it; you don't need to love it, but you need to live with it for the parts of the codebase that stay TypeScript. * Experience with Temporal / Airflow / Dagster / Flink / Kafka / Debezium / dbt at production scale. * Streaming and CDC patterns; experience with Postgres logical replication. * AI/ML infrastructure: vector stores, GPU-backed inference, embedding pipelines, prompt/response observability. * Background in voice / telephony / document processing pipelines. ## Description 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., * 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, GitOps). 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, ElectricSQL proxy, healthcheck sidecar). Decide what stays, what merges, what gets rewritten. Push Golang as the language for core systems where it pays off - proxies, gateways, high-throughput pipelines, latency-sensitive paths - without forcing it where TypeScript/Effect is already a fit. * Data layer strategy - We're on Supabase Postgres with Drizzle today, plus pgvector for embeddings, S3 for blobs, Redis for rate-limit state. You will make the call on: + Primary OLTP path forward (managed Postgres? Aurora? read-replica strategy? connection pooling? per-tenant isolation patterns?) + Data warehousing (Snowflake, BigQuery, Redshift, ClickHouse, Iceberg-on-S3, something else) - we have none today and need one. + Vector / search - keep pgvector, or move to a dedicated store? + Cache & ephemeral state - formal Redis/ElastiCache tier vs. in-process. * Processing pipelines & async work - We currently run Effect.js workflow clusters plus a homegrown durable-streams service for everything async. It works but it's bespoke. You'll evaluate whether to harden it, augment it, or migrate selected workloads to off-the-shelf orchestration (Temporal, Airflow, Dagster, Flink, Kafka +Connect/Debezium for CDC, etc.) and build the ETL/ELT path into the warehouse from scratch. * Observability - We have Sentry, OpenTelemetry, and Statsig wired. You'll extend with metrics/dashboards (Grafana / CloudWatch / Datadog - your call), SLOs, on-call rotation, and runbooks. * Reliability & ops - Backups, DR, multi-AZ today and a credible multi-region story for tomorrow. Capacity planning. Cost ceilings. Security hardening (we already use OpenFGA for ReBAC and Clerk for authn - extend, don't unwind). * Engineering leverage - Local dev that works in 10 minutes. CI that's fast. Deploy that's safe. Paved roads so product engineers don't have to think about infra. You will write code. You will also make the architectural calls and document the "why" so the team can keep building after each decision., * Small founding team - under ten people - building the system distributor sales, procurement, and dispatch teams will run on. You will be the most senior infra voice in the room. * San Francisco - 4 days a week in the office. Foundational platform decisions go faster at a whiteboard with the team in the room. * We ship to production frequently and trust each other to do it. * We write specs and architecture docs before big changes. We expect the same of you.