Interview Prep:
- By default, Notion uses CodeSignal as our coding interview tool (IDE). You should receive a CodeSignal link in your email confirmation. No further preparation is needed.
- If you are NOT comfortable this pre-built environment, you can use your preferred text editor, or IDE. We want you to use the tools you're most comfortable with.
<aside>
💡 Please let your recruiting coordinator know if you are going to be using your own framework
</aside>
What to Expect in Coding Interviews
- Agenda:
- Intros (5 min)
- Problem solving (45 min)
- You’ll pair with a Notion engineer and build a solution to a real world problem. You should expect to run your code and test it in this timeframe.
- Q+A (5-10 min)
General Tips for Coding and Design Interviews
- 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 or designing details.
- You're welcome to look up anything you need on Google, StackOverflow, etc, and any common libraries can be used. We just ask to avoid using any code generating LLM tools.
- 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.
- Note: While we are big fans of AI and the potential it unlocks, we kindly ask you refrain from using tools like ChatGPT, Gemini, Claude, or agentic coding tools or similar to generate code during the interview as we care deeply about ensuring a consistent and fair experience for all. AI Overview answers from Google are fine to use when looking up questions or documentation. Thank you!