Manager, Semantic Layer Engineering

for prose. We need headings: About the role (intro paragraph). Responsibilities (list). Requirements (maybe combine required experience/skills). Qualifications? Could treat required as Qualifications. Skills maybe separate but we can combine. Benefits (list). Pay (salary range). Schedule? Not mentioned; we should not create Schedule section if no content. So omit. We need to ensure we don't create empty sections. Let's extract content. Intro: "Who are we looking for? Choice Hotels, one of the world’s largest lodging franchisors, is looking for a Manager, Semantic Layer Engineering to build and maintain a semantic layer, a single source of truth for business metrics across reporting, operations, and AI. The Advanced Analytics team at Choice is the team that makes sure everyone across the company — from the franchise owners running our hotels to our commercial teams and senior leaders — is working from the same trusted numbers, whether those numbers show up in a report, an operational system, or an AI assistant. As a key member of our Advanced Analytics team, you will build the governed, machine-readable metric definitions that consolidate logic across dashboards and spreadsheets into one certified foundation every report, system, and AI consumer can trust. Are you a hands-on data leader who thinks in metric definitions, holds a high bar for governance and documentation, and is energized by turning inconsistent business logic into trusted, code-based standards? We invite you to apply today for our Manager, Semantic Layer Engineering role and #MakeItYourChoice." We can put that under About the role. Responsibilities: multiple bullet points under headings: Semantic Layer Architecture & Metric Quality, Metric Lifecycle & Governance Operations, AI Enablement & Trusted Consumption, People Management & Stakeholder Coordination. Each has sub-bullets. We'll flatten into a list? The instruction: Use

• for any list of duties/requirements/benefits. So we can create a
  with each duty as
  • . Could also nest? Probably just flat list. We need to preserve all substantive info; we can break into separate
  • items each containing the sentences. Let's list responsibilities: - Build and maintain the enterprise semantic layer as the default source for governed metrics consumed by dashboards, operational systems, data science, and AI agents, following established semantic layer and metrics tooling standards set by governance leadership. - Implement metric definitions as version-controlled, tested, reusable logic — including SQL, transforms, and joins against AWS Redshift, S3, and other systems — in alignment with established business meaning and product-defined governance criteria. - Execute performance, reliability, and cost optimization tasks for metric query execution, following established observability practices and escalating significant infrastructure decisions for supervisor review. - Operate automated test coverage, SLA monitoring, lineage tracking, anomaly detection rules, and incident response processes for enterprise-certified metrics, following documented quality standards. - Review proposed changes to enterprise-certified metric definitions and support technical change approvals in coordination with the defining product manager, ensuring all updates follow established change management protocols and propagate through the semantic layer. - Execute the metric certification lifecycle, administering promotion gates through which metrics graduate from exploration to product-scoped use to enterprise certification based on usage, quality, and cross-team impact. - Work with product managers under a shared ownership model — product defines the metric need, meaning, quality thresholds, and freshness expectations — and execute implementation, monitoring, and enforcement activities. - Identify metric inconsistencies within assigned functional areas, consolidating duplicate and conflicting metric logic into shared, governed definitions (e.g., a single enterprise definition of RevPAR), and escalating cross-team conflicts that cannot be resolved at the team level to the Senior Director for governance review. - Document workflows, build processes, and approval paths for metric proposal, validation, certification, and consumption. - Maintain accurate records of metric lifecycle status, quality results, and open issues, providing regular and ad hoc status updates to the Senior Director to support governance oversight. - Expose governed metrics and business context to BI platforms (Tableau), operational systems, data science, and AI agents, following established integration patterns so that new products, reports, and AI consumers inherit trusted definitions automatically. - Maintain governed business context within the supporting data catalog so that generative AI applications operate on certified business metadata as well as semantic logic, in alignment with catalog standards set by the Manager, Governance & Stewardship. - Operate monitoring and alerting workflows for metric quality, freshness, and usage in the analytics platform, in partnership with the Manager, Governance & Stewardship, providing regular reports on consumption patterns and anomalies. - Support prototyping and iteration on integrated data catalog and data fabric capabilities in partnership with the Manager, Governance & Stewardship, who serves as product owner for the enterprise data catalog. - Research emerging semantic layer, metadata, and AI-enablement tooling and surface findings and potential adoption options to the Senior Director for evaluation and decision-making. - Directly manage and develop one direct report, closely monitoring their day-to-day tasks and assignments, providing consistent coaching and support, and recommending development opportunities and staffing decisions to the Senior Director for review and approval. - Execute assigned phases of the semantic layer and governance roadmap under the direction of the Senior Director, contributing to the organization’s progress from identifying key metrics and owners to embedding governance directly in systems. - Support the expansion of the semantic layer as the trusted default for enterprise reporting and AI — earning adoption by making it the most reliable, easiest-to-use source and reducing reliance on shadow logic and one-off definitions, within established timelines and priorities. - Communicate progress, metric quality status, and delivery updates to stakeholders as directed, and provide timely reporting to the Senior Director to support broader communications with business unit leadership. - Maintain documentation and ownership records that make every governed metric traceable, explainable, and audit-ready. That's a lot but okay. Now Required Experience, Skills & Competencies: list items: - Bachelor’s degree or equivalent practical experience in computer science, analytics engineering, data engineering, or a related field. - 5+ years of progressive experience in analytics engineering, data engineering, or BI platform roles, including building governed metrics, reusable data models, and enterprise-scale reporting infrastructure (hands-on semantic-layer ownership a strong plus). - Solid, demonstrable SQL skills, with experience in Redshift or other columnar databases; ability to write, optimize, and review complex analytical queries in a production environment. - Hands-on experience implementing semantic layer or metrics-store tooling (e.g., dbt Semantic Layer/MetricFlow, Cube, AtScale, LookML, or similar), including version control (git), CI/CD, and automated testing practices. - Working knowledge of data modeling concepts — dimensional modeling, joins, aggregation logic — performance optimization, and semantic layer design principles. - Demonstrated experience executing data quality frameworks in production: automated tests, SLAs, monitoring, alerting, and incident response for trusted data products. - Experience with Tableau or comparable BI platforms, including how governed, certified data sources power enterprise reporting at scale. - Strong attention to detail with accountability for the accuracy, consistency, and governance of enterprise metric definitions consumed by leadership, franchisees, and AI systems. - Strong communication skills, with the ability to coordinate on metric definitions and methodologies across product, analytics, and business teams, and to provide clear and regular status updates to management. - Demonstrated ability to manage multiple concurrent tasks and priorities while maintaining data quality and delivery timelines. Preferred: - Advanced degree in a quantitative or technical field. - Experience with data catalog, lineage, and data quality tooling (e.g., Atlan, Collibra, Alation, DataHub, Monte Carlo, or similar) and how these integrate with a governed semantic layer. - People-leadership experience, or demonstrated readiness to manage and develop a direct report while standing up a new organizational capability. - Experience with Jira, Confluence, or other Atlassian products for project tracking, documentation, and cross-functional coordination in agile delivery environments. Your Team: This is a leadership role that will report to the Senior Director, Data Delivery and Enterprise Governance. You will have 1 direct report and collaborate with cross-functional departments on a regular basis. Salary Range: The salary range for this position is $123,600 to $145,400 annually. In addition to the annual salary, this role is eligible for an annual bonus based on the terms of Choice’s Management Incentive Plan (MIP). The pay range listed is for this position and is what Choice Hotels reasonably expects to pay. We may ultimately pay more or less than the posted range, and the range may be modified in the future. An employee’s pay position within the pay range will be based on several factors including, but not limited to, relevant education, qualifications, certifications, experience, skills, seniority, geographic location, performance, shift, travel requirements, sales or revenue-based metrics, and business or organizational needs. Benefits: Choice prioritizes our associate wellbeing by offering a comprehensive benefits program that is both competitive and flexible to help you achieve your wellbeing goals — here are just a few: Competitive compensation and benefits, including medical, dental, and vision coverage Leave and paid time-off for holidays, vacation, personal, family, volunteer, sick, jury duty, bereavement, military, and religious observance Financial benefits for retirement and health savings Employee recognition programs Discounts at Choice hotels worldwide Note there is duplicated paragraph; we need to preserve but not duplicate? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. Remove duplicated lines. So we should deduplicate the benefits paragraph (it appears twice). We'll keep one copy. About Choice: paragraphs about Choice Hotels International, etc. We'll keep. We should not include location details? It's substantive but maybe not required; but we can include as part of About Choice? It's about corporate office locations. Might be considered substantive. We'll include. Now structure:

    About the role

    ... intro ...

    Responsibilities

    • ... each duty ...
    ...

    Requirements

    • ... required items ...
    ...
    Maybe also

    Preferred Qualifications

    but we can combine under Requirements? The instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we could have Requirements and Qualifications separate. But we have required experience/skills/competencies; we could put under Requirements. Preferred could be under Qualifications? Or Skills? Might be better to have Requirements (required) and Qualifications (preferred). But we also have Skills separate? Could combine skills under Requirements. To follow instruction, we can have Requirements and Qualifications. Let's put required under Requirements, preferred under Qualifications. We also have Skills maybe not needed separately. We'll have:

    Requirements

    required items

    Qualifications

    preferred items

    Your Team

    ...

    Pay

    ... salary range ...

    Benefits

    benefits items

    About Choice

    ...

    We should not include Schedule. Now ensure we don't include any filler like "commensurate with experience". Not present. Now produce HTML fragment. Let's