Staff ML Engineer

We need to output HTML fragment with sections:

for headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections where posting has real specific content. We need to parse the job posting: It includes Company Description (maybe not needed). Then "We are seeking a Staff ML Engineer to lead..." That's about the role. Then "What You'll Do" (Responsibilities). Then "What You'll Bring" (Requirements/Qualifications). Then "Preferred Qualifications". Then "Additional Information" includes EEO, Pay Transparency, etc. Also includes salary range: "The expected base salary for this position ranges from $130,000 to $190,000." That's Pay info. Also mentions "In addition to base salary and a competitive benefits package, successful candidates are eligible to receive a discretionary bonus or commission tied to achieved results." That's Benefits info. Also maybe schedule? Not mentioned. So we can include Pay and Benefits sections. No schedule. We need to avoid repeating job title as heading. So we will not have heading "Staff ML Engineer". We'll have sections: About the role (maybe from the first paragraph after "We are seeking..."). Responsibilities (What You'll Do). Requirements (What You'll Bring). Qualifications? Could combine Requirements and Qualifications; but we have both "What You'll Bring" (required) and "Preferred Qualifications". Could make Requirements section for required qualifications, and maybe a separate Qualifications section for preferred? But guidelines: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We can include Requirements and Qualifications separately if content exists. We have required qualifications (What You'll Bring) and preferred qualifications (Preferred Qualifications). So we can have Requirements (required) and Qualifications (preferred). Also Skills maybe not separate; we could embed skills within Requirements. But we can also have Skills section if we want to list skills. However guidelines: Prefer few substantive sections over many thin ones. Might combine Requirements and Qualifications into one? But they said we can use those headings. I'd include both Requirements and Qualifications as separate sections because we have distinct content. We need to use

• for any list of duties/requirements/benefits. So for responsibilities we should list each bullet as
• . For requirements we list each bullet. For preferred qualifications list each bullet. For benefits we list bullet points (maybe just one). For pay we can just put

  with salary range. We need to preserve all substantive information; do not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we need to remove the EEO statement, accommodations contact, Pay Transparency notice, privacy policy link, etc. Also remove "Additional Information For US Based Jobs" etc. Also remove "Press Ganey is committed to providing reasonable accommodations..." etc. Also remove "Don’t meet every single requirement? Studies have shown..." maybe that's encouraging but could be considered boilerplate? It's more of a encouragement; but it's not substantive about the role. Likely we should remove it as it's generic encouragement. Also remove "You may be just the right candidate..." etc. Also remove "Additional Information For US Based Jobs" and everything after that (EEO, Pay Transparency, etc). Also remove the company description? The company description at start is substantive about the company; but guidelines: we should include About the role section, not company description. The company description could be considered "About the role"? Actually "About the role" is about the role, not company. The company description is about Press Ganey. Might be considered not needed. The instruction: "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can include an About the role section that describes the role and maybe includes company context? The posting includes a company description before the role. We could incorporate that into About the role? But we should not repeat job title as heading. The About the role section could contain a paragraph describing the role and maybe company mission. We need to preserve ALL substantive information; we cannot discard company description if it's substantive about the role? The company description is about Press Ganey, not the role. But it's still substantive information about the employer; maybe we should keep it as part of About the role? The guidelines didn't explicitly say to keep company description, but they said preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep the company description somewhere. Where to put? Could be part of About the role section (maybe a brief intro). Or we could add a separate section like "About the Company" but not in allowed headings. Since only allowed headings are those listed, we should fit it into one of those. Probably About the role is appropriate to include a brief description of the team and mission. We'll include the company description paragraph(s) as prose in About the role. Thus About the role: combine the company description paragraphs (first big block) and the sentence "We are seeking a Staff ML Engineer to lead the design, delivery, and operation of production-grade AI systems." plus maybe the following sentence about building services etc. Actually that sentence is part of the role description. We'll include that. Now Responsibilities: the bullet list under "What You'll Do". We'll extract each line starting with a verb. Let's list them: - Own technical delivery from prototype through deployment and ongoing production support, partnering with AI Scientists and Product to define requirements, plan implementation, and resolve cross-team dependencies. - Evaluate proposed AI solutions for production suitability, identify technical risks, and choose architectures that meet quality, reliability, and cost requirements without unnecessary complexity. - Architect and build high-volume AI services and processing pipelines, including fault tolerance, backpressure, retries, idempotency, and recovery from partial failures. - Lead the evolution of our Python services and Databricks-based platform for distributed processing, model serving, and integration of traditional ML and LLM-based components. - Establish production engineering standards for automated testing, CI/CD, model and prompt versioning, load testing, controlled rollouts, and rollback. - Build evaluation and monitoring capabilities to detect AI quality regressions and track service reliability, throughput, latency, and inference cost. - Partner with Product and Responsible AI teams to define release criteria and implement requirements for model validation, data privacy, security, and governance. - Optimize processing and inference workloads, balancing model quality, throughput, latency, capacity, and cost. - Mentor engineers and lead architecture and code reviews, maintaining consistent standards for software quality and maintainability. We need to preserve all detail; keep as

  items. Now Requirements (What You'll Bring): list each bullet: - Bachelor's degree in Computer Science, Electrical Engineering, or a related technical discipline, or equivalent practical experience. - 8+ years of professional software engineering experience, including at least 3 years owning ML or LLM systems in production and their operational support. - Proven track record of independently leading complex technical initiatives from requirements through production, making architectural decisions and coordinating delivery across stakeholders. - Advanced proficiency in Python for production services and data processing, with strong SQL skills. - Experience designing and operating high-throughput distributed systems, with a strong understanding of failure recovery, multi-tenancy, and capacity planning. - Hands-on experience deploying and operating LLM-based applications, including evaluation, output validation, observability, and cost management. - Strong production engineering practices across automated testing, CI/CD, monitoring, incident response, and root-cause analysis. - Demonstrated technical leadership through system design, hands-on implementation, code review, and mentorship. - Ability to communicate technical decisions and tradeoffs clearly to engineering, research, product, and governance stakeholders. Now Qualifications (Preferred Qualifications): list each bullet: - Experience with Databricks or comparable cloud-based data and AI platforms for workflow orchestration, scalable processing, model deployment, and evaluation. - Experience with NLP, text analytics, or large-scale processing of unstructured data. - Experience building shared infrastructure for inference, evaluation, and model lifecycle management. - Familiarity with retrieval-augmented generation, semantic search, and LLM orchestration frameworks. - Experience with speech-to-text, speaker diarization, or processing conversational audio data. - Experience deploying and operating cloud-native services on AWS or Azure. - Experience with healthcare or other regulated environments, including sensitive data handling, auditability, and model governance. Now Benefits: we have "In addition to base salary and a competitive benefits package, successful candidates are eligible to receive a discretionary bonus or commission tied to achieved results." Also maybe "competitive benefits package" is vague; we should not include vague placeholder like "competitive benefits package" if not specific. But we have a specific: discretionary bonus or commission tied to achieved results. That's a benefit. We can list that as a bullet. Also maybe we could mention "competitive benefits package" but that's vague; guidelines: avoid filler like "not specified", "N/A", "varies", "TBD". "competitive benefits package" is vague but still substantive? It's a statement that they offer a benefits package but not details. Might be considered filler. Safer to only include the specific discretionary bonus/commission. Also maybe we could include "base salary" but that's Pay. Thus Benefits section:

  • Eligible for a discretionary bonus or commission tied to achieved results.

  Pay: we have salary range: $130,000 to $190,000. Also note: "It is not typical for offers to be made at or near the top of the range." That's substantive detail about pay. Also "Salary offers are based on a wide range of factors including relevant skills, training, experience, education, and, where applicable, licensure or certifications obtained. Market and organizational factors are also considered." That's also substantive. We should preserve all substantive information about pay. So we need to include that prose. Not a list. So we can put

  with that info. We should not include the Pay Transparency Non-Discrimination notice (boilerplate). Also remove EEO etc. Now we need to ensure we don't include any duplicated lines. Also we should not include headings for sections with no content. Thus final HTML fragment:

  About the role

  Press Ganey is the leading experience measurement, data analytics, and insights provider for complex industries—a status we earned over decades of deep partnership with clients to help them understand and meet the needs of their key stakeholders. Our earliest roots are in U.S. healthcare –perhaps the most complex of all industries. Today we serve clients around the globe in every industry to help them improve the Human Experiences at the heart of their business. We serve our clients through an unparalleled offering that combines technology, data, and expertise to enable them to pinpoint and prioritize opportunities, accelerate improvement efforts and build lifetime loyalty among their customers and employees. Like all great companies, our success is a function of our people and our culture. Our employees have world-class talent, a collaborative work ethic, and a passion for the work that have earned us trusted advisor status among the world’s most recognized brands. As a member of the team, you will help us create value for our clients, you will make us better through your contribution to the work and your voice in the process. Ours is a path of learning and continuous improvement; team efforts chart the course for corporate success. Our Mission We empower organizations to deliver the best experiences. With industry expertise and technology, we turn data into insights that drive innovation and action. Our Values To put Human Experience at the heart of organizations so every person can be seen and understood. Energize the customer relationship: Our clients are our partners. We make their goals our own, working side by side to turn challenges into solutions. Success starts with me: Personal ownership fuels collective success. We each play our part and empower our teammates to do the same. Commit to learning: Every win is a springboard. Every hurdle is a lesson. We use each