Palantir Technologies Application Support Engineer Interview Questions
& Process

I got a call from a recruiter for a quick pre-screen, about 15-20 minutes. Then, I had a second phone interview with a Support Team lead, which was about 45 minutes and covered my technical skills and some personality stuff. After that, I was invited for an in-person interview at their NY office. I met with the same lead again for about 40 minutes, and this time it was more about personal questions than technical ones. Finally, I had a video conference interview with the Technical Support manager from Palo Alto, which was also more personality-focused.

I gave my resume to a recruiter at my university's career fair. The recruiter then emailed me to set up a 30-minute chat about the product support role. During the call, he mentioned that my time as a teaching assistant, my technical background, and my strong desire to assist people made him believe I'd be a great fit for this position. He asked me about my past experiences, and I asked him about Palantir. About a week later, I had a technical phone interview. The interviewer acted like a customer who was having trouble logging into a Palantir product. I had to explain what questions I would ask and to whom, and the interviewer would respond as if he were the IT team, a coworker, etc. Ultimately, I figured out that the customer's computer had a slightly different setup that was causing the problem. I also got to ask him a few questions about his experiences at Palantir. He mentioned that the average age of employees is 25, with 35 being on the older side, and sometimes considers work like family. If they have free time (which is rare, especially when starting out), employees can take on side projects that benefit the company. Meeting deadlines can be very stressful. Roughly 3 hours after the phone interview ended, my recruiter called to inform me that I had advanced to the onsite interview. He sounded very enthusiastic about my performance during the phone screen, sharing specific details about my past experiences and complimenting my clear thinking during the technical question. He asked about my availability to travel to Washington D.C. for their interview event, where the whole team would be interviewing many candidates simultaneously. He stressed that I should let him know immediately if I couldn't make it because spots were limited. Since I was swamped with schoolwork, traveling from California to D.C. would be very challenging with classes and midterms. I emailed him to explain this and requested to interview at their Palo Alto office instead. After some back-and-forth, where he inquired about alternative dates or my availability to travel to New York in a different week, I was scheduled to fly to Palo Alto. They mentioned that I would eventually need to fly to D.C. to meet with the head hiring manager, but they would make arrangements if I reached that stage. My onsite interview lasted 3-4 hours and I finished around 12pm. I showed my ID to the receptionist on the ground floor, and after some confusion about whom I was there to see, I signed in on an iPad using my recruiter's name and signed an NDA. About a week later, my recruiter contacted me to let me know that the team had decided to proceed with other candidates.

First I talked to a recruiter who asked me about myself and my career goals, and explained different job openings. Then I had to do a coding challenge that I could do in any programming language I knew. After a couple of weeks, I had a phone interview with someone already in the role. We went over general interview questions, and they threw in a technical support question where I had to act like I was dealing with a customer issue, basically. They gave me a situation and I had to figure out how to fix it for the client. About a week later, I had a similar chat with the department head. And then, about half a week after that, I got a generic rejection email.