Data & AI Governance Manager

We need to output HTML fragment with sections: About the role? Actually we have sections: "The opportunity", "About Kubrick", "What you'll be doing", "Details of role:", "What we're looking for", "Benefits". Also location and salary given at top: "Location: New York Salary: $115,000 - $130,000". According to rules: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use

• for any list of duties/requirements/benefits, and

  for prose. 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. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. We have location and salary: we can include them in a short

  maybe before sections. Not as headings. So we can have

  Location: New York. Salary: $115,000 - $130,000.

  Now sections: "The opportunity" is a prose paragraph describing role. Could be under heading "About the role"? The rules say use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to map content to these headings. We have "About Kubrick" maybe "About the role"? Actually "About Kubrick" is about company, not role. Could be "About the role" for description of role. But we also have "What you'll be doing" which is responsibilities. "Details of role:" also responsibilities. "What we're looking for" is requirements/qualifications. "Benefits" is benefits. We need to avoid thin sections. So we can combine similar content. Let's decide sections: - About the role: combine "The opportunity" and "About Kubrick"? Actually "About Kubrick" is about company, not role. Could be separate "About the company"? Not in list. But we could put under "About the role" maybe include both? Might be okay. Better: Use headings: About the role (includes opportunity and Kubrick description). Responsibilities (includes "What you'll be doing" and "Details of role:" bullet points). Requirements (includes "What we're looking for" bullet points). Benefits (list). Possibly Skills? Not needed. We must not create Pay or Schedule sections unless stated. Salary is given but we already included in paragraph; we could also make a Pay section? The rule says never create Pay/Schedule/Benefits sections unless posting actually states them. It does state salary, so we could create a Pay section. But they said prefer few substantive sections over many thin ones. We already have salary in paragraph; maybe better to include Pay section with salary? But they said include a section ONLY when posting has real, specific content for it — never emit a heading followed by filler/placeholder text. Salary is specific. So we could have a Pay section with the salary range. However they also said use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So Pay is allowed. But we already have location and salary in a paragraph; we could move salary to Pay section and location maybe in a short paragraph. But we need to preserve all substantive information. So we need to include location somewhere. Could be in a short

  before sections. Thus final structure:

  Location: New York.

  Pay

  $115,000 - $130,000

  Then sections:

  About the role

  ... combine opportunity and Kubrick description.

  Responsibilities

  • ... list items from "What you'll be doing" and "Details of role:"

  Requirements

  • ... list items from "What we're looking for"

  Benefits

  • ... list benefits
  We must not include duplicated lines. Need to extract content. Let's extract: The opportunity paragraph: "We are seeking an experienced and forward-thinking Data & AI Governance Manager to join our growing Data Management capability, based in New York. This role blends client-facing delivery with thought leadership and internal development responsibilities, helping shape and scale Kubrick’s Data & AI Governance proposition." About Kubrick paragraph: "Kubrick is an award-winning consultancy that helps organizations design, build and scale data and AI solutions that deliver lasting impact.We work with organizations across industries including financial services, healthcare, retail, energy, aviation, and the public sector, and partner with leading technology providers such as Microsoft, Snowflake, Databricks, and Collibra.What sets us apart is how we build capabilities and careers. Through continuous learning, real-world experience, and a collaborative culture, we help our people develop the skills, confidence, and experience to build rewarding careers." We can combine into About the role paragraph. Now responsibilities: from "What you'll be doing" paragraph and "Details of role:" bullet list. What you'll be doing paragraph: "You’ll oversee delivery of a variety of data management engagements, whether focused on standing up business glossaries and ownership models, rolling out enterprise data catalogues and lineage, implementing data quality frameworks and issue triage processes, or designing data governance operating models.In addition to hands-on technical work, you will often play a leadership role in Kubrick’s delivery squads, providing technical guidance and ensuring best practices are followed throughout the project lifecycle. You will work closely with clients and internal stakeholders to translate business requirements into robust technical solutions, ensuring projects are delivered on time, within scope, and aligned with client expectations." Details of role: bullet list (each line starts with a verb). Let's list them: - Lead delivery of data governance, metadata management, and data quality workstreams for clients. - Define and implement enterprise frameworks covering stewardship, ownership, policy and standards, issue management, and governance processes. - Support configuration, implementation, and enablement of tooling (e.g. Collibra, Immuta, Anomalo, Ataccama etc.). - Design metadata strategies, business glossary structures, and conceptual data models. - Support data lineage initiatives, including mapping end-to-end data flows and identifying critical data elements. - Develop and implement data quality frameworks, profiling strategies, and remediation processes. - Lead internal squads and coach junior team members, providing delivery oversight and subject matter expertise. - Engage with stakeholders to translate business needs into data governance initiatives. - Contribute to internal growth of the capability—developing playbooks, methods, reusable templates, and IP. - Participate in pre-sales efforts and develop client proposals that highlight the value of data management. - Work with Kubrick & client staff of other disciplines to understand and assess requirements, design solutions and inform delivery planning. - Seek, build, and maintain effective client relationships contributing to Kubrick’s commercial priorities and supporting our partnering approach to working with clients. We need to combine with earlier paragraph items (some overlapping). We'll create a unified list, avoiding duplicates. Let's extract unique items. From "What you'll be doing": oversee delivery of data management engagements (business glossaries, ownership models, enterprise data catalogues, lineage, data quality frameworks, issue triage, data governance operating models). Also leadership role in delivery squads, technical guidance, best practices, translate business requirements into technical solutions, ensure on time/scope. From details list we have many similar items. We'll combine. Let's produce a concise but comprehensive list: - Oversee delivery of data management engagements: standing up business glossaries and ownership models, rolling out enterprise data catalogues and lineage, implementing data quality frameworks and issue triage processes, designing data governance operating models. - Provide leadership and technical guidance within Kubrick delivery squads, ensuring best practices are followed throughout the project lifecycle. - Work with clients and internal stakeholders to translate business requirements into robust technical solutions, ensuring projects are delivered on time, within scope, and aligned with expectations. - Lead delivery of data governance, metadata management, and data quality workstreams for clients. - Define and implement enterprise frameworks covering stewardship, ownership, policy and standards, issue management, and governance processes. - Support configuration, implementation, and enablement of governance tooling (e.g., Collibra, Immuta, Anomalo, Ataccama). - Design metadata strategies, business glossary structures, and conceptual data models. - Support data lineage initiatives, including mapping end-to-end data flows and identifying critical data elements. - Develop and implement data quality frameworks, profiling strategies, and remediation processes. - Lead internal squads and coach junior team members, providing delivery oversight and subject matter expertise. - Engage with stakeholders to translate business needs into data governance initiatives. - Contribute to internal capability growth by developing playbooks, methods, reusable templates, and IP. - Participate in pre-sales efforts and develop client proposals highlighting the value of data management. - Collaborate with Kubrick and client staff across disciplines to understand requirements, design solutions, and inform delivery planning. - Seek, build, and maintain effective client relationships supporting Kubrick’s commercial priorities and partnering approach. That seems comprehensive. Now Requirements: from "What we're looking for" paragraph and bullet list. Paragraph: "You’ll bring deep expertise across core data management disciplines such as metadata management, data quality, governance frameworks, stewardship, regulatory compliance, and AI governance practices. You will lead delivery squads, define strategic roadmaps, and guide the configuration and rollout of governance tooling such as Collibra, Ataccama, Informatica or equivalent platforms.The role also requires a strong understanding of how governance adds business value, enabling trusted, discoverable, and well-managed data for analytics, regulatory reporting, operational resilience, and AI enablement." Bullet list under Key Requirements: - Experience in data governance, metadata management, or data quality implementation across large-scale organisations. - Demonstrated expertise in tooling such as Collibra, Ataccama, Immuta, Anomalo etc. - Proven experience designing operating models, governance frameworks, and stewardship roles. - Data Governance or Technology Partner qualifications preferred e.g. DAMA CDMP, Collibra Ranger etc. - Strong understanding of metadata, lineage, CDE management, data cataloguing, and data quality dimensions. - Experience delivering data management solutions on modern platforms such as Databricks, Snowflake, Azure, or AWS. - Strong stakeholder engagement, workshop facilitation, and written/verbal communication skills. - Ability to lead delivery teams and provide coaching or line management to more junior staff. - Comfortable creating documentation, training materials, and supporting upskilling of client users. - Ability to contribute to thought leadership and help define the evolution of the Data & AI Governance capability. We can combine paragraph items into list or keep as prose then list. Since we need
  • for any list of duties/requirements/benefits. So we should put requirements in a list. We'll incorporate the paragraph's points as list items as well. Let's create list: - Deep expertise across core data management disciplines: metadata management, data quality, governance frameworks, stewardship, regulatory compliance, and AI governance practices. - Ability to lead delivery squads, define strategic roadmaps, and guide configuration and rollout of governance tooling (e.g., Collibra, Ataccama, Inform