Available question text
Related questions
Continue with questions that share topics or the same question type.
- Coding problems seemed more implementation intense, it seems the interviewers have a strong emphasis on writing clean, understandable code. Communication and collaborating with the interviewer also appears important, solving the problem perfectly doesn't seem to be as important as you might expect.
One of the system design interviews was walking through a system you developed (I believe system design questions are only asked to lateral/experienced applicants).
I was not asked any explicit behavioral questions outside of the typical ones you might expect when retrospecting during the "walk through a system you developed" interview. I am told Jane Street doesn't have behavioral rounds for engineers in general.
System design
- Design a Backend That Answers One Question Across 100,000 Documents with an LLM
System design · System Design
- Lots of system design (not leetcode). API integration was just time constrained.
System design
- Please explain me this project that you worked in your past X company and also make me understand the whole system design flow and how you navigated from the front end to back end and also explain the thought process for the cloud architecture used and why a SQL v. NoSQL was used.
System design
Sources · 1 reference
These records explain where the question appears. A company tag or candidate report does not guarantee a future interview question.
Glassdoor · 1 record
Snap
Three programming interviews (including phone screen). One of them was an annoying leetcode-y question with a trick (which I didn't see) but the other two were reasonable. Two system design interviews. I got the sense the interviewers wanted specific answers that matched how they'd solved those problems. Some behavioural questions but no interview focused on this (unusual to not focus on this for an L6 role).
Reported Apr 2023 · 1 source report
Software Engineer
Source snapshot: Nov 12, 2026
View source