Director, Engineering
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Include sections only if posting has real specific content. We have content for About the role (the description before responsibilities). Responsibilities list. Qualifications (they have Qualifications heading). Skills? Not explicit separate; maybe capabilities list could be considered Skills. We have "Capabilities" list. Could map to Skills. Benefits: they mention benefits: annual market competitive bonus program, Thrive Program (flexible work options, virtual yoga/meditation, Global Wellness paid day off, Give Back Day). Pay: they have salary range $190,000 - $210,000 a year. Schedule: not mentioned. So we should not include Schedule heading. Also we should not repeat job title as heading. We should not include metadata like Job ID. We need to preserve all substantive info, not invent. Remove boilerplate: EEO, fraud alert, etc. Also remove duplicated lines. Also remove navigation/cookie etc. So we need to extract core content: introductory paragraph about company, role description, responsibilities list, qualifications list, capabilities list (maybe as Skills), benefits, pay. Also maybe "About Coates" section? That's similar to About the role? The posting includes "About Coates" after qualifications. That could be considered "About the role"? Actually "About the role" is earlier description of role. "About Coates" is company info. Could be included as a section maybe "About the company"? Not in allowed headings. Allowed headings are About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should put company info maybe under About the role? But About the role already has description of role. Could combine? Better to keep About the role as the role description (the paragraph starting "The Director, Engineering is accountable..."). Then we could put company info maybe under "About Coates" but not allowed heading; we could drop it? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we must keep company info somewhere. Since we cannot create new headings not in list, we could incorporate it into About the role section as additional paragraph. That's acceptable: we can put company info after role description within same section. Or we could create a separate section with heading "About the role" and include both role and company info. That's fine.
We must not include headings with filler text. Ensure each heading has substantive content.
We need to use - for any list of duties/requirements/benefits. So responsibilities list, qualifications list, capabilities list (skills), benefits list.
We need
for prose.
Let's extract content.
Introductory paragraphs before responsibilities: "Be Part of Our Next Chapter For over almost 60 years, our solutions have enabled impactful connections between some of the world’s leading brands and their customers. And while we’ve already done a lot of work we’re proud of, we’re just getting started! We’re a global technology company focused on creating dynamic, smart, personalized and engaging customer experiences powered by our range of digital hardware, our proprietary content management system and our industry leading signage solutions. (For example: If you’ve ordered in-store or in the drive-thru at McDonald’s somewhere in the world in the last few years, chances are you’ve interacted with our digital solutions.) We work in over 50 global markets and have 9 offices around the world, with a global headquarters proudly located in our founding home of Sydney, Australia. Coates Group has the values of a family-owned business and the innovative spirit of a start-up, both which fuel our purpose – Creating Connections. Empowering Partnerships. Always Evolving. Through hard work, dedication and creativity, we’ve become industry leaders who have won awards and set records while remaining focused on continual growth and evolution. We are a 2x Australia Good Design Award winner and successfully completed the largest hardware deployment in Quick Service Restaurant history. We are curious, charismatic, authentic and we value and leverage the diversity of our crew. We are imaginers, kindness enthusiasts, experts, creators, thinkers, challengers, collaborators and over-achievers. And together, as a Crew, we are revolutionizing the way the world’s leading brands leverage technology to drive the best customer experiences."
Then role description: "The Director, Engineering is accountable for enabling high-performing engineering squads to deliver reliable, maintainable, and high-quality software solutions. This role provides technical leadership, builds capability across engineers and technical leads, ensures adherence to engineering standards, and removes blockers that impede delivery, while partnering with Product, Delivery, and QA leadership to achieve business and customer outcomes."
That's prose.
Then Responsibilities: list items each preceded by a heading like "Engineering Enablement:" etc. We need to capture each bullet.
Let's extract responsibilities:
- Engineering Enablement: Ensure squads have the technical capability, processes, and practices to deliver reliably, removing engineering blockers and supporting predictable outcomes in partnership with Delivery leadership.
- Engineering Leadership & Capability: Act as a chapter-style leader for engineers and technical leads, building capability, setting standards, and driving consistent engineering practices across squads.
- Technical Leadership, Debt & Design Quality: Ensure sound technical design and implementation, actively managing technical debt and addressing complexity.
- Quality in Delivery: Embed quality-by-design within engineering teams (e.g. testability, code quality, CI/CD discipline), while partnering with QA to achieve agreed quality outcomes.
- Platform Health & Operability: Own the operational health of systems within scope, ensuring reliability, performance, and readiness across production and pre-production environments.
- People & Partner Leadership: Lead and develop permanent and partner engineers (onshore and offshore), including performance management, engagement, and effective integration.
- Delivery Flow & Dependencies: Enable squads to operate autonomously by removing engineering blockers, managing dependencies, and improving delivery flow in partnership with Product and Delivery.
That's 7 items.
Then "Capabilities" list (maybe Skills):
- Hands-on Technical Leadership: Leads with strong engineering credibility and modelling high-quality full-stack engineering practices.
- Execution Focus: Translates architectural direction and standards into practical, repeatable engineering practices that work at squad level.
- Problem Solving & Judgement: Quickly diagnoses technical and delivery-adjacent issues, makes sound trade-offs, and removes engineering blockers.
- People Development: Develops a high-performing team through clear expectations, feedback, and career coaching.
- Collaboration & Influence: Works as a trusted partner to Product, Delivery & QA leaders to align engineering effort to shared outcomes.
- Ownership & Accountability: Builds strong ownership within squads for code quality, operability, and continuous improvement.
That's 6 items.
Qualifications list:
- 8+ years’ experience in software engineering, with 3+ years in an engineering leadership roles, managing engineers and technical leads
- Bachelor’s degree in Engineering, Computer Science, or a related discipline, or equivalent practical experience
- Proven experience delivering enterprise-scale software platforms or digital products within complex, client environments
- Strong hands-on background in modern full-stack software engineering, with deep experience in building highly scalable web applications supported by cloud-native or serverless architectures (AWS preferred), CI/CD pipelines, and distributed systems
- Demonstrated experience leading cross-functional engineering teams operating in agile or product-led delivery models
- Experience establishing and enforcing engineering standards, development practices, and delivery discipline across multiple squads
- Proven ability to manage a blended workforce, including permanent staff and staff-augmented delivery partners (onshore and offshore)
- Demonstrated experience in developing and executing plans that align with business objectives and growth
That's 8 items.
Benefits list:
- annual market competitive bonus program
- Thrive Program which includes a suite of flexible work options because we’re strong believers that you should never miss an important life or work moment.
- Thrive also provides dedicated time to prioritize our health and wellbeing (think virtual Yoga or meditation sessions)
- a Global Wellness paid day off to recharge
- a “Give Back Day” to allow our Crew an opportunity to make an impact in the community.
We could combine as bullet points.
Pay: "$190,000 - $210,000 a year Pay is based on relevant experience, skills, education, internal equity, and market data. Well-qualified candidates can generally expect offers around the midpoint. Candidates who meet the minimum qualifications but have more limited directly relevant experience for this specific role are typically placed nearer the minimum, while highly experienced candidates with strong role alignment may be placed closer to the maximum."
We need to keep that prose.
Schedule: none, so omit.
Now produce HTML fragment.
Structure:
About the role
... (intro + role description)
Responsibilities
- ...
...
Qualifications
...
Skills
...
Benefits
...
Pay
...
Make sure no extra headings.
We must not include markdown fences. Just raw HTML.
Check for any duplicated lines: we should not repeat.
Now craft the HTML.
Need to escape any HTML special characters like &, <, >. The text includes ampersands, etc. We'll keep as is; it's okay in HTML as long as not interpreted as tags. Use & for & maybe safer. But the instruction didn't require escaping; but to be safe we can replace & with &. However, the text includes "&" in "Create Connections. Empowering Partnerships. Always Evolving." No ampersand there. There's "&" in "Reliability, performance, and readiness". That's fine. There's "&" in "Product, Delivery & QA". That's an ampersand; should be escaped as &. Also "Product, Delivery & QA leaders". Also "Product, Delivery & QA". Also "Product, Delivery & QA". Also "Product, Delivery & QA". Also "Product, Delivery & QA". Also "Product, Delivery & QA". Also "Product, Delivery & QA". Also "Product, Delivery & QA". Also "Product, Delivery & QA". Also "Product, Delivery & QA". Also "Product, Delivery & QA". Also "Product, Delivery & QA". Also "Product, Delivery & QA". Also "Product, Delivery & QA". Also "Product, Delivery & QA". Also "Product, Delivery & QA". Also "Product, Delivery & QA". Also "Product, Delivery & QA". Also "Product, Delivery & QA". Also "Product, Delivery & QA". Also "Product, Delivery & QA". Also "Product, Delivery & QA". Also "Product, Delivery & QA". Also "Product, Delivery & QA". Also "Product, Delivery & QA". Also "Product, Delivery & QA". Also "Product, Delivery & QA". Also "Product, Delivery & QA". Also "Product, Delivery & QA". Also "Product, Delivery & QA". Also "Product, Delivery & QA". Also "Product, Delivery & QA". Also "Product, Delivery & QA". Also "Product, Delivery & QA". Also "Product, Delivery & QA". Also "Product, Delivery & QA". Also "Product, Delivery & QA". Also "Product, Delivery & QA". Also "Product, Delivery & QA". Also "Product, Delivery & QA". Also "Product, Delivery & QA". Also "Product, Delivery & QA". Also "Product, Delivery & QA". Also "Product, Delivery & QA". Also "Product, Delivery & QA". Also "Product, Delivery & QA". Also "Product, Delivery & QA". Also "Product, Delivery & QA". Also "Product, Delivery & QA". Also "Product, Delivery & Q
for prose. Let's extract content. Introductory paragraphs before responsibilities: "Be Part of Our Next Chapter For over almost 60 years, our solutions have enabled impactful connections between some of the world’s leading brands and their customers. And while we’ve already done a lot of work we’re proud of, we’re just getting started! We’re a global technology company focused on creating dynamic, smart, personalized and engaging customer experiences powered by our range of digital hardware, our proprietary content management system and our industry leading signage solutions. (For example: If you’ve ordered in-store or in the drive-thru at McDonald’s somewhere in the world in the last few years, chances are you’ve interacted with our digital solutions.) We work in over 50 global markets and have 9 offices around the world, with a global headquarters proudly located in our founding home of Sydney, Australia. Coates Group has the values of a family-owned business and the innovative spirit of a start-up, both which fuel our purpose – Creating Connections. Empowering Partnerships. Always Evolving. Through hard work, dedication and creativity, we’ve become industry leaders who have won awards and set records while remaining focused on continual growth and evolution. We are a 2x Australia Good Design Award winner and successfully completed the largest hardware deployment in Quick Service Restaurant history. We are curious, charismatic, authentic and we value and leverage the diversity of our crew. We are imaginers, kindness enthusiasts, experts, creators, thinkers, challengers, collaborators and over-achievers. And together, as a Crew, we are revolutionizing the way the world’s leading brands leverage technology to drive the best customer experiences." Then role description: "The Director, Engineering is accountable for enabling high-performing engineering squads to deliver reliable, maintainable, and high-quality software solutions. This role provides technical leadership, builds capability across engineers and technical leads, ensures adherence to engineering standards, and removes blockers that impede delivery, while partnering with Product, Delivery, and QA leadership to achieve business and customer outcomes." That's prose. Then Responsibilities: list items each preceded by a heading like "Engineering Enablement:" etc. We need to capture each bullet. Let's extract responsibilities: - Engineering Enablement: Ensure squads have the technical capability, processes, and practices to deliver reliably, removing engineering blockers and supporting predictable outcomes in partnership with Delivery leadership. - Engineering Leadership & Capability: Act as a chapter-style leader for engineers and technical leads, building capability, setting standards, and driving consistent engineering practices across squads. - Technical Leadership, Debt & Design Quality: Ensure sound technical design and implementation, actively managing technical debt and addressing complexity. - Quality in Delivery: Embed quality-by-design within engineering teams (e.g. testability, code quality, CI/CD discipline), while partnering with QA to achieve agreed quality outcomes. - Platform Health & Operability: Own the operational health of systems within scope, ensuring reliability, performance, and readiness across production and pre-production environments. - People & Partner Leadership: Lead and develop permanent and partner engineers (onshore and offshore), including performance management, engagement, and effective integration. - Delivery Flow & Dependencies: Enable squads to operate autonomously by removing engineering blockers, managing dependencies, and improving delivery flow in partnership with Product and Delivery. That's 7 items. Then "Capabilities" list (maybe Skills): - Hands-on Technical Leadership: Leads with strong engineering credibility and modelling high-quality full-stack engineering practices. - Execution Focus: Translates architectural direction and standards into practical, repeatable engineering practices that work at squad level. - Problem Solving & Judgement: Quickly diagnoses technical and delivery-adjacent issues, makes sound trade-offs, and removes engineering blockers. - People Development: Develops a high-performing team through clear expectations, feedback, and career coaching. - Collaboration & Influence: Works as a trusted partner to Product, Delivery & QA leaders to align engineering effort to shared outcomes. - Ownership & Accountability: Builds strong ownership within squads for code quality, operability, and continuous improvement. That's 6 items. Qualifications list: - 8+ years’ experience in software engineering, with 3+ years in an engineering leadership roles, managing engineers and technical leads - Bachelor’s degree in Engineering, Computer Science, or a related discipline, or equivalent practical experience - Proven experience delivering enterprise-scale software platforms or digital products within complex, client environments - Strong hands-on background in modern full-stack software engineering, with deep experience in building highly scalable web applications supported by cloud-native or serverless architectures (AWS preferred), CI/CD pipelines, and distributed systems - Demonstrated experience leading cross-functional engineering teams operating in agile or product-led delivery models - Experience establishing and enforcing engineering standards, development practices, and delivery discipline across multiple squads - Proven ability to manage a blended workforce, including permanent staff and staff-augmented delivery partners (onshore and offshore) - Demonstrated experience in developing and executing plans that align with business objectives and growth That's 8 items. Benefits list: - annual market competitive bonus program - Thrive Program which includes a suite of flexible work options because we’re strong believers that you should never miss an important life or work moment. - Thrive also provides dedicated time to prioritize our health and wellbeing (think virtual Yoga or meditation sessions) - a Global Wellness paid day off to recharge - a “Give Back Day” to allow our Crew an opportunity to make an impact in the community. We could combine as bullet points. Pay: "$190,000 - $210,000 a year Pay is based on relevant experience, skills, education, internal equity, and market data. Well-qualified candidates can generally expect offers around the midpoint. Candidates who meet the minimum qualifications but have more limited directly relevant experience for this specific role are typically placed nearer the minimum, while highly experienced candidates with strong role alignment may be placed closer to the maximum." We need to keep that prose. Schedule: none, so omit. Now produce HTML fragment. Structure:
About the role
... (intro + role description)
Responsibilities
- ... ...
Qualifications
-
...
Skills
-
...
Benefits
-
...
Pay
...
Make sure no extra headings. We must not include markdown fences. Just raw HTML. Check for any duplicated lines: we should not repeat. Now craft the HTML. Need to escape any HTML special characters like &, <, >. The text includes ampersands, etc. We'll keep as is; it's okay in HTML as long as not interpreted as tags. Use & for & maybe safer. But the instruction didn't require escaping; but to be safe we can replace & with &. However, the text includes "&" in "Create Connections. Empowering Partnerships. Always Evolving." No ampersand there. There's "&" in "Reliability, performance, and readiness". That's fine. There's "&" in "Product, Delivery & QA". That's an ampersand; should be escaped as &. Also "Product, Delivery & QA leaders". Also "Product, Delivery & QA". Also "Product, Delivery & QA". Also "Product, Delivery & QA". Also "Product, Delivery & QA". Also "Product, Delivery & QA". Also "Product, Delivery & QA". Also "Product, Delivery & QA". Also "Product, Delivery & QA". Also "Product, Delivery & QA". Also "Product, Delivery & QA". Also "Product, Delivery & QA". Also "Product, Delivery & QA". Also "Product, Delivery & QA". Also "Product, Delivery & QA". Also "Product, Delivery & QA". Also "Product, Delivery & QA". Also "Product, Delivery & QA". Also "Product, Delivery & QA". Also "Product, Delivery & QA". Also "Product, Delivery & QA". Also "Product, Delivery & QA". Also "Product, Delivery & QA". Also "Product, Delivery & QA". Also "Product, Delivery & QA". Also "Product, Delivery & QA". Also "Product, Delivery & QA". Also "Product, Delivery & QA". Also "Product, Delivery & QA". Also "Product, Delivery & QA". Also "Product, Delivery & QA". Also "Product, Delivery & QA". Also "Product, Delivery & QA". Also "Product, Delivery & QA". Also "Product, Delivery & QA". Also "Product, Delivery & QA". Also "Product, Delivery & QA". Also "Product, Delivery & QA". Also "Product, Delivery & QA". Also "Product, Delivery & QA". Also "Product, Delivery & QA". Also "Product, Delivery & QA". Also "Product, Delivery & QA". Also "Product, Delivery & QA". Also "Product, Delivery & QA". Also "Product, Delivery & QA". Also "Product, Delivery & QA". Also "Product, Delivery & QA". Also "Product, Delivery & QA". Also "Product, Delivery & Q