Staff/Senior Data Engineer

We need to produce HTML fragment with sections: h3 headings for sections present. Must not repeat job title. Must not include Job ID etc. Must include only sections with real content. Must not include filler like "commensurate with experience". Must not include Pay/Schedule/Benefits unless stated. The posting mentions base salary based on market location, may vary, total compensation may include equity, benefits. That's some compensation info but not explicit numbers. The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state base salary offered is based on market location, may vary, total compensation may include equity, benefits. That's some mention of compensation and benefits. Should we include a Pay section? It says base salary offered is based on market location, may vary further depending on individualized factors... That's not a specific number but it's still stating something about pay. The rule: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state something about pay (base salary offered is based on market location...). So we could include a Pay section with that info. Benefits: mentions "full range of medical, financial, and/or other benefits". That's a statement about benefits. So we could include Benefits section. Schedule: mentions hybrid — Burlingame Office 2-3x/week Required. That's schedule info. So we could include Schedule section. However we must avoid filler like "not specified". The schedule is specified: hybrid, 2-3x/week required. So we can include Schedule section. We need to include sections: About the role? There's a Position Overview paragraph. Could be About the role. Responsibilities: Key Responsibilities with bullet points. Qualifications: Technical Qualifications, Experience & Abilities, Soft Skills. Could combine into Requirements or Qualifications. Use headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we should only include sections that have real content. We have content for About the role (Position Overview). Responsibilities (Key Responsibilities). Qualifications (Technical Qualifications, Experience & Abilities, Soft Skills). Skills maybe part of Qualifications. Benefits (mentioned). Pay (mentioned). Schedule (hybrid). We could also include a section for "Company Overview" but not required. We must not repeat job title as heading. Use

for each section heading. We must use

• for any list of duties/requirements/benefits. So responsibilities list should be
  • . Qualifications list maybe also
    • . Benefits list maybe
      • . Skills maybe also list. We must use

        for prose. We must preserve all substantive information; do not invent or summarize away detail. So we need to keep details like specific tools: Postgres, Google Cloud Storage, Jira, web analytics platforms, BigQuery, dbt, Terraform, Apache Beam, Airflow, GCP, etc. Also mention GDPR, PII, SOC2. Must keep all. We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. The posting includes some lines about AI tools in hiring process, contact us, etc. Those are likely boilerplate/legal; we should remove them. Also lines about "Simbe Values: R. E. T. A. I. L." maybe could be kept? It's substantive about culture. Might be considered part of About the role or separate section? Could be included as part of About the role or a separate "Culture" section but we don't have a heading for culture; we could include under About the role. But we must not invent sections. Could add a section "Culture" if we have content. But we only have headings list predetermined; we could add other headings if needed? The instruction says use

        for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not exclusive. It says "use

        for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can use those or similar. Probably safest to stick to those. We need to include all substantive info. Let's extract: Location: San Francisco Bay Area (Hybrid — Burlingame Office 2-3x/week Required) Must currently reside locally; this is not a remote-eligible role. Company description: Simbe Robotics is a leading retail robotics company providing in-store intelligence solutions that help retailers optimize operations, improve shelf execution, and deliver valuable data insights. Our autonomous robots and multi-modal data collection systems are transforming how retailers manage inventory and make data-driven decisions. Position Overview: The Data Engineer in will own the design, implementation, and scaling of our analytics infrastructure to form the foundation of a cohesive analytics ecosystem. This role also empowers analytics engineers and data scientists to follow DataOps best practices to independently create metrics. Additionally, the Data Engineer will interface with the application database team to synergistically improve the overall cloud ecosystem, enabling scalable ways to share large volumes of data with clients. The ideal candidate will have demonstrable experience implementing data warehouses, a strong foundation in SQL and Python, and a mindset for cloud systems design. Leveling (Senior or Staff) will be determined through the interview process based on your background and technical depth. Key Responsibilities: - Data Warehousing: Ingest data from Postgres, Google Cloud Storage, Jira, web analytics platforms, and other sources into BigQuery. Use Data Build Tool (dbt) to transform raw data into user friendly “data-marts” for use by AI and BI tools. - External Data Exchange: Guide the organization on how data is ingested from and delivered to clients. Establish the infrastructure for scalable and traceable inbound feeds (product catalogs, planograms) and large outbound delivery (reporting extracts, cloud-native data sharing) - Optimizing and Monitoring Cloud Costs: Monitor and implement controls to ensure data warehousing costs are predictable and within reasonable levels. Unlock synergies between the application database and data warehouse to deliver timely insights and reduce overall cloud costs. - Data Quality & Governance: Use dbt to establish a robust data testing framework that ensures data remains accurate and trustworthy, while also producing a comprehensive suite of metric definitions and documentation accessible to anyone in the organization. Champion DataOps best practices across teams to cultivate a consistent, high-quality approach to data management and analytics. - Security & Compliance: Help ensure account permissions remain appropriate and enforced across the data consumption layer. Implement controls to ensure the data warehouse maintains compliance with GDPR, PII laws, SOC 2, and other regulations Qualifications: Technical Qualifications: - Bachelor's or master's degree in Computer Science or related field highly recommended, not required - 5+ years of experience with SQL, BigQuery, Terraform, Apache Beam, Airflow, and GCP - Hands-on expertise with dbt and event-driven analytics highly desirable Experience & Abilities: - Proven experience implementing and owning data warehouses end-to-end - Track record of data modeling for analytical use cases - Background empowering peers through DataOps best practices - Strong emphasis on data security and governance - Deep understanding of the strengths and weaknesses of transactional vs. analytical databases Soft Skills: - Excellent communication skills; able to convey complex technical concepts across cross-functional teams - Autonomous and independent, with strong ownership and accountability - Able to evangelize and champion best practices, ensuring alignment and consistent adoption across the org Company culture/values: At Simbe, you will be at the forefront of retail innovation, working with cutting-edge AI and robotics technologies to transform retail operations. Our culture is dynamic, inclusive, and driven by a passion for improving the way retailers operate and serve their customers. Join us to be a part of a team that is not only reshaping the future of retail but also offering immense value to our clients worldwide. Simbe Values: R. E. T. A. I. L. Result Driven - We are customer-centric and results-driven. We strive to create immense value for our team, partners, customers, and investors. Empathetic - We are sensitive and mindful. We support each other in challenging times, both professionally and personally. Transparent - We highly value open communication internally, and with our partners and customers. We are receptive to feedback. Agile - We are agile and always eager to learn. We quickly adapt to changes and customer needs. Innovative - We are bold and innovative, with an intense focus on product design and user experience. Leaders - We strive for excellence. We are accountable, the best at what we do, and leaders in our field. Compensation: The base salary offered is based on market location, and may vary further depending on individualized factors for job candidates, such as job-related knowledge, skills, experience, and other objective business considerations. Subject to those same considerations, the total compensation package for this position may also include other elements, including equity compensation, in addition to a full range of medical, financial, and/or other benefits. Simbe's approach emphasizes total rewards - base pay, equity, incentives, and benefits - rather than viewing compensation as cash alone. We believe the full package, including ownership through equity and well-being support, is what drives engagement, retention, and alignment with our mission. AI hiring process note: We may use artificial intelligence (AI) tools to support parts of the hiring process... This is boilerplate/legal; should be removed. Contact us line: If you would like more information about how your data is processed, please contact us. Also boilerplate. We should remove those. Now construct HTML. We'll have sections:

        About the role

        with paragraphs: company description + position overview + maybe culture/values? Could include culture/values as part of About the role.

        Responsibilities

        with
        • each responsibility.

          Requirements

          maybe combine Technical Qualifications, Experience & Abilities, Soft Skills into Requirements. Or we could have Qualifications and Skills separate. The instruction list includes Qualifications, Skills. We could do Qualifications for technical qualifications and experience, Skills for soft skills. But we have both technical and soft. Let's follow: Qualifications (technical + experience) and Skills (soft). Or we could have Requirements for experience & abilities, Qualifications for technical, Skills for soft. But we need to avoid thin sections. Let's decide: - Qualifications: Technical Qualifications (degree, years experience, expertise) - Skills: Soft Skills (communication, autonomy, evangelize) - Requirements: Experience & Abilities (proven experience, track record, background, emphasis, deep understanding) But that's three sections. Could combine Experience & Abilities into Qualifications. Let's do:

          Qualifications

          containing Technical Qualifications and Experience & Abilities as
          • .

            Skills

            containing Soft Skills as
            • . That seems fine. Then Benefits:

              Benefits

              with
              • items: full range of medical, financial, and/or other benefits, equity compensation, total rewards approach. Pay:

                Pay

                with

                base salary based on market location, may vary depending on factors, total compensation may include equity, etc. Schedule:

                Schedule

                with

                Hybrid — Burlingame Office 2-3x/week required; must reside locally; not remote-eligible. We also need to include location maybe in Schedule. Now ensure we preserve all details: mention specific tools, dbt, BigQuery, Postgres, Google Cloud Storage, Jira, web analytics platforms, Terraform, Apache Beam, Airflow, GCP, GDPR, PII, SOC2, etc. Also mention Leveling (Senior or Staff) will be determined through interview process based on background and technical depth. That's substantive; we should include it somewhere, maybe in About the role or Qualifications. Let's add a sentence in About the role after position overview. Also mention "The ideal candidate will have demonstrable experience implementing data warehouses, a