Senior / Staff Platform Engineer (AWS · Infrastructure · Distributed System)

Technologies we use

About the project

Your responsibilities

• Own all AWS infrastructure end-to-end — architecture, cost, security, reliability, and compliance. No infrastructure team above you.
• Design and maintain CI/CD pipelines that let engineers ship confidently and fast — zero manual steps from commit to production
• Build monitoring and alerting that surfaces real problems early: queue depth, processing failures, latency spikes, delivery anomalies — dashboards that tell you what’s actually wrong
• Manage PostgreSQL at scale — configuration, connection pooling, migration strategy, performance, backup and restore
• Keep real-time and async processing components healthy across Lambda, SQS, Redis, S3, and the services that connect them
• Enforce IAM least-privilege across the system — service-to-service trust, secrets management, network isolation
• Manage environments (dev / staging / prod) with infrastructure parity and clean promotion paths
• Own cost visibility and optimization across a growing AWS footprint
• Use modern AI tooling to accelerate infrastructure work and experimentation

Our requirements

• 6+ years building and running production infrastructure.
• Deep AWS knowledge and strong operational instincts.
• Infrastructure as Code only — no manual steps, no console dependency.
• Strong distributed systems thinking: ordering, retries, idempotency, recovery.
• Experience with PostgreSQL, Lambda, SQS, Redis, S3, and CI/CD.
• Obsessed with reliability, security, visibility, and automation.
• Comfortable owning critical infrastructure end to end.

This is how we organize our work

This is how we work

What we offer

• Competitive B2B compensation based on experience
• Equity — own a piece of what you build
• Fully remote work in an async-first environment
• Direct collaboration with the founding team
• High autonomy and fast decision-making
• Small team, outsized impact
• Work on technology that is genuinely novel
• End-to-end ownership across product, systems, and production
• Protocols don’t get built by committees. They get built by small teams who understood the problem before anyone else did

What You Bring

• Deep AWS expertise across compute, messaging, storage, networking, and observability — not just familiarity, but operational instinct built from running things in production
• Strong IaC discipline — CDK, SAM, or CloudFormation; you version everything, you don’t click in consoles
• Understanding of distributed systems fundamentals: ordering guarantees, idempotency, at-least-once delivery, outbox patterns, partial failure recovery
• Experience operating event-driven architectures under load — you know what failure looks like before it becomes an incident
• Enough application-layer literacy to read TypeScript/Node.js code and understand what a service is doing, not just that it’s running
• Strong opinions about observability — structured logging, distributed tracing, dashboards built for on-call humans at 3am