Research Engineer Jobs in San Francisco, USA

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

79 Open roles
23 Companies hiring
305K Average salary

What do Research engineers in San Francisco work on?

The titles and summaries suggest work that sits at the intersection of rigorous engineering and active research. Several roles at Anthropic centre on building and refining reinforcement learning environments for specific domains: chip design asks for deep ASIC or FPGA knowledge, while code RL focuses on training frontier models to write and debug real software end-to-end. Computer Use combines computer vision with agentic capability work, and Domain Scaling involves creating RL environments across finance, healthcare, and legal verticals. Life Sciences pairs ML engineering with scientific rigour around biology. Across almost all sample summaries, designing evaluation frameworks is a core responsibility, reflected in the broader skills counts. Model Evaluations makes this explicit, requiring candidates to build distributed infrastructure that runs evaluations reliably at scale and own monitoring during training runs. Other titles—Interpretability, Safeguards, Cybersecurity RL, Economic Research Data Platform—point to a wide spread of application areas beyond the sample summaries provided.

Skills and experience employers ask for

The skills counts reflect mentions in posting descriptions across all postings on this page, not formal requirements. Evaluation appears most widely, followed by LLMs and reinforcement learning, with Python and PyTorch also prominent. Lower-frequency mentions—CUDA, Go, A/B testing, publications—appear in a meaningful minority. Because the counts come from a single snapshot of open roles, they indicate current emphasis rather than stable industry norms.

Evaluation 72%
LLMs 59%
Reinforcement learning 54%
Python 48%
Agents 44%
PyTorch 38%
GPUs 34%
Fine-tuning 30%
Distributed training 27%
Publications 20%
CUDA 19%
A/B testing 19%
APIs 16%
Go 13%

Research 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?

On-site is by far the predominant arrangement in these postings; only a small minority state hybrid working, and fully remote roles are rare. The two hybrid sample summaries from Anthropic specify at least 25 per cent office time in San Francisco, so even hybrid here implies regular physical presence. No postings in the set have an unknown work mode, which is unusually complete, but candidates should still confirm exact attendance expectations directly with each employer, as stated policies can differ from day-to-day practice.

Make your application specific to the work

  1. Read the full posting carefully Research engineer roles here span very different domains—chip design, life sciences, cybersecurity—so the detailed requirements in each posting matter more than the shared job title. Check that your background matches the specific domain before applying.
  2. Prepare domain-specific evidence The sample summaries ask for demonstrated experience rather than general familiarity: past work training or fine-tuning large models, RL environment design, or evaluation framework development. Gather concrete examples from previous projects or publications before writing your application.
  3. Check pay transparency early Only a subset of postings on this page include advertised salary ranges, and the ranges that exist vary widely even within the same employer. If compensation is a deciding factor, look for the pay information in the individual posting or ask the recruiter at first contact.
  4. Confirm on-site expectations Most postings list the role as on-site in San Francisco; a smaller number state hybrid with a minimum office percentage. Verify the exact arrangement with the employer before progressing, particularly if relocation or regular travel would be required.

Questions about Research Engineer jobs in San Francisco

The fact pack does not include sponsorship information for any of the postings on this page, so that is not stated here. You would need to check each individual posting or contact the employer directly.

Only a portion of the postings on this page advertise pay. Among those that do, the ranges vary considerably—from figures around 200,000 dollars at the lower end to over 500,000 dollars at the upper end for certain OpenAI and Decagon roles. These are advertised ranges from specific postings, not a reflection of the wider market.

Degree requirements are not stated in the fact pack, and the sample summaries emphasise demonstrated experience—training models, designing evaluations, building pipelines—rather than specifying a particular qualification level. Check each posting individually for any formal education criteria.

Remote options are rare in these postings. The large majority are listed as on-site, with a smaller number hybrid. The two hybrid roles with available details (from Anthropic) require at least 25 per cent in-office time in San Francisco.

Evaluation design appears in the majority of postings, followed by LLMs and reinforcement learning. Python and PyTorch are also frequently mentioned. CUDA, distributed training, and fine-tuning appear in a meaningful minority. These are mentions in posting descriptions rather than stated requirements, and the counts are based solely on the postings shown on this page.

Jobs checked 1 hour ago. · Guide reviewed 14 September 2026.