have built a platform that uses AI to transform publicly available data into real time operational insights. With a huge part of... ...their business growing, they are now looking to hire a Senior Data Engineer, who will…
Engineering & IT · San Francisco, CA
Data Engineer jobs in San Francisco, CA
Data engineers build the pipelines and warehouses that move data from source systems to the people and models that need it, keeping it fresh, correct, and queryable at scale.
551
Open roles today
$52–$131/hr
Typical pay range
$181k
Median, full-time
5
Fresh in this list
No email, no resume, no sign-up. Save any listing below and you start anonymously.
You're signed in. Saving a listing drops it straight into your pipeline.
01
Open data engineer roles
12 shown of 551 · sorted by freshness
$190.8k - $238.8k
offices in New York, Washington D.C., London and Amsterdam. Making data- driven decisions is key to Plaid's culture. To support that, we... ...data. We provide golden datasets and tooling to teams across engineering, pro…
$157.2k - $214.8k
New York, Washington D.C., London and Amsterdam. The Analytics Engineering team owns the full-stack analytics foundation for Plaid's GTM,... ...Marketing organizations. We build and maintain the core semantic layer data…
Job Title : Data Engineer (Entry Level) Job Type: Full Time - Permanent Location: San Francisco Bay Area, CA Note: Client is looking for US Citizen or Green Card Holder/Must be from big Tech company or small startup or f…
Onsite) 1. Minimum 10 years of relevant experience 2. Primary Skills: Snowflake AWS PySpark 3. Secondary Skills: BI/ Data Analytics understanding Healthcare domain knowledge Role Descriptions: Primary Skills:...
$90k - $160k
of technology and build a more sustainable, more inclusive world. Location San Francisco CA Your Role The GenAI Engineer / Data Scientist is responsible for designing, developing, deploying, and maintaining Generative AI…
**We’re Hiring: Senior Data Engineer* * We are looking for a highly experienced **Senior Data Engineer** with strong technical expertise, excellent English communication skills, and the ability to collaborate effectively…
$197k - $270.6k
in on this mission. If you are too, let's talk. The Technology, Data, and Intelligence Team Okta is the leading independent... ...The Technology, Data, and Intelligence (TDI) organization is the engine that powers Okta's…
$197k - $270.6k
in on this mission. If you are too, let's talk. The Technology, Data, and Intelligence Team Okta is the leading independent... ...The Technology, Data, and Intelligence (TDI) organization is the engine that powers Okta's…
$25 per hour
modern and aspirational banking experience by bringing rewards and benefits to the everyday debit card. We are looking for a Data Engineer to pioneer the data team at Point and be responsible for building out the data pi…
$255k - $405k
About the Team OpenAI’s Financial Engineering (FinEng) team powers how revenue flows through our products—pricing & packaging, checkout... ..., reliable, and efficient worldwide. About the Role As a Data Scientist on Fin…
$160k - $180k
high-quality curriculum is layered with robust teacher and leader data insights to drive the continuous improvement of instructional... ...work as hard as they do. We're looking for an experienced software engineer with…
02
What data engineers earn in San Francisco
Hourly first — that's how the offer arrives
| Experience | Hourly | Annual, full-time |
|---|---|---|
| Entry level | $52–$73 | $109k–$151k |
| Mid level | $73–$101 | $151k–$210k |
| Senior | $98–$131 | $203k–$273k |
Adjusted for the San Francisco market from national ranges.
03
What employers ask for
The skills these listings keep naming
SQL and data modelingPython or ScalaAirflow or similar orchestrationSpark or other batch processingWarehouses (Snowflake, BigQuery)dbtStreaming (Kafka)Data quality testingCloud infrastructure
04
Interview questions worth rehearsing
With the thing the interviewer is actually listening for
Design a pipeline that loads data from a production database into a warehouse daily.
Cover extraction strategy, incremental loads versus full refresh, idempotency, and monitoring. Saying how you would backfill after a failure shows real pipeline experience.
How do you handle late-arriving or duplicate data?
Discuss idempotent upserts, watermarks, and dedup keys. This is a daily reality of the job, so a concrete example lands well.
Batch or streaming — how do you decide?
Anchor on the actual freshness requirement and cost. Most 'real-time' asks are fine at minutes; recognizing that is the mature answer.
A stakeholder says the numbers in their dashboard are wrong. Walk me through your debugging.
Trace lineage from the dashboard back to the source, isolating which layer diverged. Showing calm, structured lineage-tracing is the point of the question.
How do you model data for analytics — star schema, wide tables, something else?
Show you know the classic patterns and modern warehouse economics, and that you choose based on query patterns and team skill, not doctrine.
How do you test data pipelines?
Talk about schema and freshness checks, row-count and distribution tests, and tools like dbt tests or Great Expectations — plus alerting when they fail.
Tell me about a pipeline that failed badly and what you changed.
Structure it like an incident review: impact, cause, fix, prevention. Emphasize the durable improvement, such as monitoring or contract enforcement.
05
Resume tips that move the needle
For data engineers specifically — generic advice costs you here
01
State data scale plainly — rows per day, terabytes managed, pipeline counts — because it is the first thing hiring managers scan for.
02
Name your orchestration, processing, and warehouse tools per role; the modern stack (Airflow, dbt, Snowflake) is a keyword screen.
03
Highlight reliability outcomes: pipeline failure rates, data freshness SLAs met, incident reductions.
04
Show cost work if you have it — warehouse spend is a live concern and optimization stories differentiate.
05
Mention who consumed your data (analysts, ML teams, executives) to show you build for users, not just movement.
06
Where this role goes
Typical progression
01
Junior Data Engineer
02
Data Engineer
03
Senior Data Engineer
04
Staff Data Engineer
05
Data Platform Lead
Ten quiet minutes a day
Applying for data engineer jobs in San Francisco?
Robbi carries this page into your first day: your role, your city, your shift preference. Then it hands you a few small things each morning and keeps the pipeline honest.
Save what looks right here, then let Robbi hand you a few small things each morning and keep the follow-ups honest.
Start with this search
No email, no resume, no sign-up.
Open your tracker
Everything you saved is already there.