Job Opportunities API

WHY JOIN IVO? Every civilization runs on the same infrastructure: agreements between people who don't fully trust each other. Sumerians pressed them into clay. Romans carved them into stone. We bury them in 80-page PDFs. The way those agreements are reviewed hasn't changed in four thousand years - a human reads the whole thing and tries not to miss anything. We're building the AI that finally changes that. Ivo is the contract intelligence platform of choice for companies like Uber, Meta, Canva, IBM, and Shopify. We recently raised our Series B and have grown 800% over the last 12 months. ENGINEERING AT IVO Engineers at Ivo are inventors. Ivo was first-to-market with: - 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] THE ROLE: WHY, WHAT AND THE WHO Why? Infrastructure Engineers build the foundation for Ivo’s entire platform. Customers are cagey about their contracts, so each customer gets their isolated environment with containers, database, VPC, etc. Things break. Regions go down. Cloud and LLM providers have “incidents.” Customers still expect us to hit our SLAs. What? 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) Who? 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, networki