Senior Staff Engineer, Enterprise Data Platform

We need to output HTML fragment with sections: About the role? Actually the posting includes Company Description, Job Description (with duties), Qualifications, Additional Information (EEO etc), Compensation & Benefits Details. We must remove boilerplate EEO, legal, accommodation, etc. Also remove navigation, cookie, duplicated lines, application instructions. We must keep substantive info: Company Description, Job Description (Essential Duties and Responsibilities), Qualifications (Required and Preferred), Compensation & Benefits Details (salary range, STI, LTI, benefits list). Also maybe "Additional Information" includes accommodation request and deadline; that's boilerplate? It includes application deadline and accommodation request; we should remove application instructions and accommodation request? The instruction says remove application instructions. The accommodation request is part of application instructions, so remove. The deadline also is application instruction; remove. So Additional Information likely only contains EEO and accommodation etc, which we remove. So we may not have a section for Additional Information. We need headings: About the role? Not present. Could use "Company Description" as a section heading? The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid using other headings like Company Description, but they gave examples. Probably we should map content to those headings: Company Description could be under "About the role" or maybe we can create a section "About the company". But they said use those examples; not strict but we should follow. Likely we should include sections: About the role (company description), Responsibilities (essential duties), Requirements (qualifications), Benefits (compensation & benefits). Pay could be separate but we can combine Pay and Benefits? They said prefer few substantive sections over many thin ones. So we could have About the role, Responsibilities, Requirements, Benefits (including pay). Or we could have Pay and Benefits separate if both present. The posting includes salary range and benefits details. So we could have Pay section (salary range, STI, LTI) and Benefits section (benefits list). That's two sections. We must not repeat job title as heading. No Job ID. We must use

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

  for prose. We must preserve all substantive information; do not invent or summarize away detail. We need to extract details: Company Description paragraph: "Sandisk understands how people and businesses consume data and we relentlessly innovate to deliver solutions that enable today’s needs and tomorrow’s next big ideas. With a rich history of groundbreaking innovations in Flash and advanced memory technologies, our solutions have become the beating heart of the digital world we’re living in and that we have the power to shape. Sandisk meets people and businesses at the intersection of their aspirations and the moment, enabling them to keep moving and pushing possibility forward. We do this through the balance of our powerhouse manufacturing capabilities and our industry-leading portfolio of products that are recognized globally for innovation, performance and quality. Sandisk has two facilities recognized by the World Economic Forum as part of the Global Lighthouse Network for advanced 4IR innovations. These facilities were also recognized as Sustainability Lighthouses for breakthroughs in efficient operations. With our global reach, we ensure the global supply chain has access to the Flash memory it needs to keep our world moving forward." That's the company description. Responsibilities: Essential Duties And Responsibilities with subheadings: Architecture & Strategy, Data Engineering & Platform Delivery, Governance, Metadata, and Quality, Collaboration & Leadership. Each has bullet-like sentences. We need to turn each duty into

• items. Could group under a single
  or separate? Probably one list for responsibilities. We need to preserve all details: Let's list each bullet: Under Architecture & Strategy: - Define and continuously evolve the target data architecture across the stack—Data Governance, data engineering, data modeling and Databricks lakehouse in Azure and GCP - Translate business and technical goals into scalable and resilient platform designs. - Own and maintain architectural roadmaps, standards, and decision frameworks. - Act as the bridge between architects, Business SME/Analysts, data engineers, and analytics teams to ensure alignment and compliance with platform standards. Data Engineering & Platform Delivery: - Build and maintain Databricks Lakehouse platforms using Delta Lake, Iceberg, or equivalent technologies. - Design and implement modern ELT/ETL pipelines using tools like Spark, Python, SQL, Scala, and cloud-native components (e.g., Fivetran, Databricks, Snowflake, BigQuery). - Manage data ingestion from heterogeneous sources including ERP, CRM, IoT, and third-party APIs. - Guide hands-on development of robust, reusable, and automated data flows in Azure and GCP Governance, Metadata, and Quality: - Implement and enforce data governance frameworks including data lineage, metadata management, and access controls. - Partner with Data Stewards and Governance Analysts to catalog data domains, define entities, and ensure SOX compliance. - Drive adoption of tools like Atlan and Unity Catalog for metadata, quality, and stewardship. - Develop data models (ERDs, dimensional and 3NF) and define canonical data representations. - Define and maintain Data Products including end to end data flows, Data Lineage, Data Access and Data Catalog Collaboration & Leadership: - Review solution designs and provide architectural guidance to engineering teams. - Mentor technical staff while fostering best practices and continuous improvement. - Collaborate with DevOps to embed CI/CD, version control, and environment automation across the data lifecycle. - Continuously assess and improve platform reliability, scalability, performance, and cost-efficiency Qualifications: Required and Preferred. Required: - 9+ years of hands-on experience in data architecture, engineering, and analytics delivery. - Proven success in building modern data platforms on cloud (AWS, Azure, GCP). - Deep knowledge of data lakehouse architectures (e.g., Databricks, Fabric). - Proficiency with Python, SQL, Spark, and orchestration frameworks. - Experience with ETL/ELT tools (e.g., Informatica, Talend, Fivetran) and containerization (Docker, Kubernetes). - Strong background in data modeling (ERD, star/snowflake, canonical models). - Familiarity with REST APIs, GraphQL, and event-driven design. - Demonstrated experience integrating AI/ML and GenAI components into data platforms. Preferred: - 15+ years of experience including solution architecture roles for large-scale data initiatives. - Experience with BI/visualization tools like Power BI, Tableau, and Looker. - Understanding of Master Data Management, data profiling, cleansing, and enrichment techniques. - Exposure to DataOps and DevOps practices for CI/CD and platform automation. - Strong analytical and problem-solving skills with the ability to communicate clearly to both technical and business audiences. - Knowledge of high-tech business domains such as engineering, sales, finance, supply chain, or semiconductor operations is a strong plus. - Knowledge of SAP and SAP-BDC a plus Compensation & Benefits Details: We need to extract salary range, STI, LTI, benefits list. Paragraph: "The salary range is what we believe to be the range of possible compensation for this role at the time of this posting. We may ultimately pay more or less than the posted range and this range is only applicable for jobs to be performed in California, Colorado, New York or remote jobs that can be performed in California, Colorado and New York. This range may be modified in the future." But they didn't actually give numbers? Wait they didn't specify the range numbers. The text says "The salary range is what we believe to be the range of possible compensation..." but no actual numbers. That's placeholder? It says "The salary range is what we believe to be the range of possible compensation for this role at the time of this posting." No numbers given. According to instruction: do NOT include a section when posting has only filler/placeholder text like "not specified", "N/A", "varies", "TBD". Here they didn't give numbers, but they said "The salary range is what we believe...". That's still not giving a range; it's vague. Likely we should not create a Pay section because no actual numbers. However they also mention STI, LTI, benefits list. Those are substantive. So we could have Benefits section (including STI, LTI, benefits). Pay section maybe omitted if no numbers. But we could still have a Pay section with the description that range is not specified? That would be filler. Better to omit Pay section and just include Benefits. But the instruction: "Prefer a few substantive sections over many thin ones." So we could combine Pay and Benefits into one Benefits section, but if Pay has no numbers, we might still include the description about salary range being not specified? That's not substantive. Better to omit Pay entirely. Thus we will have sections: About the role (company description), Responsibilities, Requirements (qualifications), Benefits (including STI, LTI, benefits list). Use

  for each. Now we need to format. About the role: use

  for the company description paragraph(s). It's one paragraph but could be multiple sentences; we can keep as one

  . Responsibilities:

  Responsibilities

  then
  • each duty. Requirements:

    Requirements

    then
    • each required and preferred? Could separate Required and Preferred as subheadings? But they said use headings for sections; we could have Required and Preferred as subheadings (

      ?) but not allowed? Only

      for section headings. Could we make two sections: Required Qualifications and Preferred Qualifications? That would be two sections. But we could combine into one list with both required and preferred, but we need to differentiate? The instruction says preserve all substantive information; we can keep both required and preferred in same list but maybe add a note? Better to have two subsections: but we cannot use

      for sub-sub? Could use inside

      ? But they said use

      for section headings. Not prohibited to use other headings like

      but they gave examples. Safer to keep one Requirements section and list both required and preferred items, maybe with a note like "Required:" and "Preferred:" as inside

      . That preserves info. Thus

      • Required: ...
      etc. But that would be many
      • each containing a bold label and then the text. Could also separate required and preferred as separate
        but still under same heading. We'll do:

        Requirements

        then

        Required:

        then
        • each required item. Then

          Preferred:

          then
          • each preferred item. But they said use

            for prose. So we can have

            Required:

            then list. Similarly for Benefits: we need to include STI, LTI, benefits list. Benefits paragraph: "You will be eligible to participate in Sandisk's Short-Term Incentive (STI) Plan, which provides incentive awards based on Company and individual performance. Depending on your role and your performance, you may be eligible to participate in our annual Long-Term Incentive (LTI) program, which consists of restricted stock units (RSUs) or cash equivalents, pursuant to the terms of the LTI plan. Please note that not all roles are eligible to participate in the LTI program, and not all roles are eligible for equity under the LTI plan.RSU awards are also available to eligible new hires, subject to Sandisk's Standard Terms and Conditions for Restricted Stock Unit Awards.We offer a comprehensive package of benefits including paid vacation time; paid sick leave; medical/dental/vision insurance; life, accident and disability insurance; tax-advantaged flexible spending and health savings accounts; employee assistance program; other voluntary benefit programs such as supplemental life and AD&D, legal plan, pet insurance, critical illness, accident and hospital indemnity;