Head of the Agile Release Train
for section headings (About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)
2. Use - for lists of duties/requirements/benefits, and
for prose
3. Do NOT repeat the job title as a heading
4. Do NOT put Job ID/requisition numbers as headings
4. Preserve ALL substantive information; do NOT invent or summarize away detail
5. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions
6. Include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text
7. Never create Pay/Schedule/Benefits sections unless the posting actually states them
8. Prefer a few substantive sections over many thin ones
9. Output ONLY the HTML fragment — no /, no markdown code fences
Let me analyze the job posting content:
The posting has:
- Job Description Summary of Position (this is the "About the role" section)
- Required Qualifications (with Experience, Education, Soft skills, Certifications)
- Responsibilities (with multiple sub-sections)
- Related Qualities (soft skills/leadership qualities)
- Important Skills (Technical Skills)
- About Us (company info)
- Benefit Highlights (benefits)
- Some boilerplate at the end (Equal Opportunity Employer, Know Your Rights notice)
I need to structure this into appropriate sections. Let me map:
1. "About the role" - from the Summary of Position
2. "Responsibilities" - from the Responsibilities section (with sub-items)
3. "Requirements" or "Qualifications" - from Required Qualifications
4. "Skills" - from Related Qualities and Important Skills
5. "Benefits" - from Benefit Highlights
6. "About the company" - from About Us (but the rules say to use specific headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. "About Us" might not fit exactly, but it's company info. I could include it as a section or fold into a paragraph. The rules don't mention "About the company" as a heading, but it's substantive content. I'll include it as a section with h3 "About the company" or similar. However, the rules say "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It says "e.g." so other headings are allowed. But I should prefer the listed ones. I could put company info under a generic "About the company" heading. But the rules say "include a section ONLY when the posting has real, specific content for it". The About Us section has real content. I'll include it as "About the company".
But note: the rules say "Do NOT repeat the job title as a heading (the page already shows it)". The job title is "Head of an Agile Release" (from the first line). I should not include that as a heading.
Also, there's no Pay or Schedule information, so I won't create those sections.
Now, I need to remove boilerplate: "Equal Opportunity Employer/Protected Veterans/Individuals with Disabilities This employer is required to notify all applicants of their rights pursuant to federal employment laws. For further information, please review the Know Your Rights notice from the Department of Labor." That's legal/EEO boilerplate, remove.
Also remove "Follow Us Facebook X formerly Twitter LinkedIn Instagram YouTube" - that's navigation/social media.
Also remove "More -- FirstHorizon.com/First-Horizon-National-Corporation/Careers/Our-Benefits" - that's a link, but the benefits are listed. I'll keep the benefits list.
Now, structure:
- About the role: the summary paragraph.
- Responsibilities: each bullet point from the Responsibilities section. They are already structured with bold headings and descriptions. I'll make each a list item, perhaps with the bold part as a strong tag inside the li.
- Qualifications: from Required Qualifications. Could be a list of items: Experience, Education, Soft skills, Certifications. Each as a list item.
- Skills: combine Related Qualities and Important Skills. Related Qualities are bullet points, Important Skills has Technical Skills list. I'll make a Skills section with two sub-lists or combined.
- Benefits: from Benefit Highlights, list items.
- About the company: from About Us, a paragraph.
I need to use - for lists,
for prose.
Let me write the HTML.
First, About the role: one paragraph.
About the role
The Head of an Agile Release is responsible for directing the multi-year roadmap for Product Management (Credit Card, Deposits, and Lending) lines of business, ensuring strategic alignment with enterprise banking priorities and regulatory requirements. This leader facilitates Program Increment (PI) and release planning, synchronizes multiple release trains, manages cross-product dependencies, and orchestrates seamless, continuous deployment across consumer and core banking channels. Leveraging predictive AI and analytics, they proactively govern delivery, identify risks, and accelerate the software development life cycle through the adoption of GenAI-powered tools. The role also leads the integration of intelligent automation—such as credit decisioning and real-time fraud mitigation—while enforcing rigorous stage-gate governance from ideation to post-launch. Partnering closely with Model Risk Governance, Fair Lending, Fraud, InfoSec, and Legal, the Head of the ART ensures compliance across all releases and AI models. Finally, they measure and optimize delivery metrics, including ART predictability, deployment frequency, straight-through processing rates, deposit growth efficiency, and defect density, to advance operational success.
Responsibilities: each bullet.
Responsibilities
- Roadmap & Strategic Alignment: Own and direct the multi-year product and technology roadmap across Credit Card, Deposits, and Auto lending lines of business, aligning cross-functional capabilities with enterprise banking priorities and regulatory mandates.
- Program Increment (PI) & Release Planning: Facilitate cadence-based PI planning, synchronize multi-tiered release trains, manage cross-product dependency boards, and orchestrate zero-downtime, continuous deployment pipelines across core banking and consumer-facing channels.
- Intelligent Program Governance & Dependency Mapping: Leverage predictive AI and natural language analytics across project management platforms (e.g., Jira, Azure DevOps) to proactively identify cross-train delivery bottlenecks, forecast sprint velocity, and surface release risks before PI execution.
- Software Development Life Cycle (SDLC) Acceleration & Requirement Engineering: Champion the adoption of GenAI-powered tooling across the value stream to automate user story generation, acceptance criteria synthesis, test case creation, and API contract scaffolding, cutting delivery lead times.
- AI & Intelligent Automation Integration: Spearhead the discovery and deployment of predictive and generative AI capabilities—such as automated credit decisioning, dynamic risk-tiered pricing for auto loans, real-time fraud mitigation, and personalized deposit-growth recommendations.
- End-to-End Stage-Gate Governance: Enforce a structured delivery framework governing initiatives from initial ideation and business case development through Architecture Review, compliance/model risk validation, user testing, and post-launch verification.
- Cross-Functional Risk & Compliance Management: Partner with Model Risk Governance, Fair Lending, Fraud, InfoSec, and Legal to ensure all software releases and AI-driven models strictly satisfy regulatory expectations (FCRA, ECOA, GLBA).
- Delivery Metrics & Success Measurement: Track, optimize, and report on key performance indicators, including ART predictability, cycle time, deployment frequency, automated underwriting straight-through processing (STP) rates, deposit capture efficiency, and post-release defect density.
Qualifications: from Required Qualifications.
Qualifications
- Experience: Minimum of 10-15+ years experience in agile Product or Value Stream management.
- Education: Bachelor’s degree in business, Data Science, or a related field (master’s preferred).
- Soft skills: Strong understanding of customer needs, industry trends, and market dynamics.
- Certifications: Project Management Professional (PMP), ICAgile - Product or SAFe - Product.
Skills: combine Related Qualities and Important Skills.
Skills
- Related Qualities:
- Ability to influence a diverse group of stakeholders; strong leadership skills
- Sees the big picture in terms of strategic Product vision at Value Stream level
- Fosters a culture of collaboration and alignment across Value Stream Leaders
- Represent customer and user needs from a business and technical perspective
- Drive an experimental mindset to spark innovation
- Champion the Value Stream to secure stakeholder alignment, support, and investment
- Strong communication skills with ability to communicate complex messages and trade-offs to tell a compelling story and influence stakeholders
- Technical Skills: JIRA, Confluence, Strategic Leadership, Product Vision Strategy & Development, Architectural Thinking, Cost/Benefit Analysis, Inspire and guide teams by removing barriers rather than commanding work, Neutralize disputes across teams and stakeholders to reach a shared consensus, View the entire value stream and cross-team dependencies instead of isolated parts, Visualize bottlenecks using program Kanban boards and value stream mapping.
But the Technical Skills list is a comma-separated list. I could make each a separate li, but the posting groups them as a list. I'll keep as a single li with the list, or break into multiple li. The rule: use - for any list of duties/requirements/benefits. The Technical Skills are a list of skills. I'll make each skill a separate li under a sub-ul.
Better:
Skills
Related Qualities
- Ability to influence a diverse group of stakeholders; strong leadership skills
- Sees the big picture in terms of strategic Product vision at Value Stream level
- Fosters a culture of collaboration and alignment across Value Stream Leaders
- Represent customer and user needs from a business and technical perspective
- Drive an experimental mindset to spark innovation
- Champion the Value Stream to secure stakeholder alignment, support, and investment
- Strong communication skills with ability to communicate complex messages and trade-offs to tell a compelling story and influence stakeholders
Technical Skills
- JIRA
- Confluence
- Strategic Leadership
- Product Vision Strategy & Development
- Architectural Thinking
- Cost/Benefit Analysis
- Inspire and guide teams by removing barriers rather than commanding work
- Neutralize disputes across teams and stakeholders to reach a shared consensus
- View the entire value stream and cross-team dependencies instead of isolated parts
- Visualize bottlenecks using program Kanban boards and value stream mapping
But the rules say use for section headings. It doesn't mention . But using for subsections is okay semantic HTML. However, the instruction
for prose 3. Do NOT repeat the job title as a heading 4. Do NOT put Job ID/requisition numbers as headings 4. Preserve ALL substantive information; do NOT invent or summarize away detail 5. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions 6. Include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text 7. Never create Pay/Schedule/Benefits sections unless the posting actually states them 8. Prefer a few substantive sections over many thin ones 9. Output ONLY the HTML fragment — no /, no markdown code fences Let me analyze the job posting content: The posting has: - Job Description Summary of Position (this is the "About the role" section) - Required Qualifications (with Experience, Education, Soft skills, Certifications) - Responsibilities (with multiple sub-sections) - Related Qualities (soft skills/leadership qualities) - Important Skills (Technical Skills) - About Us (company info) - Benefit Highlights (benefits) - Some boilerplate at the end (Equal Opportunity Employer, Know Your Rights notice) I need to structure this into appropriate sections. Let me map: 1. "About the role" - from the Summary of Position 2. "Responsibilities" - from the Responsibilities section (with sub-items) 3. "Requirements" or "Qualifications" - from Required Qualifications 4. "Skills" - from Related Qualities and Important Skills 5. "Benefits" - from Benefit Highlights 6. "About the company" - from About Us (but the rules say to use specific headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. "About Us" might not fit exactly, but it's company info. I could include it as a section or fold into a paragraph. The rules don't mention "About the company" as a heading, but it's substantive content. I'll include it as a section with h3 "About the company" or similar. However, the rules say "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". It says "e.g." so other headings are allowed. But I should prefer the listed ones. I could put company info under a generic "About the company" heading. But the rules say "include a section ONLY when the posting has real, specific content for it". The About Us section has real content. I'll include it as "About the company".
But note: the rules say "Do NOT repeat the job title as a heading (the page already shows it)". The job title is "Head of an Agile Release" (from the first line). I should not include that as a heading.
Also, there's no Pay or Schedule information, so I won't create those sections.
Now, I need to remove boilerplate: "Equal Opportunity Employer/Protected Veterans/Individuals with Disabilities This employer is required to notify all applicants of their rights pursuant to federal employment laws. For further information, please review the Know Your Rights notice from the Department of Labor." That's legal/EEO boilerplate, remove.
Also remove "Follow Us Facebook X formerly Twitter LinkedIn Instagram YouTube" - that's navigation/social media.
Also remove "More -- FirstHorizon.com/First-Horizon-National-Corporation/Careers/Our-Benefits" - that's a link, but the benefits are listed. I'll keep the benefits list.
Now, structure:
- About the role: the summary paragraph.
- Responsibilities: each bullet point from the Responsibilities section. They are already structured with bold headings and descriptions. I'll make each a list item, perhaps with the bold part as a strong tag inside the li.
- Qualifications: from Required Qualifications. Could be a list of items: Experience, Education, Soft skills, Certifications. Each as a list item.
- Skills: combine Related Qualities and Important Skills. Related Qualities are bullet points, Important Skills has Technical Skills list. I'll make a Skills section with two sub-lists or combined.
- Benefits: from Benefit Highlights, list items.
- About the company: from About Us, a paragraph.
I need to use - for lists,
for prose.
Let me write the HTML.
First, About the role: one paragraph.
About the role
The Head of an Agile Release is responsible for directing the multi-year roadmap for Product Management (Credit Card, Deposits, and Lending) lines of business, ensuring strategic alignment with enterprise banking priorities and regulatory requirements. This leader facilitates Program Increment (PI) and release planning, synchronizes multiple release trains, manages cross-product dependencies, and orchestrates seamless, continuous deployment across consumer and core banking channels. Leveraging predictive AI and analytics, they proactively govern delivery, identify risks, and accelerate the software development life cycle through the adoption of GenAI-powered tools. The role also leads the integration of intelligent automation—such as credit decisioning and real-time fraud mitigation—while enforcing rigorous stage-gate governance from ideation to post-launch. Partnering closely with Model Risk Governance, Fair Lending, Fraud, InfoSec, and Legal, the Head of the ART ensures compliance across all releases and AI models. Finally, they measure and optimize delivery metrics, including ART predictability, deployment frequency, straight-through processing rates, deposit growth efficiency, and defect density, to advance operational success.
Responsibilities: each bullet.
Responsibilities
- Roadmap & Strategic Alignment: Own and direct the multi-year product and technology roadmap across Credit Card, Deposits, and Auto lending lines of business, aligning cross-functional capabilities with enterprise banking priorities and regulatory mandates.
- Program Increment (PI) & Release Planning: Facilitate cadence-based PI planning, synchronize multi-tiered release trains, manage cross-product dependency boards, and orchestrate zero-downtime, continuous deployment pipelines across core banking and consumer-facing channels.
- Intelligent Program Governance & Dependency Mapping: Leverage predictive AI and natural language analytics across project management platforms (e.g., Jira, Azure DevOps) to proactively identify cross-train delivery bottlenecks, forecast sprint velocity, and surface release risks before PI execution.
- Software Development Life Cycle (SDLC) Acceleration & Requirement Engineering: Champion the adoption of GenAI-powered tooling across the value stream to automate user story generation, acceptance criteria synthesis, test case creation, and API contract scaffolding, cutting delivery lead times.
- AI & Intelligent Automation Integration: Spearhead the discovery and deployment of predictive and generative AI capabilities—such as automated credit decisioning, dynamic risk-tiered pricing for auto loans, real-time fraud mitigation, and personalized deposit-growth recommendations.
- End-to-End Stage-Gate Governance: Enforce a structured delivery framework governing initiatives from initial ideation and business case development through Architecture Review, compliance/model risk validation, user testing, and post-launch verification.
- Cross-Functional Risk & Compliance Management: Partner with Model Risk Governance, Fair Lending, Fraud, InfoSec, and Legal to ensure all software releases and AI-driven models strictly satisfy regulatory expectations (FCRA, ECOA, GLBA).
- Delivery Metrics & Success Measurement: Track, optimize, and report on key performance indicators, including ART predictability, cycle time, deployment frequency, automated underwriting straight-through processing (STP) rates, deposit capture efficiency, and post-release defect density.
Qualifications: from Required Qualifications.
Qualifications
- Experience: Minimum of 10-15+ years experience in agile Product or Value Stream management.
- Education: Bachelor’s degree in business, Data Science, or a related field (master’s preferred).
- Soft skills: Strong understanding of customer needs, industry trends, and market dynamics.
- Certifications: Project Management Professional (PMP), ICAgile - Product or SAFe - Product.
Skills: combine Related Qualities and Important Skills.
Skills
- Related Qualities:
- Ability to influence a diverse group of stakeholders; strong leadership skills
- Sees the big picture in terms of strategic Product vision at Value Stream level
- Fosters a culture of collaboration and alignment across Value Stream Leaders
- Represent customer and user needs from a business and technical perspective
- Drive an experimental mindset to spark innovation
- Champion the Value Stream to secure stakeholder alignment, support, and investment
- Strong communication skills with ability to communicate complex messages and trade-offs to tell a compelling story and influence stakeholders
- Technical Skills: JIRA, Confluence, Strategic Leadership, Product Vision Strategy & Development, Architectural Thinking, Cost/Benefit Analysis, Inspire and guide teams by removing barriers rather than commanding work, Neutralize disputes across teams and stakeholders to reach a shared consensus, View the entire value stream and cross-team dependencies instead of isolated parts, Visualize bottlenecks using program Kanban boards and value stream mapping.
But the Technical Skills list is a comma-separated list. I could make each a separate li, but the posting groups them as a list. I'll keep as a single li with the list, or break into multiple li. The rule: use - for any list of duties/requirements/benefits. The Technical Skills are a list of skills. I'll make each skill a separate li under a sub-ul.
Better:
Skills
Related Qualities
- Ability to influence a diverse group of stakeholders; strong leadership skills
- Sees the big picture in terms of strategic Product vision at Value Stream level
- Fosters a culture of collaboration and alignment across Value Stream Leaders
- Represent customer and user needs from a business and technical perspective
- Drive an experimental mindset to spark innovation
- Champion the Value Stream to secure stakeholder alignment, support, and investment
- Strong communication skills with ability to communicate complex messages and trade-offs to tell a compelling story and influence stakeholders
Technical Skills
- JIRA
- Confluence
- Strategic Leadership
- Product Vision Strategy & Development
- Architectural Thinking
- Cost/Benefit Analysis
- Inspire and guide teams by removing barriers rather than commanding work
- Neutralize disputes across teams and stakeholders to reach a shared consensus
- View the entire value stream and cross-team dependencies instead of isolated parts
- Visualize bottlenecks using program Kanban boards and value stream mapping
But the rules say use for section headings. It doesn't mention . But using for subsections is okay semantic HTML. However, the instruction
for prose. Let me write the HTML. First, About the role: one paragraph.
About the role
The Head of an Agile Release is responsible for directing the multi-year roadmap for Product Management (Credit Card, Deposits, and Lending) lines of business, ensuring strategic alignment with enterprise banking priorities and regulatory requirements. This leader facilitates Program Increment (PI) and release planning, synchronizes multiple release trains, manages cross-product dependencies, and orchestrates seamless, continuous deployment across consumer and core banking channels. Leveraging predictive AI and analytics, they proactively govern delivery, identify risks, and accelerate the software development life cycle through the adoption of GenAI-powered tools. The role also leads the integration of intelligent automation—such as credit decisioning and real-time fraud mitigation—while enforcing rigorous stage-gate governance from ideation to post-launch. Partnering closely with Model Risk Governance, Fair Lending, Fraud, InfoSec, and Legal, the Head of the ART ensures compliance across all releases and AI models. Finally, they measure and optimize delivery metrics, including ART predictability, deployment frequency, straight-through processing rates, deposit growth efficiency, and defect density, to advance operational success.
Responsibilities: each bullet.Responsibilities
- Roadmap & Strategic Alignment: Own and direct the multi-year product and technology roadmap across Credit Card, Deposits, and Auto lending lines of business, aligning cross-functional capabilities with enterprise banking priorities and regulatory mandates.
- Program Increment (PI) & Release Planning: Facilitate cadence-based PI planning, synchronize multi-tiered release trains, manage cross-product dependency boards, and orchestrate zero-downtime, continuous deployment pipelines across core banking and consumer-facing channels.
- Intelligent Program Governance & Dependency Mapping: Leverage predictive AI and natural language analytics across project management platforms (e.g., Jira, Azure DevOps) to proactively identify cross-train delivery bottlenecks, forecast sprint velocity, and surface release risks before PI execution.
- Software Development Life Cycle (SDLC) Acceleration & Requirement Engineering: Champion the adoption of GenAI-powered tooling across the value stream to automate user story generation, acceptance criteria synthesis, test case creation, and API contract scaffolding, cutting delivery lead times.
- AI & Intelligent Automation Integration: Spearhead the discovery and deployment of predictive and generative AI capabilities—such as automated credit decisioning, dynamic risk-tiered pricing for auto loans, real-time fraud mitigation, and personalized deposit-growth recommendations.
- End-to-End Stage-Gate Governance: Enforce a structured delivery framework governing initiatives from initial ideation and business case development through Architecture Review, compliance/model risk validation, user testing, and post-launch verification.
- Cross-Functional Risk & Compliance Management: Partner with Model Risk Governance, Fair Lending, Fraud, InfoSec, and Legal to ensure all software releases and AI-driven models strictly satisfy regulatory expectations (FCRA, ECOA, GLBA).
- Delivery Metrics & Success Measurement: Track, optimize, and report on key performance indicators, including ART predictability, cycle time, deployment frequency, automated underwriting straight-through processing (STP) rates, deposit capture efficiency, and post-release defect density.
Qualifications
- Experience: Minimum of 10-15+ years experience in agile Product or Value Stream management.
- Education: Bachelor’s degree in business, Data Science, or a related field (master’s preferred).
- Soft skills: Strong understanding of customer needs, industry trends, and market dynamics.
- Certifications: Project Management Professional (PMP), ICAgile - Product or SAFe - Product.
Skills
- Related Qualities:
- Ability to influence a diverse group of stakeholders; strong leadership skills
- Sees the big picture in terms of strategic Product vision at Value Stream level
- Fosters a culture of collaboration and alignment across Value Stream Leaders
- Represent customer and user needs from a business and technical perspective
- Drive an experimental mindset to spark innovation
- Champion the Value Stream to secure stakeholder alignment, support, and investment
- Strong communication skills with ability to communicate complex messages and trade-offs to tell a compelling story and influence stakeholders
- Technical Skills: JIRA, Confluence, Strategic Leadership, Product Vision Strategy & Development, Architectural Thinking, Cost/Benefit Analysis, Inspire and guide teams by removing barriers rather than commanding work, Neutralize disputes across teams and stakeholders to reach a shared consensus, View the entire value stream and cross-team dependencies instead of isolated parts, Visualize bottlenecks using program Kanban boards and value stream mapping.
- for any list of duties/requirements/benefits. The Technical Skills are a list of skills. I'll make each skill a separate li under a sub-ul.
Better:
Skills
Related Qualities
- Ability to influence a diverse group of stakeholders; strong leadership skills
- Sees the big picture in terms of strategic Product vision at Value Stream level
- Fosters a culture of collaboration and alignment across Value Stream Leaders
- Represent customer and user needs from a business and technical perspective
- Drive an experimental mindset to spark innovation
- Champion the Value Stream to secure stakeholder alignment, support, and investment
- Strong communication skills with ability to communicate complex messages and trade-offs to tell a compelling story and influence stakeholders
Technical Skills
- JIRA
- Confluence
- Strategic Leadership
- Product Vision Strategy & Development
- Architectural Thinking
- Cost/Benefit Analysis
- Inspire and guide teams by removing barriers rather than commanding work
- Neutralize disputes across teams and stakeholders to reach a shared consensus
- View the entire value stream and cross-team dependencies instead of isolated parts
- Visualize bottlenecks using program Kanban boards and value stream mapping
for section headings. It doesn't mention
. But using
for subsections is okay semantic HTML. However, the instruction