Tinfoil (YC P25) is hiring an applied AI security engineer in San Francisco

Tinfoil (YC P25) is hiring an applied AI security engineer in San Francisco

About Tinfoil

Tinfoil: https://tinfoil.sh/ is a security research lab building an AI cloud for private, verifiable computation. Our customers include DuckDuckGo, Mozilla, financial institutions, AI labs and startups. Frontier labs, Google Deepmind, Trail of Bits, Redhat and Canonical, have also used us for research.

As attacks on infrastructure grow more powerful, our goal is to bring state-of-the-art defenses to individuals and organizations as quickly as possible, without making them trade away performance or ease of use. Our mission[1] is to create a private garden for thought, where people keep control of their own agency, and we keep evolving our research[2] to stay ahead of rapidly changing threat models.

About this role

As an Applied AI Security Engineer, you’ll help companies deploy AI on Tinfoil when security or privacy is a hard requirement. Our customers include enterprises in regulated industries, AI labs and startups that need secure compute, and privacy-first product companies. You’ll partner with Sales to guide strategic customers from technical discovery through deployment. Then you’ll bring what you learn back to Product, Engineering, and Research so that what we build next reflects what customers need. The role is equal parts product engineer, security advisor, field expert, and connective tissue.

This role is based in our San Francisco office, in person at least 3 days a week.

With customers, you’ll become a trusted technical advisor. You’ll turn their threat models and privacy requirements into a working architecture, and show them how to verify Tinfoil’s guarantees themselves. You will help strategic customers understand the value of Tinfoil and paint the vision on how they can successfully integrate and deploy Tinfoil into their technology stack. When they hit problems, you’ll get hands-on: reproducing their environment, digging into the issue, and building working solutions with them.

With product, you’ll get involved early to build deep expertise on new capabilities as they develop. You’ll help test new products to understand their strengths and limitations, and build demos for public or customer-facing use. And throughout, you'll help shape our roadmap by synthesizing what you're learning across customers and products into clear signal about what’s working, what isn’t, and what matters most.

To succeed, you’ll need the technical depth to push the limits of what Tinfoil can do and a strong understanding of our product and security model. You’ll also need to explain complex capabilities clearly to many different audiences in a world where threat models keep changing.

Responsibilities:

1. Serve as the primary technical advisor to strategic customers from discovery through production deployment, working across Sales, Product, Engineering, and Research to make them successful

2. Turn each customer’s threat model and security or privacy requirements into a deployment architecture built on Tinfoil

3. Build pilots, prototypes, and eval suites that prove Tinfoil meets a customer’s performance and security bar

4. Lead architecture and security reviews with the customer’s engineering, security, and compliance teams, including showing them how to verify Tinfoil’s guarantees themselves

5. Get hands-on when customers hit new problems: reproduce their environment, find a solution, and turn it into an approach other customers can reuse

6. Create reference architectures, playbooks, and public content (blogs, talks) and talks at conferences on deploying AI with high-assurance security

7. Find patterns across customers (adoption blockers, capability gaps, compliance needs) and work with Product and Research to get them on the roadmap

8. Travel occasionally to customer sites for workshops and implementation support

You may be a good fit if you have:

1. 2+ years of experience in technical roles such as software engineer, forward deployed engineer, security engineer or technical product manager, with a desire to work closely with customers. Former technical founders are also encouraged to apply.

2. Strong programming skills in Python or TypeScript and experience building production applications.

3. A solid background in security, networking, or infrastructure, and comfort explaining threat models and security guarantees to skeptical audiences.

4. Hands-on experience building with LLMs, such as agents, workflows, or LLM-powered products, including designing evals and prototypes.

5. Strong communication skills: you can explain complex technical and security concepts clearly to founders, engineers, security and compliance teams, and executives, with a low ego and a collaborative approach.

6. A track record of going deep on technical problems and turning what you learned into materials, tools, or training that helped others succeed.

7. The ability to quickly build expertise in new domains and work through ambiguity, finding simple solutions to complex problems

8. Passion for building AI systems with privacy, verifiability, and control as core properties

Bonus:

1. Experience with applied cryptography or hardware security

2. Experience deploying software in regulated industries (finance, cybersecurity, government, biotech) or guiding customers through security reviews

3. Experience with model serving or inference infrastructure

4. Public technical writing or speaking

We encourage you to apply even if you don’t meet every single qualification!

If this sounds like a good fit, please reach out to work@tinfoil.sh or apply here: https://tinfoil.sh/join.

[1] https://tinfoil.sh/mission [2] https://tinfoil.sh/blog

Discussion 0 comments · 1 points · FrasiertheLion · 6d
Open on HN
Loading the discussion…

Domain filters

Stories from these domains are hidden from every list. Subdomains match too: blocking substack.com also hides danluu.substack.com. Type a domain, or paste a link to block its site, and press Enter.

New collection

Delete this collection?

About YAVCHN

YAVCHN is a reader for Hacker News and Lobsters, with articles and discussions in separate windows or Classic pages.

Created by Paul Parks and built with PUDL.

YAVCHN source code on GitHub

Privacy policy · Terms of use

Help

Keyboard

j / k
Move down and up the story list. The arrow keys scroll whatever has focus.
Enter
Read the marked story in the article reader.
[ / ]
Read the story above or below in the list, in the same article reader. Back returns to the story you came from.
p
Pin or unpin the marked story, which keeps it in Pinned.
n / N
Move to the next or previous top-level comment in the window in front.
c
Collapse or expand that comment.
f
Hide or show the story list.
Esc
Close a menu or this help.
Access key m
Go to the menu bar. Most browsers take it with Alt on Windows and Linux, and Safari with Control and Option.
?
Show this help.

Windows

Each story opens in a window holding its article above its discussion; drag the bar between them to share the room differently. A window can be moved by its title bar, resized from any edge, snapped to a half or a corner by dragging it there, maximised, or minimised to the bar at the foot of the page. Use Window > New reader window to open an empty reader, or Story > Open in new reader window to open another reader for the current article. Docked readers keep their articles when you select another story from the sidebar. Minimized readers can be restored and reused for their site. A window's Previous and Next buttons read up and down the list in the same window.

A link in a comment or an article to another Hacker News or Lobsters thread opens that thread in a window too. A link to a single HN comment opens the comment above its replies.

While a story's window is in front, the Story and Discussion menus in the menu bar hold its commands: pinning, Previous and Next story, sorting, collapsing every thread, jumping to the first new comment. Each window also remembers where you were in its article and discussion, so a reload, or Back to a story that Next took you past, finds your place again. Closing a window forgets it.

The whole arrangement lives in the address, so a bookmark or a shared link brings it back, and Back undoes the last change. Moving between Hacker News, Lobsters, their lists, Pinned and Find changes only the list, and leaves the windows open.

The list

The pin at the start of a row keeps the story in Pinned, and the cross at its end hides it. Pinned can be narrowed by words in the title, site or author, by source, and to the stories you haven't opened yet, and ordered by when you pinned them, by points or by comments; the filters are part of the address, so a filtered view can be bookmarked. Scroll past the end of the list to load more. Domain filters, in the View menu, hide every story from a site.

Collections are named lists of stories. Story > Add to collection files the story in front into one or more of them, and the Collections feed shows them all or one at a time; the menu that chooses collections also creates, renames, and deletes them. A note is your own text on a story. Choose Add note in a story's toolbar to write one; it saves as you type. Rows with a note carry the note mark, and the Notes feed lists every noted story and searches the text of your notes.

Browsing view

View > Windowed and View > Classic select the browsing view and save your default in this browser. Window view reuses a reader for each feed. Classic view opens stories and applets as pages. Open as a page is a one-off action that does not change your saved default. Use the Windowed selector to return an article to a window. Direct page links always open as pages.

Applets

The Applets menu in the menu bar holds three tools, each a window of its own. Replies to me takes your Hacker News user name and lists the replies to your last thirty comments and stories, checking again every three minutes while it is open, and marking what is new since you last marked them read. Look up a user opens a profile on Hacker News or Lobsters, with their submissions and recent comments, as a commenter's name in any discussion does; the bar at the top of a profile looks up someone else in the same window, and Back returns to the one before. Who is hiring? filters the posts of HN's monthly hiring threads by the words you type.

They read only what the sites publish to everyone, so none of them asks for a login, and your user name stays in this browser anonymously and is included in retained applet state when signed in.

Find

Find takes any link and lists every time it was submitted to Hacker News and Lobsters, so you can read each discussion of it.

About

YAVCHN never sees your Hacker News or Lobsters login. The discussion is fetched from each site's public API; to vote or reply, follow the link above the discussion, or the arrow beside a comment, to the source's own site. Without a YAVCHN account, your data stays in this browser. When signed in, pins, collections, notes, blocked domains, and retained reading state are stored with your account and synchronized across devices. Hidden stories and layout stay in this browser. The privacy policy has the details.

Open source: github.com/paulmooreparks/yavchn. Built with PUDL.