Deployment Strategist applicants have rated the interview process at Palantir Technologies with 3.2 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 59% positive. To compare, the company-average is 46.3% positive. This is according to Glassdoor user ratings.
Candidates applying for Deployment Strategist roles take an average of 35 days to get hired, when considering 230 user submitted interviews for this role. To compare, the hiring process at Palantir Technologies overall takes an average of 28 days.
Common stages of the interview process at Palantir Technologies as a Deployment Strategist according to 230 Glassdoor interviews include:
Phone interview: 38%
One on one interview: 25%
Skills test: 14%
Group panel interview: 6%
Personality test: 5%
Presentation: 4%
Other: 4%
IQ intelligence test: 2%
Background check: 2%
Drug test: 1%
Here are the most commonly searched roles for interview reports -
I applied through a recruiter. The process took 2 weeks. I interviewed at Palantir Technologies (New York, NY) in Sep 2016
Interview
one Phone interview with HR, than one phone interview with a Deployment Strategist who asked me behavioral questions. Then two weeks later I had an on site interview that lasted half a day with behavioral and technical question, at the NY office.
I interviewed at Palantir Technologies (New York, NY)
Interview
Made it to the last round! Process was over many months without clear direction of what the next step was. Easier interviews then other technical interviews I have had in the past.
Interview questions [1]
Question 1
What is a problem in the world you wish you could solve
I interviewed at Palantir Technologies (New York, NY)
Interview
They really want to get to know you throughout the process, and see how you think about data in different ways and how you solve problems. You have to build a product which takes a long time.
Started with a quick review of my recent experiences and behavioral questions, and then jumped into a SQL interview. It was mostly a large code file which had a lot of bugs in it that had to be fixed.
Interview questions [1]
Question 1
They asked my about a recent project I worked on at my recent experience and then asked follow up questions about implementation decisions for the project.