# AI Enablement Manager — Patreon

- Location: San Francisco, CA
- Posted pay: $175k–$263k/yr
- Posted: Nov 13, 2026
- Status: open (checked Nov 20, 2026)
- Apply (employer's site): https://jobs.ashbyhq.com/patreon/f4b245f6-1ae7-4b9a-8866-76b7afe19a28
- Employer record: https://visajobs.io/company/patreon.md

## Sponsorship history
- Tier: Employer history only
- With this exact title: 0

## Description
Patreon is a media and community platform where over 300,000 creators give their biggest fans access to exclusive work and experiences. We offer creators a variety of ways to engage with their fans and build a lasting business including: paid memberships, free memberships, community chats, live video, and selling to fans directly with one-time purchases.
Ultimately our goal is simple: fund the creative class. And we're leaders in that space, with:
$10 billion+ generated by creators since Patreon's inception
100 million+ free memberships for fans who may not be ready to pay just yet, and
25 million+ paid memberships on Patreon today.
We're continuing to invest heavily in building the best creator platform with the best team in the creator economy and are looking for an AI Enablement Manager to support our mission.
This role is based in New York or San Francisco and open to those who are able to be in-office 3 days per week on a hybrid work model.
About the Team
The IT team makes sure every Patreon employee has the tools they need to build and support our product. We sit alongside Workplace, People Operations, and Systems which gives us a view across every business function and the access to act on what we see. You’ll join a team that already administratively owns the AI stack, the identity and access layer, and the systems that connect them.
Our approach to AI at Patreon
At Patreon, we believe in the power of human creativity and see AI as a tool to support our teams, not replace the creators at the heart of our mission.
Patreon does NOT use creator work to train generative AI models (i.e. LLMs or image generators) that allow other people to replicate your work.
We ARE actively fighting to protect creators from AI spam, and from having their work scraped without their consent.
We are NOT blanket-prohibiting work that was made with AI tools or AI assistance. While we’re incredibly frustrated that AI companies aren’t paying creators, there are clear examples of deeply creative people using these tools in a beautiful way for true self expression, and we do not want Patreon to stifle that.
Human creativity is not going anywhere. Humans will be making and enjoying art made by other humans for a long, long time. Our strategy and vision (and business success) actually depend on that. Patreon is going all in on the belief that humans love the creativity of other humans.
Learn more about Patreon's approach to AI from our CEO, Jack Conte .
About the Role
Patreon runs on a modern AI stack (Claude, Zapier, Replit, Gemini, Databricks and more), and most of the company uses it daily. What we have not yet built is the connective tissue between the people who know their workflows best and the practices that turn those workflows into durable, governed tools.
This role owns that connection. You will work alongside teams across the company to redesign how work gets done, in two directions at once: building new workflows and tools with AI, and making existing workflows AI-enabled so that the systems people already rely on become faster and smarter. Some of that you will build yourself. Some of it will help enable non-eng teams to build. All of it you will ship with the same discipline necessary to maintain systems over time: version control, review, testing, staged rollout, monitoring and a clear ownership.
The scope is company-wide and the role is an individual contributor with real autonomy. You will set the roadmap, run intake, and be accountable for a portfolio of deliverables and the metrics behind them.
These deliverables support Patreon's push for operating leverage: a company where every function gets measurably more done as AI becomes part of how work happens, without trading away data integrity or trust. Rough time allocation is a guide, not a rule.
Partner with Engineering to enable non-Eng teams to build internal tools (about 25%)
Operate as the standing bridge between business functions and Engineering. Write problem statements, MVP definitions, data contracts and success criteria that engineers can build to support non-eng tooling.
Carry prototypes into internal production in partnership with Engineering: participate in design and code review for internal tools, and own the business side of launch and post-launch iteration
Co-own, with Engineering and Security, the standards for how AI-enabled workflows touch production data: data classification, read and write permissions, connector and agent approval, audit logging, retention, and what must never leave a governed environment
Help Engineering prioritize internal tooling work by bringing quantified business impact, clear scope and committed business owners to the table
Dissect workflows and co-build automation with their owners (about 30%)
Map high-friction workflows end to end with the people who run them, and identify where AI removes steps, where it augments judgment, and where it should stay out
Co-build with the owner using no-code and low-code platforms (Zapier, Claude, Replit, Google Workspace, Slack). The owner leaves able to run, monitor and extend what you built together
Make existing systems AI-enabled where that beats building something new: layering agents, summarization, classification or routing onto tools teams already use
Run a lightweight intake and prioritization process for requests, scored on impact, effort, data readiness and risk
Carry light product and project management for each build: scope, milestones, stakeholder updates, launch, and a named owner afterward
Maintain a shared library of reusable automations, prompts, agents and templates with clear ownership and discoverability
Raise AI literacy and develop power users (about 20%)
Design and deliver role-based enablement for low-adoption users, built around their actual work rather than generic tool training
Identify and develop at least one power user per function, with a defined path from first use to independent builder
Publish company-wide skills, prompts and work

> History, not a promise: past H-1B filings do not mean an employer will sponsor you or a given role. Data: U.S. DOL OFLC LCA disclosure (FY2024–FY2026 for role counts, certified LCAs) and the USCIS H-1B Employer Data Hub. Not legal advice. Methodology: https://visajobs.io/methodology
