Data Engineering Manager, Regulatory Compliance
for each section heading. Use - for lists. Use
for prose. Remove boilerplate: "This position is listed on behalf of a partner company..." etc. Also remove "How Jobgether Works", "Why Apply Through Jobgether?", "Data Privacy Notice", etc. Also remove "Our partner is looking for a Data Engineering Manager, Regulatory Compliance based in United States." That's maybe part of about the role? We can keep description but not as heading. We need to preserve all substantive information. So we need to extract the role description, responsibilities list, requirements list, benefits list, pay (salary range). Also maybe mention remote work environment as benefit.
We must not include sections with placeholder text. So we will have sections: About the role (maybe a paragraph summarizing). Responsibilities (list). Requirements (list). Benefits (list). Pay (maybe a paragraph with salary range). Schedule not present, so omit.
We must not include Job ID etc.
Let's craft.
First, About the role: combine sentences: "As a Data Engineering Manager, Regulatory Compliance, you will lead a data engineering team responsible for building scalable, reliable, and high-quality data solutions in a highly regulated environment. You will work closely with Data Services, Analytics Engineering, Product, Finance, Compliance, and business stakeholders to support critical analytics and regulatory initiatives. The role combines people leadership with hands-on technical guidance across data pipelines, infrastructure, architecture, and tooling. You will serve as a key point of contact for regulatory professionals and help ensure data programs meet strict deadlines, audit requirements, and compliance expectations. You will also influence technical priorities, improve engineering practices, and strengthen the reliability and scalability of the data platform. This is an opportunity to lead a growing technical team while contributing to data products within the sports, betting, gaming, and entertainment space."
That's substantive.
Responsibilities: list from "Accountabilities" bullet points. They are sentences separated by periods but we can treat each as list item.
List items:
- Lead the day-to-day activities of the data engineering team, including goal setting, mentorship, coaching, performance management, feedback, delegation, and technical guidance.
- Establish clear expectations and communicate professionally with state and provincial regulatory professionals, supporting a high-responsibility workstream subject to regulatory scrutiny and audits.
- Partner with Analytics, Finance, Compliance, Product, Data Services, and other engineering teams to develop data pipelines, infrastructure, and tooling that support critical analytics and regulatory initiatives.
- Prioritize and manage data-related projects across functions, guiding initiatives from initial planning and requirements through delivery and ongoing improvement.
- Contribute to the design, maintenance, and continuous enhancement of data pipelines, architecture, infrastructure, and engineering processes.
- Ensure data engineering solutions meet appropriate standards for performance, scalability, reliability, data quality, and regulatory requirements.
- Make and defend technical and project-priority decisions with stakeholders based on engineering assessments, business needs, delivery timelines, and regulatory considerations.
- Support effective project planning and execution while maintaining strong time management, risk management, and problem-solving practices.
- Stay current with emerging data engineering technologies, techniques, industry practices, and other developments relevant to the team's technical roadmap.
- Communicate technical concepts, project status, risks, and priorities clearly to both technical and non-technical stakeholders across the organization.
- Promote strong teamwork, collaboration, and professional development while helping engineers grow their technical and leadership capabilities.
Requirements: list from "Requirements" bullet points.
List items:
- Bring at least 3 years of experience in a data-oriented leadership or management role combined with 5+ years of software or data development experience.
- Have experience managing or leading teams of at least three engineers, with demonstrated ability to mentor, delegate, provide feedback, and build an effective engineering culture.
- Possess a strong foundation in computer science, distributed systems, software engineering, system design, data architecture, and data governance.
- Have experience working in a regulated industry or environment where compliance requirements, audits, strict deadlines, and regulatory stakeholders are important considerations.
- Demonstrate strong project management, time management, prioritization, and problem-solving skills, with experience using Atlassian and other Agile tools.
- Be able to communicate complex technical information clearly to stakeholders at different levels, including non-technical audiences and regulatory professionals.
- Possess excellent written, verbal, presentation, collaboration, and stakeholder-management skills.
- Demonstrate the ability to make thoughtful technical and business priority decisions and confidently communicate the rationale behind those decisions.
- Have experience with data pipeline and workflow technologies such as Airflow, dbt, AWS Lambda, or comparable tools.
- Bring strong knowledge of relational databases, SQL, Python, and Docker, along with experience working with cloud platforms such as AWS or GCP and related services.
- Have a solid understanding of systems design fundamentals, data architecture, and data governance principles.
- Experience with React, Django, Flask, Kubernetes, Terraform, or machine learning concepts is considered a plus.
- An interest in professional sports, sports betting, gaming, or eSports is an advantage.
Benefits: list from "Benefits" bullet points.
List items:
- Competitive compensation package, with the source-listed salary range of $165,000–$200,000 CAD.
- Remote work environment.
- A relaxed and collaborative workplace culture.
- Education and conference reimbursement to support continued professional development.
- Opportunities for career progression and leadership development.
- Opportunities to mentor and develop other members of the engineering organization.
- Access to a broad range of benefits and support designed to help employees manage their physical, financial, and emotional well-being.
- Personalized benefits options and resources intended to support employees through major life milestones and everyday needs.
But note salary range also appears in Benefits; we could also have a Pay section. The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." Benefits are stated, so we can have Benefits section. Pay is also stated (salary range) but it's within Benefits. Could we separate Pay? The instruction says prefer a few substantive sections over many thin ones. So we could keep salary range inside Benefits. But we could also create a Pay section if we want, but that would be thin. Better to keep within Benefits.
Thus we have sections: About the role, Responsibilities, Requirements, Benefits.
We must not repeat job title as heading. So no heading for Data Engineering Manager.
We must output only HTML fragment, no /, no markdown fences.
Let's craft:
About the role
... paragraphs ...
Responsibilities
- ...
...
Similarly for Requirements and Benefits.
Make sure to preserve all substantive information. Ensure we didn't lose any detail.
Check About the role: we included all sentences from description. Did we miss "This position is listed on behalf of a partner company, who manages all applications and next steps." That's boilerplate about partner managing applications; we should remove as per instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. That sentence is about partner managing applications; it's not substantive about role, it's about application process. So we can drop.
Also "Our partner is looking for a Data Engineering Manager, Regulatory Compliance based in United States." That's basically repeating job title and location; we can incorporate location maybe? Not required. Could keep location as part of About the role? It's not essential but could be considered substantive. However location is not repeated elsewhere. Might be worth keeping. But we must not repeat job title as heading; we can include location in paragraph. The sentence: "Our partner is looking for a Data Engineering Manager, Regulatory Compliance based in United States." That's basically stating the role and location. Since we already have role description, we could mention location: "based in the United States". Let's incorporate: add "based in the United States" somewhere.
Thus About the role paragraph: "As a Data Engineering Manager, Regulatory Compliance based in the United States, you will lead a data engineering team ..." That includes location.
Check we didn't lose any other details: "As a Data Engineering Manager, Regulatory Compliance, you will lead a data engineering team responsible for building scalable, reliable, and high-quality data solutions in a highly regulated environment." Good.
Now Responsibilities: we captured all bullet points from "Accountabilities". Ensure we didn't miss any: The list includes 11 items. Let's verify each:
Original Accountabilities text:
"Accountabilities Lead the day-to-day activities of the data engineering team, including goal setting, mentorship, coaching, performance management, feedback, delegation, and technical guidance.Establish clear expectations and communicate professionally with state and provincial regulatory professionals, supporting a high-responsibility workstream subject to regulatory scrutiny and audits.Partner with Analytics, Finance, Compliance, Product, Data Services, and other engineering teams to develop data pipelines, infrastructure, and tooling that support critical analytics and regulatory initiatives.Prioritize and manage data-related projects across functions, guiding initiatives from initial planning and requirements through delivery and ongoing improvement.Contribute to the design, maintenance, and continuous enhancement of data pipelines, architecture, infrastructure, and engineering processes.Ensure data engineering solutions meet appropriate standards for performance, scalability, reliability, data quality, and regulatory requirements.Make and defend technical and project-priority decisions with stakeholders based on engineering assessments, business needs, delivery timelines, and regulatory considerations.Support effective project planning and execution while maintaining strong time management, risk management, and problem-solving practices.Stay current with emerging data engineering technologies, techniques, industry practices, and other developments relevant to the team's technical roadmap.Communicate technical concepts, project status, risks, and priorities clearly to both technical and non-technical stakeholders across the organization.Promote strong teamwork, collaboration, and professional development while helping engineers grow their technical and leadership capabilities."
We have all.
Requirements: list from "Requirements". Let's verify each:
"Bring at least 3 years of experience in a data-oriented leadership or management role combined with 5+ years of software or data development experience."
"Have experience managing or leading teams of at least three engineers, with demonstrated ability to mentor, delegate, provide feedback, and build an effective engineering culture."
"Possess a strong foundation in computer science, distributed systems, software engineering, system design, data architecture, and data governance."
"Have experience working in a regulated industry or environment where compliance requirements, audits, strict deadlines, and regulatory stakeholders are important considerations."
"Demonstrate strong project management, time management, prioritization, and problem-solving skills, with experience using Atlassian and other Agile tools."
"Be able to communicate complex technical information clearly to stakeholders at different levels, including non-technical audiences and regulatory professionals."
"Possess excellent written, verbal, presentation, collaboration, and stakeholder-management skills."
"Demonstrate the ability to make thoughtful technical and business priority decisions and confidently communicate the rationale behind those decisions."
"Have experience with data pipeline and workflow technologies such as Airflow, dbt, AWS Lambda, or comparable tools."
"Bring strong knowledge of relational databases, SQL, Python, and Docker, along with experience working with cloud platforms such as AWS or GCP and related services."
"Have a solid understanding of systems design fundamentals, data architecture, and data governance principles."
"Experience with React, Django, Flask, Kubernetes, Terraform, or machine learning concepts is considered a plus."
"An interest in professional sports, sports betting, gaming, or eSports is an advantage."
All captured.
Benefits: list from "Benefits". Let's verify each:
"Competitive compensation package, with the source-listed salary range of $165,000–$200,000 CAD."
"Remote work environment."
"A relaxed and collaborative workplace culture."
"Education and conference reimbursement to support continued professional development."
"Opportunities for career progression and leadership development."
"Opportunities to mentor and
for prose. Remove boilerplate: "This position is listed on behalf of a partner company..." etc. Also remove "How Jobgether Works", "Why Apply Through Jobgether?", "Data Privacy Notice", etc. Also remove "Our partner is looking for a Data Engineering Manager, Regulatory Compliance based in United States." That's maybe part of about the role? We can keep description but not as heading. We need to preserve all substantive information. So we need to extract the role description, responsibilities list, requirements list, benefits list, pay (salary range). Also maybe mention remote work environment as benefit. We must not include sections with placeholder text. So we will have sections: About the role (maybe a paragraph summarizing). Responsibilities (list). Requirements (list). Benefits (list). Pay (maybe a paragraph with salary range). Schedule not present, so omit. We must not include Job ID etc. Let's craft. First, About the role: combine sentences: "As a Data Engineering Manager, Regulatory Compliance, you will lead a data engineering team responsible for building scalable, reliable, and high-quality data solutions in a highly regulated environment. You will work closely with Data Services, Analytics Engineering, Product, Finance, Compliance, and business stakeholders to support critical analytics and regulatory initiatives. The role combines people leadership with hands-on technical guidance across data pipelines, infrastructure, architecture, and tooling. You will serve as a key point of contact for regulatory professionals and help ensure data programs meet strict deadlines, audit requirements, and compliance expectations. You will also influence technical priorities, improve engineering practices, and strengthen the reliability and scalability of the data platform. This is an opportunity to lead a growing technical team while contributing to data products within the sports, betting, gaming, and entertainment space." That's substantive. Responsibilities: list from "Accountabilities" bullet points. They are sentences separated by periods but we can treat each as list item. List items: - Lead the day-to-day activities of the data engineering team, including goal setting, mentorship, coaching, performance management, feedback, delegation, and technical guidance. - Establish clear expectations and communicate professionally with state and provincial regulatory professionals, supporting a high-responsibility workstream subject to regulatory scrutiny and audits. - Partner with Analytics, Finance, Compliance, Product, Data Services, and other engineering teams to develop data pipelines, infrastructure, and tooling that support critical analytics and regulatory initiatives. - Prioritize and manage data-related projects across functions, guiding initiatives from initial planning and requirements through delivery and ongoing improvement. - Contribute to the design, maintenance, and continuous enhancement of data pipelines, architecture, infrastructure, and engineering processes. - Ensure data engineering solutions meet appropriate standards for performance, scalability, reliability, data quality, and regulatory requirements. - Make and defend technical and project-priority decisions with stakeholders based on engineering assessments, business needs, delivery timelines, and regulatory considerations. - Support effective project planning and execution while maintaining strong time management, risk management, and problem-solving practices. - Stay current with emerging data engineering technologies, techniques, industry practices, and other developments relevant to the team's technical roadmap. - Communicate technical concepts, project status, risks, and priorities clearly to both technical and non-technical stakeholders across the organization. - Promote strong teamwork, collaboration, and professional development while helping engineers grow their technical and leadership capabilities. Requirements: list from "Requirements" bullet points. List items: - Bring at least 3 years of experience in a data-oriented leadership or management role combined with 5+ years of software or data development experience. - Have experience managing or leading teams of at least three engineers, with demonstrated ability to mentor, delegate, provide feedback, and build an effective engineering culture. - Possess a strong foundation in computer science, distributed systems, software engineering, system design, data architecture, and data governance. - Have experience working in a regulated industry or environment where compliance requirements, audits, strict deadlines, and regulatory stakeholders are important considerations. - Demonstrate strong project management, time management, prioritization, and problem-solving skills, with experience using Atlassian and other Agile tools. - Be able to communicate complex technical information clearly to stakeholders at different levels, including non-technical audiences and regulatory professionals. - Possess excellent written, verbal, presentation, collaboration, and stakeholder-management skills. - Demonstrate the ability to make thoughtful technical and business priority decisions and confidently communicate the rationale behind those decisions. - Have experience with data pipeline and workflow technologies such as Airflow, dbt, AWS Lambda, or comparable tools. - Bring strong knowledge of relational databases, SQL, Python, and Docker, along with experience working with cloud platforms such as AWS or GCP and related services. - Have a solid understanding of systems design fundamentals, data architecture, and data governance principles. - Experience with React, Django, Flask, Kubernetes, Terraform, or machine learning concepts is considered a plus. - An interest in professional sports, sports betting, gaming, or eSports is an advantage. Benefits: list from "Benefits" bullet points. List items: - Competitive compensation package, with the source-listed salary range of $165,000–$200,000 CAD. - Remote work environment. - A relaxed and collaborative workplace culture. - Education and conference reimbursement to support continued professional development. - Opportunities for career progression and leadership development. - Opportunities to mentor and develop other members of the engineering organization. - Access to a broad range of benefits and support designed to help employees manage their physical, financial, and emotional well-being. - Personalized benefits options and resources intended to support employees through major life milestones and everyday needs. But note salary range also appears in Benefits; we could also have a Pay section. The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." Benefits are stated, so we can have Benefits section. Pay is also stated (salary range) but it's within Benefits. Could we separate Pay? The instruction says prefer a few substantive sections over many thin ones. So we could keep salary range inside Benefits. But we could also create a Pay section if we want, but that would be thin. Better to keep within Benefits. Thus we have sections: About the role, Responsibilities, Requirements, Benefits. We must not repeat job title as heading. So no heading for Data Engineering Manager. We must output only HTML fragment, no /, no markdown fences. Let's craft:
About the role
... paragraphs ...
Responsibilities
- ... ...