3. Roles & Expectations
The expectations I care about most are consistency and communication. Working steadily and telling me where things stand matters much more to me than raw hours. It’s one of the most useful habits you’ll build during your training, and it keeps deadlines from piling up. Consistent work and open communication also let us iterate, which is how we get to high-quality results.
1:1s and time with me #
We meet weekly for a 1:1, and I try to book them on our shared in-person days (Wednesday and Thursday). The meeting is yours, so don’t cancel it just because progress feels slow. Some weeks we’ll take a walk and talk through early ideas, and other weeks we’ll dig into specifics. If you need more dedicated time, book it through my booking page [TBD].
What you can expect from me #
Day-to-day communication is Monday to Friday, roughly 9 to 5. If you send me a message on Zulip, I tend to respond much faster than by email. Don’t let me block you: if you need something unblocked, ping me. Don’t feel bad about it, really ping me.
I keep hard boundaries around evenings and weekends, and I don’t expect messages or replies outside office hours. I want us to treat these research positions like real jobs and be professional about our time. That’s good training for the real world whether you become a professor or go into industry. Emergencies sometimes happen, and for those we have an explicit emergency contact policy in our shared spreadsheet [TBD].
How we work together shifts over time. Your first year is really about figuring out how we work together well, so I’ll give you more concrete, scoped projects. By the final years of a PhD (and right from the start as a postdoc), I expect you to work much more independently, pursuing your own ideas and leading things.
As a newer PI, I’m still learning how to juggle everything and stay on top of all the moving parts while making sure everyone gets good mentorship, room to grow, and feedback in a way that’s useful. If something isn’t feeling smooth, tell me.
Coding critique #
I recommend everyone do at least one coding session or code critique, with me or with other people in the lab. It shows you how someone else reads your code. Even with good AI tools, writing code yourself is worth practicing because it trains how you break problems into small, approachable tasks. For why working alongside others helps, see Codemates.
By role #
PhD students. For a classic perspective on what a PhD actually is, see Matt Might’s The illustrated guide to a Ph.D. I expect at least three works that you lead. The first teaches you how to get into the field, the second builds up the difficulty, and the third should be ambitious enough to help define your direction after graduation. One natural way to make a project more ambitious is to connect it to experiments through collaborators. Leading three works across five years is a reasonable baseline, though doing more will help your career. See Career & Milestones for the year-by-year timeline.
Master’s students. An MASc is two years with a thesis. Your first year is really about scoping a clear, doable project so you can succeed at it, aiming for one work that you lead. Especially if you’re jumping somewhere else next, publishing something is a great public artifact that shows what you built. See Career & Milestones for the two-year timeline.
Undergraduates. The aim is a well-scoped project, whether a summer position or a course project. Really, the goal is to give you a sense of what research is. If a publication comes out of it and helps you apply to grad school, that’s great.
Postdocs. Publishing and leading ideas independently are expected, and you’re much more in control of your career. A big part of a postdoc is defining where you want to grow next, whether that’s academia, industry, or starting something, and making sure you get the right opportunities (like lecturing, grant writing, or mentoring). Let’s talk early about where you want to go so I know how best to support you.
Growing as a researcher #
You probably won’t know how to propose a project at the start. It’s very common not to have ideas at the beginning, since you’re still learning the process. The hope is that by the end of your PhD you’ll know how, and you’ll have tons of ideas. Chris Olah’s research taste exercises are a great way to practice: write down ideas and have a mentor rate them.
Science is open-ended discovery, which means sometimes things don’t work. Open-ended projects carry more risk, and that’s okay.
Mentoring and helping others is expected, but flexible. Some people want to mentor students and some don’t, and that’s fine. It’s always good practice, though: we’ll always be working with people, and learning how to do that well is something worth getting better at.