Staff Software Engineer (Tech Lead)

OpenLoop is a telehealth support solutions company that aims to bring care anywhere. They are seeking a Technical Lead to own the architecture and execution of their AI-driven platform, involving hands-on leadership and collaboration with a senior engineering team.

Responsibilities:

• Own System Architecture: Design and evolve distributed systems on GCP (Cloud Run, Pub/Sub, BigQuery), making final decisions on service boundaries, data models, and technology trade-offs across Go, Python, and TypeScript
• AI & LLM Strategy: Lead hands-on integration of AI systems, including open-source LLMs, embeddings, and speech models. Define prompt optimization, evaluation strategies, and safety practices using tools like LangFuse
• Operational Excellence: Champion observability, reliability, and scale. Oversee event-driven ingestion and automated QA pipelines for call transcripts and healthcare data (FHIR / Medplum)
• Delivery & Execution: Contribute code to critical paths while leading major technical initiatives. Identify gaps, unblock teams, and drive projects to completion
• Cross-Functional Leadership: Translate complex technical constraints into clear options and trade-offs for Product, Design, and Clinical Operations

Requirements:

• 8+ years of software engineering experience, with 2+ years leading projects or serving as a Tech Lead
• Staff-level scope or equivalent technical impact
• Strong LLM experience in production environments (hands-on required)
• Expert-level proficiency in Go, Python, or TypeScript/Node, with the ability to review code across the stack
• Deep experience with distributed systems, containerized deployments (Docker, Kubernetes, Cloud Run), and event-driven architectures
• Experience hosting or integrating open-source models (e.g., vLLM, Ollama), with a strong understanding of RAG architectures
• Background in regulated environments (HIPAA, SOC 2) or healthcare data standards (FHIR, HL7)
• Strong written and verbal communication skills, including writing RFCs and explaining technical strategy to non-technical stakeholders