Jobs · Minnesota

Agile Project Leader / Scrum Master - Medical Device

Vantive · Minneapolis, MN · 4 wk ago
$128k–$176k/yrFull-time
We need to output HTML fragment with 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. Must not include boilerplate like EEO, fraud notice, etc. Must preserve all substantive info. We need to parse the posting. Content: - Intro about Vantive (company description). Could be "About the role"? Actually "About the role" is a heading for description of role. The intro about company could be part of "About the role"? Usually "About the role" includes description of role and maybe company. We'll include a paragraph summarizing Vantive mission and role context. - Then "Your Role" description: "Our PrisMax systems..." etc. That's role description. - Then "Vantive is seeking an experienced Scrum Master / Agile Specialist / Project Leader to drive Agile delivery across cross-functional medical device software development teams." That's role summary. - Then "The role involves facilitating Agile practices, managing project timelines, and ensuring smooth collaboration between engineering, product, and business teams." - Then "Experience guiding agile (scrum) teams working on embedded device software, controls, and test development in a regulated industry will prepare you well for this position." - Then "This is a leadership role, with cross-team and cross-site influence, empowered to exercise servant leadership and impact agile delivery across the acute software organization." - Then "What You'll Be Doing" list: bullet points. - Then "What You’ll Bring" list: bullet points. - Then "Preferred Skills" list: bullet points. - Then "Vantive is committed to supporting the need for flexibility in the workplace. We do so through our flexible workplace policy which includes a minimum of 3 days a week onsite." That's schedule info. - Then "We understand compensation is an important factor..." includes pay range: $128,000 to $176,000 annually, plus discretionary bonuses. - Then "US Benefits At Vantive" paragraph describing benefits. - Then "For additional information regarding Vantive’s US Benefits, please speak with your recruiter or visit our Benefits site: Benefits | Vantive" - we can keep as part of Benefits. - Then EEO etc to be removed. - Also "Know Your Rights..." etc removed. - "Recruitment Fraud Notice" removed. Thus sections: - About the role: could include company mission and role overview. - Responsibilities: the "What You'll Be Doing" list. - Requirements: maybe "What You’ll Bring" list (mandatory). Could also include experience guiding agile teams etc. But we can treat "What You’ll Bring" as Requirements. - Qualifications: maybe education requirement: Bachelor's degree in engineering-related field and five years or more of relevant experience. Could be part of Requirements. - Skills: Preferred Skills list. - Benefits: US Benefits description. - Pay: salary range and bonus info. - Schedule: flexible workplace policy (minimum 3 days a week onsite). We must not create sections with filler like "commensurate with experience". Not present. We need to use

for section headings. Use
  • for any list of duties/requirements/benefits. Use

    for prose. We must not repeat job title as heading. Not include Job ID. We must output only HTML fragment. Let's craft. First, maybe a

    about Vantive mission and role. Then

    About the role

    with paragraph(s). Then

    Responsibilities

    with
      list. Then

      Requirements

      with
        list (What You’ll Bring mandatory). Then

        Qualifications

        with

        for degree and years experience. Then

        Skills

        with
          list (Preferred Skills). Then

          Benefits

          with

          describing benefits. Then

          Pay

          with

          salary range and bonus. Then

          Schedule

          with

          flexible workplace policy. Check that we didn't include any boilerplate. Make sure to preserve all substantive info: include details about PrisMax systems, ICU, CRRT, building new platforms, etc. That is in role description; we should include that in About the role or Responsibilities? Probably About the role includes that description. Let's extract substantive sentences: - "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 an experienced Scrum Master / Agile Specialist / Project Leader to drive Agile delivery across cross-functional medical device software development teams. The role involves facilitating Agile practices, managing project timelines, and ensuring smooth collaboration between engineering, product, and business teams. Experience guiding agile (scrum) teams working on embedded device software, controls, and test development in a regulated industry will prepare you well for this position. This is a leadership role, with cross-team and cross-site influence, empowered to exercise servant leadership and impact agile delivery across the acute software organization." - Responsibilities list: * Facilitating Agile ceremonies (stand-ups, sprint planning, retrospectives) for two scrum teams * Managing project timelines, milestones, and dependencies, and cross-project coordination with other agile leaders * Coordinating software, testing, and document release activities * Removing blockers and ensuring smooth team execution * Collaborate with Engineering Leaders, Project Management, and stakeholders * Maintain and manage Jira boards, backlog, and sprint tracking * Monitor team performance using Agile metrics (velocity, burndown) - What You’ll Bring (mandatory): * Strong experience in Agile methodologies (Scrum/Kanban) * Experience in embedded software delivery/processes in a regulated industry * Proficiency in Jira and Confluence * Background in technical project/program management * Excellent communication and stakeholder management * Strong problem-solving and adaptability skills * Bachelor's degree in an engineering-related field and five years or more of relevant experience. - Preferred Skills: * Professional/Expert level certification, such as CSP-SM / PSM-III * Agile Project Management degree or certification such as PMI-ACP * Experience acting as an agile coach within the medical device software development space - Benefits: paragraph about health, dental, vision, life, accident, disability, business travel insurance, Aon Pooled Employer Plan, 401(k), Flexible Spending Accounts, educational assistance, time-off benefits (paid holidays, PTO 20-35 days, family/medical leave, paid parental leave), commuting benefits, Employee Discount Program, EAP, childcare benefits. - Pay: estimated base salary $128,000 to $176,000 annually, discretionary bonuses, note about location, skills, etc. - Schedule: flexible workplace policy includes a minimum of 3 days a week onsite. We must not include "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." That's application instruction; remove. Also remove "For additional information regarding Vantive’s US Benefits, please speak with your recruiter or visit our Benefits site: Benefits | Vantive" - that's also application instruction? It's a reference but could be considered boilerplate; but it's about benefits info. Might be okay to keep? The instruction says remove application instructions. This is a pointer to benefits site; could be considered application instruction. Safer to remove. Thus Benefits section will just have the descriptive paragraph. Now craft HTML. We'll start with a

          for intro mission and role description (maybe combine Vantive mission and role). Then

          About the role

          with maybe a

          that includes the role summary sentences (Vantive seeking..., etc). Or we could put the role summary in About the role. Let's structure:

          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.

          Then

          About the role

          with

          containing: "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 an experienced Scrum Master / Agile Specialist / Project Leader to drive Agile delivery across cross-functional medical device software development teams. The role involves facilitating Agile practices, managing project timelines, and ensuring smooth collaboration between engineering, product, and business teams. Experience guiding agile (scrum) teams working on embedded device software, controls, and test development in a regulated industry will prepare you well for this position. This is a leadership role, with cross-team and cross-site influence, empowered to exercise servant leadership and impact agile delivery across the acute software organization." That seems fine. Then Responsibilities

          Responsibilities

            with each bullet. Then Requirements

            Requirements

              with What You Bring items (including bachelor's degree etc). Could separate degree/experience as separate but it's okay. Then Qualifications

              Qualifications

              maybe we could embed degree/experience there, but we already included in Requirements. To avoid duplication, we could move degree/experience to Qualifications and keep Requirements as the other items (experience, proficiency, etc). Let's do that. Thus: Requirements list: Strong experience in Agile methodologies (Scrum/Kanban); Experience in embedded software delivery/processes in a regulated industry; Proficiency in Jira and Confluence; Background in technical project/program management; Excellent communication

Similar jobs