Pinterest Data Engineer Interview
Pinterest Data Engineer Interview Process
5 to 6 rounds, 4 to 5 weeks. Mostly virtual.
- 01
Recruiter Screen (30 min)
Conversational call. Pinterest hires across Home Feed, Search, Ads, Trust and Safety, Creator Tools, ML Platform, Analytics Engineering. Each team has its own data character: Home Feed leans recommendation features, Ads leans attribution and reporting, Trust and Safety leans graph and behavioral signal pipelines. Mention experience with recommendation systems, ad tech, or graph data if you have it. - 02
Technical Phone Screen (60 min)
Live SQL or Python in CoderPad. SQL leans on funnel analytics (impression to click to save to outbound click) and rolling-window aggregations. Python leans on graph traversal (find related pins via shared boards) and feature engineering with PySpark. - 03
System Design Round (60 min)
Common: design the home feed recommendation feature pipeline, design the ad attribution pipeline with 28-day click window, design the trust and safety signal aggregation system. Use the 4-step framework. Cover real-time + batch dual-track for features, point-in-time correctness for training data, schema evolution as model features churn weekly. - 04
Live Coding Onsite (60 min)
Second live coding round, opposite language from phone screen. Often includes a follow-up that adds a graph traversal or feature engineering component. - 05
ML Platform Round (60 min, ML-adjacent teams only)
Feature stores, training data pipelines, online vs offline features, point-in-time correctness, A/B test instrumentation. Asked of candidates targeting Home Feed, Search, Ads, or ML Platform teams. Skipped for Analytics Engineering or Trust and Safety roles. - 06
Behavioral Round (60 min)
STAR-D format. Pinterest values pragmatic decisions in product-ambiguous contexts. Stories about cutting scope to ship, choosing the simpler model over the elegant one, and influencing PMs on metric definitions all score well. Decision postmortem heavily weighted.
Pinterest Data Engineer Compensation (2026)
Total comp from levels.fyi and verified offers. US-based.
| Level | Title | Range | Notes |
|---|---|---|---|
| IC2 | Data Engineer | $170K - $250K | 2-4 years exp. Owns individual pipelines, on-call rotation. |
| IC3 | Senior Data Engineer | $240K - $370K | Most common hiring level. Cross-team systems, architecture decisions. |
| IC4 | Staff Data Engineer | $330K - $500K | Sets technical direction for a domain. Cross-org influence. |
| IC5 | Senior Staff Data Engineer | $430K - $620K | Multi-org technical leadership. Internal promo typical. |
Pinterest Data Engineering Tech Stack
Languages
Processing
Storage
Streaming
Query Engines
Orchestration
ML Platform
Graph
15 Real Pinterest Data Engineer Interview Questions With Worked Answers
Questions reported by candidates in 2024-2026 loops, paraphrased and de-identified. Each answer covers the approach, the gotcha, and the typical follow-up.
Compute pin engagement funnel: impression to click to save to outbound click
Find boards with the highest engagement growth this week
Compute pin similarity from board co-occurrence
Attribute conversions to ad impressions within 28-day window
Detect spam at scale: pinners with abnormal behavior
Find related pins via shared-board graph traversal
def related_pins(pin_id: str, top_k: int = 50) -> list[tuple[str, int]]:
boards = pin_to_boards[pin_id]
candidates: dict[str, int] = {}
for board_id in boards:
for other_pin in board_to_pins[board_id]:
if other_pin == pin_id:
continue
candidates[other_pin] = candidates.get(other_pin, 0) + 1
# Top-k by co-occurrence count
return sorted(candidates.items(), key=lambda x: -x[1])[:top_k]Sessionize pin-engagement events with 30-min idle gap
Compute point-in-time features for training data
Implement ad-attribution with multi-touch weighting
Design the home feed recommendation feature pipeline
User events -> Kafka (engagement_events topic, key=user_id)
-> Flink (real-time features, RocksDB state, EXACTLY_ONCE)
-> Redis (online store, 30-day TTL, p99 < 10ms)
-> S3 feature log (immutable, event-time partitioned)
Spark daily batch features:
S3 events -> Spark -> S3 feature parquet
-> Iceberg table for query
-> registered in Galaxy feature catalog
Training data:
Spark as_of_join between labels (next-day clicks) and feature
log, joined by (user_id, event_ts) where feature_ts <= label_ts.
Produces leak-free training data.
Online inference:
Ranker service reads features from Redis by user_id.
On Redis miss: fall back to default vectors.
Drift monitor: daily PSI / KS-test on feature distributions.Design the ad attribution pipeline with 28-day click window
Design the trust-and-safety signal aggregation system
Design the schema for pin, board, user, topic graph
Migrate from Hive to Iceberg without breaking downstream
Tell me about a time you chose a simpler model over an elegant one
What Makes Pinterest Data Engineer Interviews Different
Graph data shapes every system
Ad attribution at scale is the platform tax
Modern lakehouse + legacy Hive coexistence
ML platform questions show up in non-ML teams
How Pinterest Connects to the Rest of Your Prep
Pinterest overlaps with Instacart Data Engineer interview process and questions on the learning-to-rank and feature-store patterns, with Twitter Data Engineer interview process and questions on graph data modeling, and with Netflix Data Engineer interview process and questions on the recommendation-pipeline architecture.
If you're targeting an ML platform role, also see the ML data engineer interview prep guide. The streaming feature work overlaps with the real-time Data Engineer interview prep guide. Drill the rounds in data pipeline system design interview prep and schema design interview walkthrough for the feature store and graph design patterns.
Data engineer interview prep FAQ
How long does Pinterest's Data Engineer interview take?+
Is Pinterest remote-friendly?+
What level should I target?+
Does Pinterest test algorithms / LeetCode?+
How important is recommendation systems knowledge?+
What languages can I use?+
Is the Iceberg migration over?+
How does the Pinterest behavioral round compare to other companies?+
Practice Recommendation Pipelines and Graph Modeling
Drill the feature store, ad attribution, and graph traversal patterns that win the Pinterest data engineer loop.
Adjacent Data Engineer Interview Prep Reading
More data engineer interview prep guides
Stripe Data Engineer process, comp, financial-precision SQL, and the collaboration round.
Uber Data Engineer process, marketplace and surge data modeling, geospatial pipelines.
Airbnb Data Engineer process, experimentation platform questions, two-sided marketplace modeling.
Databricks Data Engineer process, Spark internals, lakehouse architecture, Delta Lake questions.
Snowflake Data Engineer process, micro-partitions, query optimization, warehouse architecture.
Netflix Data Engineer process, streaming pipelines, A/B test infra, and the keeper test.