Senior Controls Engineer

We need to output only HTML fragment, using

for section 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. We need to parse the posting. Key sections: - About the role: The description after "Your Role" maybe? Actually "Your Role" heading then description about PrisMax systems etc. That is about the role. So we can put that under

About the role

with paragraphs. - Responsibilities: The bullet list under "What You'll Be Doing". That's responsibilities. - Requirements: The "Required Skills" bullet list. - Qualifications: Possibly "Preferred Skills" could be qualifications? But we have separate Skills section maybe. The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to decide what content goes where. We have: - About the role: description of role, mission, etc. - Responsibilities: list of duties (What You'll Be Doing). - Requirements: maybe the "Required Skills" (Bachelor's degree etc.) could be Requirements. - Qualifications: maybe the "Preferred Skills" could be Qualifications? Or we could treat Preferred Skills as Skills? Actually we have Skills heading separate. Could put "Preferred Skills" under Skills. But we also have Required Skills which could be Requirements. The posting also includes "Experience in industries such as aerospace..." etc. That's part of Required Skills. We also have "Vantive is committed to supporting the needs for flexibility in the workplace..." that's about Schedule? Actually it's about flexible workplace policy: minimum of 3 days a week onsite. That's schedule info. So we can put Schedule section. Pay: The salary range $88,000 to $121,000 annually, plus discretionary bonus. So we can include Pay section. Benefits: The US Benefits section. We should not include boilerplate like EEO, Recruitment Fraud Notice, etc. We must not include sections with filler like "commensurate with experience". Not present. We need to preserve all substantive information. So we need to include details from each relevant part. Let's extract content. About the role: The paragraph starting "Vantive is a vital organ therapy company..." up to "Join us in advancing our mission to extend lives and expand possibilities." Also includes "Your Role Our PrisMax systems..." Actually after that there is "Your Role". The content about PrisMax systems etc is part of role description. So we can combine. Let's copy that text exactly (but we can reformat into paragraphs). Must not invent or summarize away detail. We need to preserve all substantive information; we can break into paragraphs but keep same info. We'll produce:

About the role

Vantive is a vital organ therapy company on a mission to extend lives and expand possibilities for patients and care teams everywhere. For 70 years, our team has driven meaningful innovations in kidney care. As we build on our legacy, we are deepening our commitment to elevating the dialysis experience through digital solutions and advanced services, while looking beyond kidney care and investing in transforming vital organ therapies. Greater flexibility and efficiency in therapy administration for care teams, and longer, fuller lives for patients— that is what Vantive aspires to deliver. We believe Vantive will not only build our leadership in the kidney care space, it will also offer meaningful work to those who join us. At Vantive, you will become part of a community of people who are focused, courageous and don’t settle for the mediocre. Each of us is driven to help improve patients’ lives worldwide. Join us in advancing our mission to extend lives and expand possibilities.

Your Role Our PrisMax systems are used in the ICU to support patients experiencing life-threatening acute kidney injury. Clinicians rely on our devices to deliver continuous renal replacement therapy (CRRT), helping to maintain critical kidney function while patients recover. We’re building new platforms, devices, and connected systems to make therapy administration more efficient, consistent, and intuitive—so care teams can focus on the patient. Vantive is seeking a Controls and Model-Based Design Systems Engineer (Controls Engineer, Senior) to support new product development for current and next-generation medical devices. In this role, you will develop, test, and verify control algorithms that help automate therapy delivery. You’ll work hands-on with rapid prototyping, model-based software development, hardware/software-in-the-loop (HIL/SIL) testing, and automated test scripting to verify performance. Experience in industries such as aerospace, automotive, electro-hydraulics, or process control translates well to this position. This is an individual contributor role, working under the guidance of a functional manager and collaborating closely with a cross-functional, global team.

That seems good. Responsibilities: list under "What You'll Be Doing". We'll extract each bullet. List: - Design and develop embedded closed-loop control algorithms using model-based design tools to manage electro-mechanical components (pumps, motors, valves) and sensor inputs (pressure, temperature, weight, conductivity) to conduct the treatment - Translate clinical and user needs into clear control-system behaviors by defining requirements, logic diagrams, operating modes, alarm conditions, and thresholds - Utilize rapid prototyping and simulation capabilities, including software-in-the-loop (SIL) and hardware-in-the-loop (HIL) environments, to accelerate development and de-risk designs - Plan and execute verification activities—from automated test scripting to hands-on lab evaluations—to demonstrate compliance with control requirements and characterize algorithm performance - Create high-quality design documentation for product release, including requirements, design descriptions, test plans/protocols, and test results that support the Design History File (DHF) - Serve as a Controls subject matter expert (SME) by troubleshooting system-level issues, leading/participating in root-cause investigations, and identifying corrective actions in partnership with software, electrical, test, and systems team members - Support the matrix organization by providing Controls expertise and guidance as a dedicated team member on one or more cross-functional new product development projects while communicating progress, technical risks, schedule impacts, and key dependencies to the team We'll put inside

• ...

. Requirements: The "Required Skills" bullet list. List: - Bachelor’s degree and three years or more of relevant experience, or Master’s degree and two years or more of relevant experience, with a degree in Electrical, Mechanical, Biomedical, Controls, Systems, Software, or a related engineering field That's one bullet? Actually it's a single sentence but could be considered requirement. We'll keep as

. Qualifications: maybe we could treat "Preferred Skills" as Qualifications? But we also have Skills heading. Let's see: The instruction includes Qualifications as a possible heading. We have "Preferred Skills" list. That could go under Qualifications. Or we could put under Skills. But we need to decide. We have also "Skills" heading. Could put the list of skills under Skills. However the "Preferred Skills" list includes many items like hands-on experience with MathWorks model-based design tools, etc. That's more like skills/qualifications. The "Required Skills" is more like minimum requirements. So we could put Required Skills under Requirements, Preferred Skills under Qualifications, and maybe also a Skills section for something else? But we don't have other skills list. Could combine Preferred Skills into Skills and omit Qualifications. But we need to follow instruction: include a section ONLY when posting has real, specific content for it. We have content for Requirements (Required Skills). We have content for Qualifications (Preferred Skills). We have content for Skills? Not really separate; but we could treat Preferred Skills as Skills and skip Qualifications. However we have both Required and Preferred; maybe we can put Required under Requirements, Preferred under Skills. That seems logical: Requirements = mandatory; Skills = desired/preferred. Qualifications could be omitted. But the instruction list includes Qualifications as a possible heading; we can omit if not needed. We'll decide to put Preferred Skills under Skills. Thus:

Skills

• ... each bullet from Preferred Skills list

Now Benefits: The US Benefits section. We need to capture all benefits details. Paragraphs: "At Vantive This is where your well-being matters. Vantive offers comprehensive compensation and benefits packages for eligible roles. Our health and well-being benefits include medical, dental and vision coverage that start on day one, as well as insurance coverage for basic life, accident, short-term and long-term disability, and business travel accident insurance. Financial and retirement benefits include the Aon Pooled Employer Plan (“Aon PEP”), Vantive’s 401(k) retirement savings plan, to help you prepare for your future. The Aon PEP is designed to help improve retirement outcomes by providing retirement resources more efficiently. The plan offers a robust set of investment options, financial education, and a suite of resources to support your retirement goals. We also offer Flexible Spending Accounts, educational assistance programs, and time-off benefits such as paid holidays, paid time off ranging from 20 to 35 days based on length of service, family and medical leaves of absence, and paid parental leave. Additional benefits include commuting benefits, the Employee Discount Program, the Employee Assistance Program (EAP), and childcare benefits. Join us and enjoy the competitive compensation and benefits we offer to our employees. For additional information regarding Vantive’s US Benefits, please speak with your recruiter or visit our Benefits site: Benefits | Vantive" We should preserve all that. We'll put into

maybe multiple paragraphs. Pay: The salary range and bonus. Paragraph: "We understand compensation is an important factor as you consider the next step in your career. At Vantive, we are committed to equitable pay for all employees, and we strive to be more transparent with our pay practices. The estimated base salary for this position is $88,000 to $121,000 annually. The estimated range is meant to reflect an anticipated salary range for the position. We may pay more or less than of the anticipated range based upon market data and other factors, all of which are subject to change. Individual pay is based on upon location, skills and expertise, experience, and other relevant factors. This position is also eligible for a discretionary bonus. For questions about this, our pay philosophy, and available benefits, please speak to the recruiter if you decide to apply and are selected for an interview." We'll keep that. Schedule: The flexible workplace policy. Paragraph: "Vantive is committed to supporting the needs for flexibility in the workplace. We do so through our flexible workplace policy which includes a minimum of 3 days a week onsite. This policy provides the benefits of connecting and collaborating in-person in support of our Mission." We'll put that. Now ensure we didn't include any boilerplate like EEO, Recruitment Fraud Notice, etc. We also need to exclude the "Advanced Molding and Extrusion techniques..." list etc. That appears after the pay paragraph? Actually after the pay paragraph there is a list of competencies with levels (Learning/Doing etc). That seems like some internal framework; not sure if it's substantive. It might be considered part of skills? But it's a list of categories with proficiency levels. The instruction says preserve ALL substantive information; do NOT invent or summarize away detail. Should we include that list? It appears under the pay section maybe as part of "Advanced Molding and Extrusion techniques (Learning / Doing (1)), ..." That seems like a list of skill areas with proficiency levels. Could be considered part of Skills or Qualifications. However it's not clearly labeled; it's just a list. Might be part of the job posting's "skills" section. Since we already have a Skills section from Preferred Skills, we could incorporate this list as additional bullets under Skills. But we need to decide if it's substantive. It appears to be a list of competencies with proficiency levels (e.g., Advanced Molding and Extrusion techniques (