Thinking Machines Lab logo

Software Engineer, Privacy & Data Governance

Thinking Machines Lab

San Francisco, CAJob$300–350K/yrPosted 1w agoStill listed today

Most applications go out cold — see where you stand first. No sign-up to start.

You apply on the employer's site, with no Olive account needed.

Watch jobs like this.

Don't just apply. Show up ready.

Olive works from this exact posting.

At a glance

Compensation
$300–350K/yr
Location
San Francisco, CA
Work Authorization
Visa required • Visa sponsorship

Olive lists jobs from US employers, including remote roles you can work from the United States.

Job overview

Thinking Machines Lab seeks an engineer to build and operate systems governing data collection, storage, access, use, retention, and deletion. The role applies privacy controls across AI/ML training, evaluation, and products, including customer-data isolation. The engineer will translate legal and policy obligations into code, conduct privacy reviews and threat models, and collaborate with researchers and product engineers to make defensible privacy decisions.

Skills & qualifications

RequiredNice to have

Skills

Artificial IntelligenceMachine LearningAuditClassification AlgorithmsData LineageResearchML InfrastructurePrivacyData EngineeringMulti Tenant SystemsData GovernancePrivacy EngineeringPythonAI/ML Data PipelinesPragmatic Control SelectionLegal-to-Technical RequirementsPrivacy-Enhancing TechniquesDeidentificationDifferential PrivacySecure EnclavesMetadata ToolingPolicy EnginesSecurity EngineeringAccess Control

Qualifications

Production Privacy or Governance SystemProduction Code ExperienceAI/ML Pipeline Privacy ExperienceLegal or Policy Control ExperienceAI Lab or ML Infrastructure ExperienceData Lineage or Policy Tooling ExperienceSecurity Team ExperienceEarly Privacy Function Experience

Benefits

Medical Insurance
Dental Insurance
Vision Insurance
Paid Time Off
Parental Leave
Relocation Assistance

Full job description

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.

How this job compares

Set against the 40,832 open Software Engineer jobs on Olive Jobs, counted November 5, 2026.

Pay
  • This posting$300–350K/yr
  • California median$165–246K/yr7,688 salary ranges
  • US median$135–218K/yr32,472 salary ranges

This range's midpoint, $325K, is 59% above the California median midpoint ($205K) — in the top quarter of Software Engineer salary ranges in California.

Openings
Olive Jobs lists 9,560 open Software Engineer jobs in California and 40,832 across the US. 7% of them nationwide are listed as remote or flexible.
Hiring the most in California
Experience
Software Engineer postings that state a minimum ask for 5 years of experience at the median; the middle half ask for 3 to 7 years (33,318 postings).
Education
14,022 of the 40,832 open Software Engineer jobs (34%) ask for a bachelor's degree or higher.

Counted across the open, public US postings on Olive Jobs on November 5, 2026. Pay medians are the middle values of the low ends and of the high ends of postings that list both ends of a range in the same cadence (a yearly salary or an hourly rate); a range's midpoint is halfway between its ends. Pay and experience figures resting on fewer than 20 postings are left out.

Prepare for this role

You've read the whole posting — now see how you match it.