Senior Software Engineer II, Enterprise Auth Platform

Your Impact at LILA

We're hiring a Senior Software Engineer II, Enterprise Auth Platform to own critical systems across two areas: the enterprise lifecycle (multi-tenancy, auth, auditability) and the developer ecosystem (public APIs, SDKs, MCPs, and bring-your-own integrations) that let customers and developers build on Lila. Our internal scientists across both physical and life sciences are first-class customers of this platform, so you'll build for them as directly as for external developers.

This is a high-autonomy role: you'll own outcomes, ship regularly, and operate with technical judgment about tradeoffs.

What You'll Be Building

• Multi-Tenancy & Authorization. Build secure tenant isolation, authentication, authorization, and audit across customer organizations. Implement the access boundaries and isolation guarantees that enterprise and regulated (e.g. GxP, FedRAMP) deployments require. Build resilient backend services in Python/FastAPI. Own schema design for multi-tenant data, tenant-aware query patterns, and operational correctness in a regulated environment.
• Tenant Self-Serve & Lifecycle. Build the services behind tenant provisioning, self-serve administration, and the customer onboarding lifecycle. Support billing, pricing, and metering surfaces for enterprise customers.
• Public & Agent-Facing APIs. Own and evolve Lila's public APIs (REST, streaming, async) designed for both human developers and autonomous agents as first-class consumers. Ship SDKs and define the tool/function interfaces agents call.
• MCP & Agent Integration. Build the integration paths that connect MCPs, agents, and data into the platform — including how customers bring their own MCPs, agents, and data, and how those integrations are scoped, isolated, and trusted within a tenant.

Qualifications:

• 7+ years of backend software engineering, with meaningful experience in APIs, backend services, or platform infrastructure.
• Strong expertise in one or more of: API design and versioning, multi-tenancy, authentication/authorization, or backend services at scale.
• Solid in Python (FastAPI), Kubernetes, AWS, databases (SQL or document).
• You care about developer experience — you know what makes APIs easy or painful. You write clear errors and think about backward compatibility.
• Ship working code regularly. Debug production issues. Own systems end-to-end.
• Work well across teams you'll have real overlap with infra, data, apps, and science teams. Our internal scientists, across both physical and life sciences, are first-class customers of the platform, so you'll build for them as directly as for external developers. Communicate tradeoffs clearly and make decisions under ambiguity.

What You'll Need to Succeed

• 7+ years of backend software engineering, with meaningful experience in APIs, backend services, or platform infrastructure.
• Strong expertise in one or more of: API design and versioning, multi-tenancy, authentication/authorization, or backend services at scale.
• Solid in Python (FastAPI), Kubernetes, AWS, databases (SQL or document).
• You care about developer experience — you know what makes APIs easy or painful. You write clear errors and think about backward compatibility.
• Ship working code regularly. Debug production issues. Own systems end-to-end.
• Work well across teams you'll have real overlap with infra, data, apps, and science teams. Our internal scientists, across both physical and life sciences, are first-class customers of the platform, so you'll build for them as directly as for external developers. Communicate tradeoffs clearly and make decisions under ambiguity.

Bonus Points For

• Built or maintained multi-tenant SaaS platforms with audit, compliance, or isolation requirements (SOC 2, HIPAA, GxP, FedRAMP).
• Shipped public developer platforms, APIs, or SDKs and understand what makes integrations sticky.
• Familiarity with MCP, OpenAPI, or OIDC/OAuth 2.0.
• Worked on tenant isolation patterns (row-level security, schema per tenant, search-path isolation).
• Experience with policy-based authorization (OPA) or externalized authz.