Staff Engineer, Software (Deployment)

We need to output only HTML fragment with headings for sections that have real content. Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include only those sections that have real specific content. The posting includes a Position Summary (maybe About the role). It includes Responsibilities (detailed). It includes Required Qualifications (maybe Requirements/Qualifications). It includes Preferred Experience (maybe Skills). It includes Salary Range (Pay). It does not mention Benefits or Schedule explicitly. So we should not create Benefits or Schedule sections. Also we should not repeat job title as heading. We need to include metadata like Job ID? Not present. We need to preserve all substantive information, but remove boilerplate like EEO, etc. We need to keep the mission description? That's part of About the role? The posting starts with company description and mission; that could be considered About the role or company overview. The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have About the role (maybe summarizing the role and company). Then Responsibilities (list). Then Requirements (maybe Required Qualifications). Then Qualifications? Actually they have Required Qualifications and Preferred Experience. Could combine Required Qualifications as Requirements, Preferred Experience as Skills. Or we could have Requirements and Qualifications separate? The instruction says use those headings as examples; we can choose which to include based on content. We have Required Qualifications (list) and Preferred Experience (list). Could map Required Qualifications to Requirements, Preferred Experience to Skills. Or we could have Qualifications for Required Qualifications and Skills for Preferred Experience. Let's decide: Use Requirements for Required Qualifications, Skills for Preferred Experience. Also we have Pay from Salary Range. So sections: About the role, Responsibilities, Requirements, Skills, Pay. We need to use

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

  for prose. So About the role: prose (company description + position summary). Responsibilities: list of duties (multiple paragraphs each maybe a duty). We'll make each bullet a

• . Requirements: list of required qualifications (each line). Skills: list of preferred experience. Pay: maybe a

  with salary range. We must not include boilerplate like EEO, etc. Also remove staffing agency note, accommodation contact, etc. Also remove "All listed tasks and responsibilities are deemed as essential functions..." etc. Also remove "Candidates must have current authorization to work in the United States..." maybe that's a requirement? Could be considered a requirement but it's about work authorization; could be included in Requirements? It's a substantive detail. However it's near the end; we could include it as a requirement bullet. But the instruction says preserve ALL substantive information; do not invent or summarize away detail. So we should include that work authorization requirement. Also the bit about visiting PacBio locations etc. That's also substantive. We'll include that as a requirement bullet maybe. We need to be careful not to include duplicated lines. Also remove the repeated EEO statement at bottom. Let's extract content. Company description and mission: first paragraph(s) up to "Position Summary". Actually the text: "PacBio (NASDAQ PACB) is a premier life science technology company that designs, develops, and manufactures advanced sequencing solutions to help scientists and clinical researchers resolve genetically complex problems. Our mission is to enable the promise of genomics to better human health. Genomics is core to all biological processes, and our advanced genomics tools provide scientists and clinical researchers the insights to better understand biology and health. We are now entering the century of biology and genomics is at the heart of the next revolution. Become part of the new paradigm in gene sequencing and help shape the future of genomic study by joining the PacBio team. Position Summary PacBio’s sequencing instruments are critical to sequencing labs around the world. As a Staff Deployment Engineer, you will work cross-functionally to design, develop, and deploy the compute platforms integrated into our sequencing appliances, our customers’ data centers, and the cloud. You will be expected to set technical direction rather than receive it to decide what our deployment and platform architectures should look like several years out, build the pieces that do not exist yet, and deliver a product that satisfies CLIA labs and other regulated customers." That's the About the role content (including position summary). We'll put that in a

  (maybe multiple paragraphs but we can combine into one

  with line breaks? Better to keep as one

  with the whole text). Could split into two

  but not required. Responsibilities: after "Responsibilities" heading, there is a block with multiple paragraphs each starting with a bolded topic? Actually the text: "Responsibilities Cloud deployment. Bring core data analysis pipelines to the cloud to offer flexible, on-demand compute capacity for our customers. Provide a secure, reliable, and transparent alternative to on-prem compute. Define and implement the deployment model for cloud-hosted services, including infrastructure as code, environment promotion, secrets management, and delivery pipelines, and establish the patterns other teams will adopt.Build and release pipelines. Consolidate build infrastructure onto a single CI/CD platform, moving builds into containers so they are reproducible and independent of hand-maintained agents. Rationalize dependency management, proselytize statelessness and immutability, and instrument deployment pipelines for predictability and uptime. Develop and implement traceability and retention policies for product lifecycle management.Image architecture and hardware integration. Own image architecture jointly with instrument engineering composition, maintainability, and performance across node roles and hardware variants. You will build the images themselves with curated package sets, PacBio software, purposeful partition layouts, and the driver, device, and firmware integration each variant requires. This includes virtual machines in production and virtualized server equivalents used for development and test. Support custom hardware interfaces, robotics packages, and low-latency user interfaces.Infrastructure and Configuration as code. Replace bespoke scripting and image-baked state with declarative, reviewable configuration for instruments, build infrastructure, and laboratory systems.Supply-chain integrity and security posture. Establish the assurance capability the product needs artifact and image signing, verified boot, automated software bill of materials generation, continuous vulnerability ingestion and triage against a defined patch cadence, and a documented hardening baseline.Cross-functional and regulatory execution. Partner with Quality, Regulatory, Manufacturing, IT, and Field Service to make deployment auditable and predictable traceability from commit to shipped artifact, change control and release documentation, and validated builds delivered to manufacturing on schedule.Technical leadership and resilience. Set engineering standards, review designs and code, and mentor engineers across the organization. Document and de-risk the systems that currently rely on individual knowledge." We need to turn each of these topic paragraphs into

• items. Each sentence after the bolded heading is part of that responsibility. We'll make each responsibility a
• containing the sentences. We'll need to split by the bolded headings: "Cloud deployment.", "Build and release pipelines.", "Image architecture and hardware integration.", "Infrastructure and Configuration as code.", "Supply-chain integrity and security posture.", "Cross-functional and regulatory execution.", "Technical leadership and resilience." We'll include the text after each heading as part of the
• . Ensure we keep all details. Now Required Qualifications: after "Required Qualifications" heading, there is a list numbered 1-? Actually it's a paragraph with multiple sentences separated by periods. Let's extract: "Required Qualifications 10+ years of professional experience in systems, platform, release, or deployment engineering, or a Master’s degree in computer science, computer engineering, or a related discipline plus 8+ years of such experience.Demonstrated experience delivering Linux-based systems on appliance, instrument, or other purpose-built hardware into customer or field environments.Fluency in Python and shell, sufficient to build and maintain production automation that others depend on.Deep, hands-on Linux systems expertise boot chain, systemd, filesystems and partitioning, packaging, and kernel or driver integration.Experience designing and operating automated, reproducible image build pipelines, with a clear point of view on what makes a build trustworthy.Experience delivering software under formal change control in a regulated or otherwise high-consequence setting, where releases must be auditable and any prior version reproducible on demand.Strong hands-on ownership of CI/CD systems at scale, including pipeline-as-code, containerized builds, build agent fleet management, and infrastructure as code.Production experience deploying cloud services for customer use with at least one major cloud platform (AWS, Azure, or GCP).A track record of setting technical direction for a platform and driving it to completion across multiple teams, including the parts that require persuasion rather than authority.Excellent interpersonal, written, and verbal communication skills." We need to make each of these as
• . They are separated by periods but no clear delimiter. We'll split at each capital letter start after a period? Actually each begins with a capital letter after a period. We'll manually separate: - 10+ years of professional experience in systems, platform, release, or deployment engineering, or a Master’s degree in computer science, computer engineering, or a related discipline plus 8+ years of such experience. - Demonstrated experience delivering Linux-based systems on appliance, instrument, or other purpose-built hardware into customer or field environments. - Fluency in Python and shell, sufficient to build and maintain production automation that others depend on. - Deep, hands-on Linux systems expertise boot chain, systemd, filesystems and partitioning, packaging, and kernel or driver integration. - Experience designing and operating automated, reproducible image build pipelines, with a clear point of view on what makes a build trustworthy. - Experience delivering software under formal change control in a regulated or otherwise high-consequence setting, where releases must be auditable and any prior version reproducible on demand. - Strong hands-on ownership of CI/CD systems at scale, including pipeline-as-code, containerized builds, build agent fleet management, and infrastructure as code. - Production experience deploying cloud services for customer use with at least one major cloud platform (AWS, Azure, or GCP). - A track record of setting technical direction for a platform and driving it to completion across multiple teams, including the parts that require persuasion rather than authority. - Excellent interpersonal, written, and verbal communication skills. Now Preferred Experience: after "Preferred Experience" heading, there is a list of items separated by periods. Let's extract: "Preferred Experience Supply-chain security experience code and artifact signing, UEFI Secure Boot, dm-verity or equivalent integrity measures, SBOM generation, and software composition analysis tooling.Familiarity with hardening baselines and audit tooling such as CIS Benchmarks, STIG, SCAP, or SELinux policy work.Experience with modern image build tooling such as mkosi, Packer, Yocto, or Buildroot, and with immutable or A/B-updated operating systems.Configuration management and infrastructure-as-code experience with tools such as Ansible, Terraform, or Salt.Experience owning on-premises development infrastructure systems such as Bitbucket, Jenkins, and Artifactory as an end-to-end administrator and architect, not only as a consumer.Experience building or operating an observability stack (for example Prometheus, Grafana, Loki, and Alertmanager).Experience managing secure remote access management systems (for example Tailscale or SecureLink).Experience with on-premises virtualization at scale, such as Proxmox VE or VMware vSphere. Experience mentoring senior engineers or acting as a technical lead without direct reports." We need to split each bullet: - Supply-chain security experience code and artifact signing, UEFI Secure Boot, dm-verity or equivalent integrity measures, SBOM generation, and software composition analysis tooling. - Familiarity with hardening baselines and audit tooling such as CIS Benchmarks, STIG, SCAP, or SELinux policy work. - Experience with modern image build tooling such as mkosi, Packer, Yocto, or Buildroot, and with immutable or A/B-updated operating systems. - Configuration management and infrastructure-as-code experience with tools such as Ansible, Terraform, or Salt. - Experience owning on-premises development infrastructure systems such as Bitbucket, Jenkins, and Artifactory as an end-to-end administrator and