Regional Director
for section headings. Use - for any list of duties/requirements/benefits, and
for prose.
We need to preserve all substantive information, remove boilerplate (EEO, equal opportunity, etc). Also remove duplicated lines, navigation, cookie, legal, scam-warning, application instructions. The posting includes "We are an equal opportunity employer..." which is boilerplate; remove. Also "The above job description is not intended to be an “all inclusive” list..." also boilerplate; remove.
We need to keep the brief description (intro) maybe as a
under no heading? The instruction: Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it.
Thus we can have a leading
for the brief description (the "Brief Description At The IRONMAN Group..."). Then sections: About the role (maybe from "The Opportunity" paragraph). Responsibilities (from Responsibilities & Duties). Qualifications (from Qualifications/Experience). Possibly Skills (maybe combine some). But we need to only include sections when posting has real specific content. The posting includes responsibilities list, qualifications list, physical & equipment requirements (maybe part of qualifications). There's no explicit Skills section separate; but we could treat Qualifications as covering skills. However we have both Qualifications and Skills as possible headings; we should only include if there is content. The posting includes "Qualifications/Experience" which is a mix of qualifications and experience; we can put that under Qualifications heading. There's also a list of abilities under Qualifications/Experience that could be considered skills; but we can just put them under Qualifications.
We also have Physical & Equipment Requirements; could be part of Qualifications or a separate section like Requirements? The instruction says use headings like Requirements, Qualifications, Skills. We could put Physical & Equipment Requirements under Requirements heading. Or we could create a Requirements heading and include that list.
We need to decide: The posting has "Qualifications/Experience" and "Physical & Equipment Requirements". Both are substantive. We could have two sections: Qualifications (covering degree, experience, etc) and Requirements (covering physical/equipment). Or we could combine them under Qualifications. But the instruction says prefer a few substantive sections over many thin ones. So maybe combine into Qualifications (including physical). However the physical requirements are distinct; but we could still include them under Qualifications as bullet points.
We also need to include any list as
- . For prose, use
.
We need to preserve all substantive information: The brief description paragraph(s) about purpose, BE ICONIC vision, etc. Also the "The Opportunity" paragraph describing role. Also the responsibilities list (multiple bullet points). Also the qualifications list. Also the physical & equipment requirements list. Also the KPIs section? The posting includes "Key Performance Indicators (KPIs)" with bullet points. That is substantive; should be included perhaps under a heading like "Key Performance Indicators" but not in the allowed headings list. However we could treat KPIs as part of Responsibilities or maybe a separate section; but the instruction only gave examples of headings, not an exhaustive list; we could add other headings if needed? It says "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The e.g. suggests those are examples, but we should likely stick to those headings only? It says "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". It doesn't forbid other headings, but the examples are given. Safer to stick to those headings; we can map KPIs under Responsibilities or maybe under a separate heading like "Performance Metrics" but not in list. Might be better to include under Responsibilities as a sub-list? However the instruction says use - for any list of duties/requirements/benefits. KPIs are a list of metrics; could be considered duties? Not exactly. But we could still include as a list under a heading like "Key Performance Indicators" but that's not one of the examples. However the instruction didn't forbid other headings; it just gave examples. I'd say we can add a heading for KPIs if we want, but to be safe, maybe incorporate KPIs under Responsibilities as a sub-section? But the instruction says "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say we cannot use other headings, but the examples are typical sections. I'd include KPIs as a separate heading maybe "Key Performance Indicators". However the instruction says "Prefer a few substantive sections over many thin ones." Adding KPIs as a separate section may be thin but it's substantive. Could merge into Responsibilities.
Let's think: The posting includes a lot of detail; we want to preserve all. If we merge KPIs into Responsibilities, we still preserve the content. That's okay.
Thus sections: About the role (from The Opportunity). Responsibilities (combining Responsibilities & Duties and KPIs). Qualifications (combining Qualifications/Experience and Physical & Equipment Requirements). Possibly Skills? Not needed.
We need to ensure we don't include boilerplate: remove EEO statement, the "We are an equal opportunity employer..." and the "The above job description is not intended to be an “all inclusive” list..." Also remove navigation/footer etc. There's no explicit navigation in the text.
Now craft HTML.
We'll start with a
for brief description: "Brief Description At The IRONMAN Group, our purpose is clear: to inspire people to unlock their greatest potential through sport, pushing beyond limits to become the fullest expression of human achievement. Through our BE ICONIC vision, we are building the most loved brands, producing the world’s most inspiring events, and fostering deeply engaged communities that change lives. We aim to empower over a million athletes to cross a finish line each year and inspire a billion people worldwide through the power of the human spirit. As part of our team, you’ll join a high-performance, caring culture where innovation thrives, communities are uplifted, and every achievement, big or small, is celebrated. You’ll help shape experiences that fill hearts, consume minds, and enrich souls. This is more than a job. It’s a chance to be part of a global movement, to lead from the front, and to leave a legacy. Together, we create moments that last a lifetime. The IRONMAN Group is the world's largest operator of mass participation sports, delivering over 200+ events a year across 55+ countries thanks to a passionate global team. For more information, visit www.ironman.com/about-ironman-group."
Then maybe a
for metadata: "We are seeking a highly motivated individual for the position of Regional Director reporting to MD, North America & World Championship Events based in North America." But instruction says do NOT put Job ID/requisition numbers as headings — fold minor metadata into a short
or drop it. This is metadata about the role; we can include as a short
before About the role.
Then
About the role
and then a containing the Opportunity paragraph: "The Opportunity The Regional Director serves as the representative of The IRONMAN Group within assigned markets, driving regional strategy, business development, and operational excellence. This role leads a team of Operations Managers and Race Directors to deliver world-class IRONMAN events that create life-changing experiences for athletes worldwide. As the operational and strategic leader of the region, the Regional Director holds ultimate responsibility for safe event execution, athlete experience outcomes, and financial results. The role carries full accountability for regional performance across safety, permits and compliance, risk management, operational delivery, and the regional P&L, ensuring profitability and alignment with the company’s long-range plan. Additionally, the Regional Director fosters cross-functional collaboration and champions talent development across all levels. The role is also expected to build trusted, visible relationships across the community ecosystem - including athletes, clubs, coaches, host cities, local businesses, volunteers, public safety partners, and residents - recognizing that relationships are a core part of the IRONMAN experience and a critical driver of long-term event success."
We need to ensure we keep the dash and hyphens; fine.
Then
Responsibilities
and then a with - items for each duty and KPI.
We need to extract list items from Responsibilities & Duties and KPIs.
Responsibilities & Duties sections:
- Strategic Leadership
* Define and execute regional strategy aligned with global objectives.
* Drive operational excellence and continuous improvement across all events.
- Event Delivery
* Ensure safe, high-quality execution of all IRONMAN events in the region.
* Oversee compliance with technical standards, procedures, and risk management protocols.
- Financial Management
* Own regional P&L performance, budgeting, and forecasting; partner closely with Finance to highlight key drivers of business performance.
* Monitor financial performance and implement cost optimization strategies.
* Proactive outreach to municipalities and vendors to enable efficient growth of the region (i.e., revenue is growing faster than costs).
* Partner closely with Marketing and Finance to align course capacity and athlete sales targets.
- People Leadership, Culture & Performance
* Lead, coach, and develop a high performing team through clear expectations, regular feedback, and meaningful career conversations.
* Model IRONMAN’s BE ICONIC behaviors and athlete first mindset in daily decisions, team rituals, and onsite/offsite leadership presence.
* Build a culture of creativity, accountability, and continuous improvement, encouraging experimentation and learning across events.
* Partner cross functionally to strengthen alignment, shared ownership, and consistency of experience across the event ecosystem.
* Take active ownership of team engagement, clarity of roles, and performance outcomes.
- Business Development
* Identify and pursue opportunities for new events, acquisitions, and renewals engaging with key Business Development stakeholders
* Support commercial growth initiatives in line with IRONMAN’s long-range plan.
- Safety & Critical Incident Support
* Own the region’s event safety strategy and ensure readiness across all venues, courses, and operating plans.
* Ensure compliance with all applicable safety requirements, permits, medical/EMS plans, and incident reporting standards.
* Lead critical incident response at events, including escalation, coordination with medical and public safety agencies, and communication to internal stakeholders.
* Oversee post-incident debriefs and corrective action plans; implement learnings across the regional portfolio to reduce risk and improve outcomes.
- Community Engagement & Relationships
* Foster positive and collaborative relationships with local communities, authorities, and stakeholders to ensure successful event integration and long-term partnerships.
* Proactively cultivate relationships with athletes, tri clubs, coaches, local businesses, volunteers, and civic partners to strengthen trust, advocacy, and community pride around each event.
* Engage the local community year-round to surface and share stories of athlete journeys, volunteer impact, local pride, and community benefit, ensuring IRONMAN is experienced as an ongoing community presence rather than only
for prose. We need to preserve all substantive information, remove boilerplate (EEO, equal opportunity, etc). Also remove duplicated lines, navigation, cookie, legal, scam-warning, application instructions. The posting includes "We are an equal opportunity employer..." which is boilerplate; remove. Also "The above job description is not intended to be an “all inclusive” list..." also boilerplate; remove. We need to keep the brief description (intro) maybe as a
under no heading? The instruction: Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Thus we can have a leading
for the brief description (the "Brief Description At The IRONMAN Group..."). Then sections: About the role (maybe from "The Opportunity" paragraph). Responsibilities (from Responsibilities & Duties). Qualifications (from Qualifications/Experience). Possibly Skills (maybe combine some). But we need to only include sections when posting has real specific content. The posting includes responsibilities list, qualifications list, physical & equipment requirements (maybe part of qualifications). There's no explicit Skills section separate; but we could treat Qualifications as covering skills. However we have both Qualifications and Skills as possible headings; we should only include if there is content. The posting includes "Qualifications/Experience" which is a mix of qualifications and experience; we can put that under Qualifications heading. There's also a list of abilities under Qualifications/Experience that could be considered skills; but we can just put them under Qualifications. We also have Physical & Equipment Requirements; could be part of Qualifications or a separate section like Requirements? The instruction says use headings like Requirements, Qualifications, Skills. We could put Physical & Equipment Requirements under Requirements heading. Or we could create a Requirements heading and include that list. We need to decide: The posting has "Qualifications/Experience" and "Physical & Equipment Requirements". Both are substantive. We could have two sections: Qualifications (covering degree, experience, etc) and Requirements (covering physical/equipment). Or we could combine them under Qualifications. But the instruction says prefer a few substantive sections over many thin ones. So maybe combine into Qualifications (including physical). However the physical requirements are distinct; but we could still include them under Qualifications as bullet points. We also need to include any list as
- . For prose, use
. We need to preserve all substantive information: The brief description paragraph(s) about purpose, BE ICONIC vision, etc. Also the "The Opportunity" paragraph describing role. Also the responsibilities list (multiple bullet points). Also the qualifications list. Also the physical & equipment requirements list. Also the KPIs section? The posting includes "Key Performance Indicators (KPIs)" with bullet points. That is substantive; should be included perhaps under a heading like "Key Performance Indicators" but not in the allowed headings list. However we could treat KPIs as part of Responsibilities or maybe a separate section; but the instruction only gave examples of headings, not an exhaustive list; we could add other headings if needed? It says "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The e.g. suggests those are examples, but we should likely stick to those headings only? It says "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". It doesn't forbid other headings, but the examples are given. Safer to stick to those headings; we can map KPIs under Responsibilities or maybe under a separate heading like "Performance Metrics" but not in list. Might be better to include under Responsibilities as a sub-list? However the instruction says use
- for any list of duties/requirements/benefits. KPIs are a list of metrics; could be considered duties? Not exactly. But we could still include as a list under a heading like "Key Performance Indicators" but that's not one of the examples. However the instruction didn't forbid other headings; it just gave examples. I'd say we can add a heading for KPIs if we want, but to be safe, maybe incorporate KPIs under Responsibilities as a sub-section? But the instruction says "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say we cannot use other headings, but the examples are typical sections. I'd include KPIs as a separate heading maybe "Key Performance Indicators". However the instruction says "Prefer a few substantive sections over many thin ones." Adding KPIs as a separate section may be thin but it's substantive. Could merge into Responsibilities. Let's think: The posting includes a lot of detail; we want to preserve all. If we merge KPIs into Responsibilities, we still preserve the content. That's okay. Thus sections: About the role (from The Opportunity). Responsibilities (combining Responsibilities & Duties and KPIs). Qualifications (combining Qualifications/Experience and Physical & Equipment Requirements). Possibly Skills? Not needed. We need to ensure we don't include boilerplate: remove EEO statement, the "We are an equal opportunity employer..." and the "The above job description is not intended to be an “all inclusive” list..." Also remove navigation/footer etc. There's no explicit navigation in the text. Now craft HTML. We'll start with a
for brief description: "Brief Description At The IRONMAN Group, our purpose is clear: to inspire people to unlock their greatest potential through sport, pushing beyond limits to become the fullest expression of human achievement. Through our BE ICONIC vision, we are building the most loved brands, producing the world’s most inspiring events, and fostering deeply engaged communities that change lives. We aim to empower over a million athletes to cross a finish line each year and inspire a billion people worldwide through the power of the human spirit. As part of our team, you’ll join a high-performance, caring culture where innovation thrives, communities are uplifted, and every achievement, big or small, is celebrated. You’ll help shape experiences that fill hearts, consume minds, and enrich souls. This is more than a job. It’s a chance to be part of a global movement, to lead from the front, and to leave a legacy. Together, we create moments that last a lifetime. The IRONMAN Group is the world's largest operator of mass participation sports, delivering over 200+ events a year across 55+ countries thanks to a passionate global team. For more information, visit www.ironman.com/about-ironman-group." Then maybe a
for metadata: "We are seeking a highly motivated individual for the position of Regional Director reporting to MD, North America & World Championship Events based in North America." But instruction says do NOT put Job ID/requisition numbers as headings — fold minor metadata into a short
or drop it. This is metadata about the role; we can include as a short
before About the role. Then
About the role
and then acontaining the Opportunity paragraph: "The Opportunity The Regional Director serves as the representative of The IRONMAN Group within assigned markets, driving regional strategy, business development, and operational excellence. This role leads a team of Operations Managers and Race Directors to deliver world-class IRONMAN events that create life-changing experiences for athletes worldwide. As the operational and strategic leader of the region, the Regional Director holds ultimate responsibility for safe event execution, athlete experience outcomes, and financial results. The role carries full accountability for regional performance across safety, permits and compliance, risk management, operational delivery, and the regional P&L, ensuring profitability and alignment with the company’s long-range plan. Additionally, the Regional Director fosters cross-functional collaboration and champions talent development across all levels. The role is also expected to build trusted, visible relationships across the community ecosystem - including athletes, clubs, coaches, host cities, local businesses, volunteers, public safety partners, and residents - recognizing that relationships are a core part of the IRONMAN experience and a critical driver of long-term event success." We need to ensure we keep the dash and hyphens; fine. Then
Responsibilities
and then a- with
- items for each duty and KPI. We need to extract list items from Responsibilities & Duties and KPIs. Responsibilities & Duties sections: - Strategic Leadership * Define and execute regional strategy aligned with global objectives. * Drive operational excellence and continuous improvement across all events. - Event Delivery * Ensure safe, high-quality execution of all IRONMAN events in the region. * Oversee compliance with technical standards, procedures, and risk management protocols. - Financial Management * Own regional P&L performance, budgeting, and forecasting; partner closely with Finance to highlight key drivers of business performance. * Monitor financial performance and implement cost optimization strategies. * Proactive outreach to municipalities and vendors to enable efficient growth of the region (i.e., revenue is growing faster than costs). * Partner closely with Marketing and Finance to align course capacity and athlete sales targets. - People Leadership, Culture & Performance * Lead, coach, and develop a high performing team through clear expectations, regular feedback, and meaningful career conversations. * Model IRONMAN’s BE ICONIC behaviors and athlete first mindset in daily decisions, team rituals, and onsite/offsite leadership presence. * Build a culture of creativity, accountability, and continuous improvement, encouraging experimentation and learning across events. * Partner cross functionally to strengthen alignment, shared ownership, and consistency of experience across the event ecosystem. * Take active ownership of team engagement, clarity of roles, and performance outcomes. - Business Development * Identify and pursue opportunities for new events, acquisitions, and renewals engaging with key Business Development stakeholders * Support commercial growth initiatives in line with IRONMAN’s long-range plan. - Safety & Critical Incident Support * Own the region’s event safety strategy and ensure readiness across all venues, courses, and operating plans. * Ensure compliance with all applicable safety requirements, permits, medical/EMS plans, and incident reporting standards. * Lead critical incident response at events, including escalation, coordination with medical and public safety agencies, and communication to internal stakeholders. * Oversee post-incident debriefs and corrective action plans; implement learnings across the regional portfolio to reduce risk and improve outcomes. - Community Engagement & Relationships * Foster positive and collaborative relationships with local communities, authorities, and stakeholders to ensure successful event integration and long-term partnerships. * Proactively cultivate relationships with athletes, tri clubs, coaches, local businesses, volunteers, and civic partners to strengthen trust, advocacy, and community pride around each event. * Engage the local community year-round to surface and share stories of athlete journeys, volunteer impact, local pride, and community benefit, ensuring IRONMAN is experienced as an ongoing community presence rather than only
- for any list of duties/requirements/benefits. KPIs are a list of metrics; could be considered duties? Not exactly. But we could still include as a list under a heading like "Key Performance Indicators" but that's not one of the examples. However the instruction didn't forbid other headings; it just gave examples. I'd say we can add a heading for KPIs if we want, but to be safe, maybe incorporate KPIs under Responsibilities as a sub-section? But the instruction says "Use