The first part of our interview process for engineers is a virtual coding screen. Our goal is to simulate your normal working environment as much as possible so that we can see how you work day to day.

We'll ask you to solve a coding problem in the language and editor of your choice, including running code, in 40 minutes. The interview will be over screenshare, so please make sure you have a working programming environment on the machine you'll be using.

We've found that candidates do best when they work in a language that (1) they know well, and that (2) is fast to write in. Typically this means Python or Javascript; if your daily driver is C++ or Rust you may want to brush up on a scripting language.

Please shut off copilot if you use it and please don't use ChatGPT or other LLMs. Otherwise, feel free to use any tools you would normally have access to while coding: references, documentation, and Google are all fair game (just don't look up the answer).

We don't ask questions that require complex algorithms to solve. We're checking to see if you can quickly write and debug working code, not if you've reviewed graph theory recently.

Before the start of your interview, please set up your editor and anything else you normally use (terminal, debugger, etc.) on your machine. We'll ask you to share your screen with us while you work through the problem.

Cracking the Coding Interview and LeetCode are great resources for practice.