Fellowship Handbook
Everything admitted Fellows need to know: how mentor matching works, what we expect, how the Fellowship is structured, and the practical details.
For admitted Fellows
Mentor Matching Process
- Explore the mentors. Browse the Iliad Mentor Matcher to get acquainted with our affiliated mentors, their research interests, and the approaches they work on.
- Tell us about any existing arrangement. Some Fellows already have an agreement with a mentor, either inside or outside our network. If both parties want Iliad to provide a platform and funding for their research, we assess whether the mentor’s expertise and proposed project align with our mission. We welcome this initiative.
- Submit your profile and motivations. After admission, Fellows seeking a match describe their background and submit personalized motivations for working with individual mentors. To promote a healthy spread, there is a cap on the number of applications each mentor receives. Investigate their work, give thought to your choices and explain the fit.
- Mentors consider the applications. Mentors select Fellows based on their background and motivations. A pairing may be agreed directly, or both parties may decide after a short introductory interview.
- Begin the research conversation. Most pairings start swiftly. Often, the first call already focuses on scientific questions, exploratory reading, and possible research directions.
- Stay open to unexpected matches. We arrange a mentor for every Fellow, although it may not be the person they first had in mind. Matching is an exchange of ideas as well as a way to find guidance. You may get the most out of the Fellowship by swimming a little farther from the shore.
What Success Looks Like
The primary goal is to establish that you are on your way to conducting independent alignment research. A publication can be a valuable outcome, but it is not a requirement. What matters is a good research trajectory.
That means developing a clear understanding of your topic, identifying worthwhile questions, making informed choices about how to investigate them, and explaining how your work could contribute to alignment. We value depth, creativity, mastery of the material, and honest recognition of assumptions and limitations.
Progress can take different forms: an original result, a clearer research direction, a useful analysis of why an approach does not work, or a well-grounded proposal for what to investigate next. Even just becoming an expert on a new useful toolkit, and bringing that to your mentor’s disposal, can earn you your stay as a researcher beyond the initial three months.
Possible next steps include an extension or a role at an organization in our wider research community. Neither is guaranteed; outcomes depend on the work, the fit, and available opportunities.
Fellowship Structure and Milestones
Ideally, all Fellows follow the Iliad Intensive before they start their research. After that, the three months of Fellowship begin in earnest.
During the first week, you should have your first working call with your mentor and a short introductory meeting with your research manager.
Over the Fellowship, you will give three short presentations in a small group of Fellows:
- Start of month two: introduce your topic, research question, and proposed direction, and explain how you intend to use your time.
- Start of month three: share interim results, what is working, and what is not.
- End of month three: present your results, what you learned, and the next steps you would take.
These presentations contribute to evaluation and create opportunities to exchange ideas and collaborate. There are journal clubs, and research retreats are slated for the near future.
Fellows who have not previously attended an Iliad Intensive are expected to attend the next Intensive at their base. It provides a broad introduction to theoretical research in technical AI alignment.
What to Expect from Your Mentor
Most mentors and Fellows meet weekly, with a typical baseline of one hour per week. You may agree on a different arrangement together, and additional communication between meetings is encouraged.
Your mentor provides guidance on research direction, candid feedback, help when you are stuck, and an introduction to how their subfield approaches problems. They will also tell you when a direction does not seem to be working.
Mentorship is something your mentor has volunteered alongside their own research. The relationship works best when you drive it: your mentor is a guide, and you are responsible for moving the project forward.
What We Expect from Fellows
Come to meetings with something to show and specific questions to discuss. Keep a written record of your work: notes, a running research document, or another format that someone else can follow.
Take ownership of the project. You should be able to explain your choices, distinguish established results from conjectures, and identify the assumptions behind your arguments.
Use the Fellowship community. Discuss your work with peers, ask questions, and look for opportunities to collaborate. We provide community chat and research discussion spaces to help Fellows exchange ideas and stay connected.
Using AI in Your Research
We encourage Fellows to use language models as part of their research. The standard is simple: you must understand what you produce and be able to defend it.
You should be able to reconstruct an argument, explain why each step holds, identify its assumptions, and describe where it would break. Check that citations exist and support the claims you make. If you use generated code, make sure it runs and understand why it works.
Work you cannot defend will be returned for further work. Volume is not the measure of progress; understanding is. If a model has produced something you have not verified, it is not yet your work.
Teaching and Community Participation
Fellows contribute to Iliad’s Intensive teaching. Over a three-month Fellowship, expect roughly one to two days of involvement, typically as a teaching assistant and as a lead.
Teaching is scheduled around research, with the exact commitment depending on the needs of each term. Explaining a topic to others is also a useful way to test your own understanding. If the load becomes difficult to manage, let us know so we can adjust it.
Funding and Practical Support
The Fellowship provides a $6,000/month travel-and-housing allowance. It covers travel, visas, housing, and living costs; these expenses are not reimbursed separately. Additional costs directly related to research, such as compute or AI subscriptions, may be supported on an ad hoc basis.
The allowance is contingent upon physical presence in London or the Bay Area. If you are away for more than 6 days, the allowance is prorated accordingly.
Workspace and weekday lunch and dinner are provided at our Fellowship bases. Specific arrangements are communicated before the Fellowship begins.
You are responsible for arranging any necessary visa and ensuring you have the right to stay at your Fellowship location. Iliad provides a Letter of Admission to support visa applications.
Testimonials

Satya Benson
Before joining Iliad, I studied Mathematics and Cognitive Science at Williams College, graduating in June 2026. By the time I applied, I knew I wanted to pursue abstractions research: understanding how agents organise what they know about the world, and whether there are underlying structures that different kinds of agents have in common.
I joined the Iliad Fellowship because it could support that direction. Very few organisations help junior researchers work on agent foundations, and many of the usual routes into AI safety focus on other approaches. For me, finding a programme where these questions were welcome was a major part of the appeal.
My research asks how agents break their knowledge of the world into modular, reusable pieces, and how much of that structure is shared across different agents and cognitive architectures. During the Fellowship, I focused on two frameworks in particular: Wentworth and Lorell’s natural latents, and Eisenstat’s condensation. These gave me concrete approaches to investigate the broader questions I was interested in.
My mentor and I developed a great working relationship, and continuing into an extension felt like a natural next step. That relationship was central to how my Fellowship developed. Looking back, I would encourage prospective Fellows to pay attention to the fit between their interests and their mentor’s, alongside the research topic itself.
I’m now continuing this work during the extension, applying condensation to a range of toy settings. The aim is to understand its shortcomings more precisely and work out how to address them. Iliad has given me a way to keep pursuing a research direction that can be difficult to find support for early in a research career.

Brianna Grado-White
Before moving into AI safety, I was a postdoctoral researcher in physics. There weren’t many jobs in my particular subfield, so I started looking at what a transition out of academia could look like. I wanted to keep doing intellectually interesting work, but I also cared about what that work would contribute to. Quant finance and projects aimed mainly at making AI more capable didn’t particularly appeal to me. My interest in safety came partly from wanting a different direction, and from concerns about whether the organisations developing AI would use it responsibly.
I had already done MATS before joining Iliad in summer 2026. In my experience, there was a strong focus at MATS on producing experimental results: “make a plot,” then keep moving. I wanted more room to step back and ask whether the assumptions behind an experiment made sense, or whether we were pursuing the right question. Iliad gave me that freedom, alongside a research direction closer to my theoretical interests.
I worked with Charles, another Fellow, with Dmitri Vaintrob as our mentor. Charles brought extensive AI knowledge, and we spent much of the first three months reading papers and exploring ideas together. It was valuable, but also frustrating. We weren’t finding original results, and we sometimes got on each other’s nerves. Looking back, I wish I’d better understood how much time building expertise in a new area could take. By the end of those three months, I had developed a much deeper understanding of the literature and the questions we wanted to pursue.
Things started coming together almost immediately after we began the extension, with promising early results in a direction connected to our earlier explorations. A talk at the Iliad conference helped us connect those interests to robustness and error correction in neural networks. We’re now investigating why networks can develop discrete structures in their internal representations, where substantial changes to an internal activation can leave the output largely unaffected. And whether understanding those structures could make networks easier to interpret.
The work is still exploratory, but we now have a direction we’re excited about. What Iliad gave me was the time to think deeply, a collaborator to work through ideas with, and a community of peers and senior researchers. Together, those helped turn a frustrating period of learning into a research project I want to keep pursuing.

Tudor Dimofte
There is a great diversity of experiences and stories in AI Safety. I came to Iliad after a long career in academia, working at the intersection of mathematics and theoretical physics (most recently as a professor at the University of Edinburgh). Much of my work in the past two decades has focused on translating between these two fields, harnessing intuition from one to produce surprising results and better understanding of the other. In recent years, I wanted to explore new research areas and was inspired by the amazing developments in AI for science. I also found the problems of interpretability and alignment to be both scientifically fascinating and incredibly important. I decided I needed to quickly learn more and try to help.
I signed up for the Iliad Intensive in April 2026, and with Iliad’s help organized an AI Safety event for our math and physics students (and faculty) in Edinburgh in May. At the same time, I got in touch with former colleagues working in AI safety, most notably at Timaeus. I was very strongly drawn to the perspective Timaeus took in its research, combining a creative application of techniques from geometry and physics with careful experimental validation, all focused on characterizing and controlling generalization in models. When offered an Iliad Fellowship, I reached out directly to Daniel Murfet at Timaeus to ask if he could serve as my mentor, and he graciously agreed.
My Fellowship research in the summer of 2026 was a combination of technical experimentation, theory development, and exploration of new ideas. I was given substantial leeway in charting my own course, which (in my case) was hugely beneficial: I could find projects that were best suited to my tastes and background. My main technical work was in determining how best to apply “patterning” methodology from SLT to steer for desired behaviors in reinforcement learning, and to prevent reward hacking. I worked on this with a small team of Timaeus researchers, as I got to know the company better. I also learned a great deal from conversations with other fellowship participants and researchers at LISA; a group of us set out to learn about physics-inspired approaches in alignment, which turned into a new Physics of Deep Learning day at the Iliad Intensive.
It became increasingly clear during this summer that I wanted to make alignment research a full-time pursuit. The science was fascinating, the community was enthusiastic and supportive, and the goals were becoming critical. It had been a long time since my research moved this quickly and could have such a large potential impact. As Timaeus transitioned to part of Resolution, I applied for a full-time position with them. I’ve gone on leave from my university job and am now working at Resolution. I’m doing research across several areas, while promoting connections with the senior academic community.
I feel incredibly fortunate to have been able to make this change. My route to the Iliad Fellowship was somewhat nonstandard, having joined with substantial senior research experience but working in a completely new area. At no point were transitions automatic, from Intensive to Fellowship, Fellowship to a full-time job. However, the experience, knowledge, and contacts I gained during the Fellowship did open up a vast array of opportunities to work in AI safety, and I feel strongly that something would have worked out no matter what. Be it leading a research group in alignment back at my university, starting my own nonprofit, or joining a growing organization like Resolution.
About the Iliad Fellowship
Dates, locations, and how to apply.
→ Explore the Fellowship