Software Engineer, Infrastructure – San Francisco

About Flow

Flow Engineering is building a requirements platform for modern engineering teams, helping them design, build, and verify complex systems in an iterative way. After a recent Series A, the team is scaling the product from thousands of users to hundreds of thousands while holding a high bar on reliability and speed.

Flow is hiring a Software Engineer with an infrastructure focus to build and scale the core platform behind Flow. You will own services and infrastructure that let “agentic systems engineers” and product teams rely on Flow in their day-to-day work.

You will join a small, senior, high-ownership team that values speed, ownership, and strong fundamentals: ship v1s quickly, learn, and iterate.

• Design, build, and operate backend services and platform primitives that support complex engineering workflows and collaboration at scale.

• Scale Flow from thousands of users to hundreds of thousands, improving performance, reliability, observability, and security across the stack.

• Own and evolve CI/CD pipelines, test infrastructure, and internal tooling so the team can ship quickly and safely.

• Collaborate with frontend and AI engineers to define APIs, data models, and integration points that are robust and easy to evolve.

• Contribute to architectural decisions and technical direction as the product and customer base grow.

• 3+ years of software engineering experience building and operating production systems in a cloud environment (e.g., AWS or GCP).

• Strong understanding of systems design, distributed systems, reliability, observability, and security best practices.

• Experience with containerization and infrastructure-as-code tooling (e.g., Docker, Terraform, or similar).

• Comfortable owning projects end-to-end in a fast-paced environment and making pragmatic tradeoffs under ambiguity.

• Collaborative, low-ego, and excited to work closely with product, design, and customer-facing teams.

• Type Script, Node.js, and React on the application side (with a strong bias toward type safety).

• Postgres and other managed cloud services for persistence and messaging.

• Containers, Terraform (or similar), and a major cloud provider (AWS/GCP) for infrastructure.

• Speed over everything: ship v1s quickly, learn, and iterate rather than chasing perfection.

• Own, downscope, ship, iterate: clear ownership, smallest real thing, tight feedback loops.

• Fundamentals done well: simple, repeatable systems that let us move fast without breaking trust.

• Competitive salary and meaningful equity.

• Health, dental, and vision coverage.

• Flexible time off and support for travel to customers when it matters (“get on a plane”).