I am currently a software developer for Xanadu Quantum Technologies, an indie game developer, an amateur podcaster, and an astrophysicist. I try my best to share my passion for astronomy and computer science with others through outreach and volunteer work. I enjoy playing as a Dungeon Master with my friends. I grew up in Northern Alberta, but I've lived in the UK, the USA, and South Korea. And most of all, when there is not a global pandemic, I enjoy traveling around the world with my wife and daughters.
This website is part personal portfolio and part personal playground. You're welcome to explore and learn about what I do and what I'm interested in.
I frequently receive questions regarding my work at Xanadu Quantum Technologies, so I wanted to lay them out here.
As a software developer at Xanadu I work on the “tools” team supporting the architecture scientists. I build and maintain software to support the scientists in their research and collaboration with each other and other teams. Sometimes that means I help them with their HPC pipelines, or database management, or developer operations, testing, or general debugging. I mostly work in Python because most of the science code is written in Python and my support needs to interact with their code. I don’t write or review the science code, but I am sometimes tasked with performance analysis or parallelization improvements.
I build internal services for the architecture scientists to simplify their interactions with supercomputing clusters or their databases. This means that I write frontend websites and the corresponding backend applications. Sometimes the backends are in Rust or in Python. My team also provisions the necessary infrastructure for these services and clusters, so sometimes I do this using Terraform. This means working with AWS resources, role-based permissions, and networking. The focus of my team is to not only build tools that simplify the scientists' work, but also productionize the tools so that they are polished and reliable.
Fundamentally, my job is understanding what tools the scientists need in order to accomplish their work and then build and maintain those tools. When I have the time, I also design and develop improvements to those tools to make them more robust, more efficient, and more effective. It’s really a jack-of-all engineering sort of position that requires incredible breadth of knowledge, consistent specialized application, and heavy triaging of priorities (balancing urgent support and new feature requests). All the work I do is classic software engineering work. I don’t do any of the quantum software, quantum architecture, or quantum information work.
I had a reasonable amount of computer science experience as an undergraduate student, completing a minor in computer science and focusing on computational physics in my major. As a Physics PhD student, I focused on skills that I knew would transfer to industry and didn’t make it an afterthought. I learned new programming languages, built working “products”, and invested in an understanding of project development. I also spent many months as a PhD student dedicated to (distracted by?) building up specific projects that I could clearly point to as evidence of my skills and knowledge. I had the advantage of being hired before the huge influx of “high-functioning LLMs/AI agents” became widely available. This meant that it was easier for me to express that my work was hard-earned and hand-built by me. (I'm sorry that's not true anymore.) Finally, I had strong references and connections from within the company who were able to provide me with references of character. However, I performed well during the technical interview, further proving that I was a capable programmer and attentive problem solver who could both clearly communicate my ideas and effectively execute on them.
To create specific example "products" I could point to, I focused a portion of my PhD work on developing a python library from scratch, AIRBALL, and I also built a video game from scratch, Quintary, without any third party libraries (using the frontend classics HTML, CSS, and JavaScript). I wanted to prove that I understood frontend, backend, and building library APIs with strong documentation. My PhD work also focused on running large-scale physics simulations in parallel on HPC clusters (showing I understood Unix, bash, git, and many other related skills).
I wasn't a perfect candidate. I had no cloud provider experience and had never written infrastructure as code before. I had limited experience with GitHub workflows (CI) and even less experience with relational and non-relational databases. However, I understood exactly what it was like to build my own tools as a Physics PhD student and navigate technical problems related to simulation-based research. So even though my research expertise is in the dynamics of the solar system, and not quantum information, I get along well with the quantum scientists and I have a strong desire to provide them with tools to make their research easier.
If you're looking for a job at Xanadu, please visit their careers page and submit your application. Or, even if you're looking for an internship at Xanadu, I want to set expectations that it is very competitive! The main route for internships is the Xanadu Residency Program; I strongly encourage you to apply. There you can select the supervisor you think best fits your research interests. Application deadline is mid-Nov for a summer term. Xanadu may also consider Mitacs if you are successful in the internship process.
But look, I don't speak for Xanadu. I'm putting my story here partly because I get so many messages about Xanadu from strangers. I cannot offer special insight, but I hope that this helps in some way.