Software Release Manager
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title as heading. We need to include sections only if posting has real specific content. We have content: About the role (the first paragraph about opportunity and role description). Responsibilities (list). Requirements (the Individual Required bullet list). Qualifications? There's Preferred section maybe qualifies as Qualifications? The posting includes "Preferred" bullet list. Could treat as Qualifications or Skills. Also there is "Key Working Relationships" maybe not needed. There's "How We Work" maybe not needed. There's "Work Environment" maybe not needed. There's "Salary Transparency" includes Pay and Benefits. There's also "Benefits" described. So we need sections: About the role (maybe heading "About the role") containing the initial description (the opportunity paragraph and role description). Responsibilities (list). Requirements (the Individual Required bullet list). Qualifications (maybe Preferred bullet list). Skills (maybe combine? but we can put skills under Qualifications? The instruction: use headings for section headings e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections have content.
We have:
- About the role: The Opportunity paragraph + The Role paragraph(s). That's content.
- Responsibilities: list of bullet points under "The Responsibilities". Good.
- Requirements: The Individual Required bullet list (starting with "Bachelor’s degree...").
- Qualifications: The Preferred bullet list (starting with "3+ years of experience as Scrum Master...").
- Skills: Could we extract skills from responsibilities? Might be redundant. But we could include a Skills section summarizing technical & soft skills? However we must not invent or summarize away detail; we should only include if posting has real specific content for it. The posting does not have a separate "Skills" heading; but we could treat the "Technical & System Awareness" etc as part of responsibilities. Might be better to not create Skills section if no explicit skills list. However the instruction says "Prefer a few substantive sections over many thin ones." So we could omit Skills.
- Benefits: The posting includes benefits description under "QuidelOrtho offers a comprehensive benefits package...". So we can have Benefits section.
- Pay: Salary range described: "The salary range for this position is $140,000 to $160,000 and is bonus eligible." So we can have Pay section.
- Schedule: The posting mentions hybrid 2 days onsite at San Diego location, also "This position will be working hybrid 2 days onsite at our San Diego (Summers Ridge) location." Also "Minimal travel required." So we can have Schedule section with hybrid work info.
We must not include boilerplate like EEO, legal, etc. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we need to strip the Equal Opportunity paragraph, etc.
Also we need to preserve all substantive information; do not invent or summarize away detail. So we need to keep details like hybrid 2 days onsite, salary range, benefits list, etc.
We must output only HTML fragment, no /, no markdown fences.
We need to use for section headings. Use - for any list of duties/requirements/benefits, and
for prose.
We need to ensure we don't repeat job title as heading. The job title is "Software Release Manager". Not to be used as heading.
We need to embed content appropriately.
Let's extract sections:
About the role: combine the opportunity paragraph and role description.
Opportunity paragraph: "The Opportunity QuidelOrtho unites the strengths of Quidel Corporation and Ortho Clinical Diagnostics, creating a world-leading in vitro diagnostics company with award-winning expertise in immunoassay and molecular testing, clinical chemistry and transfusion medicine. We are more than 6,000 strong and do business in over 130 countries, providing answers with fast, accurate and consistent testing where and when they are needed most – home to hospital, lab to clinic. Our culture puts our team members first and prioritizes actions that support happiness, inspiration and engagement. We strive to build meaningful connections with each other as we believe that employee happiness and business success are linked. Join us in our mission to transform the power of diagnostics into a healthier future for all."
Then The Role paragraph: "At QuidelOrtho, we’re advancing the power of diagnostics for a healthier future for all. Join our mission as our next Software Release Manager to join our R&D Instrument Platforms organization. This role combines scrum leadership with software release management accountability, focusing on the end-to-end planning, coordination, and execution of software releases for regulated medical device systems. The Software Release Manager is embedded within Agile development teams while also maintaining a system-level view of SDLC, integration, and release readiness. This role ensures predictable, high-quality software releases by coordinating across multiple internal and external team members, managing dependencies, mitigating risk, and aligning execution with regulatory and business objectives. This position will be working hybrid 2 days onsite at our San Diego (Summers Ridge) location."
We could keep that as prose.
Responsibilities: list bullet points under "The Responsibilities". Let's capture them exactly:
- Release Planning and Ownership
- Own end-to-end software release from planning through deployment, ensuring on-time, on-scope, and high-quality outcomes.
- Develop and manage integrated release plans, including dependencies, milestones, and critical paths along with resource forecasts.
- Coordinate cross-team integration activities to ensure system-level readiness and stability.
- Drive release readiness processes per metrics of definition of done, entry/exit criteria, and go/no-go decision support.
- Track Agile metrics (velocity, burndown, predictability) and team performance through disciplined management in systems like ADO.
- Remove impediments and foster a culture of accountability, collaboration, and continuous improvement.
- Plan, track and manage project costs within allocated budget.
- Technical & System Awareness
- Maintain working knowledge of system architecture, software components, and integration points sufficient to anticipate release risks.
- Understand the technical state of work items to accurately assess progress and risks.
- Risk, Quality, and Compliance
- Identify and proactively mitigate technical, schedule, quality, budget and integration risks.
- Ensure adherence to regulatory standards (FDA, ISO 13485, IEC 62304) and internal design controls.
- Ensure audit readiness by ensuring documentation completeness and traceability across releases.
- Support internal and external audits.
- Stakeholder & Vendor Management
- Serve as a primary Instrument Software interface at Project meetings.
- Coordinate across engineering, systems, quality, regulatory, and product stakeholders.
- Manage vendor relationships and external development partners, including statement of work, cost, milestones, performance, and change control.
- Provide clear, data-driven status reporting on release progress, risks, and mitigation plans.
- Communicate release scope, timelines, and readiness to leadership and cross-functional partners.
- Continuous Improvement & Process Excellence
- Champion best practices in Agile Framework, DevOps, and release management.
- Identify opportunities to improve release predictability, quality, and team effectiveness.
- Coach teams and stakeholders in Agile best practices within a hybrid Scrum environment.
- Perform other work-related duties as assigned.
We need to output as
- for any list of duties/requirements/benefits. Should we nest subheadings? Probably just flat list items; but we could keep headings inside li? The instruction: use
- for any list of duties/requirements/benefits. It doesn't forbid other tags inside li. We could keep the bold headings as plain text inside li.
Simplify: each bullet as
- with the text.
Requirements: The Individual Required bullet list:
- Bachelor’s degree, preferably in Computer Science, Software Engineering, or related STEM field (or equivalent experience).
- 8+ years of experience in software program management, Agile environments, or related experience.
- Demonstrated experience delivering complex software systems in cross-functional environments
- Experience managing schedules, budgets, resources, and vendor engagements
- Strong knowledge of Agile methodologies (Scrum) and release management practices.
- Experience with tools such as Azure DevOps, JIRA, or similar Agile lifecycle tools
- Ability to manage dependencies across multiple teams and systems
- Strong understanding of software development lifecycle and integration practices.
- Excellent communication skills with ability to translate technical concepts to business audiences.
- Strong ownership and accountability for software release outcomes.
- Ability to balance tactical team support with strategic oversight.
- Proven ability to identify and mitigate risks in complex systems.
- Effective cross-functional collaboration across engineering, QA, regulatory, and operations.
- Adaptability in fast-paced and evolving environments
- This position is not currently eligible for visa sponsorship
- Ability to travel up to 10%
We need to keep all.
Qualifications (Preferred): bullet list:
- 3+ years of experience as Scrum Master or Agile team facilitator.
- Experience in regulated medical device software development.
- Familiarity with FDA, ISO 13485, and IEC 62304, and design control processes.
- Awareness of DevOps, CI/CD pipelines, and release automation.
- Experience working with distributed or external development teams.
Benefits: description: "QuidelOrtho offers a comprehensive benefits package including medical, dental, vision, life, and disability insurance, along with a 401(k) plan, employee assistance program, Employee Stock Purchase Plan, paid time off (including sick time), and paid Holidays. All benefits are non-contractual, and QuidelOrtho may amend, terminate, or enhance the benefits provided, as it deems appropriate."
We could turn that into a list? It's a sentence; we can keep as
. Or we could split into list items but not required. Use
for prose.
Pay: Salary range: "The salary range for this position takes into account a wide range of factors including education, experience, knowledge, skills, geography, and abilities of the candidate, in addition to internal equity and alignment with market data. At QuidelOrtho, it is not typical for an individual to be hired at or near the top range for their role and compensation decisions are dependent on the facts and circumstances of each case. The salary range for this position is $140,000 to $160,000 and is bonus eligible."
We could keep as
.
Schedule: hybrid 2 days onsite at San Diego (Summers Ridge) location. Also mention minimal travel required, travel includes airplane, automobile travel and overnight hotel. Also "30% of time in meetings, working with team, or talking on the phone, 70% of the time at the desk on computer, doing analytical work." That's from Work Environment but could be schedule. We'll include schedule info: hybrid work, travel expectations, time split.
We need to avoid duplicating lines. Ensure we don't include boilerplate like "Equal Opportunity" etc.
Now construct HTML:
About the role
...combined paragraphs...
Responsibilities
- ... each bullet ...
...
Requirements
- ... each bullet ...
...
Qualifications
- ... each bullet ...
...
Benefits
... benefits paragraph ...
Pay
... salary paragraph ...
Schedule
... schedule paragraph ...
Make sure no extra whitespace issues.
Now craft the content precisely.
About the role paragraph:
- for any list of duties/requirements/benefits, and
for prose. We need to ensure we don't repeat job title as heading. The job title is "Software Release Manager". Not to be used as heading. We need to embed content appropriately. Let's extract sections: About the role: combine the opportunity paragraph and role description. Opportunity paragraph: "The Opportunity QuidelOrtho unites the strengths of Quidel Corporation and Ortho Clinical Diagnostics, creating a world-leading in vitro diagnostics company with award-winning expertise in immunoassay and molecular testing, clinical chemistry and transfusion medicine. We are more than 6,000 strong and do business in over 130 countries, providing answers with fast, accurate and consistent testing where and when they are needed most – home to hospital, lab to clinic. Our culture puts our team members first and prioritizes actions that support happiness, inspiration and engagement. We strive to build meaningful connections with each other as we believe that employee happiness and business success are linked. Join us in our mission to transform the power of diagnostics into a healthier future for all." Then The Role paragraph: "At QuidelOrtho, we’re advancing the power of diagnostics for a healthier future for all. Join our mission as our next Software Release Manager to join our R&D Instrument Platforms organization. This role combines scrum leadership with software release management accountability, focusing on the end-to-end planning, coordination, and execution of software releases for regulated medical device systems. The Software Release Manager is embedded within Agile development teams while also maintaining a system-level view of SDLC, integration, and release readiness. This role ensures predictable, high-quality software releases by coordinating across multiple internal and external team members, managing dependencies, mitigating risk, and aligning execution with regulatory and business objectives. This position will be working hybrid 2 days onsite at our San Diego (Summers Ridge) location." We could keep that as prose. Responsibilities: list bullet points under "The Responsibilities". Let's capture them exactly: - Release Planning and Ownership - Own end-to-end software release from planning through deployment, ensuring on-time, on-scope, and high-quality outcomes. - Develop and manage integrated release plans, including dependencies, milestones, and critical paths along with resource forecasts. - Coordinate cross-team integration activities to ensure system-level readiness and stability. - Drive release readiness processes per metrics of definition of done, entry/exit criteria, and go/no-go decision support. - Track Agile metrics (velocity, burndown, predictability) and team performance through disciplined management in systems like ADO. - Remove impediments and foster a culture of accountability, collaboration, and continuous improvement. - Plan, track and manage project costs within allocated budget. - Technical & System Awareness - Maintain working knowledge of system architecture, software components, and integration points sufficient to anticipate release risks. - Understand the technical state of work items to accurately assess progress and risks. - Risk, Quality, and Compliance - Identify and proactively mitigate technical, schedule, quality, budget and integration risks. - Ensure adherence to regulatory standards (FDA, ISO 13485, IEC 62304) and internal design controls. - Ensure audit readiness by ensuring documentation completeness and traceability across releases. - Support internal and external audits. - Stakeholder & Vendor Management - Serve as a primary Instrument Software interface at Project meetings. - Coordinate across engineering, systems, quality, regulatory, and product stakeholders. - Manage vendor relationships and external development partners, including statement of work, cost, milestones, performance, and change control. - Provide clear, data-driven status reporting on release progress, risks, and mitigation plans. - Communicate release scope, timelines, and readiness to leadership and cross-functional partners. - Continuous Improvement & Process Excellence - Champion best practices in Agile Framework, DevOps, and release management. - Identify opportunities to improve release predictability, quality, and team effectiveness. - Coach teams and stakeholders in Agile best practices within a hybrid Scrum environment. - Perform other work-related duties as assigned. We need to output as
- for any list of duties/requirements/benefits. Should we nest subheadings? Probably just flat list items; but we could keep headings inside li? The instruction: use
- for any list of duties/requirements/benefits. It doesn't forbid other tags inside li. We could keep the bold headings as plain text inside li. Simplify: each bullet as
- with the text.
Requirements: The Individual Required bullet list:
- Bachelor’s degree, preferably in Computer Science, Software Engineering, or related STEM field (or equivalent experience).
- 8+ years of experience in software program management, Agile environments, or related experience.
- Demonstrated experience delivering complex software systems in cross-functional environments
- Experience managing schedules, budgets, resources, and vendor engagements
- Strong knowledge of Agile methodologies (Scrum) and release management practices.
- Experience with tools such as Azure DevOps, JIRA, or similar Agile lifecycle tools
- Ability to manage dependencies across multiple teams and systems
- Strong understanding of software development lifecycle and integration practices.
- Excellent communication skills with ability to translate technical concepts to business audiences.
- Strong ownership and accountability for software release outcomes.
- Ability to balance tactical team support with strategic oversight.
- Proven ability to identify and mitigate risks in complex systems.
- Effective cross-functional collaboration across engineering, QA, regulatory, and operations.
- Adaptability in fast-paced and evolving environments
- This position is not currently eligible for visa sponsorship
- Ability to travel up to 10%
We need to keep all.
Qualifications (Preferred): bullet list:
- 3+ years of experience as Scrum Master or Agile team facilitator.
- Experience in regulated medical device software development.
- Familiarity with FDA, ISO 13485, and IEC 62304, and design control processes.
- Awareness of DevOps, CI/CD pipelines, and release automation.
- Experience working with distributed or external development teams.
Benefits: description: "QuidelOrtho offers a comprehensive benefits package including medical, dental, vision, life, and disability insurance, along with a 401(k) plan, employee assistance program, Employee Stock Purchase Plan, paid time off (including sick time), and paid Holidays. All benefits are non-contractual, and QuidelOrtho may amend, terminate, or enhance the benefits provided, as it deems appropriate."
We could turn that into a list? It's a sentence; we can keep as
. Or we could split into list items but not required. Use
for prose. Pay: Salary range: "The salary range for this position takes into account a wide range of factors including education, experience, knowledge, skills, geography, and abilities of the candidate, in addition to internal equity and alignment with market data. At QuidelOrtho, it is not typical for an individual to be hired at or near the top range for their role and compensation decisions are dependent on the facts and circumstances of each case. The salary range for this position is $140,000 to $160,000 and is bonus eligible." We could keep as
. Schedule: hybrid 2 days onsite at San Diego (Summers Ridge) location. Also mention minimal travel required, travel includes airplane, automobile travel and overnight hotel. Also "30% of time in meetings, working with team, or talking on the phone, 70% of the time at the desk on computer, doing analytical work." That's from Work Environment but could be schedule. We'll include schedule info: hybrid work, travel expectations, time split. We need to avoid duplicating lines. Ensure we don't include boilerplate like "Equal Opportunity" etc. Now construct HTML:
About the role
...combined paragraphs...
Responsibilities
- ... each bullet ... ...
Requirements
- ... each bullet ... ...
Qualifications
- ... each bullet ... ...
Benefits
... benefits paragraph ...
Pay
... salary paragraph ...
Schedule
... schedule paragraph ...
Make sure no extra whitespace issues. Now craft the content precisely. About the role paragraph:
- for any list of duties/requirements/benefits. Should we nest subheadings? Probably just flat list items; but we could keep headings inside li? The instruction: use