> Markdown version of [/jobs/ext/2391548-senior-platform-engineer](https://www.wearedevelopers.com/jobs/ext/2391548-senior-platform-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). --- # Senior Platform Engineer - **Company:** RIFF AI INC - **Location:** San Francisco, CA, United States (Remote available) - **Experience:** Expert - **Salary:** $150,000.0 - $300,000.0 - **Contract:** Permanent contract - **Skills:** Application Programming Interfaces (APIs), Business Analytics Applications, Audit Trail, Big Data, Continuous Integration, Distributed Systems, Identity and Access Management, Session Initiation Protocols, Python (Programming Language), PostgreSQL, Role-Based Access Control, Single Sign-On, Software Engineering, Data Streaming, Systems Integration, Twilio, WebSocket, WebRTC, Datadog, Data Logging, Real Time Systems, Large Language Models, Multi-Agent Systems, Audio Streaming, Backend, Fastapi, Kubernetes, Information Technology, Low Latency, Performance Monitor - **Published:** August 11, 2026 - **Apply:** https://www.indeed.com/viewjob?jk=feb08866252f0092 ## About the Role * 5+ years of hands-on experience building and operating production systems, with strong backend and distributed systems fundamentals. * Proven experience with cloud platforms, infrastructure as code, and container orchestration: you've run Kubernetes in production, not just in a tutorial. * Real-time systems depth: you understand latency budgets, streaming, backpressure, and what makes a live audio conversation different from a request-response API. * Experience with observability tooling (SigNoz, OpenTelemetry, or similar) and with incident response: you've been paged, found root cause, and made the pager quieter afterward. * Pride in building reliable, maintainable, and secure systems that scale, and the judgment to know when boring technology is the right answer. * High agency: you drive outcomes in a high-autonomy environment, find creative ways around obstacles, and don't wait to be told what matters. * Degree in computer science or a related field, or equivalent professional experience. Even better... * Experience building enterprise features: SSO, RBAC, IAM, audit logs, data isolation, or compliance-adjacent systems * Production experience with LLMs, agent frameworks, retrieval, or evaluation systems * Telephony or streaming audio experience: Twilio, WebRTC, SIP, or contact center integrations * Experience with large-scale data systems, analytics platforms, or ML-powered product features * Experience building developer platforms, SDKs, or internal tooling other engineers love * Leadership experience on technical projects or teams How we work Small teams, real ownership. You'll have peers to pair with and review your work, and you'll review theirs. We review all code, we write things down, and we'd rather hear an honest "I don't know yet" than a confident wrong answer. ## Description While Agent Engineers own individual client deliveries, you own the platform underneath all of them: the runtime that agents execute on, the voice infrastructure that keeps live calls fast and stable, the enterprise capabilities that get us through security reviews, and the intelligence layer that turns millions of conversations into insight. This is the highest-leverage engineering seat in the company: every improvement you ship reaches every client at once. You'll work directly with the founder on architecture and own your decisions end to end, from design through production and the incident channel. What you'll do * Build the agent platform primitives. Design and evolve the runtime, orchestration engine, and the systems behind Agent Studio: how agents are defined from written procedures, how they reason and take actions, and how guardrails make out-of-bounds behavior impossible rather than unlikely. Agent development is an evolution of software development, and you'll be building the tools it requires. * Own the voice infrastructure. Real-time audio streaming over WebSockets, STT and TTS integration at low latency, and the hard parts of live conversation: interruptions, disconnects, transfers, and telephony integrations that pick up and place calls reliably at growing volume. * Form the foundation of enterprise trust. Clients hand us regulated conversations with their own customers. You'll build and uphold the capabilities that make that possible: RBAC, access management, audit logs, data isolation, and integrations that embed into complex client environments while surviving their security reviews. * Build the evaluation layer. We believe evaluation methodology, not model capability, is the bottleneck, and you'll own the system that proves it: the DeepEval-driven suite that replays real conversations against every change, simulation of the scenarios we haven't seen yet, and experimentation frameworks that let us A/B test agent behavior and make changes with evidence instead of intuition. Every release gates on what you build here. * Build the observability layer. Observability goes beyond logging. You'll extend Reflect so that every agent decision is traceable: what the system knew at each moment, which instructions the model was given, and why it responded the way it did. Add proactive monitoring that surfaces regressions, drift, and new conversation patterns before a client notices, and turn millions of calls into insight the whole company acts on. * Close the feedback loop. Connect what evaluation and observability find back into how agents improve: recurring failure modes become new eval cases, production patterns reshape procedures, and agents get measurably better over time. * Keep the platform fast, reliable, and boring to operate. Own Kubernetes, ArgoCD-driven GitOps deployments, CI/CD, and observability with SigNoz. Build the self-serve infrastructure that lets the rest of engineering ship without waiting on you, and lead incident response and postmortems when things break. What we work with Python with FastAPI, PostgreSQL, Temporal for background workflows, WebSockets holding real-time conversations open, and STT and TTS providers on the speech side, with LLMs via OpenAI and similar underneath. Everything runs on Kubernetes with ArgoCD-driven GitOps deployments, SigNoz for observability, DeepEval driving the eval suite our CI runs before anything reaches production, Ory and OpenFGA for identity and access management, and a lot of beautifully built internal agent architecture underneath., * Trust: We do the right thing, especially when nobody is checking. Clients hand us regulated conversations with their own customers, and we earn that every day. * Transparency: We write things down, share the real numbers, and say "I don't know yet" out loud, with each other and with clients. * Technically best solution: We choose what's right, not what's easiest or trendiest. When we notice we got it wrong, we fix it. * Decisiveness: We decide quickly with the information we have, commit, and correct course fast when reality disagrees. * Simplicity: We keep systems, processes, and words simple. Complexity is a cost we pay only when it clearly buys something. ## Related Videos - [Shipping Faster with Less: Render on Cloud Hosting, AI Workloads, and the Future of DevOps](https://www.wearedevelopers.com/videos/1894-shipping-faster-with-less-render-on-cloud-hosting-ai-workloads-and-the-future-of-devops) - [Debugging in the Dark](https://www.wearedevelopers.com/videos/1658-debugging-in-the-dark) - [20 billion requests a week: Upgrading Twilio's API gateway at scale](https://www.wearedevelopers.com/videos/100234-20-billion-requests-a-week-upgrading-twilio-s-api-gateway-at-scale) - [Transforming Education: A Journey from interactive Markdown to Remote-Labs](https://www.wearedevelopers.com/videos/941-transforming-education-a-journey-from-interactive-markdown-to-remote-labs) - [API‑First: How Twilio Designs for Developers - Justin Kitagawa (Twilio)](https://www.wearedevelopers.com/videos/1801-api-first-how-twilio-designs-for-developers-justin-kitagawa-twilio) - [Hello JARVIS - Building Voice Interfaces for Your LLMS](https://www.wearedevelopers.com/videos/1641-hello-jarvis-building-voice-interfaces-for-your-llms) ## Related Articles - [How We Built a Worry-Free System That Runs for 10+ Years – And What We’d Do Again](https://www.wearedevelopers.com/magazine/751-how-we-built-a-worry-free-system-that-runs-for-10-years-and-what-we-d-do-again) - [Dev Digest 121 - AI goes offline](https://www.wearedevelopers.com/magazine/456-dev-digest-121-ai-goes-offline) - [Dev Digest 120 - Apple and peers](https://www.wearedevelopers.com/magazine/455-dev-digest-120-apple-and-peers) - [Navigating the AI Shift](https://www.wearedevelopers.com/magazine/629-navigating-the-ai-shift) - [Dev Digest 137 - AI'm not sure about this](https://www.wearedevelopers.com/magazine/485-dev-digest-137-ai-m-not-sure-about-this) - [Dev Digest 132 - Binging WADFlix?](https://www.wearedevelopers.com/magazine/473-dev-digest-132-binging-wadflix)