Senior Software Engineer II, Enterprise Auth Platform
Lila Sciences · San Francisco, CA · 3 wk ago
On-siteEngineering$180k/yrFull-time
We need to output HTML fragment with headings for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. No Job ID etc. Remove boilerplate. Preserve all substantive info.
We need to parse the posting.
Content:
- Intro: "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."
That's about the role. Could be "About the role" section.
- "What You'll Be Building" with bullet points: Multi-Tenancy & Authorization, Tenant Self-Serve & Lifecycle, Public & Agent-Facing APIs, MCP & Agent Integration. That's responsibilities.
- Then "Qualifications" repeated twice? Actually after "What You'll Be Building" there is "Qualifications" then bullet list (7+ years...). Then after that there is "What You'll Need To Succeed" which repeats same bullet list. Then "Bonus Points For" list.
- Then "Compensation" paragraph: "We offer competitive base compensation with bonus potential and generous early-stage equity. Your final offer will reflect your background, expertise, and expected impact."
- Then "U.S. Benefits." paragraph describing benefits.
- Then "International Benefits." paragraph.
- Then "Expected Base Salary Range: $180,000 USD - $256,000 USD"
- Then "About LILA" description.
- Then "Guided by our core values..." etc.
- Then "We’re All In" EEO statement (boilerplate to remove).
- Then "A Note to Agencies" (boilerplate to remove).
We need to include sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We need to decide what goes where.
- About the role: intro paragraph.
- Responsibilities: "What You'll Be Building" bullet list.
- Requirements: maybe the qualifications list (7+ years etc). Could be "Qualifications" heading.
- Skills: maybe the bonus points? Or we could treat "Qualifications" as requirements and "Skills" as bonus? But we need to follow instruction: Use headings only when posting has real specific content. We have content for Qualifications (the bullet list). Also we have Bonus Points For (additional qualifications). Could combine under Qualifications or Skills. The instruction says we can have sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which to include.
We have content for:
- About the role: yes.
- Responsibilities: yes (What You'll Be Building).
- Qualifications: yes (the bullet list). Could be under "Qualifications".
- Skills: maybe the bonus points could be under "Skills". Or we could treat "Bonus Points For" as "Skills". But we need to ensure we don't create thin sections. Bonus points list is substantive.
- Benefits: we have US Benefits and International Benefits paragraphs plus Expected Base Salary Range (that's Pay). So Benefits section can include both US and International benefits paragraphs.
- Pay: we have Expected Base Salary Range.
- Schedule: not mentioned; no info about schedule (full-time implied but not explicit). Should not create Schedule section if no specific content.
- Requirements: maybe we could put the "What You'll Need To Succeed" as Requirements (same as qualifications). But we already have Qualifications. Could treat Requirements as the same list; but we need to avoid duplication. Perhaps we can put the bullet list under "Requirements" and then "Qualifications" could be the bonus points? However the posting has "Qualifications" heading then bullet list, then "What You'll Need To Succeed" repeating same bullet list, then "Bonus Points For". So we have duplicate content. We should preserve all substantive info but not repeat duplicated lines. So we need to deduplicate.
Thus we can have:
- About the role: intro paragraph.
- Responsibilities: bullet list from "What You'll Be Building".
- Requirements: the bullet list of qualifications (7+ years etc). (We can include it once.)
- Skills: the bonus points list.
- Benefits: US Benefits paragraph + International Benefits paragraph.
- Pay: Expected Base Salary Range.
- Schedule: omit.
We also have "About LILA" description; could be part of About the role? Or maybe we could add another section like "About the Company" but not in allowed headings. The allowed headings list does not include About the Company. So we should incorporate that info somewhere else, maybe under About the role? But About the role already has intro; we could extend it with the company description. However the instruction: "Use
for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title as heading. No Job ID etc. Remove boilerplate. Preserve all substantive info.
We need to parse the posting.
Content:
- Intro: "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."
That's about the role. Could be "About the role" section.
- "What You'll Be Building" with bullet points: Multi-Tenancy & Authorization, Tenant Self-Serve & Lifecycle, Public & Agent-Facing APIs, MCP & Agent Integration. That's responsibilities.
- Then "Qualifications" repeated twice? Actually after "What You'll Be Building" there is "Qualifications" then bullet list (7+ years...). Then after that there is "What You'll Need To Succeed" which repeats same bullet list. Then "Bonus Points For" list.
- Then "Compensation" paragraph: "We offer competitive base compensation with bonus potential and generous early-stage equity. Your final offer will reflect your background, expertise, and expected impact."
- Then "U.S. Benefits." paragraph describing benefits.
- Then "International Benefits." paragraph.
- Then "Expected Base Salary Range: $180,000 USD - $256,000 USD"
- Then "About LILA" description.
- Then "Guided by our core values..." etc.
- Then "We’re All In" EEO statement (boilerplate to remove).
- Then "A Note to Agencies" (boilerplate to remove).
We need to include sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We need to decide what goes where.
- About the role: intro paragraph.
- Responsibilities: "What You'll Be Building" bullet list.
- Requirements: maybe the qualifications list (7+ years etc). Could be "Qualifications" heading.
- Skills: maybe the bonus points? Or we could treat "Qualifications" as requirements and "Skills" as bonus? But we need to follow instruction: Use headings only when posting has real specific content. We have content for Qualifications (the bullet list). Also we have Bonus Points For (additional qualifications). Could combine under Qualifications or Skills. The instruction says we can have sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which to include.
We have content for:
- About the role: yes.
- Responsibilities: yes (What You'll Be Building).
- Qualifications: yes (the bullet list). Could be under "Qualifications".
- Skills: maybe the bonus points could be under "Skills". Or we could treat "Bonus Points For" as "Skills". But we need to ensure we don't create thin sections. Bonus points list is substantive.
- Benefits: we have US Benefits and International Benefits paragraphs plus Expected Base Salary Range (that's Pay). So Benefits section can include both US and International benefits paragraphs.
- Pay: we have Expected Base Salary Range.
- Schedule: not mentioned; no info about schedule (full-time implied but not explicit). Should not create Schedule section if no specific content.
- Requirements: maybe we could put the "What You'll Need To Succeed" as Requirements (same as qualifications). But we already have Qualifications. Could treat Requirements as the same list; but we need to avoid duplication. Perhaps we can put the bullet list under "Requirements" and then "Qualifications" could be the bonus points? However the posting has "Qualifications" heading then bullet list, then "What You'll Need To Succeed" repeating same bullet list, then "Bonus Points For". So we have duplicate content. We should preserve all substantive info but not repeat duplicated lines. So we need to deduplicate.
Thus we can have:
- About the role: intro paragraph.
- Responsibilities: bullet list from "What You'll Be Building".
- Requirements: the bullet list of qualifications (7+ years etc). (We can include it once.)
- Skills: the bonus points list.
- Benefits: US Benefits paragraph + International Benefits paragraph.
- Pay: Expected Base Salary Range.
- Schedule: omit.
We also have "About LILA" description; could be part of About the role? Or maybe we could add another section like "About the Company" but not in allowed headings. The allowed headings list does not include About the Company. So we should incorporate that info somewhere else, maybe under About the role? But About the role already has intro; we could extend it with the company description. However the instruction: "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., meaning those are examples; we can use those headings. It doesn't forbid other headings? It says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect us to use only those headings. So we should fit all content under those headings.
Thus we can put company description under About the role as well.
Now we need to format.
We must not include markdown code fences. Just raw HTML.
We need to use for each section heading.
Inside each section, we need
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect us to use only those headings. So we should fit all content under those headings.
Thus we can put company description under About the role as well.
Now we need to format.
We must not include markdown code fences. Just raw HTML.
We need to use for each section heading.
Inside each section, we need
for prose,
- for lists. We must not repeat job title as heading. We must not include Job ID etc. We must remove boilerplate: EEO, Note to Agencies, etc. We must preserve all substantive info. Let's extract substantive content. Intro paragraph: "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." We can keep as is. Company description: "Lila Sciences is building Scientific Superintelligence™ to solve humankind's greatest challenges. We believe science is the most inspiring frontier for AI. Rather than hard-coding expert knowledge into tools, LILA builds systems that can learn for themselves. LILA combines advanced AI models with proprietary AI Science Factory™ instruments into an operating system for science that executes the entire scientific method autonomously, accelerating discovery at unprecedented speed, scale, and impact across medicine, materials, and energy. Learn more at www.lila.ai. Guided by our core values of truth, trust, curiosity, grit, and velocity, we move with startup speed while tackling problems of historic importance." We can append to About the role. Now Responsibilities: bullet list from "What You'll Be Building". Let's extract each bullet: - 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. We need to keep each as
- with the full text.
Now Requirements: the bullet list from Qualifications (and repeated). Let's extract unique bullet points:
- 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.
Note: The last two bullets appear also in the intro but okay.
Now Skills (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.
Now Benefits: combine US Benefits and International Benefits paragraphs.
US Benefits paragraph: "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 paragraph: "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."
We could keep as two
under Benefits. Now Pay: "Expected Base Salary Range: $180,000 USD - $256,000 USD" Also earlier compensation paragraph: "We offer competitive base compensation with bonus potential and generous early-stage equity. Your final offer will reflect your background, expertise, and expected impact." That's also compensation info. Should we include that under Pay? The Pay section should contain substantive pay info. We have both the descriptive compensation and the salary range. We can combine them. Thus Pay section:
We offer competitive base compensation with bonus potential and generous early-stage equity. Your final offer will reflect your background, expertise, and expected impact.
Expected Base Salary Range: $180,000 USD - $256,000 USD
Now Schedule: no specific content, omit. Now we need to output only HTML fragment. Let's craft. We'll start withAbout the role
then... intro ...
... company description ...
ThenResponsibilities
- ... li items ...
Then