Manager, Data Engineering

We need to output HTML fragment with sections: About the role (but we already have "About The Role" heading in source; we need to use

for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title as heading. We need to include sections only if posting has real specific content. We have content: About Niche (company description) maybe not needed as a section? The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should create sections for those headings that have content. We have "About The Role" content: description of role, responsibilities, etc. Could map to "About the role" heading. We have "What You Will Do" list of duties -> could be Responsibilities. We have "During the First Month:", "Within 3 Months:", etc. Those could be part of Responsibilities or maybe separate? Probably combine into Responsibilities. We have "Required" section: "What We Are Looking For" with bullet list of requirements -> could be Requirements or Qualifications. We have "Preferred" section: list of preferred experience -> could be Qualifications or Skills. We have "Compensation": salary range etc -> Pay section. We have "Why Niche?" includes benefits: flexible work, health plan, PTO, stipend, parental leave, 401k, etc -> Benefits section. We have no explicit Schedule info (maybe full-time). Not given specifics, so we should not create Schedule section unless posting actually states them. It says "Full time, salaried position". That's schedule info (full-time). Could we include Schedule? The rule: never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state "Full time, salaried position". So we could include Schedule section with that detail. However we also have Benefits section covering many benefits. Pay section for salary. We need to avoid boilerplate like EEO, legal, etc. Remove those. We need to preserve all substantive information; do not invent or summarize away detail. So we need to include all details from the posting, but we can structure them. We must not repeat job title as heading. No mention of job ID etc. We need to output only HTML fragment, no /, no markdown fences. Let's extract content. Company description "About Niche" maybe not needed as a section; but we could include as a

before sections? The instruction: Use

for prose. It didn't forbid a general intro paragraph. We could include it as a

before sections. However they said "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say we cannot have other headings, but we should follow that pattern. Probably we can include a brief intro as

without heading. But we need to preserve ALL substantive information. The "About Niche" paragraph is substantive; we should keep it. Could place as a

before sections. Now sections: - About the role: include the paragraph under "About The Role": "We are looking for a Manager, Data Engineering to lead a team of highly skilled data engineers in building and scaling our modern data platform. You’ll drive execution of our data product roadmap, mentor engineers across levels, and foster a strong engineering culture grounded in best practices. This is a people and project leadership role that requires both technical depth and the ability to enable others. You’ll report to the Head of Data Engineering." That's the content. - Responsibilities: include "What You Will Do" bullet list and the timeline sections (During the First Month, Within 3 Months, Within 6 Months, Within 12 Months). Also maybe "Lead and manage a team..." etc. We'll combine. We need to use

• for any list of duties/requirements/benefits. So each bullet list becomes
  • . For timeline items, they are not a simple list but we could treat each as
  • with subtext. We'll produce something like:

    Responsibilities

    • Lead and manage a team of 3-5 data/software engineers to execute on the data product roadmap
    • Oversee the design, development, and maintenance of scalable, secure, and observable data pipelines and warehouse layers using Python, SQL, Snowflake, DBT, Airflow, and Kafka to support content delivery, analytics, reporting, and operational systems
    • Drive a strong execution culture by managing sprint planning, work estimation, standups, and retrospectives
    • Collaborate closely with cross-functional partners in Analytics, Product, and Engineering to understand data requirements and deliver solutions aligned with business priorities
    • Ensure operational excellence by guiding the team on monitoring, troubleshooting, and resolving production issues
    • Implement and uphold engineering best practices including testing, CI/CD, code reviews, and documentation
    • Coach and mentor team members on technical execution, communication, and career development
    • Identify and remove process bottlenecks to improve development velocity, delivery quality, system performance, and overall cost efficiency across the data platform
    • Participate in hiring efforts and help onboard new team members
    • During the first month: Learn about Niche by meeting with various team members to learn more about our company through our Onboarding meetings; Build trust with team members and cross-functional stakeholders; Review current data systems, pipelines, and platform architecture
    • Within 3 months: Lead team rituals (standups, planning, retros) with consistency and clarity; Oversee day-to-day execution of data platform and pipeline projects; Partner with stakeholders across Analytics, Product, and Engineering to align priorities; Begin coaching team members on execution, communication, and growth areas
    • Within 6 months: Drive accountability and delivery for key roadmap initiatives; Identify and resolve process bottlenecks; promote technical best practices; Guide the team on data quality, pipeline reliability, and operational excellence; Participate in hiring and onboarding new engineers
    • Within 12 months: Demonstrate measurable impact on platform scalability, data availability, and team performance; Evolve team structure, goals, and operating model to meet growing business needs; Serve as a strategic partner across Niche to improve how data is acquired, transformed, governed, and delivered
    But note we have duplicated content: some items appear also in the earlier list; but we must preserve all substantive information, not remove duplicates? The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So we should remove duplicated lines. The timeline items may be considered duplicated of responsibilities? They are not exactly same but they elaborate. However they might be considered duplicated lines? The instruction says remove duplicated lines. The timeline items are not exactly same as earlier bullet list but they are related. I'd keep them as they add detail (timeframes). Not duplicate lines exactly. So fine. Now Requirements: from "Required" section: "What We Are Looking For" bullet list: - 6+ years of experience in data engineering, with 1–2 years of team leadership experience - Proven experience in managing and mentoring data engineers - Deep knowledge of modern data platforms (Snowflake, DBT, Airflow, Airbyte, RudderStack, Kafka, etc.) - Strong skills in Python, SQL, and data modeling (3NF, dimensional, data vault) - Experience delivering robust, observable, secure, and scalable data pipelines - Familiarity with Agile product delivery and cross-functional collaboration - Strong communication skills and a bias for clarity and action We'll put under

    Requirements

    (or Qualifications?). The instruction list includes Requirements and Qualifications as possible headings. We need to decide which to use. Since we have both Required and Preferred, we could map Required to Requirements, Preferred to Qualifications or Skills. Let's use Requirements for Required, and Qualifications for Preferred (or Skills). The instruction says we can use Skills as heading. But we have Preferred experience list; could be Qualifications. We'll use

    Qualifications

    for Preferred. Now Preferred bullet list: - Experience of the ingestion and processing of third-party data sources (e.g., CRMs, Google Analytics, ad platforms, social media), lead delivery pipelines, marketing attribution, customer segmentation, and personalized user experiences - Exposure to data monetization / licensing, or external data product delivery - Background in working with external datasets or geospatial data - Demonstrated success in fostering a high-performing, inclusive team culture We'll put under Qualifications. Now Pay: compensation details: "Our national target base salary range is $122,000-$153,000, plus participation in our Annual Bonus and Stock Option Program. Base compensation will be commensurate with experience and skills. At Niche, our Total Rewards Philosophy is centered around creating a workplace environment that attracts, motivates, and retains top talent by providing a comprehensive and competitive rewards package. This philosophy is built on the principles of performance-based compensation, best-in-class benefits and work-life balance, and employee well-being." We need to include Pay section with salary range etc. However we must avoid filler like "commensurate with experience and skills" which is placeholder? The rule: never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD"). The phrase "Base compensation will be commensurate with experience and skills." is somewhat filler but it's actual statement. Might be considered filler? It's vague but it's in the posting. The instruction says never emit a heading followed by filler/placeholder text. It's ambiguous if we should omit that sentence. Safer to include only concrete info: salary range, bonus, stock option. We could keep the sentence but risk being considered filler. I'd include the salary range and bonus/stock option; maybe omit the commensurate sentence. Now Benefits: from "Why Niche?" we have: - fully flexible workforce empowering employees to choose to work remotely, in our Pittsburgh office or whatever combination suits you - Full time, salaried position with competitive compensation in a fast-growing company (but compensation already covered) - Best-in-class 100% paid employee health plan, including vision and dental and supplemental coverage - Flexible Paid Time Off Policy - Stipend that allows you to build your work from home office in a style and function that suits your personal preferences - Parental leave for all employees (12 weeks fully paid) in addition to short term disability for birthing parents - Meaningful 401(k) with employer match - Your ideas and work will make an immediate impact on our company and millions of users - You will join a team that cares about you, our mission, our work - and celebrates our wins together! Also mention: Niche will only employ those who are legally authorized to work in the United States without sponsorship now or in the future for this opening. We are currently hiring in states where we currently have employees: list of states. Candidates only. No recruiters or agencies, please. Sorry, we do not offer relocation assistance. These are not benefits but eligibility/location. Might be considered boilerplate? Not exactly boilerplate but could be considered metadata. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The eligibility and location might be considered not boilerplate but maybe we should keep as a short paragraph? It's substantive info about work authorization and location. Could be placed under a short

    without heading, or maybe under a section like "Location & Eligibility" but not in allowed headings. Since we only allowed headings list, we should not create new headings. So we can include as a

    after sections. We also