Staff Engineer, Enterprise Externalization

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must only include sections where there is real specific content. We need to parse the posting. The posting includes: - Intro: "Your Impact at LILA ..." description of role. - "What You'll Be Building" section: details about responsibilities. - "What You'll Need To Succeed": qualifications/requirements. - "Bonus Points For You": additional nice-to-have. - "Compensation": includes base compensation, bonus potential, equity, benefits details, salary range. - "About LILA": company description. - "Guided by our core values..." etc. - "We’re All In": EEO statement (should be removed as boilerplate). - "A Note to Agencies": also boilerplate. We need to remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. There's no explicit application instructions but the EEO and note to agencies are boilerplate; remove them. We need to preserve all substantive information. We need to use

for section headings. Use

• for any list of duties/requirements/benefits, and

  for prose. We need to decide sections: About the role (intro), Responsibilities (What You'll Be Building), Requirements (What You'll Need To Succeed), Bonus Points (maybe Skills?), Benefits, Pay (compensation). Schedule not present, so omit. We need to avoid headings with filler like "commensurate with experience". Not present. We need to include Pay section only if posting states compensation. It does: "CompensationWe offer competitive base compensation with bonus potential and generous early-stage equity. Your final offer will reflect your background, expertise, and expected impact.U.S. Benefits.... Expected Base Salary Range: $192,000 USD - $272,000 USD". So we have Pay and Benefits. We need to separate Benefits and Pay? The instruction: Use headings for Benefits, Pay, Schedule. So we can have a Benefits section and a Pay section. However the posting lumps benefits and compensation together. We could split: Benefits: list of benefits (medical, dental, vision, etc). Pay: base salary range, bonus potential, equity. We need to avoid repeating job title as heading. We need to output only HTML fragment. Let's extract content. Intro: "Your Impact at LILA Lila Sciences is building the infrastructure for autonomous science — AI systems that design experiments, run them in physical labs, and close the loop across life sciences, chemistry, and materials science. Our platform enables this to operate reliably at scale for external customers who require security, auditability, and operational rigor. We’re hiring a Staff Engineer, Enterprise Platform to build the foundational systems that make Lila ready for the world’s largest pharmaceutical and research organizations. Today we have the beginnings of multi-tenancy, identity and granular permissions and scopes, audit infrastructure, usage and billing. Enterprise customers require significantly more. You will drive core enterprise capabilities to production: multi-tenancy and tenant isolation, enterprise identity and permissions to support the full lifecycle of the Lila Platform, metering and billing infrastructure, audit logging, etc. You will push the frontier — building agentic AI-powered systems for self-service tenant management, intelligent customer observability, automated compliance workflows, Lila SDK, MCP, and AI-native external APIs that let customers and third-party agents interact programmatically with Lila's platform. This is a deeply technical senior individual contributor role focused on defining and building correct, secure, and scalable platform infrastructure. This is a high-autonomy, high-impact role. We move fast, ship weekly, and expect engineers who thrive in ambiguity not ones who wait for requirements to be handed to them. You will own outcomes." That's the "About the role" (intro). We'll put in

  About the role

  then

  with that text. Next: "What You'll Be Building Enterprise infrastructure is foundational to making autonomous science deployable in the real world. The systems built in this role will determine how large organizations safely adopt, govern, and scale AI-driven scientific workflows across teams, data domains, and regulatory environments. You’ll help define the platform primitives that make that possible. Design and evolve the core identity systems powering Lila’s enterprise platform — organizations, groups, roles, SCIM provisioning, seat lifecycle management, and fine-grained authorization across experiments, datasets, models, and scientific workflows. You’ll define how tenant isolation, policy evaluation, and access governance work across the platform.Design tenant-aware schemas, metadata systems, and platform primitives that support highly heterogeneous scientific data across life sciences and materials science workloads. Drive architectural decisions around scalability, reliability, retention, and operational correctness.Architect systems for tenant provisioning, usage metering, billing, data migrations, compliance workflows, and operational automation. Push toward self-service and agentic operational workflows that reduce manual intervention while maintaining strong safety guarantees.Operate as a senior technical leader across platform engineering, infrastructure, security, AI/ML, and scientific application teams. This is a hands-on Principal Engineer role with broad architectural influence, high autonomy, and direct ownership of critical platform systems." We can treat as Responsibilities. Use

  Responsibilities

  then maybe
  • for each bullet? The text is prose with some bullet-like sentences separated by periods. Could convert to list items. But we need to preserve all substantive information; we can keep as prose

    . However instruction: Use

    • for any list of duties/requirements/benefits. This section is a list of duties; we could break into list items. Let's parse sentences: - Enterprise infrastructure is foundational to making autonomous science deployable in the real world. The systems built in this role will determine how large organizations safely adopt, govern, and scale AI-driven scientific workflows across teams, data domains, and regulatory environments. You’ll help define the platform primitives that make that possible. - Design and evolve the core identity systems powering Lila’s enterprise platform — organizations, groups, roles, SCIM provisioning, seat lifecycle management, and fine-grained authorization across experiments, datasets, models, and scientific workflows. You’ll define how tenant isolation, policy evaluation, and access governance work across the platform. - Design tenant-aware schemas, metadata systems, and platform primitives that support highly heterogeneous scientific data across life sciences and materials science workloads. Drive architectural decisions around scalability, reliability, retention, and operational correctness. - Architect systems for tenant provisioning, usage metering, billing, data migrations, compliance workflows, and operational automation. Push toward self-service and agentic operational workflows that reduce manual intervention while maintaining strong safety guarantees. - Operate as a senior technical leader across platform engineering, infrastructure, security, AI/ML, and scientific application teams. This is a hands-on Principal Engineer role with broad architectural influence, high autonomy, and direct ownership of critical platform systems. We can make each as
    • . Good. Next: "What You'll Need To Succeed 8+ years of software development experience, with a focus on Enterprise SaaS product developmentDeep expertise in enterprise SaaS platform systems: authentication/authorization (OAuth 2.0, OIDC, SAML), multi-tenancy, RBAC, billing/metering, configurations, SDK and APIsExperience with modern cloud-native architectures (Kubernetes, Terraform, AWS/GCP) and event-driven systems, familiarity with infrastructure-as-code and containerized deploymentsTrack record building enterprise platforms in high-growth environments where speed-to-value mattered as much as long-term architectureStrong cross-functional communication skills and the ability to influence architecture across teams.Hands-on coding in Python and modern backend frameworks (FastAPI, async Python)BS, MS, or Ph.D. in Computer Science or a related field of study" We need to separate into list items. Let's split by sentences or phrases. - 8+ years of software development experience, with a focus on Enterprise SaaS product development - Deep expertise in enterprise SaaS platform systems: authentication/authorization (OAuth 2.0, OIDC, SAML), multi-tenancy, RBAC, billing/metering, configurations, SDK and APIs - Experience with modern cloud-native architectures (Kubernetes, Terraform, AWS/GCP) and event-driven systems, familiarity with infrastructure-as-code and containerized deployments - Track record building enterprise platforms in high-growth environments where speed-to-value mattered as much as long-term architecture - Strong cross-functional communication skills and the ability to influence architecture across teams. - Hands-on coding in Python and modern backend frameworks (FastAPI, async Python) - BS, MS, or Ph.D. in Computer Science or a related field of study We'll put under

      Requirements

      with
      • . Next: "Bonus Points For You have practical experience with agentic systems and workflow automation where models take actions with real operational consequences in regulated environments.You’ve worked on platforms serving scientific or laboratory data such as LIMS, ELN, bioinformatics, or related systems, and understand the provenance and traceability requirements associated with scientific workflows.You’ve built self-service enterprise tooling for non-technical administrators and have thought carefully about the UX and API design required to make those systems usable.Experience with compliance frameworks: SOC 2, HIPAA, GxP, FedRAMP, or ALCOA+You’ve operated multi-tenant SaaS systems at significant scale with strict isolation, reliability, and compliance requirements." We can treat as Skills or Bonus Points. Could be

        Skills

        or

        Bonus Points

        . The instruction says use headings like Skills, Benefits, Pay, Schedule. So we can use Skills for bonus points. We'll list as
        • . Next: Compensation section: "CompensationWe offer competitive base compensation with bonus potential and generous early-stage equity. Your final offer will reflect your background, expertise, and expected impact.U.S. Benefits. Full-time U.S. employees receive a comprehensive benefits program including medical, dental, and vision coverage; employer-paid life and disability insurance; flexible time off with generous company wide holidays; paid parental leave; an educational assistance program; commuter benefits, including bike share memberships for office based employees; and a company subsidized lunch program.International Benefits. Full-time employees outside the U.S. receive a comprehensive benefits program tailored to their region. USD salary ranges apply only to U.S.-based positions; international salaries are set to local market. Expected Base Salary Range: $192,000 USD - $272,000 USD" We need Benefits and Pay sections. Benefits: list of benefits: medical, dental, vision coverage; employer-paid life and disability insurance; flexible time off with generous company wide holidays; paid parental leave; educational assistance program; commuter benefits, including bike share memberships for office based employees; company subsidized lunch program. Also mention international benefits tailored to region. We'll put under

          Benefits

          with
          • . Pay: base salary range, bonus potential, equity. Also mention that final offer reflects background etc. We'll put under

            Pay

            with

            maybe. We need to avoid repeating job title as heading; we haven't. We need to remove boilerplate: "About LILA" etc? Actually "About LILA" is company description; is that substantive? It's about the company, not role. Should we keep? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. The "About LILA" paragraph describes the company mission. Is that substantive? It's not about the role but could be considered company overview. The instruction didn't say to remove company description. It said remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we can keep About LILA as a section maybe "About the company". But we only have headings for specific list; we could