Our goal is to create an environment where you can showcase your strengths. We hope this guide and our Interview Homepage will eliminate any surprises and help you present your best self during your interviews. If you have any questions, please reach out to your Recruiter!
Overall Interview Process & What to Expect
👋 Initial Interview (30 min)
An interview with a member of our Talent team to get to know you. We want to learn about the highlights of your experience and what you're looking for in your next role, and to tell you about what we're working on at Notion now and in the future.
🧑💻 Technical Assessment (2-3 hours)
We will give you a take-home exercise that will consist of a language-agnostic coding exercise that uses Notion's new API.
📆 Live Technical Assessment (60 min)
A 60 minute interview with a Notion engineer where you will demo your take home exercise, walk through the code you wrote and discuss design choices. We'll modify the code together to add a small feature.
What to Expect in Coding Interviews
- You can use your preferred text editor, or IDE. We want you to use the tools you're most comfortable with.
- Please have your development environment set up ahead of time (more details on required setup for each interview is below), and be prepared to share your screen through Zoom.
- At the end of the interview, please share your code with us. You can use a private repo (preferred) or gist on Github, or share a link to Dropbox or Google Drive, or even paste into a Notion code block if appropriate. We just don't recommend emailing code because of spam filtering.
🏠 Virtual Onsite (2 hours)
- Coding interview
- In this interview, we're going to ask you to write code to solve a problem. No knowledge of specific libraries or technologies will be tested here, but come prepared to write and run code on your own computer.
- We encourage asking any clarification questions and make sure you understand the problem at the onset.
- Break down the problem and talk through your approach before starting to code.
- You're welcome to look up anything you need on Google, StackOverflow, etc, and any common libraries can all be used.
- Make sure you're communicating what you're doing or thinking to the interviewer, especially if you get stuck. Part of this interview is we want to see what it would be like to work with you.
- You're not required to write tests, but thinking about how you can assert the correctness of your code is always good.
- Think about edge cases and how to adapt your solution to cover them.
- Career History
- We want to understand your experience more in-depth, your achievements, challenges, and how you worked with others on teams.
- You may find it helpful to review how your past teams operated and how you collaborated with others, reflections on things that went well and that could have gone better, and achievements and challenges throughout your career.
💖 Final Interview(s) with C-Suite (45 min)
An interview where you'll discuss your past experience with our Head Of Engineering, Michael, and learn more about how we're thinking about growth for the product and company.
As a final step in the process, we will also conduct reference checks. All offers are contingent on a background check, which includes employment verification.
We want everyone who interviews with us to feel set up for success. Please reach out if you have questions!