Data Architect

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. No job title heading. No Job ID etc. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Also remove "What We Offer" maybe corresponds to Benefits. "Pay" maybe base salary mention. "Schedule" maybe flexible work schedule. Need to preserve all substantive info. Let's parse content: Intro: "As the Data Architect, you will design, build, and manage a scalable, secure, and highly optimized enterprise data architecture! ..." This is about the role description. Could be "About the role" section. Then "What You Will Do:" list of duties. Then "Supervisor Responsibilities: No" - maybe not needed. Then "What We Are Looking For:" list of requirements/experience. Then "Nice To Have:" list. Then "This job description is not designed to cover..." boilerplate - remove. Then "What We Offer" includes base salary may vary, eligibility for annual performance incentive may apply, Jazwares is multi-state employer, benefits package includes basic medical insurance 100% company-paid for employees and their children, employee basic life and AD&D insurance, a 401(K) retirement program with Jazwares matching up to 4% of pretax or post-tax deferrals, short and long-term disability, tuition reimbursement. Also work environment provides flexible work schedule: Monday-Thursday on-site, optional WFH on Fridays, up to 20 workdays fully remote each year, and Time Off for vacation and sick leave. Through Jazwares Cares volunteer up to 16 hours a year. Then "Reasonable Accommodations" - maybe part of Benefits? Could be separate but maybe not needed. It's legal boilerplate? Might be considered EEO? It's about accommodations; maybe keep as part of Benefits? But it's not a benefit per se. Could be omitted as boilerplate? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. Reasonable Accommodations might be legal but it's about disability accommodation; could be considered EEO? Might be removed. Safer to omit. Then "Working at Jazwares" description about pillars etc. Might be considered company overview; could be part of About the role? Might be considered boilerplate? Not exactly legal; it's cultural description. Might keep as part of About the role? But we already have About the role earlier. Could add a section "About the Company" but not in allowed headings list. Allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content to these. We have: - About the role: intro paragraph describing role. - Responsibilities: "What You Will Do:" list. - Requirements: "What We Are Looking For:" list (5+ years experience etc). Could also include "Nice To Have:" as Qualifications or Skills? Possibly Qualifications for required, Skills for nice-to-have? But we have separate headings: Requirements, Qualifications, Skills. The instructions: use headings for those if content exists. We have required experience (Requirements). Nice-to-have could be Qualifications or Skills. Let's treat "Nice To Have:" as Qualifications (or Skills). Since they are about degree, MLOps, global organization, CPG industry. Those are qualifications/skills. Could split: Qualifications: degree; Skills: MLOps, global org, CPG. But we can just put them under Qualifications. - Benefits: benefits package description. - Pay: base salary may vary based on experience etc. Also eligibility for annual performance incentive may apply. That's pay info. - Schedule: flexible work schedule description (Mon-Thu on-site, optional WFH Fridays, up to 20 remote days, time off). Also volunteer hours maybe part of benefits but could be schedule? We'll put volunteer under Benefits maybe. But schedule section: we have flexible work schedule details. We must not include filler like "commensurate with experience". The base salary may vary based on experience... that's not filler; it's actual statement. So we can include Pay section with that sentence. We must not repeat job title as heading. Already not. We must not include Job ID/requisition numbers. We must not include duplicated lines. We must remove boilerplate: "This job description is not designed to cover..." remove. Also "Reasonable Accommodations" maybe remove. Also "Working at Jazwares" maybe keep? It's not legal but it's company overview; could be considered part of About the role? Might be okay to keep as part of About the role? But we already have About the role intro; we could append that description there. However the instruction: "Prefer a few substantive sections over many thin ones." So we could merge company overview into About the role. Thus About the role section will contain: initial paragraph about role + company overview description (the three pillars etc). Ensure we preserve all substantive info. Let's extract company overview: "At Jazwares, we believe an innovative idea can come from anywhere and anyone. Through our three pillars, we foster innovation and encourage creativity in every area of our business. Passion: Our conviction and enthusiasm show in our products, relationships, and commitment to our community.Collaboration: We share one vision worldwide, constantly striving to improve and innovate together.Humility: We recognize the value in others and treat everyone with respect. Our strength lies in our people and talent. Don't miss out on this extraordinary opportunity to be part of the fastest-growing toy company in the industry. Connect with us today, and let's shape the future of play together!" Also earlier: "Come join one of the world's biggest toy-making companies and help us shape the future of play!" That's part of intro. Also later: "JAZWARES is an equal opportunity employer..." that's EEO boilerplate; remove. Also "Recruitment Safety" etc remove. Thus About the role will combine: - As the Data Architect, you will design, build, and manage a scalable, secure, and highly optimized enterprise data architecture! You will play a crucial role in shaping our data strategy, working across multiple departments to implement a robust data ecosystem that supports our business intelligence, analytics, AI, and data science initiatives. Applying your deep understanding of data warehousing, ETL/ELT processes, and cloud-based platforms, you will drive data-driven decisions and provide the foundation for reliable, high-quality data across the organization. Come join one of the world's biggest toy-making companies and help us shape the future of play! - At Jazwares, we believe an innovative idea can come from anywhere and anyone. Through our three pillars, we foster innovation and encourage creativity in every area of our business. Passion: Our conviction and enthusiasm show in our products, relationships, and commitment to our community.Collaboration: We share one vision worldwide, constantly striving to improve and innovate together.Humility: We recognize the value in others and treat everyone with respect. Our strength lies in our people and talent. Don't miss out on this extraordinary opportunity to be part of the fastest-growing toy company in the industry. Connect with us today, and let's shape the future of play together! Now Responsibilities: list from "What You Will Do:" bullet points. Let's extract each: - Design and maintain enterprise data architecture frameworks, conceptual and physical data models, and strategic data roadmaps to support business operations - Develop scalable data integration solutions and pipelines to consolidate internal and external sources while supporting cloud modernization initiatives - Establish and enforce data governance policies, metadata management practices, and compliance standards for data privacy and security - Design robust data structures that support reporting, dashboards, predictive analytics, and AI initiatives, including the development of a Universal Semantic Layer - Collaborate with Data Engineers, Analysts, and Business Intelligence teams to optimize data accessibility and support self-service analytics capabilities - Provide technical oversight, conduct enterprise architecture and code reviews, and maintain comprehensive architecture documentation and technical specifications - Perform other duties as assigned We should keep as

• . Now Requirements: from "What We Are Looking For:" list: - 5+ years of professional experience as a Data Architect, Enterprise Architect, or a highly similar role - 10+ years of experience with SQL, advanced data modeling, and optimizing/structuring queries across disparate datasets - 5+ years of experience designing and building scalable data pipelines (using tools like Databricks, Snowflake, Glue, Azure Data Factory, or dbt) - Proven experience implementing scalable data architectures in cloud environments (AWS, Azure, GCP) and expertise with cloud data warehouse solutions - 3+ years of experience deploying code using source control products like GitLab or GitHub, alongside strong DataOps and CI/CD principles - Exceptional communication skills with the ability to translate complex technical concepts for non-technical audiences and gather requirements from analytical stakeholders - Demonstrated ability to prioritize effectively, manage multiple projects simultaneously, and maintain excellent documentation in a fast-paced environment Now Qualifications/Nice To Have: - Bachelor’s or Master’s degree in Computer Science, Computer Information Systems, or a highly related field is a plus - Hands-on experience with MLOps - Prior experience working in a global organization or within the Consumer Packaged Goods (CPG) industry We could put these under Qualifications. Now Benefits: from "What We Offer" paragraph: - The base salary may vary based on experience, role tenure, performance, industry, and location. (But that's Pay, not Benefits) - Eligibility for the annual performance incentive may apply. (Pay) - Jazwares is a multi-state employer, so the salary range may not apply to other states. (Pay) - Our benefits package includes basic medical insurance that is 100% company-paid for employees and their children, employee basic life and AD&D insurance, a 401(K) retirement program with Jazwares matching up to 4% of pretax or post-tax deferrals, short and long-term disability, and tuition reimbursement. - Our work environment provides a flexible work schedule that includes a Monday through Thursday on-site, with an optional WFH on Fridays, up to 20 workdays fully remote each year, and Time Off for vacation and sick leave. - Through Jazwares Cares, you will have the opportunity to volunteer for up to 16 hours a year on community service projects. Thus Benefits section should include: medical insurance, life/AD&D, 401K matching, disability, tuition reimbursement, volunteer hours maybe? Volunteer could be benefit but also could be separate. We'll include volunteer under Benefits. Pay section: base salary may vary..., eligibility for annual performance incentive may apply., Jazwares is multi-state employer so salary range may not apply to other states. Schedule section: flexible work schedule details: Monday-Thursday on-site, optional WFH Fridays, up to 20 workdays fully remote each year, Time Off for vacation and sick leave. We should not duplicate volunteer hours; we already put volunteer in Benefits. Could also keep volunteer in Benefits and not repeat in Schedule. Now ensure we don't include filler like "not specified". All good. Now produce HTML fragment with sections in order: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay, Schedule. Only include if content exists. We'll wrap each section in

  heading then content: for lists use

  • . For prose use

    . We must not include or . Just fragment. Let's craft. About the role: combine two paragraphs into maybe two

    elements. Responsibilities:

    with each duty. Requirements:
    . Qualifications:
    . Benefits:
    with each benefit item. Pay:

    maybe multiple sentences; could be

    but it's prose. We'll use

    with sentences. Schedule:

    with schedule details. Check for any duplicated lines: ensure we