What does the interview process look like?

The process typically includes an online assessment, one or two video interviews, and a final round of in-person interviews. Our interviews are designed to require no preparation. We’re most interested in evaluating how quickly you learn and how you approach solving interesting problems – not in testing any prior knowledge or frameworks you may bring with you into the interview.

What are we going to ask you?

The online assessment consists of multiple-choice and short-answer questions, and typically takes an hour to complete. The video interview(s) are longer form problem-solving exercises intended to explore how you gather and apply new information. During this round, a full-time SP poses a few hypothetical business scenarios and logic puzzles for you to work through together in real time.

The final stage is a day of in-office interviews where we dive into more challenging questions that are representative of SP work at Jane Street. These exercises more deeply explore both qualitative and technical areas, but we don’t expect you to immediately understand the details or nuances of the domain at hand. Instead, we encourage you to ask clarifying questions, explore natural extensions of the problem, and take the time to build confidence in your answers.

What qualities do we look for?

The strongest candidates are sharp, logical thinkers that can communicate clearly and concisely. They enthusiastically engage with the problem space and interviewer, and they’re capable of quickly updating and incorporating new information into their solutions.

What should you not worry about?

• Prior financial knowledge. New SP hires undergo a comprehensive educational curriculum as part of onboarding – if you are smart, curious, and enjoy solving problems, we can teach you the rest.
• A particular major or background. Successful SPs come from a variety of disciplines and industries - we’re excited to hear from candidates in all fields.
• Coding experience. Understanding the information flow and interactions of technical systems is a necessary skill for SPs – writing the code to support them isn’t.