Data Engineer III
for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). But we can also use other headings if they match content? The instruction: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests we should use those headings when appropriate. However we can also use other headings if they are not in that list? The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but likely they want us to map content to those standard headings. However the posting has sections like "Who We Are", "Why This Role Matters", etc. We could map them to appropriate headings: "Who We Are" could be "About the role"? Actually "About the role" is more about role description, not company. "Who We Are" is company overview. Could be considered "About the role"? Not exactly. But we could still use "About the role" heading for company description? Might be okay.
But we need to include sections only when posting has real specific content. We have content for many sections.
We need to use - for any list of duties/requirements/benefits, and
for prose.
We need to preserve all substantive information, not invent or summarize away detail. Remove boilerplate like cookie/navigation/legal/EEO etc. There's a disclaimer at end: "Disclaimer: This description reflects the general nature and level of the role. It is not intended to be an exhaustive list of responsibilities or requirements." That's boilerplate; we should remove it.
Also there is a line: "Please note: While the current expectation is a minimum of three days per week in the office, this may evolve over time in alignment with business needs and our continued commitment to culture-building". That's part of working culture; we keep it.
Salary: we have a Salary section with range. We need to include Pay section only if posting actually states them. Yes, salary is given. So we should create a Pay section with that info.
We should not include Schedule unless posting states schedule. It mentions in-office expectation: at least three days per week. That's schedule info. So we can include Schedule section.
Benefits: not mentioned explicitly. No benefits listed. So we should not create Benefits section.
We need to avoid filler like "commensurate with experience". Not present.
We need to output only HTML fragment, no /, no markdown fences.
We need to decide which headings to use. Let's map:
- About the role: could contain "Who We Are" and "Why This Role Matters"? Actually "About the role" could be role overview. But we have separate sections. Maybe we can create multiple sections: About the role (company overview), Responsibilities (What You’ll Deliver), Requirements/Qualifications (What You’ll Bring To The Team + What Would Make You Stand Out), Skills (maybe combine), Pay, Schedule, Working Culture (maybe as "Our Working Culture").
But instruction says prefer a few substantive sections over many thin ones. So we could combine similar content.
Let's think: We could have:
About the role
containing Who We Are and Why This Role Matters (prose).
Responsibilities
containing What You’ll Deliver (list).
Qualifications
containing What You’ll Bring To The Team and What Would Make You Stand Out (list).
Skills
maybe not needed if qualifications cover.
But we could also have Pay
and Schedule
.
We need to avoid duplicate content.
Let's extract content.
Who We Are paragraph: "At Preferred Travel Group, we champion the power of travel to inspire meaningful connections and enrich lives around the world. As a global family of brands and programs representing the finest independent hotels and resorts, we are united by a shared belief in authenticity, collaboration, and the value of independent spirit. Our culture reflects our ideology in action: people first, relationships at the center, and a commitment to creating lasting impact for our partners, our global community, and one another. When you join Preferred, you become part of a purpose-driven organization where ideas are welcomed, growth is encouraged, and your work contributes to shaping the future of travel."
Why This Role Matters: "We are seeking a highly organized, proactive, and technically skilled Data Engineer III to design, build, and optimize scalable data solutions that power business operations across Preferred Travel Group. This role develops and supports modern data pipelines, integrations, and reporting capabilities while partnering closely with business stakeholders and engineering teams to deliver reliable, high-quality data. Success in this role comes from independently delivering well-designed solutions, continuously improving data processes, collaborating effectively across teams, and identifying opportunities to increase the reliability, performance, and value of our data platform."
What You’ll Deliver (list):
- Design, build, and maintain scalable data pipelines and ETL workflows.
- Develop and optimize advanced SQL, Python, and Spark solutions for data processing.
- Build and support integrations using Azure Data Factory, Microsoft Fabric, and REST/SOAP APIs.
- Monitor, troubleshoot, and improve the reliability and performance of production data processes.
- Collaborate with business stakeholders to gather requirements and deliver data solutions.
- Participate in code reviews and maintain technical documentation.
- Mentor junior engineers and contribute to engineering best practices.
What Would Make You Stand Out (list):
- Experience with dbt.
- Experience with Azure Data Factory and Microsoft Fabric.
- Demonstrated technical leadership and a history of helping engineering teams successfully deliver complex initiatives.
- Strong communication skills with the ability to clearly explain project status, risks, and technical tradeoffs to stakeholders.
- A passion for improving engineering practices, helping mature team processes, and raising the overall effectiveness of the team.
What You’ll Bring To The Team (list):
- 5+ years of experience in data engineering or a related field.
- Bachelor's degree in Computer Science, Information Systems, or equivalent experience.
- Strong SQL development and query optimization experience.
- Experience with Python and modern ETL/orchestration tools.
- Experience with Microsoft Azure, Microsoft Fabric, or similar cloud data platforms.
- Experience using Git and collaborative software development practices.
- Strong understanding of data modeling and ETL concepts.
- Strong analytical and problem-solving abilities.
- Ability to independently manage complex technical work while collaborating across teams.
- Strong written and verbal communication skills.
- Commitment to continuous improvement and knowledge sharing.
Where You’ll Thrive (prose):
"You enjoy bringing structure to complex data challenges, following projects through from design to delivery with a strong focus on accuracy, quality, and reliability. You are highly detail-oriented and thrive in environments where thoughtful analysis, technical expertise, and well-informed decision-making are valued. You work comfortably within established frameworks and best practices while taking ownership of solutions and continuously improving processes and performance. You communicate clearly and professionally, collaborate effectively across teams, and lead by example through strong follow-through, accountability, and technical excellence."
Our Working Culture (prose):
"With our in-office philosophy, our associates are expected to be in the office at least three days per week, supporting a healthy balance between in-person collaboration and flexible remote work. We take pride in our vibrant and inclusive culture, which thrives on meaningful connection, shared purpose, and cross-functional teamwork. In-office engagement plays a vital role in fostering spontaneous collaboration, accelerating innovation, and strengthening relationships across teams. It also provides valuable opportunities for mentorship, professional development, and a deeper sense of community. Please note: While the current expectation is a minimum of three days per week in the office, this may evolve over time in alignment with business needs and our continued commitment to culture-building"
Salary: "$120,000 - $150,000, actual compensation within this range will be determined by multiple factors including candidate experience and expertise."
Now we need to decide sections.
Potential sections:
- About the role (combining Who We Are and Why This Role Matters)
- Responsibilities (What You’ll Deliver)
- Qualifications (combining What You’ll Bring To The Team and What Would Make You Stand Out)
- Where You’ll Thrive (maybe as "Work Style" but not in list; could be omitted or put under About the role? But it's substantive. Could be its own section maybe "Work Style" but not in allowed headings. Could use "About the role" again? Might be okay to add a section not in list? The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but suggests those are typical. However to be safe, we could map Where You’ll Thrive to "Qualifications" or "Skills"? But it's more about work style. Could be omitted? But we must preserve all substantive information. So we need to include it somewhere. Could add a section "Work Style" but that's not in the list; risk of deviating. Perhaps we can incorporate it into "About the role" as additional prose. That would preserve info.
Similarly Our Working Culture could go under Schedule? Actually schedule is about in-office expectation. Could be part of Schedule section. But we also have culture description. Could be part of "About the role" as well.
But we need to avoid too many thin sections. Perhaps we can have:
About the role
(company overview + role significance + work style + culture)
Responsibilities
Qualifications
Pay
Schedule
That's 5 sections.
Now we need to ensure we don't include filler like "commensurate with experience". Not present.
We need to use - for any list of duties/requirements/benefits. So Responsibilities list as
- . Qualifications list as
- . Pay and Schedule as prose
.
Now we need to extract the content for each section.
About the role: combine Who We Are, Why This Role Matters, Where You’ll Thrive, Our Working Culture.
We need to preserve all substantive information, not invent or summarize away detail. So we need to include all sentences from those sections.
We'll need to concatenate them into paragraphs (
). Could be multiple
elements.
Let's gather the text:
Who We Are:
"At Preferred Travel Group, we champion the power of travel to inspire meaningful connections and enrich lives around the world. As a global family of brands and programs representing the finest independent hotels and resorts, we are united by a shared belief in authenticity, collaboration, and the value of independent spirit. Our culture reflects our ideology in action: people first, relationships at the center, and a commitment to creating lasting impact for our partners, our global community, and one another. When you join Preferred, you become part of a purpose-driven organization where ideas are welcomed, growth is encouraged, and your work contributes to shaping the future of travel."
Why This Role Matters:
"We are seeking a highly organized, proactive, and technically skilled Data Engineer III to design, build, and optimize scalable data solutions that power business operations across Preferred Travel Group. This role develops and supports modern data pipelines, integrations, and reporting capabilities while partnering closely with business stakeholders and engineering teams to deliver reliable, high-quality data. Success in this role comes from independently delivering well-designed solutions, continuously improving data processes, collaborating effectively across teams, and identifying opportunities to increase the reliability, performance, and value of our data platform."
Where You’ll Thrive:
"You enjoy bringing structure to complex data challenges, following projects
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but likely they want us to map content to those standard headings. However the posting has sections like "Who We Are", "Why This Role Matters", etc. We could map them to appropriate headings: "Who We Are" could be "About the role"? Actually "About the role" is more about role description, not company. "Who We Are" is company overview. Could be considered "About the role"? Not exactly. But we could still use "About the role" heading for company description? Might be okay.
But we need to include sections only when posting has real specific content. We have content for many sections.
We need to use - for any list of duties/requirements/benefits, and
for prose.
We need to preserve all substantive information, not invent or summarize away detail. Remove boilerplate like cookie/navigation/legal/EEO etc. There's a disclaimer at end: "Disclaimer: This description reflects the general nature and level of the role. It is not intended to be an exhaustive list of responsibilities or requirements." That's boilerplate; we should remove it.
Also there is a line: "Please note: While the current expectation is a minimum of three days per week in the office, this may evolve over time in alignment with business needs and our continued commitment to culture-building". That's part of working culture; we keep it.
Salary: we have a Salary section with range. We need to include Pay section only if posting actually states them. Yes, salary is given. So we should create a Pay section with that info.
We should not include Schedule unless posting states schedule. It mentions in-office expectation: at least three days per week. That's schedule info. So we can include Schedule section.
Benefits: not mentioned explicitly. No benefits listed. So we should not create Benefits section.
We need to avoid filler like "commensurate with experience". Not present.
We need to output only HTML fragment, no /, no markdown fences.
We need to decide which headings to use. Let's map:
- About the role: could contain "Who We Are" and "Why This Role Matters"? Actually "About the role" could be role overview. But we have separate sections. Maybe we can create multiple sections: About the role (company overview), Responsibilities (What You’ll Deliver), Requirements/Qualifications (What You’ll Bring To The Team + What Would Make You Stand Out), Skills (maybe combine), Pay, Schedule, Working Culture (maybe as "Our Working Culture").
But instruction says prefer a few substantive sections over many thin ones. So we could combine similar content.
Let's think: We could have:
About the role
containing Who We Are and Why This Role Matters (prose).
Responsibilities
containing What You’ll Deliver (list).
Qualifications
containing What You’ll Bring To The Team and What Would Make You Stand Out (list).
Skills
maybe not needed if qualifications cover.
But we could also have Pay
and Schedule
.
We need to avoid duplicate content.
Let's extract content.
Who We Are paragraph: "At Preferred Travel Group, we champion the power of travel to inspire meaningful connections and enrich lives around the world. As a global family of brands and programs representing the finest independent hotels and resorts, we are united by a shared belief in authenticity, collaboration, and the value of independent spirit. Our culture reflects our ideology in action: people first, relationships at the center, and a commitment to creating lasting impact for our partners, our global community, and one another. When you join Preferred, you become part of a purpose-driven organization where ideas are welcomed, growth is encouraged, and your work contributes to shaping the future of travel."
Why This Role Matters: "We are seeking a highly organized, proactive, and technically skilled Data Engineer III to design, build, and optimize scalable data solutions that power business operations across Preferred Travel Group. This role develops and supports modern data pipelines, integrations, and reporting capabilities while partnering closely with business stakeholders and engineering teams to deliver reliable, high-quality data. Success in this role comes from independently delivering well-designed solutions, continuously improving data processes, collaborating effectively across teams, and identifying opportunities to increase the reliability, performance, and value of our data platform."
What You’ll Deliver (list):
- Design, build, and maintain scalable data pipelines and ETL workflows.
- Develop and optimize advanced SQL, Python, and Spark solutions for data processing.
- Build and support integrations using Azure Data Factory, Microsoft Fabric, and REST/SOAP APIs.
- Monitor, troubleshoot, and improve the reliability and performance of production data processes.
- Collaborate with business stakeholders to gather requirements and deliver data solutions.
- Participate in code reviews and maintain technical documentation.
- Mentor junior engineers and contribute to engineering best practices.
What Would Make You Stand Out (list):
- Experience with dbt.
- Experience with Azure Data Factory and Microsoft Fabric.
- Demonstrated technical leadership and a history of helping engineering teams successfully deliver complex initiatives.
- Strong communication skills with the ability to clearly explain project status, risks, and technical tradeoffs to stakeholders.
- A passion for improving engineering practices, helping mature team processes, and raising the overall effectiveness of the team.
What You’ll Bring To The Team (list):
- 5+ years of experience in data engineering or a related field.
- Bachelor's degree in Computer Science, Information Systems, or equivalent experience.
- Strong SQL development and query optimization experience.
- Experience with Python and modern ETL/orchestration tools.
- Experience with Microsoft Azure, Microsoft Fabric, or similar cloud data platforms.
- Experience using Git and collaborative software development practices.
- Strong understanding of data modeling and ETL concepts.
- Strong analytical and problem-solving abilities.
- Ability to independently manage complex technical work while collaborating across teams.
- Strong written and verbal communication skills.
- Commitment to continuous improvement and knowledge sharing.
Where You’ll Thrive (prose):
"You enjoy bringing structure to complex data challenges, following projects through from design to delivery with a strong focus on accuracy, quality, and reliability. You are highly detail-oriented and thrive in environments where thoughtful analysis, technical expertise, and well-informed decision-making are valued. You work comfortably within established frameworks and best practices while taking ownership of solutions and continuously improving processes and performance. You communicate clearly and professionally, collaborate effectively across teams, and lead by example through strong follow-through, accountability, and technical excellence."
Our Working Culture (prose):
"With our in-office philosophy, our associates are expected to be in the office at least three days per week, supporting a healthy balance between in-person collaboration and flexible remote work. We take pride in our vibrant and inclusive culture, which thrives on meaningful connection, shared purpose, and cross-functional teamwork. In-office engagement plays a vital role in fostering spontaneous collaboration, accelerating innovation, and strengthening relationships across teams. It also provides valuable opportunities for mentorship, professional development, and a deeper sense of community. Please note: While the current expectation is a minimum of three days per week in the office, this may evolve over time in alignment with business needs and our continued commitment to culture-building"
Salary: "$120,000 - $150,000, actual compensation within this range will be determined by multiple factors including candidate experience and expertise."
Now we need to decide sections.
Potential sections:
- About the role (combining Who We Are and Why This Role Matters)
- Responsibilities (What You’ll Deliver)
- Qualifications (combining What You’ll Bring To The Team and What Would Make You Stand Out)
- Where You’ll Thrive (maybe as "Work Style" but not in list; could be omitted or put under About the role? But it's substantive. Could be its own section maybe "Work Style" but not in allowed headings. Could use "About the role" again? Might be okay to add a section not in list? The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but suggests those are typical. However to be safe, we could map Where You’ll Thrive to "Qualifications" or "Skills"? But it's more about work style. Could be omitted? But we must preserve all substantive information. So we need to include it somewhere. Could add a section "Work Style" but that's not in the list; risk of deviating. Perhaps we can incorporate it into "About the role" as additional prose. That would preserve info.
Similarly Our Working Culture could go under Schedule? Actually schedule is about in-office expectation. Could be part of Schedule section. But we also have culture description. Could be part of "About the role" as well.
But we need to avoid too many thin sections. Perhaps we can have:
About the role
(company overview + role significance + work style + culture)
Responsibilities
Qualifications
Pay
Schedule
That's 5 sections.
Now we need to ensure we don't include filler like "commensurate with experience". Not present.
We need to use - for any list of duties/requirements/benefits. So Responsibilities list as
- . Qualifications list as
- . Pay and Schedule as prose
.
Now we need to extract the content for each section.
About the role: combine Who We Are, Why This Role Matters, Where You’ll Thrive, Our Working Culture.
We need to preserve all substantive information, not invent or summarize away detail. So we need to include all sentences from those sections.
We'll need to concatenate them into paragraphs (
). Could be multiple
elements.
Let's gather the text:
Who We Are:
"At Preferred Travel Group, we champion the power of travel to inspire meaningful connections and enrich lives around the world. As a global family of brands and programs representing the finest independent hotels and resorts, we are united by a shared belief in authenticity, collaboration, and the value of independent spirit. Our culture reflects our ideology in action: people first, relationships at the center, and a commitment to creating lasting impact for our partners, our global community, and one another. When you join Preferred, you become part of a purpose-driven organization where ideas are welcomed, growth is encouraged, and your work contributes to shaping the future of travel."
Why This Role Matters:
"We are seeking a highly organized, proactive, and technically skilled Data Engineer III to design, build, and optimize scalable data solutions that power business operations across Preferred Travel Group. This role develops and supports modern data pipelines, integrations, and reporting capabilities while partnering closely with business stakeholders and engineering teams to deliver reliable, high-quality data. Success in this role comes from independently delivering well-designed solutions, continuously improving data processes, collaborating effectively across teams, and identifying opportunities to increase the reliability, performance, and value of our data platform."
Where You’ll Thrive:
"You enjoy bringing structure to complex data challenges, following projects
for prose. We need to preserve all substantive information, not invent or summarize away detail. Remove boilerplate like cookie/navigation/legal/EEO etc. There's a disclaimer at end: "Disclaimer: This description reflects the general nature and level of the role. It is not intended to be an exhaustive list of responsibilities or requirements." That's boilerplate; we should remove it. Also there is a line: "Please note: While the current expectation is a minimum of three days per week in the office, this may evolve over time in alignment with business needs and our continued commitment to culture-building". That's part of working culture; we keep it. Salary: we have a Salary section with range. We need to include Pay section only if posting actually states them. Yes, salary is given. So we should create a Pay section with that info. We should not include Schedule unless posting states schedule. It mentions in-office expectation: at least three days per week. That's schedule info. So we can include Schedule section. Benefits: not mentioned explicitly. No benefits listed. So we should not create Benefits section. We need to avoid filler like "commensurate with experience". Not present. We need to output only HTML fragment, no /, no markdown fences. We need to decide which headings to use. Let's map: - About the role: could contain "Who We Are" and "Why This Role Matters"? Actually "About the role" could be role overview. But we have separate sections. Maybe we can create multiple sections: About the role (company overview), Responsibilities (What You’ll Deliver), Requirements/Qualifications (What You’ll Bring To The Team + What Would Make You Stand Out), Skills (maybe combine), Pay, Schedule, Working Culture (maybe as "Our Working Culture"). But instruction says prefer a few substantive sections over many thin ones. So we could combine similar content. Let's think: We could have:
About the role
containing Who We Are and Why This Role Matters (prose).Responsibilities
containing What You’ll Deliver (list).Qualifications
containing What You’ll Bring To The Team and What Would Make You Stand Out (list).Skills
maybe not needed if qualifications cover. But we could also havePay
andSchedule
. We need to avoid duplicate content. Let's extract content. Who We Are paragraph: "At Preferred Travel Group, we champion the power of travel to inspire meaningful connections and enrich lives around the world. As a global family of brands and programs representing the finest independent hotels and resorts, we are united by a shared belief in authenticity, collaboration, and the value of independent spirit. Our culture reflects our ideology in action: people first, relationships at the center, and a commitment to creating lasting impact for our partners, our global community, and one another. When you join Preferred, you become part of a purpose-driven organization where ideas are welcomed, growth is encouraged, and your work contributes to shaping the future of travel." Why This Role Matters: "We are seeking a highly organized, proactive, and technically skilled Data Engineer III to design, build, and optimize scalable data solutions that power business operations across Preferred Travel Group. This role develops and supports modern data pipelines, integrations, and reporting capabilities while partnering closely with business stakeholders and engineering teams to deliver reliable, high-quality data. Success in this role comes from independently delivering well-designed solutions, continuously improving data processes, collaborating effectively across teams, and identifying opportunities to increase the reliability, performance, and value of our data platform." What You’ll Deliver (list): - Design, build, and maintain scalable data pipelines and ETL workflows. - Develop and optimize advanced SQL, Python, and Spark solutions for data processing. - Build and support integrations using Azure Data Factory, Microsoft Fabric, and REST/SOAP APIs. - Monitor, troubleshoot, and improve the reliability and performance of production data processes. - Collaborate with business stakeholders to gather requirements and deliver data solutions. - Participate in code reviews and maintain technical documentation. - Mentor junior engineers and contribute to engineering best practices. What Would Make You Stand Out (list): - Experience with dbt. - Experience with Azure Data Factory and Microsoft Fabric. - Demonstrated technical leadership and a history of helping engineering teams successfully deliver complex initiatives. - Strong communication skills with the ability to clearly explain project status, risks, and technical tradeoffs to stakeholders. - A passion for improving engineering practices, helping mature team processes, and raising the overall effectiveness of the team. What You’ll Bring To The Team (list): - 5+ years of experience in data engineering or a related field. - Bachelor's degree in Computer Science, Information Systems, or equivalent experience. - Strong SQL development and query optimization experience. - Experience with Python and modern ETL/orchestration tools. - Experience with Microsoft Azure, Microsoft Fabric, or similar cloud data platforms. - Experience using Git and collaborative software development practices. - Strong understanding of data modeling and ETL concepts. - Strong analytical and problem-solving abilities. - Ability to independently manage complex technical work while collaborating across teams. - Strong written and verbal communication skills. - Commitment to continuous improvement and knowledge sharing. Where You’ll Thrive (prose): "You enjoy bringing structure to complex data challenges, following projects through from design to delivery with a strong focus on accuracy, quality, and reliability. You are highly detail-oriented and thrive in environments where thoughtful analysis, technical expertise, and well-informed decision-making are valued. You work comfortably within established frameworks and best practices while taking ownership of solutions and continuously improving processes and performance. You communicate clearly and professionally, collaborate effectively across teams, and lead by example through strong follow-through, accountability, and technical excellence." Our Working Culture (prose): "With our in-office philosophy, our associates are expected to be in the office at least three days per week, supporting a healthy balance between in-person collaboration and flexible remote work. We take pride in our vibrant and inclusive culture, which thrives on meaningful connection, shared purpose, and cross-functional teamwork. In-office engagement plays a vital role in fostering spontaneous collaboration, accelerating innovation, and strengthening relationships across teams. It also provides valuable opportunities for mentorship, professional development, and a deeper sense of community. Please note: While the current expectation is a minimum of three days per week in the office, this may evolve over time in alignment with business needs and our continued commitment to culture-building" Salary: "$120,000 - $150,000, actual compensation within this range will be determined by multiple factors including candidate experience and expertise." Now we need to decide sections. Potential sections: - About the role (combining Who We Are and Why This Role Matters) - Responsibilities (What You’ll Deliver) - Qualifications (combining What You’ll Bring To The Team and What Would Make You Stand Out) - Where You’ll Thrive (maybe as "Work Style" but not in list; could be omitted or put under About the role? But it's substantive. Could be its own section maybe "Work Style" but not in allowed headings. Could use "About the role" again? Might be okay to add a section not in list? The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but suggests those are typical. However to be safe, we could map Where You’ll Thrive to "Qualifications" or "Skills"? But it's more about work style. Could be omitted? But we must preserve all substantive information. So we need to include it somewhere. Could add a section "Work Style" but that's not in the list; risk of deviating. Perhaps we can incorporate it into "About the role" as additional prose. That would preserve info.
Similarly Our Working Culture could go under Schedule? Actually schedule is about in-office expectation. Could be part of Schedule section. But we also have culture description. Could be part of "About the role" as well.
But we need to avoid too many thin sections. Perhaps we can have:
About the role
(company overview + role significance + work style + culture)
Responsibilities
Qualifications
Pay
Schedule
That's 5 sections.
Now we need to ensure we don't include filler like "commensurate with experience". Not present.
We need to use - for any list of duties/requirements/benefits. So Responsibilities list as
- . Qualifications list as
- . Pay and Schedule as prose
.
Now we need to extract the content for each section.
About the role: combine Who We Are, Why This Role Matters, Where You’ll Thrive, Our Working Culture.
We need to preserve all substantive information, not invent or summarize away detail. So we need to include all sentences from those sections.
We'll need to concatenate them into paragraphs (
). Could be multiple
elements.
Let's gather the text:
Who We Are:
"At Preferred Travel Group, we champion the power of travel to inspire meaningful connections and enrich lives around the world. As a global family of brands and programs representing the finest independent hotels and resorts, we are united by a shared belief in authenticity, collaboration, and the value of independent spirit. Our culture reflects our ideology in action: people first, relationships at the center, and a commitment to creating lasting impact for our partners, our global community, and one another. When you join Preferred, you become part of a purpose-driven organization where ideas are welcomed, growth is encouraged, and your work contributes to shaping the future of travel."
Why This Role Matters:
"We are seeking a highly organized, proactive, and technically skilled Data Engineer III to design, build, and optimize scalable data solutions that power business operations across Preferred Travel Group. This role develops and supports modern data pipelines, integrations, and reporting capabilities while partnering closely with business stakeholders and engineering teams to deliver reliable, high-quality data. Success in this role comes from independently delivering well-designed solutions, continuously improving data processes, collaborating effectively across teams, and identifying opportunities to increase the reliability, performance, and value of our data platform."
Where You’ll Thrive:
"You enjoy bringing structure to complex data challenges, following projects
- . Qualifications list as
- . Pay and Schedule as prose
. Now we need to extract the content for each section. About the role: combine Who We Are, Why This Role Matters, Where You’ll Thrive, Our Working Culture. We need to preserve all substantive information, not invent or summarize away detail. So we need to include all sentences from those sections. We'll need to concatenate them into paragraphs (
). Could be multiple
elements. Let's gather the text: Who We Are: "At Preferred Travel Group, we champion the power of travel to inspire meaningful connections and enrich lives around the world. As a global family of brands and programs representing the finest independent hotels and resorts, we are united by a shared belief in authenticity, collaboration, and the value of independent spirit. Our culture reflects our ideology in action: people first, relationships at the center, and a commitment to creating lasting impact for our partners, our global community, and one another. When you join Preferred, you become part of a purpose-driven organization where ideas are welcomed, growth is encouraged, and your work contributes to shaping the future of travel." Why This Role Matters: "We are seeking a highly organized, proactive, and technically skilled Data Engineer III to design, build, and optimize scalable data solutions that power business operations across Preferred Travel Group. This role develops and supports modern data pipelines, integrations, and reporting capabilities while partnering closely with business stakeholders and engineering teams to deliver reliable, high-quality data. Success in this role comes from independently delivering well-designed solutions, continuously improving data processes, collaborating effectively across teams, and identifying opportunities to increase the reliability, performance, and value of our data platform." Where You’ll Thrive: "You enjoy bringing structure to complex data challenges, following projects
- . Pay and Schedule as prose