Lead Data Engineer, Consumer

We need to output HTML fragment with sections: About the role? Actually the posting includes Company Description, Job Description, What You Will Do, Qualifications, Additional Information. We need to use headings for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We should only include sections that have real specific content. The posting does not have explicit Benefits, Pay, Schedule. So we should not include those headings only for sections present: About the role (maybe from Company Description?), Responsibilities (What You Will Do), Requirements (Qualifications). Possibly Skills could be derived from qualifications but we should not invent. The instruction: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. So we can include About the role (company description). Responsibilities (What You Will Do). Requirements (Qualifications). Possibly Skills could be omitted if not explicit. The qualifications list includes required and preferred qualifications; we can put that under Requirements. Could also have a Skills section but not needed. We must not repeat job title as heading. No Job ID etc. We need to preserve all substantive information, remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. The Additional Information includes equal opportunity statement, accommodation request, pay transparency, unsolicited assistance from search firms. Those are boilerplate EEO etc. Should be removed. Also the part about "As part of our selection process, external candidates may be required to attend an in-person interview..." That's not boilerplate? Might be considered part of process but not EEO. It's specific to selection process. Should we keep? It's not boilerplate; it's about interview requirement. Might keep. The equal opportunity statement definitely boilerplate; remove. The accommodation request also boilerplate? It's about disability accommodation; could be considered boilerplate but it's specific policy. Might be considered EEO. Safer to remove. The pay transparency statement: "VERSANT Media is committed to fair and equitable compensation practices. We include a good faith pay range..." This is about pay but not actual range; it's generic. Since we don't have actual pay range, we should not create Pay section. This statement is boilerplate; remove. The unsolicited assistance from search firms is also boilerplate; remove. Thus we keep: Company Description, Job Description (maybe we can incorporate into About the role?), What You Will Do, Qualifications (Required and Preferred). Also maybe "Additional Information" about in-person interview requirement. We need to use

for section headings. Use

• for any list of duties/requirements/benefits. Use

  for prose. We need to preserve all substantive information; do not invent or summarize away detail. Let's extract content: Company Description paragraph: "VERSANT (Nasdaq: VSNT) is an industry-changing media and entertainment business and home to trusted brands that shape culture, inform audiences, and build lasting connections. It operates across four core markets: political news and opinion, business news and personal finance, golf, and sports and genre entertainment. These markets are served through a powerful portfolio of iconic and innovative brands, including CNBC, MS NOW, USA Network, Golf Channel, Oxygen, E!, SYFY, and Versant's sports division USA Sports, along with complementary digital assets including Fandango, Rotten Tomatoes, GolfNow and GolfPass." Job Description paragraph: "We are seeking a hands-on Data Product Engineering Lead to lead engineering resources to deliver trusted, scalable, and reusable data products from source systems through the Silver layer of our enterprise data platform. This role is accountable for turning product and business needs into reliable, governed data capabilities: ingesting source data, applying standardized transformations, implementing data-quality controls, and publishing documented Silver-layer datasets ready for downstream analytics, reporting, AI, and operational use. The Data Product Engineering Lead works closely with Solution Architects, Data Modelers, Product Managers, domain experts, platform teams, and governance partners to ensure each data and digital product is built on a scalable data foundation." What You Will Do: multiple paragraphs with bullet-like sentences. We need to turn into

  • for any list of duties/requirements/benefits. The content is a series of sentences each starting with a verb. We can treat each as a list item. Let's list them: - Lead delivery of source-to-Silver data products - Lead and develop a distributed/offshore team of Data Engineers responsible for delivery from source ingestion through curated Silver-layer data products. - Translate product roadmaps and requirements into actionable engineering plans, milestones, estimates, dependencies, and delivery commitments. - Design and oversee ingestion, transformation, standardization, orchestration, and publication of data from operational, SaaS, file, streaming, API, and partner sources. - Ensure Silver-layer data products are validated, standardized, documented, reusable, performant, secure, and ready for Gold-layer analytics and AI consumption. - Establish repeatable patterns for batch, incremental, change-data-capture, and event-driven processing. - Build scalable engineering foundations - Implement reusable data-engineering frameworks, templates, libraries, and pipeline patterns that reduce repeated effort across products and domains. - Apply modern engineering practices, including source control, peer review, automated testing, CI/CD, observability, release management, and incident remediation. - Define and maintain standards for naming, partitioning, schema evolution, error handling, replay/recovery, performance, cost management, and documentation. - Partner with the Data Platform team to use approved workspace, compute, storage, security, and deployment patterns. - Identify technical debt and lead pragmatic improvements that increase delivery speed, reliability, and maintainability. - Partner across architecture, modeling, and product - Work with Data Modelers to implement canonical entities, conformed dimensions, data contracts, source-to-target mappings, and enterprise modeling standards. - Work with Product Managers and domain leaders to clarify intended outcomes, source-system realities, priority use cases, and acceptance criteria. - Coordinate dependencies with source-system owners, platform teams, analytics teams, and external partners. - Ensure trusted, governed data - Establish data profiling, reconciliation, quality testing, freshness monitoring, lineage, and alerting for every delivered data product. - Ensure source-to-Silver traceability, including authoritative source identification, transformation logic, ownership, metadata, and data-quality expectations. - Implement appropriate access controls, sensitive-data classification, masking, retention, and regional/data-residency requirements. - Drive resolution of data defects, schema changes, pipeline failures, and quality issues through clear ownership and service-level expectations. - Lead the team and delivery operating model - Set clear priorities, technical direction, delivery expectations, and quality standards for the engineering team. - Coach engineers in data engineering, cloud development, testing, observability, and product-oriented delivery practices. - Create a healthy onshore/offshore delivery model with defined handoffs, overlap hours, documentation standards, ceremonies, and escalation paths. - Communicate delivery progress, risks, tradeoffs, and decisions clearly to technical and business stakeholders. - Build a culture of ownership, continuous improvement, and reliable execution. What Success Looks Like: also a list of bullet-like sentences. Should we include as part of Responsibilities? Could be separate section but we don't have a heading for "What Success Looks Like". Not in allowed headings list. Could incorporate into Responsibilities or maybe treat as part of Responsibilities. Since we only allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could put success criteria under Responsibilities as part of duties? Or maybe we could create a separate section but not allowed. Better to incorporate into Responsibilities as additional bullet points. Thus Responsibilities will include all the "What You Will Do" and "What Success Looks Like" bullet points. Now Qualifications: Required qualifications paragraph and Preferred qualifications paragraph. We'll put under Requirements heading (or Qualifications). The allowed headings include Requirements and Qualifications both. We need to decide which to use. The instruction: Use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have both Requirements and Qualifications sections if content exists. We have Required qualifications and Preferred qualifications. Could split: Requirements for required, Qualifications for preferred? Or combine. Better to have Requirements for required qualifications, and Qualifications for preferred qualifications. That matches typical usage. Thus:

    Requirements

    with
    • list of required qualifications.

      Qualifications

      with
      • list of preferred qualifications. We must not repeat job title. Now we need to preserve all substantive information: include the required qualifications text exactly as given, but we can break into list items. Required qualifications text: "8+ years of data engineering, software engineering, or data-platform experience, including 2+ years leading engineers, technical workstreams, or large-scale delivery. Demonstrated experience designing and delivering enterprise-scale ingestion and transformation pipelines. Strong hands-on expertise in SQL, Python, Spark/PySpark, and modern ELT/ETL patterns. Experience with Databricks, Delta Lake, or a comparable lakehouse platform; experience with cloud storage, orchestration, and CI/CD. Strong understanding of Bronze/Silver/Gold or equivalent layered data-platform patterns. Experience implementing data quality, observability, lineage, metadata, and production support practices. Proven ability to partner with architects, data modelers, product leaders, and domain stakeholders. Experience leading distributed teams and creating effective delivery practices across time zones. Strong communication skills and the ability to explain technical choices, risks, and tradeoffs to non-technical stakeholders." We can split each sentence into a list item. Preferred qualifications text: "Experience with Unity Catalog or comparable governance, catalog, and access-control capabilities. Experience with data contracts, schema evolution, change data capture, APIs, event streaming, and large-volume data processing. Experience supporting multiple data domains, global data products, or regional data-residency requirements. Experience with infrastructure-as-code, DataOps, and automated environment provisioning. Experience in a regulated, high-scale, or operationally sensitive environment." Again list items. Now About the role: combine Company Description and Job Description? The heading "About the role" likely expects description of role and company. We'll put company description and job description as prose under About the role. We need to avoid duplication: The Job Description paragraph repeats some of what is in What You Will Do? It's okay to keep. Thus About the role will have two paragraphs: company description and job description. Now we need to ensure we removed boilerplate: equal opportunity, accommodation, pay transparency, unsolicited assistance. Also remove the line "As part of our selection process, external candidates may be required to attend an in-person interview with a VERSANT Media employee at one of our locations prior to a hiring decision." This is not boilerplate; it's specific. Should we keep? It's part of Additional Information. We could include it under About the role maybe as a note. But there is no specific heading for selection process. Could we add a paragraph under About the role? It's still substantive. We'll keep it as a paragraph under About the role after job description. Thus About the role will have three paragraphs: company description, job description, selection process note. Now we need to output only HTML fragment, no /, no markdown. Let's craft. Structure:

        About the role

        Company description...

        Job description...

        Selection process note...

        Responsibilities

        • ...
        ...

        Requirements

        • ...
        ...

        Qualifications

        • ...
        ...
        Check that we didn't miss any substantive info: The "What Success Looks Like" bullet points we need to include. We'll add them under Responsibilities as additional list items. Let's extract those bullet points: - Product teams receive reliable Silver-layer data products on predictable timelines. - New sources and data products