Software Engineer, Privacy & Data Governance
Thinking Machines Lab is hiring a Software Engineer, Privacy & Data Governance in San Francisco, United States. It pays $300k-$350k a year and Level rates it ; you can apply on Thinking Machines Lab.
Level's read on this job
- Builds AI ●●●● is how Level rates this software engineer role: the job is building AI systems.
- The listed pay starts 80% above the typical software engineer posting on Level.
- Thinking Machines Lab mentions visa sponsorship in this posting.
- Tools and skills the posting cites include fine tuning.
- Level lists 49 other open roles at Thinking Machines Lab.
AI in this role
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 RoleWe'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 DoImplement 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.
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.
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 we rate this
Software Engineer, Privacy & Data Governance at Thinking Machines Lab rates 83 out of 100 for how much of the daily work is AI. That makes it Builds AI (AI Level 4 of 4). The level is about AI in the job, not seniority.
Builds AI. The job is building AI systems.
- ●●●● Builds AI80 to 100
- ●●●○ Works on AI60 to 79
- ●●○○ Uses AI40 to 59
- ●○○○ Little AI0 to 39
Levels come from how often the tools, models and workflows of the role are named in the posting itself. Read the description and count the AI tools, models and workflows it names.
Prepare for this job
Built from this posting and from similar jobs on Level.
Skills and AI tools this role asks for
Also common in software engineer jobs at this level
Pay
- This job starts at
- $300k
- Typical software engineer job
- $167k
This posting starts 80% above the typical software engineer job. See software engineer jobs
Questions you could be asked
- Walk me through fine-tuning a model: what data did you use, and how did you check the result?
- How would you decide a model or AI system is ready to ship?
- Tell me about a time a model underperformed in production. How did you find out, and what did you change?
Adapt your resume
- List these exact terms on your resume: Fine-tuning. An applicant tracking system matches the wording, not the idea.
- Attach one line of real, concrete experience to at least one of them. A tool named with nothing behind it rarely survives a human read.
- Lead with what you built, trained or shipped. This role is judged on the AI system itself, not the tools around it.
Want an expert to read your CV for this job?
Free. Send your CV and the role you want next. We reply by email within 2 to 4 business days.
Get new software engineer jobs (Builds AI ●●●●) by email
One email a week with the new software engineer jobs (Builds AI ●●●●), each rated for how much AI is in the work. No recruiter spam, unsubscribe in one click.
Free. One email a week. Unsubscribe in one click.
Similar roles
Software Engineering roles that build AI, at other companies.
What kind of AI work fits you?
Answer 12 practical questions in about three minutes. Get a simple profile, the work it points to, and live roles to explore next.
Find my next step