> Markdown version of [/jobs/ext/4621955-staff-infrastructure-engineer](https://www.wearedevelopers.com/jobs/ext/4621955-staff-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). --- # Staff Infrastructure Engineer - **Company:** Ivo Inc. - **Location:** San Francisco, CA, United States - **Experience:** Expert - **Salary:** $287,000 - **Contract:** Permanent contract - **Skills:** Microsoft Word, Application Programming Interfaces (APIs), Amazon Web Services, Microsoft Azure, Cluster Analysis, Databases, Continuous Integration, Software Debugging, DevOps, Disaster Recovery, Distributed Systems, Failover, Github, Role-Based Access Control, Pulumi, Large Language Models, Backend, Kubernetes, Front End Software Development, Virtual Agents, Software Coding, Terraform, Docker - **Published:** November 7, 2026 - **Apply:** https://www.juju.com/job/28_25304_0ae1841cddeee552551986426e283497 ## About the Role * You love writing code, but you love having impact more: We're a team of engineers at heart, but our #1 goal is building the best possible product. That means making pragmatic choices and looking for 80/20 solutions. * Would describe yourself as being relentlessly resourceful. * You have a strong internal sense of urgency. You have a bias towards doing things today, rather than tomorrow. * Experience working in a startup environment is preferred but not required. * Are excited about the adventure of building a company! ## Description * An AI agent that lives in MS word and edits the document for you [2023] * Ditching imprecise embeddings models in favor of agentic RAG [2023] * Large-scale LLM-based legal fact extraction [2024] * A legal assistant that can search large contract databases, without sacrificing accuracy [2024] * Clustering legal documents descended from the same family [2025] * Automatic deviation analysis to locate buried risk in huge contract databases [2025] * Merging contracts with their amendments to make a time series of "composite" contracts (a customer actually cried when we showed her this) [2025], This list isn't a checklist, it's a direction. We don't need you to have done all of it - we need you excited to figure out the parts you haven't. * Run Kubernetes like it's your own startup within the startup - own multi-cluster, multi-region deployments across AWS/GCP/Azure, with failover and disaster recovery that actually works when it matters (not just on paper) * Build the tools that build our infra - internal tooling for spinning up and managing clusters, so dev-to-prod is consistent and nobody's hand-crafting environments at 2am * Figure out the right way to isolate workloads - ML vs. API traffic have very different needs; you'll design the strategy that balances cost, performance, and reliability without over-engineering it * Make security invisible, not annoying - RBAC, workload identity, secrets management, data residency, audit trails. Enterprise customers need to trust us; product velocity shouldn't suffer for it * Set SLOs that don't lie - define targets that are real, enforceable, and won't page you at 3am for nothing. Hold teams (including yourself) to them * Own the pipes - GitHub Actions for CI/CD, Pulumi for infra as code. If it ships, you had a hand in it * Keep Docker environments sane - across dev, staging, and prod, so "works on my machine" stops being a punchline * Go wherever the bug is - APIs, workers, jobs, frontend builds and performance. You're not siloed to "infra"; you debug end-to-end * Make everyone's day faster - faster builds, cleaner environments, less manual toil. If it's repetitive, automate it * Own uptime like it's personal - build observability that tells you what broke, why, and how often, before a customer has to tell you first * Lead when things go sideways - run incident response, write postmortems people actually read (and learn from), This isn't a "keep the lights on" role. You'll be building the system that keeps the company running. In addition to helping us run a solid, high-performance distributed system, we'd love someone who's as excited about LLMs as we are. You'd be deeply embedded into the engineering team and highly encouraged to push the frontiers. * You've actually lived in Kubernetes, not just deployed to it. You get cluster architecture, scheduling, networking, storage primitives, and the fun ways distributed systems fail * IaC and CI/CD are second nature - Pulumi or Terraform, Docker, GitHub Actions, and you've done it across multi-cluster, multi-region setups, not just a single happy-path environment * You think in failure modes. Not "will this break," but "when this breaks, what happens next" - and you design for that from day one * You can turn "the contract says X" into "the infra does X." Compliance and legal requirements don't stay abstract with you around - you translate them into real constraints * You're a DevOps/infra person at your core, with enough full-stack range to not get stuck when the bug crosses into backend or frontend territory * You debug like a detective. Systematic, relentless, not afraid to go five layers deep to find the real root cause * Ambiguity doesn't scare you. "Something's broken somewhere" is a starting point, not a blocker - you trace it across systems until you find it * Years of experience: 8+