J'ai postulé en ligne. J'ai passé un entretien chez Jane Street
Entretien
A sad experience. I was offered an interview but got rejected before I had a chance to speak to anyone. Let me preface this by saying this was due to an error on my part.
Because the job spec was so general, I wanted to make sure my skillset was understood by their hiring manager. So I responded to the invite with a clarification of what skills were in my domain and what skills weren't.
In describing my coding style, I typically say that "I tend to find elegant solutions to complex problems", or "I strive towards minimal code that delivers maximum results". There's never been an issue with this.
However, in my letter to Jane Street, my wording was admittedly off. In trying to communicate the same notion, I wrote "I like problem solving, usually with minimal code if possible". Suffice to say their recruiting specialist took this in a negative light. Her response as follows:
"If you're not interested in doing a lot of work with code this probably isn't going to be a good match for you. It seems it's best we don't proceed with an interview at this time."
I followed up with a polite letter attempting to repair the miscommunication, but it fell on deaf ears. Live and learn.
31
Autres retours d’entretien d’embauche pour un poste comme Software Engineer chez Jane Street
It was a very quick and painless process. Recruiter very responsive, kind interviewers. High implementation and difficult problems, so failed onsite after 3 interviews and a Question and Answer Session.
J'ai passé un entretien chez Jane Street (Londres, Angleterre)
Entretien
Did not pass the initial coding round. I tried to explain my thought in details to the interviewer but failed to translate my thought into code. So far interviewer is very nice.
J'ai postulé en ligne. J'ai passé un entretien chez Jane Street (New York, NY)
Entretien
My experience interviewing at Jane Street was definitely challenging, but also surprisingly collaborative. Instead of focusing only on whether I could get the right answer quickly, the interviewers were much more interested in how I approached problems and explained my thinking. I worked through a few coding questions involving data structures and algorithms, and there were also some probability-style questions that tested logical reasoning. The interviewers were clearly very sharp, but they were also approachable and encouraged me to talk through my thought process the entire time. When I got stuck, they would sometimes guide me with small hints so we could keep exploring the problem together. Overall, it felt less like a typical high-pressure interview and more like a thoughtful technical conversation with experienced engineers.
Questions d'entretien [1]
Question 1
“What is the expected number of coin flips needed to get two heads in a row?”