Getting an Interview
Getting an Interview
Interviews for Top Jobs at Palantir Technologies
- Software Engineer (101)
- Forward Deployed Engineer (73)
- Deployment Strategist (61)
- Embedded Analyst (23)
- Forward Deployed Software Engineer (21)
- Mission Specialist (18)
- QA Engineer (16)
- Software Engineering (15)
- Product Quality Engineer (15)
- Business Development (13)
- Software Engineer Intern (9)
- Software Developer (8)
- Engineering (8)
- Software Engineering Intern (8)
- Business Operations and Strategy (8)
- Wordsmith (7)
- Intern (7)
- Financial Analyst (6)
- Software Engineer Internship (6)
- Support Engineer (5)
- Product Expert (5)
- Product Support Engineer (5)
- Administrative Assistant (4)
- Financial Operations Analyst (4)
- Product Quality Engineer Intern (4)
- Site Reliability Operations Analyst (4)
- Missions Operations Analyst (4)
- Forward Deployed Engineer Intern (3)
- Infrastructure Quality Engineer (3)
- Product Support Intern (3)
- No OfferPositive ExperienceDifficult Interview
I applied through a recruiter. The process took 1+ week. I interviewed at Palantir Technologies (Philadelphia, PA) in September 2015.
A few short behavioral questions (Where I'm from, Why Palantir, Why FDSE). Then, a long, relatively difficult technical question. I answered it first by writing some pseudocode on a whiteboard, then I was handed a computer to code the problem in a language of my choice. I was asked to explain my thought process as I went and was given hints if the interviewer felt I was stuck for too long. In the end I didn't end up finishing the actual program.
- Given an nxn matrix of 1's and 0's, figure out if all of the 1's are connected. 1 Answer
Helpful (1)No OfferNegative ExperienceEasy Interview
I was asked by a friend to apply. He seemed pretty nonchalant when I asked him about his experiences there, but he said he was after the referral bonus. They had recently ramped up the reward. Someone reached out to schedule a Skype interview and asked for my Skype name. They couldn't do it later in the day so I was forced to leave work early. It is what it is. They told me to be in business casual for the Skype call. I got a phone call while standing in front of my laptop at home in business casual for a Skype call (a call that I could have taken in the office and gone back to work afterwards). Apparently the same guy interviewed my friend a month prior. He's currently on a project to revamp their hiring process so he does the majority of the interviewing. All of the questions (yes all), were behavioral and are what you would find on About.com. It felt pretty long and inadequate in terms of gauging problem-solving abilities. The interviewer mumble inaudibly and I had to ask him to repeat himself a numerous times. I guess it was good practice considering I don't often get asked the more generic interview questions. Usually I'm asked a hypothetical or conceptual question to test my analytical aptitude. At the end, the interviewer asked for current contacts including my current boss. I was very reluctant to give him this information and had never been asked that by an interviewer so early in the process. I got an e-mail saying that they wouldn't be moving forward with me.
- What are your three greatest strengths? Three greatest weaknesses? What project are you most proud of? Answer Question
Helpful (1)No OfferNegative ExperienceDifficult Interview
I applied through a recruiter. I interviewed at Palantir Technologies.
Round of phone interviews, then an obnoxiously time consuming data test (basically an analytics entry exam to weed people out), multiple in person interviews. After all of this, the Founders get a whack at you. You could crush every level of the interview process and then the Founders could meet you for 5 minutes and decide you don't fit into the Palantir cult. More power to them, but after the interview process I didn't want to work there.
- lots of questions about different types and ways of organizing data. 1 Answer
- No OfferNegative ExperienceAverage Interview
I applied through an employee referral. The process took a week. I interviewed at Palantir Technologies (San Francisco, CA) in August 2015.
Referred to the role and had a quick phone call where the woman was nice but judged me for not being as Type A as she was. I sent her my resume and then didn't hear back for a while and then got a generic rejection. My interviewer also did not really want to answer the questions I asked.
- How would you perform if something didn't go your way? How would you think on your feet? Answer Question
- No OfferNegative ExperienceEasy Interview
I applied through an employee referral. The process took 3 weeks. I interviewed at Palantir Technologies (New York, NY) in August 2015.
Referred by a friend. They emailed me and set up a time to call my cell. I responded but they took a long time to confirm the call time. They didn't explain the purpose of the call and didn't send a job description. I am still baffled about what they are looking for. A job description or any info about the role of a deployment strategist would have been useful.
- To describe my career (they didn't have my resume). They quizzed me on the job description.... which they hadn't sent to me. Answer Question
- No OfferPositive ExperienceDifficult Interview
I applied online. The process took 4+ weeks. I interviewed at Palantir Technologies (Palo Alto, CA) in August 2015.
I was contacted by a recruiter to do a phone call and talk about the company for about 30 minutes. She asked me a couple technical questions that were easy and also found on this website. After that, I had a phone call with an engineer but it wasn't a typical coding phone screen. I didn't even need to have my laptop as we talked through some system design questions (how would you design an elevator, Amazon, etc). Then I had another phone screen with an actual coding question which I completed on CoderPad. After that phone call I was invited to come onsite where I had a breakfast with an engineer to just ask questions and then 3 interviews in the afternoon followed by a demo by two other engineers. Before my interview, they had let me know that the hiring manager was on vacation that week so if I had done a good job, I would still have to do one more Skype interview with them. Ultimately, I did not move on past this stage but I really enjoyed meeting the team and the interviewers were all really nice. I think that Palantir is just a very top company and you have to interview almost perfectly.
- System design questions mainly Answer Question
- No OfferNeutral ExperienceAverage Interview
I applied online. The process took 3 weeks. I interviewed at Palantir Technologies in August 2015.
I applied online and got a response maybe 1.5 weeks later. Scheduled an initial phone screen with recruiter who asked about my background and "why Palantir?". A week later had a technical phone interview with a Product Expert. He asked a conceptual question, a simple coding questions (on CodePair) and, again, "why Palantir?".
- No OfferPositive ExperienceAverage Interview
I applied through a recruiter. The process took a week. I interviewed at Palantir Technologies.
Telephone Interview with Recruiter: Asked questions about my background and interest in the company. No oddball/fun questions asked. Recruiter asked about other opportunities on my horizon so that company could expedite interviewing which I appreciated. Telephone Interview #2 with Manager on Team: Asked about my background and behavioral questions.
- What are you looking to do in your next role? Answer Question
Helpful (4)No OfferNeutral ExperienceAverage Interview
I applied through a recruiter. The process took 2 days. I interviewed at Palantir Technologies (Washington, DC) in July 2015.
I was recruited through LinkedIn. Had a phone interview with the recruiter and then exchanged some follow up emails. During our interview the recruiter failed to inform me that the job required 50% travel, which is a key piece of information that should have been delivered up front. Once I discovered that I cancelled the next interview. The next step would have been an interview with another Technical Project Manager, and then a visit onsite to meet with a team and conduct some face-to-face interviews.
- The first interview is basically just a chance from the recruiter to explain about Palantir and then offer some high-level explanation of the job. I asked way more questions of the recruiter than they asked of me. Hopefully the next stage of the interview process would be a little more in-depth. Answer Question
- No OfferNegative ExperienceDifficult Interview
I applied online. The process took 1+ week. I interviewed at Palantir Technologies (San Francisco, CA).
I applied online and a couple days later heard back from a recruiter who was really nice and asked me about my interests and background. The next day I got an email scheduling a phone interview, I was really excited for the interview but disappointed when the lady was not only really late calling me but sounded completely bored the whole time. She didn't ask me about my interests at all and when I asked her questions about the company like "Is Palantir currently profitable?" she didn't know any any of them. She told me they were trying to give a new face to their UI then we launched into the technical interview. The technical interview wasn't front end at all though! It like a really vague hashmap/linked list problem that really threw me since I was expecting JS questions for a frontend interview. Overall she was pretty rude and I decided pretty much at the beginning of the interview I would never want to work there
- A question involving an API's integration with hash map where the buckets of hash map are made up of linked lists 1 Answer
Is this helpful? The community relies on everyone sharing – Add Anonymous Interview Review
See What Palantir Technologies Employees Are Saying
2 people found this helpful
Pros: “I've originally joined Palantir because I was intrigued by the FDE position and - more interestingly, considering the luxury of choices engineers have these days - it's the reason...”“I've originally joined Palantir because I was intrigued by the FDE position and - more interestingly, considering the luxury of choices engineers have these days - it's the reason that keeps me working here. As a FDE I get to work with a relatively small team (average around 5 people probably) on a project that's deemed critical to some of the biggest institutions in the world. That constellation (big problem, small team) comes with some interesting implications: * You can't "just" be an engineer. Yes, there are really interesting technical problems that come with handling large-scale data and yes, you need to set up (and/or develop) the architecture that supports your team and the customer, but since there's so much to do you need to be able to wear lots of different hats. Engaging with the user and giving a demo, talking to IT teams and talking through the architecture or meeting C-level executives on a regular basis are all part of an FDE's responsibilities. I've always been very technical but having to respond to questions from non-technical CEOs has taught me how to hone "soft" skills that I consider immensely valuable (even beyond my career). * You learn how to solve a problem. With the growth of the business it's becoming more and more common to be working in a vertical that's new to Palantir. This is really, really hard because you're coming up with a solution from scratch, but it's also really, really exciting and rewarding. You'll learn how to go from 0->1 (using Peter Thiel's words) and understand the difficulties and intricacies of starting something new (navigating through a jungle of uncertainty, finding the valuable thing, prototyping on it and iterating on feedback). I honestly think that this position is a great learning ground for future entrepreneurs. * Your work actually matters. Palantir's customers are amongst the most important institutions in the world and we're always working on some of their biggest problems. Moreover, in a team of ~5 people the work you do has direct impact on the project. You make or break the project. * Execution is critical, but you're also setting the vision. One of the rather amazing (and probably unique) things about Palantir is that it puts a lot of trust in and ownership on project teams. When you're working on a project, you're not just merely executing someone's plan, you're part of the team that's also defining the vision and the approach and is ultimately responsible for its success.” – Full Review