Back to jobs

Software Engineer, Privacy & Data Governance

San Francisco, California, United States

Actively hiring, first seen by us 10 hours ago
Pay
USD 300,000–350,000/year — pay source
Location: This role is based in San Francisco, California. Compensation: Depending on background, skills and experience, the expected annual salary range for this position is $300,000 - $350,000 USD. Visa sponsorship: We sponsor visas. While we can't guarantee success for every candidate or role, if you're the right fit, we're committed to working through the visa process together.
Read the full posting
Work setting
On-site — work setting source
Work setup in the employer’s posting: On-site
From the employer’s posting
Employment
Full-time — employment source
Employment type in the employer’s posting: FullTime
From the employer’s posting

What you’ll work on

Full posting

We're looking for an engineer to help manage how data is handled across Thinking Machines: what we collect and acquire, where it is stored, who and what systems can access it, how long we keep it, and how it's used in training, evaluation, and products.

This is a role for someone who knows privacy deeply and treats it as an engineering problem rather than a checklist.

  • Translate legal and policy requirements (GDPR, CCPA, contractual commitments) into working code: policy-as-code, CI checks, and pipeline enforcement, built and maintained by you.

  • Maintain shared libraries and guardrails that make the private path the default, and fix them when they break or fall out of date.

From the employer’s posting
We're looking for an engineer to help manage how data is handled across Thinking Machines: what we collect and acquire, where it is stored, who and what systems can access it, how long we keep it, and how it's used in training, evaluation, and products. You'll help build the systems that let us protect privacy and make definitive statements about our practices from data inventory and classification through access and purpose controls to retention, deletion, and audit. You'll also collaborate closely with researchers and product engineers to answer privacy questions that don’t have textbook answers.
This is a role for someone who knows privacy deeply and treats it as an engineering problem rather than a checklist. The questions we face are rarely settled by policy alone: what it means to honor a deletion request against a trained model; how customers' fine-tuning data on Tinker should be isolated, never commingled, and only used for the customer; when to deidentify data (and how) vs. apply differential privacy to it. We want someone who can weigh privacy against model quality, research velocity, and product usefulness, pick a defensible answer, and then build it.
Run privacy reviews and threat models on new data sources, training runs, and product features, and close them out by shipping the control, the check, or the tooling, not only a recommendation. Translate legal and policy requirements (GDPR, CCPA, contractual commitments) into working code: policy-as-code, CI checks, and pipeline enforcement, built and maintained by you. Maintain shared libraries and guardrails that make the private path the default, and fix them when they break or fall out of date.
Translate legal and policy requirements (GDPR, CCPA, contractual commitments) into working code: policy-as-code, CI checks, and pipeline enforcement, built and maintained by you. Maintain shared libraries and guardrails that make the private path the default, and fix them when they break or fall out of date. Skills and Qualifications

Before you apply

Work authorization
Sponsors visas

What you’ll bring

All qualifications

Preferred experience

  • Experience at an AI lab or with ML infrastructure: training data curation, multi-tenant fine-tuning platforms, or inference systems that handle user data.
  • Experience building data lineage, metadata, or policy-engine tooling, or large-scale deletion and retention systems.
Qualification wording
Experience at an AI lab or with ML infrastructure: training data curation, multi-tenant fine-tuning platforms, or inference systems that handle user data.
Experience building data lineage, metadata, or policy-engine tooling, or large-scale deletion and retention systems.

About thinkingmachines

The mission of Thinking Machines is to build AI that extends human will and judgment.

In the employer’s words · Read in context

Apply at thinkingmachines

Posting record

Report an error

Actively hiringFirst seen by us today, still listed, and not a repost of an earlier posting.

Status in our records
Live
First seen by us
Nov 18, 2026today
Recorded sightings
2
Last seen by us
Nov 19, 2026
Employer says posted
Oct 27, 2026

These dates show when we found the posting. Check the employer’s website to confirm it is still accepting applications.

How this job compares

Pay

Higher than most similar jobs

$300K–$350K against $127K–$190K, the middle half of what similar US postings state.

From 2,396 postings in the last year. Stated ranges, not salaries paid.

Time since we first saw it

Day 0

Early. Similar jobs usually come down between day 6 and day 56.

From 14,133 similar postings that came down. Coming down is not always a hire.

thinkingmachines is hiring

4 open jobs

Open jobs by the week we first saw them, last 12 weeks.

Hiring record

See how this role fits your experience

Add your resume and we’ll mark which of these tools you already use, and point out anything in the posting that could rule you out.

  • Python
Where the posting names them
- Built and shipped at least one production privacy or data governance system (retention/deletion pipeline, policy evaluation engine, data cataloging and/or lineage system, consent system, or similar) and owned it through to operation, not just design. - Written and operated production code in Python or a comparable language, evidenced by a system you can walk through in detail: what it does, how it fails, how you debugged it. - Direct experience with enforcing privacy or governing data in an AI/ML data pipeline (training data, fine-tuning, inference, or evaluation) and can describe a specific privacy risk you identified or mitigated in one of these systems.

Your next step

Complete your application on jobs.ashbyhq.com. The employer’s form will show what is required.

Applying through Ashby

  • No account needed. “Autofill from resume” at the top of the form fills the key fields from your file.

Already applied? Track this application

Job description

View original posting ↗

About Thinking Machines

The mission of Thinking Machines is to build AI that extends human will and judgment. We are training frontier models with Inkling, developing Tinker to let people make models their own, and crafting interfaces that broaden human-AI communication. We believe the future worth building is human, and we're hiring people who want to build it.

About the Role

We're looking for an engineer to help manage how data is handled across Thinking Machines: what we collect and acquire, where it is stored, who and what systems can access it, how long we keep it, and how it's used in training, evaluation, and products. You'll help build the systems that let us protect privacy and make definitive statements about our practices from data inventory and classification through access and purpose controls to retention, deletion, and audit. You'll also collaborate closely with researchers and product engineers to answer privacy questions that don’t have textbook answers.

This is a role for someone who knows privacy deeply and treats it as an engineering problem rather than a checklist. The questions we face are rarely settled by policy alone: what it means to honor a deletion request against a trained model; how customers' fine-tuning data on Tinker should be isolated, never commingled, and only used for the customer; when to deidentify data (and how) vs. apply differential privacy to it. We want someone who can weigh privacy against model quality, research velocity, and product usefulness, pick a defensible answer, and then build it.

What You'll Do
  • Implement and enforce privacy and data governance across internal systems day to day by building systems like data classification tagging, retention jobs, deletion pipelines, and data classifiers and integrating them across systems at Thinking Machines.

  • Build the isolation guarantees that keep customer and user data separate and protected, including the training data customers bring to Tinker and the conversations people have with our interfaces.

  • Run privacy reviews and threat models on new data sources, training runs, and product features, and close them out by shipping the control, the check, or the tooling, not only a recommendation.

  • Translate legal and policy requirements (GDPR, CCPA, contractual commitments) into working code: policy-as-code, CI checks, and pipeline enforcement, built and maintained by you.

  • Maintain shared libraries and guardrails that make the private path the default, and fix them when they break or fall out of date.

Skills and Qualifications

Minimum qualifications

  • Built and shipped at least one production privacy or data governance system (retention/deletion pipeline, policy evaluation engine, data cataloging and/or lineage system, consent system, or similar) and owned it through to operation, not just design.

  • Written and operated production code in Python or a comparable language, evidenced by a system you can walk through in detail: what it does, how it fails, how you debugged it.

  • Direct experience with enforcing privacy or governing data in an AI/ML data pipeline (training data, fine-tuning, inference, or evaluation) and can describe a specific privacy risk you identified or mitigated in one of these systems.

  • Has chosen pragmatic controls over ideal ones on real systems, and can describe what was shipped as a result.

  • Has written a technical requirement or control directly from a legal or policy obligation (GDPR, CCPA, or similar), and can name the obligation and the control.

Preferred qualifications

  • Experience at an AI lab or with ML infrastructure: training data curation, multi-tenant fine-tuning platforms, or inference systems that handle user data.

  • Has implemented a privacy-enhancing technique (deidentification, differential privacy, secure enclaves) in a real system, and can describe where it fell short.

  • Experience building data lineage, metadata, or policy-engine tooling, or large-scale deletion and retention systems.

  • Background in security engineering, or has worked directly with a security team on access control implementation.

  • Has been one of the first engineers building out a privacy function, and can point to the specific systems they personally built, not just the program they ran.

Logistics
  • Location: This role is based in San Francisco, California.

  • Compensation: Depending on background, skills and experience, the expected annual salary range for this position is $300,000 - $350,000 USD.

  • Visa sponsorship: We sponsor visas. While we can't guarantee success for every candidate or role, if you're the right fit, we're committed to working through the visa process together.

  • Benefits: Thinking Machines offers generous health, dental, and vision benefits, unlimited PTO, paid parental leave, and relocation support as needed.

Demand for Data Engineer roles

New Data Engineer postings at the employers we follow are up 14% over the last 6 weeks compared with the 6 before.

Weekly new Data Engineer postings at the same employers, from the week of August 17 to the week of November 9. The fewest in a week was 860, the most 1,353, and the latest week had 1,020.
August 17Last week

Each bar is one week of new postings. The darkest bars are the last 6 weeks.

Counted from the hiring pages we’ve followed for at least five weeks, so employers we add don’t look like growth. Updated weekly.

About the role

We file this job under Data Engineer, by the work the posting describes.

Data engineers build and run the pipelines that copy data out of apps and outside services into a warehouse or lake, and fix them when a source changes or a load fails.

Expect SQL, Python, a cloud platform, a scheduler such as Airflow, and often tools for large data such as Spark or Kafka.

An analytics engineer works one step later, turning the raw data a data engineer lands into clean tables people can query.

US government figures for database architects

Median yearly pay, May 2025
$139,500
Expected change, 2025 to 2035
9.4% more jobsagainst 3.5% for all jobs

The government has no code for data engineers, so these figures are for the closest group, database architects, which includes data integration and data warehousing specialists.

Source: US Bureau of Labor Statistics, Occupational Employment and Wage Statistics (May 2025) and Employment Projections (2025 to 2035). Occupation code 15-1243.

Source details

View original posting ↗

Source notes

Source excerpts

Selected passages from the saved posting. Check the full description for conditions and exceptions.

Pay
Location: This role is based in San Francisco, California. Compensation: Depending on background, skills and experience, the expected annual salary range for this position is $300,000 - $350,000 USD. Visa sponsorship: We sponsor visas. While we can't guarantee success for every candidate or role, if you're the right fit, we're committed to working through the visa process together.
Location & working pattern

San Francisco, California, United States

Working pattern and location restrictions need checking in the full posting.

Work authorization
- Compensation: Depending on background, skills and experience, the expected annual salary range for this position is $300,000 - $350,000 USD. - Visa sponsorship: We sponsor visas. While we can't guarantee success for every candidate or role, if you're the right fit, we're committed to working through the visa process together. - Benefits: Thinking Machines offers generous health, dental, and vision benefits, unlimited PTO, paid parental leave, and relocation support as needed.

Find answers in the posting

AI
How answers work

AI selects complete passages from this posting. Check them for conditions and exceptions.

Uses this posting and your question. No profile needed.