The phone screen featured a well-known system design problem from the interview circuit, with a variant that included an additional constraint.

The process consisted of an OA followed by a 4-round onsite split across two days. A rejection was received within two days of completing the onsite.

The interviewer was very nice and chill. He also asked about projects on my resume and some technical / non-technical challenges I’ve faced.

I originally applied to Palantir through a mass application or possibly a career fair, but didn’t hear back for a while. Later, a recruiter suddenly reached out asking if I was int...

Four rounds split across two days. The overall interview experience was positive with friendly interviewers and moderate difficulty. I felt I was not sufficiently prepared. I heard...

I received the opportunity through an internal referral. The phone screen was structured as: 5 minutes of self-introduction, 50 minutes of coding and discussion, and 5 minutes for...

The MLE phone screen had no coding round. It went straight into a project deep dive. The interviewer asked very detailed questions about my past projects. Time was left at the end...

The phone screen featured a known problem. I believed my performance was good, caught a typo before running and the final code was bug-free. Despite this, a rejection was received...

All problems in this onsite were known problems. I struggled with the debugging round, being unfamiliar with that format and spending too long on an obvious bug. I also ran out of...

I went through a phone screen with a single coding problem, followed by a virtual onsite with four rounds: a code craft round, a system design round, a debugging round, and a hirin...