I first met Thomas at a workshop at a major ML conference. We hit it off right away and found that we agreed on a lot, including the importance of AI safety. We kept crossing paths at the workshop party and then at the after-party. By the end of the night, he had told me he would be up for collaborating if I was interested. Once I got home, I sat on the offer. He was far more senior than me, and I was clearly the one with more to gain. Frankly, I lacked the confidence to accept. Taking him up on it felt like forcing him into an obligation to supervise me. Three days later, before I had decided anything, Thomas messaged me to ask whether I had made it home okay. A project proposal was already attached. We have worked together ever since.
Read full testimonialShow excerpt
The first proposal did not stick, and neither did the next few. Thomas never treated that as wasted time. Whenever we hit a dead end, we were brainstorming again within days. From the beginning, he asked what I wanted from the collaboration and what kinds of problems I wanted to work on. Once I chose an area, he sent a shortlist that separated the papers I needed to read from the directions worth exploring. He even flagged work he had not gotten to himself but suspected would be useful. None of it came with pressure to settle on a project by the end of the meeting. He would rather spend time at the start understanding why a question matters and whether it is the right one to pursue than commit too quickly and scramble later. I had already learned the hard way, on my first workshop paper, what it costs to skip that step. What surprised me was how much energy Thomas put into teaching me that process rather than just getting us to a result.
He also picked up quickly on how I work. I like to explore a problem top down and form my own view before going bottom up to test hypotheses. Once he saw that, he stopped assigning me experiments and started bringing me directions instead. He would walk me through the evidence and ask what I thought. Then we would debate it. His instincts were usually better than mine, but he asked anyway. When I was wrong, he made sure I understood why instead of overruling me. When I got stuck, he helped me find the thread again without taking over. The project remained mine to think through, not merely mine to execute.
The project was in AI safety, asking how a recently observed failure mode arises and whether it can be reduced during training. A few months later, we had two papers accepted at a workshop at a top ML conference, with Thomas as senior author and me as co-first author.
English is not my first language, and as we wrote those papers, Thomas's advice went well beyond correcting my prose. He taught me to think of a paper as a door into the problem for someone encountering it for the first time. One figure in one of them looked clear to me because I already knew what it meant. Thomas began by telling me what worked. Then he pointed out that the figure mixed quantitative and qualitative information in a way someone deep in the field would follow, but a reader arriving through the paper would not. I rebuilt it, and it became much clearer.
He is generous with his time, too. Our weekly meetings are booked for an hour and often run past ninety minutes because we are still brainstorming. He is quick to reply, and that was true even early on, when the results I sent him were a mess. When another collaborator joined us, I saw that this was not a one-off. Thomas gave them the same attention but not the same guidance. He adapted to how each of us thought and worked. His mentorship also extends beyond the project. I can book time with him for career questions or anything else I need to think through. If I mention a paper I found interesting, he often knows one of the authors and offers an introduction. The simplest way I can put it is that he actually cares about my success. Knowing that gives me more energy to put into the work.
It was Thomas who pointed me toward research programs I would not have found on my own. He helped me polish my CV and decide which ones genuinely fit my interests. He knows that ecosystem far better than I do, and he was candid about which mentors and programs would suit me and which would not. Today, I am a research fellow at one of those programs, and I have reached the final stage of another.
Beyond the papers and the programs, the larger change is in how I do research. When we started working together, I knew how to run experiments, but I did not yet know how to scope a project with this much independence or how to make a decision like withdrawing a submission when the result no longer held. Now I do. Thomas never made those decisions for me. He taught me how to make them. Accomplishments and technical ability aside, he is a genuinely good person who cares about the people he mentors. Time and again, he has helped me in ways I would not have known to ask for. I hope to keep working with him for a long time, and I already envy his future mentees.