Senior Software Engineer, Apollo.io

• 5+ years building and shipping production software, with real depth on both the frontend and backend of the same product
• Strong TypeScript and React skills, including complex, stateful UIs such as editors, canvases, builders, or real-time collaborative surfaces
• Solid backend and API design experience, ideally including event-driven or workflow systems where retries, idempotency, and observability matter
• Hands-on experience building with LLMs in production: agent loops, tool calling, context management, code generation, or evals. You know where models break and how to design around it
• Comfort making sound security calls on systems that run untrusted or generated code: sandboxing, delegated auth, scoped tokens, and secrets handling
• A track record of taking an ambiguous 0 to 1 product from rough prototype to something customers rely on, and making the scope-versus-quality calls that requires
• Product instinct and empathy for non-technical users. You care whether a RevOps lead can understand what their app is doing, not just whether the code is correct
• Genuine, current fluency with AI-assisted development and a high bar for quality and ownership

Desirable

• You will own major slices of Builder Studio end to end, across the builder experience customers see and the systems that make generated apps actually run
• You will work on problems most engineers have never touched: an agent that writes and edits software on a customer's behalf, a runtime that safely executes that code with the user's own Apollo permissions, and an interface that makes all of it understandable to someone who has never read a line of code
• Build the core Studio experience: the chat-driven build loop, live preview, canvas, and the publish and share flow, so a non-technical user can go from an idea to a working tool in minutes
• Shape how the agent turns a natural-language goal into a plan, a set of pages, databases, and workflows, and then safely applies follow-up edits without breaking what already works
• Design the runtime and workflow layer for generated apps, including triggers, scheduled jobs, retries, logging, and the line between deterministic steps and agentic steps
• Own delegated identity, permissions, secrets, and isolation so generated apps act with exactly the access the user has, and nothing more
• Expand "connect once, use anywhere" integrations across Apollo data (contacts, companies, lists) and external systems like Google Sheets, Google Drive, CRMs, and MCP-based connectors
• Make the relationships between pages, data, workflows, and agents legible in the UI, so customers trust what their app is doing
• Work directly with design partners and customers, turn their feedback into shipped improvements quickly, and help define what the product becomes
• Raise the quality bar on a fast-moving 0 to 1 team: set patterns, write the tests and evals that matter, and own reliability, performance, and cost of what you ship
• You treat AI-assisted development as a core part of how you work. You use agents to move faster on design, investigation, and implementation, with clear judgment about where to review closely, and you look for ways AI raises the leverage of the whole team
• On Builder Studio this is doubly true: you are building an AI that writes software, so your own instincts for where AI-generated code succeeds and fails directly shape the product
• Our tech stack:
• TypeScript and React on the front end; Ruby on Rails and Node.js on the backend; Cloudflare Workers and Durable Objects for the Builder Studio runtime; Python, MongoDB, and Elasticsearch across the wider platform; Kubernetes, Docker, and Terraform in infrastructure; GCP for cloud