Senior Software Engineer Ii, Enterprise Platform

Lila Sciences Lila Sciences · AI Frontier · San Francisco, CA · Software

Senior Software Engineer II, Enterprise Platform role at Lila Sciences, focusing on building the enterprise lifecycle and developer ecosystem for autonomous science platforms. This involves developing multi-tenancy, authorization, public APIs, SDKs, and agent integration systems to enable secure and scalable adoption of AI-driven scientific workflows for external customers and internal scientists. The role requires strong backend engineering experience, particularly in APIs, services, and platform infrastructure, with proficiency in Python, Kubernetes, and AWS.

What you'd actually do

  1. Build secure tenant isolation, authentication, authorization, and audit across customer organizations.
  2. Build the services behind tenant provisioning, self-serve administration, and the customer onboarding lifecycle.
  3. Own and evolve Lila's public APIs (REST, streaming, async) designed for both human developers and autonomous agents as first-class consumers.
  4. Build the integration paths that connect MCPs, agents, and data into the platform.

Skills

Required

  • 7+ years of backend software engineering
  • APIs
  • backend services
  • platform infrastructure
  • API design and versioning
  • multi-tenancy
  • authentication/authorization
  • backend services at scale
  • Python
  • FastAPI
  • Kubernetes
  • AWS
  • databases
  • developer experience
  • Ship working code regularly
  • Debug production issues
  • Own systems end-to-end
  • Work well across teams
  • Communicate tradeoffs clearly
  • Make decisions under ambiguity

Nice to have

  • Built or maintained multi-tenant SaaS platforms with audit, compliance, or isolation requirements (SOC 2, HIPAA, GxP, FedRAMP)
  • Worked on platforms serving scientific or laboratory data such as LIMS, ELN, bioinformatics, or related systems
  • understand the provenance and traceability requirements associated with scientific workflows
  • Shipped public developer platforms, APIs, or SDKs
  • MCP
  • OpenAPI
  • OIDC/OAuth 2.0
  • tenant isolation patterns (row-level security, schema per tenant, search-path isolation)
  • policy-based authorization (OPA)
  • externalized authz

What the JD emphasized

  • regulated (e.g. GxP, FedRAMP) deployments require
  • operational correctness in a regulated environment
  • audit, compliance, or isolation requirements (SOC 2, HIPAA, GxP, FedRAMP)