Skip to main content

Data Engineer, Product

Posted yesterday

notion labsMillbrae (CA)

SENIORITY

Lead

Apply (opens in a new tab)

About the role

Overview: In this Data Engineer role, you will design and operate data pipelines and datasets that become the company’s single source of truth. You will partner with product, marketing, finance, and other teams to enable scalable analytics and decision-making across Notion’s org. You’ll build ETL processes, implement automated workflows, and empower self-serve data exploration using AI-enabled tools. This is a hands-on role at a fast-growing, product-focused company with a strong emphasis on data-driven impact and cross-functional collaboration. Compensation / Benefits highly competitive cash compensation equity benefits onsite presence with Anchor Days in San Francisco
Responsibilities: Define ETL processes and infrastructure to make data readily available across the company Build core datasets as single sources of truth for product and business teams Partner with data scientists and stakeholders to design, build, and monitor scalable pipelines Implement automated workflows to reduce operational costs, define SLAs, and democratize data via dashboards and AI-enabled exploration
Key requirements: 5+ years of experience as a data engineer building core datasets and supporting business functions Strong understanding of scalable cloud data solutions (AWS, GCP, Azure) across multiple data stores (Snowflake, Redshift, Hive, SQL/NoSQL) and methodologies (dimensional modeling) SQL expert with high-performance query optimization Proficiency in object-oriented programming (Python, Java, Scala) Experience using AI/agent-based tools to accelerate data development and define guardrails for production-scale data work Self-starter with strong stakeholder communication Ability to gather high-impact needs and translate into technical solutions Clear communication about deliverables, timelines, and tradeoffs AWS, GCP, Azure cloud data solutions Snowflake, Redshift, Hive SQL with aggregation, window functions, UDFs, self-joins

Before you apply

Applying takes about a minute. These four things decide how fast it moves after that.

Your profile is current

It's what we read first. Occupations, seniority and locations matter more than a long history.

Two examples you can talk through

Not a portfolio — just two pieces of work where you can explain the decisions and what you'd change.

A number in mind

What you're on now and what would make you move. We negotiate better when we know both.

Your notice period

Employers plan around it, and it's the question that stalls offers most often.

Once you apply, someone reads it and calls you before anything reaches the employer — usually within two working days.

More like this