The Autumn 2026 program will run for 10 weeks in Berkeley, CA and London, UK from September 28th to December 4th. Fellows will receive mentorship from world-class researchers and at organizations like Anthropic, Google DeepMind, OpenAI, Redwood Research, and ARC, with the option to apply for a 6–12 month funded extension beyond the main program. For the first time, we are running Founding & Field-Building and Biosecurity tracks.
Applications are now closed.

Key dates for the application and admissions timeline
Applications typically open several months before the program begins. Applicants complete a multi-stage admissions process, beginning with a general application. Depending on the tracks, streams, and mentors they apply to, applicants may also complete additional evaluations such as interviews, work tests, coding assessments, or writing samples before final admissions decisions are made.

The main program is a 10 to 12 week full-time research fellowship. Fellows work closely with one or more mentors on independent research projects while participating in workshops, talks, office hours, and the broader MATS community. Research directions are developed collaboratively with mentors, with increasing independence throughout the program.
The extension phase typically begins approximately two weeks after the main program concludes. Fellows who demonstrate strong research potential during the main program may apply for a funded 6 to 12 month extension. Extension fellows continue developing independent research with ongoing mentorship and support, typically working from MATS offices or other approved research locations. In recent cohorts, roughly 80% of fellows who applied to the extension phase were accepted.
MATS aims to accelerate researchers who will:
MATS alumni have gone on to publish safety research, join alignment organizations, including Anthropic and MIRI, and found an alignment research lab. You can read more about MATS alumni here.
In stage one, applicants apply to one or more tracks (broad research areas): Empirical, Theory, Strategy & Forecasting, Policy & Governance, System Security, Biosecurity, and Founding & Field-Building. In stage two, advancing applicants choose specific streams within those tracks, each led by one or more mentors with their own research agenda. You can view this list as a grid here.
Essential:
Preferred:
Optional extras:
I will discuss a few projects with each fellow, and give time for fellows to work on each problem to get a sense of which ones they would like to move forward with. I would expect fellows to be working almost entirely on a single problem by the third week.
This stream will focus on monitoring, stress-testing safety methods, and evals, with a focus on risks from scheming AIs. Examples include (black-box) AI control techniques, white-box monitors (probes etc.), chain-of-thought monitoring/faithfulness, building evaluation environments, and stress-testing mitigations.
This varies a bit by mentor, but generally we expect fellows to autonomously drive their project forward (alongside their teammate(s)) and meet with their mentor once a week.
Fellows are responsible for:
Mentors are responsible for:
In addition to weekly meetings, you may set up ad hoc meetings with your mentor, reach them on Slack, or send them proposals / paper drafts for review. All meetings will be at times compatible with the BST / CEST timezones.
We're looking for fellows who want to dedicate their careers to making transformative AI go well, and who have strong technical skills. You don't need to be exceptional at every technical skill below, but you should have basic competence across the list and be excellent (or improving fast) in some of them.
Mission orientation
Technical skills
Working style
Close to program start, we will share a list of proposed projects, each tied to a primary mentor (some projects may also have a secondary mentor). You will then have some time to think, look up relevant literature, ask mentors questions and talk to other fellows. Then we will send out a form for you to indicate your top N projects, ranked, as well as any teammate or mentor preferences. We will then optimise fellow allocation into teams and projects to maximally satisfy everyone’s preferences.
Advance global DNA synthesis through projects on customer screening, mapping synthesis companies, benchtop integration, and sequence of concern annotation.
Each fellow will have a weekly 1:1 with their mentor for high-level project guidance (though some weeks may be missed due to travel constraints). Fellows will be invited to join our Slack instance for async communication with their mentors and the rest of the IBBIS team. Mentors are in different timezones (California, Argentina) and IBBIS is a primarily remote organization that typically offers minimal supervision.
The skills needed for the fellows will vary by project. Here are a few desired skills for each:
Robust, automated customer screening:
Global DNA Synthesis map:
Improving benchtop device security:
Improving SOC annotations:
Fellows will select one of the four project areas before starting with IBBIS, then work with their mentor to develop a specific project plan and deliverables by the end of Week 2.
This stream focuses on physical access controls for biotech governance: live pathogen repositories, CROs, cloud labs, cell-free expression systems, plasmid vendors, or secondhand lab equipment.
On high-conviction areas, you'll tackle specific open research questions and assess interventions; on exploratory areas, you'll conduct deep dives to determine whether they're worth pursuing. Your findings will directly shape Sentinel's grantmaking strategy and provide strategic guidance to the broader biosecurity community.
I'll hold a one-hour weekly check-in by default, with higher frequency during onboarding. I'm available via Slack with quick turnarounds on async messages, and you can schedule ad-hoc calls as needed.
If I bring on multiple fellows or external contractors, I'll add a weekly all-hands to make sure everyone has situational awareness.
Essential:
Preferred:
While fellows will have some flexibility in selecting the chokepoint they focus on (based on their background and interests), we've designed specific projects and open research questions for each chokepoint to shape their contributions.
Implementing SL4/5 and searching for differentially defense-favored security tools.
I love asynchronous collaboration and I'm happy to provide frequent small directional feedback, or do thorough reviews of your work with a bit more lead time. A typical week should look like either trying out a new angle on a problem, or making meaningful progress towards productionizing an existing approach.
Essential:
Preferred:
Mentor(s) will talk through project ideas with scholar, or scholar will pick from a list of projects.
We are excited to supervise projects:
Essential knowledge:
Essential experience:
Desired experience:
Bonus:
Lee's stream will focus primarily on improving mechanistic interpretability methods for reverse-engineering neural networks.
Mentorship looks like a 1 h weekly meeting by default with approximately daily slack messages in between. Usually these meetings are just for updates about how the project is going, where I’ll provide some input and steering if necessary and desired. If there are urgent bottlenecks I’m more than happy to meet in between the weekly interval or respond on slack in (almost always) less than 24h. We'll often run daily standup meetings if timezones permit, but these are optional.
As an indicative guide (this is not a score sheet), in no particular order, I evaluate candidates according to:
In the past cohort I chose a diversity of candidates with varying strengths and I think this worked quite well. Some mentees were outstanding in particular dimensions, others were great all rounders.
In general I'd like projects in my stream to at least be conceptually informed by parameter decomposition, manifolds, and minimum description length framings of interpretability, if not build on them directly.
Scholars and I will discuss projects and come to a consensus on what feels like a good direction. I will not tell scholars to work on a particular direction, since, in my experience, intrinsic motivation to work on a particular direction is important for producing good research.
The SL5 Task Force will build out a prototype SL5 datacenter this year together with frontier AI labs. This will be a massive research and engineering project with many avenues for spinning out new organizations and research programs. This project is urgent due to this technology being needed in the next 1 to 2 years.
We will meet at least 1h a week synchronously and communicate daily via standard-ups on slack. I typically respond within a few hours for additional feedback and within 1-3 days for indepth code or other review. Scholars can also schedule adhoc calls with me or my co-mentor Luis if they're stuck.
You may have the option to join company meetings and work from our offices 1+ days a week to collaborate with SL5 engineering staff.
This stream is best for strong technical IC's looking to move into research lead / tech lead / org lead positions in the future.
Essential:
Preferred:
Not a good fit:
A track is a broad research area within MATS. Empirical, Theory, Strategy & Forecasting, Policy & Governance, Systems Security, Founder & Field-Building, and Biosecurity are our current tracks. Each track contains multiple streams. In Stage 1, you apply to tracks.
Streams are organized around a research agenda, led by one or more mentors who guide fellows through related projects. In Stage 2, applicants apply to streams within tracks based on research that interests them.
You may apply to as many tracks as you wish at Stage 1. At Stage 2, depending on which tracks you progress in, you may then apply to as many streams as you wish within those tracks; there is no cap. The process is comparable to applying to PhD supervisors.
We want to be flexible for applicants who have urgent prior commitments. Based on individual circumstances, we may be willing to alter the time commitment of the program and allow fellows to leave early or arrive late. Please inform us of your availability in the application process.
Applicants who will be 18 years or older before the program start date are eligible to apply. Both US and non-US citizens are eligible to apply. All backgrounds and levels of experience are welcome and prior AI safety experience is not required.
Yes. The 12-week program requires fellows to commit 40 hours per week to their MATS research. For exceptionally strong candidates with significant concurrent responsibilities, the time commitment can be reduced to 20 hours per week on a case-by-case review. However, the program maintains an expectation of sustained, high-level engagement, including regular participation in core activities and most organized events. Candidates that require a J1 visa to come to the US are unable to participate part time; they can only work part time if they participate remotely or from the UK.
Yes, upon submitting you will receive a link that lets you edit your response. Please note that you will not be able to edit your response once the application period ends.
LLMs may not be used to write any part of your application unless specific work tests or forms explicitly permit it. MATS monitors for LLM use, and applicants found to have used LLMs may be disqualified.
Depending on the evaluations of the tracks and streams you apply to in Stages 1 and 2, we will contact your references. We will send them a form with our own set of questions, so they will not have to prepare a reference letter.
Although MATS sometimes supports UC Berkeley-based mentors, MATS is an independent program and is not formally part of UC Berkeley. As such, MATS will not be providing student cards to our scholars.
The main program, or Research Phase, takes place in person in Berkeley, CA and London, UK. Historically, most fellows participate from Berkeley. London is typically chosen by fellows who want to co-locate with their mentor or who have a preference to work from the UK instead of US.Will this program be remote or in-person?
The main program, or the Research Phase takes place in Berkeley, CA and London, UK, with the majority of fellows participating from Berkeley. We strongly encourage in-person participation when possible, as a core part of the program experience comes from day-to-day interactions with your cohort and others in the broader AI safety ecosystem.
Decisions about remote participation are made on a case-by-case basis and depend primarily on mentor preferences, many of whom are open to the possibility, especially if you have family or other obligations that make in-person participation difficult. We strongly encourage in-person participation when possible, as a core part of the program experience comes from day-to-day interactions with your cohort and others in the broader AI safety ecosystem.
If you have difficulties in securing a visa to participate from Berkeley, we are likely to be able to support participation from our London office.The 6–12 month extension gives fellows the option to participate from Berkeley, London, or remotely.
MATS is a scientific and educational seminar and independent research program, and provides J1 visas for non-American participants. Participants can also opt to participate from our London office; however, please note that visa support is not available for that option.
During the main program, fellows should expect to meet with their mentor for at least one hour per week, with more frequent communication via Slack. The extent of mentor support will vary depending on the project and the mentor.
Fellows will also receive support from MATS’ Research Management team, who work with mentors by tracking scholar research progress, unblocking scholar research, and assisting with grant applications and deadlines.
Fellows develop as researchers by working with an experienced research mentor, interacting with other fellows, and receiving support from our Research Management team. Research managers meet weekly with most fellows and mentors and help with research strategy, research unblocking, and project coordination.
Other forms of training include workshops on different parts of the research process and seminars on a variety of AI technical safety and governance research.
Throughout the program, each fellow will work on an independent research project with input and guidance from your mentor(s). Depending on which stream you participate in, you may collaborate with other fellows in your stream.
Traditionally, fellows submit a Research Plan midway through the program and present their research at the Fellow Symposium at the end of the program.
We welcome feedback. For feedback for the whole team (visible by all MATS staff), please use this form. For feedback that will only be visible to the Co-Executive Directors, Ryan and Christian, please submit here.
You can contact the MATS Board of Directors using this linked form (responses are only viewable by the Board). Please only use this if you feel your question or concern requires board-level attention.