Data Engineer Jobs in San Francisco, USA

Looking for a data engineer job in San Francisco? Choose from 44 open roles at 26 employers. Explore real salary data and skills breakdown across remote, hybrid and on-site roles.

44 Open roles
26 Companies hiring
266K Average salary

What do Data engineers in San Francisco work on?

The roles on this page span a wide band of responsibility. At the individual contributor end, engineers build and operate production data pipelines — ingesting data from product databases, third-party systems, and lab instruments, then transforming it into warehouse-ready models using tools such as dbt and Snowflake. Benchling's Data Engineer is a clear example, owning the full stack from ingestion through to the BI layer.

Several postings are specifically tied to AI and machine learning infrastructure. Anthropic's Software Engineer, Research Data Platform involves building pipelines and APIs that help researchers manage and query training data, while Lila Sciences asks for ETL work transforming raw scientific instrument outputs into analysis-ready datasets.

At the senior and staff levels, the emphasis shifts toward architectural decisions, cross-team adoption, and mentorship. The MaintainX Staff Data Engineer role frames the work as defining standards and driving governance across multiple squads, while Anthropic's Engineering Manager role adds people leadership over a platform serving machine learning researchers. Pinterest's Principal Engineer operates at petabyte-to-exabyte scale with Spark, Flink, and Kubernetes.

Skills and experience employers ask for

Python and SQL appear in the clear majority of these postings, making them the most consistently mentioned skills across the sample of 44 roles. Airflow follows closely, suggesting workflow orchestration is a common expectation. Spark and Snowflake appear in roughly a third to a half of postings. Agent-related work and API design appear in a notable minority. Less common mentions include Kafka, Kubernetes, Java, LLMs, and GCP. Because these are counts of mentions in descriptions rather than formal requirements, frequency reflects emphasis, not necessarily a strict gate.

Python 75%
SQL 59%
Airflow 50%
Spark 41%
Snowflake 34%
APIs 34%
Agents 30%
AWS 27%
Kafka 23%
Evaluation 18%
LLMs 16%
Kubernetes 16%
Java 16%
GCP 14%

Data Engineer roles that state a salary

The employers' own advertised ranges, for individual roles at different levels — not an average and not a market rate.

San Francisco office, hybrid or remote?

Onsite arrangements account for the majority of postings on this page, indicating that most employers expect regular in-office presence. A meaningful minority of roles list hybrid arrangements, and only two postings explicitly offer remote work. No posting was left unstated on this dimension, so the split is relatively clear. Hybrid terms are not always defined in the postings — the Pinterest Principal Engineer summary specifies one to two days per quarter on-site, which is notably lighter than a typical hybrid pattern, but most other postings do not detail which days or how frequently office attendance is expected.

Make your application specific to the work

  1. Check seniority before applying Many of these postings skew toward senior, staff, or lead levels, and several name specific years-of-experience thresholds in their summaries. Confirm the level fits your background before investing time in an application.
  2. Review the technical stack carefully Postings vary considerably in their expected tooling — some centre on Snowflake and dbt, others on Spark, Kafka, or Kubernetes. Read each job description for the specific stack rather than assuming a common baseline.
  3. Note the work-mode arrangement Most roles on this page require onsite presence in San Francisco, so confirm the arrangement stated in each posting matches your situation before applying, particularly if you need remote or hybrid flexibility.
  4. Check pay and visa details directly Only a portion of postings show advertised pay ranges, and visa sponsorship eligibility is not stated in the fact pack for any employer. Contact the employer or check the full job posting to confirm both before proceeding.

Questions about Data Engineer jobs in San Francisco

A minority of postings on this page include advertised ranges. Where stated, figures vary substantially by seniority and employer. For example, OpenAI lists a range of $235,000–$385,000 for a Data Engineer posting and $385,000–$490,000 for a Technical Lead Manager role. Perplexity lists $175,000–$330,000 for an analytics engineer level position. These are individual advertised ranges from specific postings, not a general market figure.

The majority of postings on this page specify onsite work. A smaller number are listed as hybrid, and only two explicitly offer remote arrangements. If flexible working is important to you, check each posting individually, as terms differ and are not always fully described.

Python and SQL are mentioned in the majority of postings, and Airflow appears in roughly half. Spark, Snowflake, Kafka, and AWS appear in a notable share of postings. Less commonly mentioned are Kubernetes, Java, LLMs, and GCP. These are counts of mentions across 44 postings, not universal requirements.

Most postings whose seniority can be determined are at senior or lead level. A large share of postings do not state a seniority level explicitly. The sample summaries reference experience thresholds such as three or more years, nine or more years, and twelve or more years, which suggests the overall set skews experienced. Entry-level roles may exist among unstated-seniority postings, but this cannot be confirmed from the available data.

Employers with the most postings on this page include OpenAI, Anthropic, Harvey, Perplexity, CoreWeave, Lila Sciences, Pinterest, and Brex. Other employers are present in the full set but are not named in the summary data provided here. Check the individual job listings for the complete employer list.

Jobs checked 4 hours ago. · Guide reviewed 9 September 2026.