We need to output HTML fragment with sections for headings: 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: EEO, equal opportunity, scam warning, etc. Also remove navigation/cookie etc. Keep substantive info.
We need to parse the posting.
Content:
- Intro: "We’re a well-funded start-up. You’ll get a chance to wear many hats, be a part of a growing team, and have the potential for exciting financial and career growth. Here’s what sets us apart. We’ve set our sights on some of the biggest challenges facing biology today. We’re amassing a world class team of engineers, scientists, team builders and problem solvers to tackle these challenges heads-on. We’re passionate about developing the next generation technologies that will unravel the complexities of biology. This is a unique opportunity to build, be part of an exciting start-up and be surrounded by good humans who are super capable, humble and down-to- earth."
That's about the company/role. Could be "About the role" or "About the company". The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can put "About the role" for that intro.
- Reporting into Sr. Director of Cloud, role will bring Cellanome’s revolutionary technology to life by designing, developing, and deploying our cloud platform capabilities and tools. As the Staff Cloud Engineer you'll shape how our team builds with AI coding agents, setting the patterns, guardrails, and review standards that let a small team ship at the pace of a much larger one. This is an in-office role and can be based at our Foster City or San Diego site.
That's also about role.
- Essential Duties list: bullet points.
List them:
- Partner closely with the Computational Biology team to translate scientific workflows into scalable cloud-based solutions.
- Understand client needs, objectives, and challenges to provide tailored solutions and recommendations.
- Collaborate with internal teams (e.g., R&D, product development, regulatory, and marketing) to align solutions with client goals and timelines.
- Design, implement, and maintain cloud software systems, leveraging AWS, TypeScript, and AI-assisted development tools.
- Lead the team’s adoption of AI coding agents: define workflows, guardrails, and review standards so that AI-generated code meets our bar for quality, security, and compliance.
- Serve as a key reviewer of designs and code changes, including AI-generated changes, holding a high bar for correctness, security, and maintainability.
- Optimize data pipelines, storage, and computational workflows for performance, cost, and reliability.
- Develop and document APIs and interfaces to enable seamless integration between tools and technologies.
- Monitor and troubleshoot cloud infrastructure, ensuring high availability and security.
- Stay current with advancements in cloud technologies, AI-assisted development, and computational biology tools to drive innovation.
That's responsibilities.
- Minimum Qualifications: list.
- Typically requires a minimum of 8 years of relevant professional experience with a Bachelor’s degree; or 6 years and a Master’s degree; or equivalent work experience.
- In depth experience with full software development life cycle, including coding standards, code reviews, source control management, build processes, testing, and operations experience.
- Strong test-driven API development using TypeScript.
- Ability to use tests and clear specifications to guide and verify AI-generated code.
- Hands-on experience using AI coding assistants or agents (e.g., Claude Code, Cursor, GitHub Copilot) in professional software development, with sound judgment on when to trust, verify, or reject their output.
- Proven ability to lead design or architecture (design patterns, reliability, and scaling).
- Experience building cloud technology using AWS.
- Familiarity with other cloud provider technologies (e.g. Azure and GCP) preferred.
- Experience with large scale systems data analysis, visualization tools, and/or debugging.
- Ability to work in a startup environment at various stages of growth.
- Strong analytical and problem-solving skills, with the ability to troubleshoot problems and develop effective solutions.
- Demonstrated ability to perform the Essential Duties of the position with or without reasonable accommodations.
That's qualifications.
- Preferred Qualifications: list.
- Early-stage company experience.
- Previous experience in a technical leadership role.
- Experience building LLM-powered features or agent integrations (e.g., tool-calling APIs, MCP servers) into products or internal tooling.
- Pharmaceutical or biotech industry experience.
- Experience as an end-user of related instrumentation.
That could be "Skills" or "Preferred Qualifications". The headings list includes Skills. We could put Skills for both minimum and preferred? But we need to avoid filler. We could have "Requirements" for minimum qualifications, "Skills" for preferred qualifications, maybe "Qualifications" for education? But we have both min and pref. The instruction: Use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can map:
- About the role: intro paragraphs.
- Responsibilities: Essential Duties list.
- Requirements: Minimum Qualifications (maybe also include education/experience).
- Qualifications: maybe Preferred Qualifications? Or we could combine. But we need to avoid duplicate content. Could put Requirements for minimum qualifications, Skills for preferred qualifications, and maybe Qualifications for education? But we have education in minimum qualifications. Could treat "Qualifications" as the education/experience requirement (the first bullet). But that seems odd.
Better: Use "Requirements" for minimum qualifications (including education/experience). Use "Skills" for technical skills (like AWS, TypeScript, AI coding agents, etc.) but those are also in minimum qualifications. However we can still list them under Skills. But we must not repeat content. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we need to include all info, but we can organize it into sections without duplication. If we split content across sections, we must ensure each piece appears somewhere. Duplication is allowed? It says do NOT repeat the job title as a heading and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. It doesn't forbid repeating content across sections, but better to avoid duplication. However we can split: e.g., Minimum Qualifications bullet list can go under Requirements; Preferred Qualifications under Skills; and maybe also include some technical skills under Skills as well. But we need to ensure we don't lose any info.
Let's decide:
- About the role: intro paragraphs (first two paragraphs about company, role, location).
- Responsibilities: Essential Duties list.
- Requirements: Minimum Qualifications (including education/experience, full SDLC, TypeScript, AI coding agents, lead design, AWS, etc.) Actually many of those are skills. But we can put them under Requirements.
- Skills: Preferred Qualifications (early-stage company experience, technical leadership, LLM-powered features, pharma/biotech, end-user instrumentation). Also maybe we could add some additional skills not captured? But we already captured many under Requirements. To avoid missing, we could also put some technical skills under Skills, but they'd duplicate. Safer to put Preferred Qualifications under Skills.
- Benefits: The paragraph about competitive total compensation packages, base pay, benefits, equity, and then "What You Can Expect From Us" includes competitive salary, generous stock options, great individual and family health plans, 401(k), flexibility to balance work and life. Also "We provide competitive total compensation packages, including base pay, benefits, and equity." Also "In California, the estimated base salary range for this position is $170,000 - $200,000/year." That's Pay. So we need Benefits and Pay sections.
- Benefits: health plans, 401(k), flexibility, stock options (maybe equity). Also "competitive total compensation packages, including base pay, benefits, and equity." Could be under Benefits.
- Pay: base salary range $170k-$200k/year, note about location and factors.
- Schedule: The posting mentions "This is an in-office role and can be based at our Foster City or San Diego site." That's location, not schedule. No explicit schedule (full-time, hours). Not given. So we should not create Schedule section because no specific content. So omit Schedule.
- Also we have "We embrace and celebrate the diversity..." EEO boilerplate; we must remove that. Also "We are proud to be an equal opportunity workplace." etc. Remove.
- Also "Please contact us to request accommodation." That's part of EEO; remove.
Thus final HTML:
About the role
We’re a well-funded start-up. You’ll get a chance to wear many hats, be a part of a growing team, and have the potential for exciting financial and career growth. Here’s what sets us apart. We’ve set our sights on some of the biggest challenges facing biology today. We’re amassing a world class team of engineers, scientists, team builders and problem solvers to tackle these challenges heads-on. We’re passionate about developing the next generation technologies that will unravel the complexities of biology. This is a unique opportunity to build, be part of an exciting start-up and be surrounded by good humans who are super capable, humble and down-to-earth. Reporting into the Sr. Director of Cloud, your role will bring Cellanome’s revolutionary technology to life by designing, developing, and deploying our cloud platform capabilities and tools. As the Staff Cloud Engineer you'll shape how our team builds with AI coding agents, setting the patterns, guardrails, and review standards that let a small team ship at the pace of a much larger one. This is an in-office role and can be based at our Foster City or San Diego site.
Responsibilities
- Partner closely with the Computational Biology team to translate scientific workflows into scalable cloud-based solutions.
- Understand client needs, objectives, and challenges to provide tailored solutions and recommendations.
- Collaborate with internal teams (e.g., R&D, product development, regulatory, and marketing) to align solutions with client goals and timelines.
- Design, implement, and maintain cloud software systems, leveraging AWS, TypeScript, and AI-assisted development tools.
- Lead the team’s adoption of AI coding agents: define workflows, guardrails, and review standards so that AI-generated code meets our bar for quality, security, and compliance.
- Serve as a key reviewer of designs and code changes, including AI-generated changes, holding a high bar for correctness, security, and maintainability.
- Optimize data pipelines, storage, and computational workflows for performance, cost, and reliability.
- Develop and document APIs and interfaces to enable seamless integration between tools and technologies.
- Monitor and troubleshoot cloud infrastructure, ensuring high availability and security.
- Stay current with advancements in cloud technologies, AI-assisted development, and computational biology tools to drive innovation.
Requirements
- Typically requires a minimum of 8 years of relevant professional experience with a Bachelor’s degree; or 6 years and a Master’s degree; or equivalent work experience.
- In depth experience with full software development life cycle, including coding standards, code reviews, source control management, build processes, testing, and operations experience.
- Strong test-driven API development using TypeScript.
- Ability to use tests and clear specifications to guide and verify AI-generated code.
- Hands-on experience using AI coding assistants or agents (e.g., Claude Code, Cursor, GitHub Copilot) in professional software development, with sound judgment on when to trust, verify, or reject their output.
- Proven ability to lead design or architecture (design patterns, reliability, and scaling).
- Experience building cloud technology using AWS.
- Familiarity with other cloud provider technologies (e.g. Azure and