Federico Mora joined the Cheriton School of Computer Science as a tenure-track Assistant Professor in July 2026. He is also a faculty affiliate at the Vector Institute. Before joining the University of Waterloo, he was an applied scientist at Amazon Web Services.
Federico earned his PhD in Computer Science from the University of California, Berkeley in 2025, his MSc in Computer Science from the University of Toronto in 2018, and a BSc in Mathematics and Computer Science from Mount Allison University in 2016. His research focuses on automated reasoning and formal methods.
He is the recipient of a Qualcomm Innovation Fellowship, the Demetri Angelakos Memorial Achievement Award, and UC Berkeley’s Outstanding Graduate Student Peer Mentor Award. Most recently, he received the David J. Sakrison Memorial Prize, awarded annually to UC Berkeley Electrical Engineering and Computer Sciences students whose PhD dissertations are judged by a faculty committee to represent outstanding research.
What follows is a lightly edited transcript of a Q&A interview.

Tell us a bit about your research.
I work in formal methods and automated reasoning. Formal methods is largely about trying to get rigorous guarantees about systems that you’re building, be it software or hardware. I’ve mostly been working in software, an area that sometimes overlaps with research in programming languages. I’ve done a lot of work on verifying distributed systems, making sure that they’re safe, secure and work as we want them to. That’s the formal methods side of my work.
Automated reasoning comes into play when we try to achieve the goals of formal methods. To do this, we often take systems, model them in first-order logic, and then try to prove that there are no bugs using automated theorem provers. Building these automated theorem provers is the automated reasoning side of my work.
That’s broadly the space I work in. At the School of Computer Science, I’m a member of the formal methods group, but my research is such that I’d like to engage with people working on programming languages, systems, software engineering, and beyond.
What challenges in automated reasoning and formal methods for software engineering do you find most interesting to tackle?
I really enjoy the automated reasoning side of my research. These days, when people hear reasoning, they think of LLMs working through a problem step by step, or something similar. In automated reasoning, we’re looking for rigorous guarantees about large systems. That can make the problems more challenging, but also more exciting. How do you carry out logical deduction at a massive scale? Answering this question for specific problem domains turns out to be a lot of fun.
As a side effect, when working in automated reasoning, you get to learn a lot about the problem domains that you target, which is also super fun.
What do you see as your most significant contribution?
I’m quite proud of my PhD thesis. I think the body of work that my collaborators and I produced has some staying power.
We took a specific application domain — verifying distributed systems — and built an entire automated reasoning stack for it. If you want to get things like this to work at scale, you need to look at the entire stack as an integrated system and optimize it for the specific domain you’re tackling at every layer. A lot of times, people have their area of expertise and stay at one level, but my thesis work touched on every level and spanned several areas of computer science. We presented the work at a range of conferences — at NeurIPS on the machine learning side, AAAI and SAT for the artificial intelligence side, CAV on the formal methods side, and OOPSLA for the programming languages side. Each layer is quite different but, taken together, the work formed a cohesive stack. That’s what I’m most proud of, bringing these different areas together into a unified body of work.
What advice do you have for students interested in pursuing research in your field?
It’s a bit hard to offer advice to students early in their careers because they are often not even aware of formal methods as a research area. A lot of universities in North America don’t offer formal methods courses as part of their undergraduate degrees. Waterloo does offer such courses, but the university I attended as an undergraduate, for example, did not. So, the first bit of advice would be to give formal methods a chance. I’ve found that students with backgrounds in mathematics can be particularly well suited to this work. It is generally relatively easy to bring them up to speed on the formal methods, programming languages and software engineering side of things.
For people that have found themselves in this area, one thing I’ve noticed these days is a big pull to abandon rigour. We now have these seemingly magic boxes — LLMs — that can do a pretty decent job at a lot of things. It can be tempting to use them to get quick results that work relatively well. My advice to students, and a reminder to myself, is that it’s time to double down on mathematical guarantees and getting things right. Safety and security of systems matter more than ever, so don’t be drawn solely to the appeal of immediate results.
Do you see opportunities for collaborative research at the Cheriton School of Computer Science?
Yes! I’m fortunate to be joining a university with so many people working in formal methods, not just at the School of Computer Science but also in the Department of Electrical and Computer Engineering. We also have exceptional faculty working in systems, programming languages, software engineering, and more. In formal methods, we depend on having domain experts. There’s no point in doing automated theorem proving in a vacuum. I’m excited to work with these domain experts to ensure that our work addresses real problems and to learn more about other research areas.
This term I’m teaching a graduate seminar on topics at the intersection of formal methods and artificial intelligence. A lot of the students taking it are working in other areas of computer science. It’s been exciting to see how their research, from seemingly unrelated domains, connects to the content of the course in unexpected ways. The quality of the work, presentations, and discussions has really impressed me too. Hopefully this course will lead to many collaborations.
What aspect of joining Waterloo excites you?
When I was in high school, my dream was to attend Waterloo for computer science. I didn’t actually end up applying because I assumed I wouldn’t be accepted. Coming to Waterloo now as a professor has been a very positive personal journey. Maybe there’s a lesson in that, too: don’t rule yourself out.
Who has inspired you in your career?
I’ve been very lucky with the formal supervision I’ve had as a master’s and PhD student. Marsha Chechik, my master’s supervisor while I was at the University of Toronto, and Sanjit Seshia, my PhD advisor while I was at UC Berkeley, are both great researchers and supportive mentors. Beyond those two, there have been so many others who have volunteered their time and shared their expertise to help me grow as a researcher. Yi Li, who was a PhD student in Marsha’s lab when I was a master’s student, deserves a huge amount of credit for my career. Elizabeth Polgreen, who was a postdoc in Sanjit’s lab when I was a PhD student, does too.
What do you do in your spare time?
I play a lot of soccer. When I moved back to the region, I messaged old friends to see if they had a team for me, and I immediately reconnected with them. It can take a lot of effort to find the right group of people, so I’ve been lucky to slot back into a community of soccer players here.