Getting an Interview
Getting an Interview
Interviews for Top Jobs at Palantir Technologies
- Software Engineer (100)
- Forward Deployed Engineer (72)
- 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)
- Intern (7)
- Financial Analyst (6)
- Software Engineer Internship (6)
- Wordsmith (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)
Site Reliability Operations Analyst Interview
I applied through other source. The process took 3 weeks. I interviewed at Palantir Technologies (Washington, DC) in June 2015.
I'm currently employed as a Project Manager - loving my job and have great salary and benefits. I'm not actively looking for something new. Palantir contacted me via LinkedIn. The recruiter and interview scheduler were very friendly and organized - great first impressions. The first interview was a phone screen/interview with the recruiter - went well. Second interview was a phone interview with a current New York Site Reliability Operations Analyst - went very well - he had great questions and we talked for 1.5 hours - I was inspired and interested at this point. Third interview was a series of one-on-one on-site 30 minute interviews (they flew me to DC from NYC because the managers for NYC sit there) with four people: one more Site Reliability Operations Analyst, two managers, and the director of the department. This last series of interviews turned out to be a big mess. It felt as if only one person read my resume ahead of time and two of the four people I met with were late to meet with me (so, our half hour together turned into 20 mins). Everyone I met with was generally friendly but seemed super stressed out. Positive side note: the offices were really nice, lunch is provided, and there isn't a dress code. Further description of why this last series of interviews wasn't great: the group hadn't prepared anything substantive to really determine if it was a good match - and they almost ironically 'interviewed for cultural fit' - using casual conversation - which I enjoy but we didn't talk about anything work related so I left without a clear idea of what I'd actually be doing there - even after trying several times to find out more. I asked one person to describe a "day in the life for this role" and he simply replied, "the job is too variable to answer that question" and cut me off - kind of baffling since this is a really common interviewee question that most people are prepared to answer with common tasks of the position. Lastly, the KICKER - this same person asked me what job I was interviewing for - I almost thought he was joking. Yes, he was doing a quick hello to meet me and determine overall fit - but this kind of basic prep is required in my opinion. Someone needs to remind him that his team is emailing people on LinkedIn trying to fill this position - I would recommend he come prepared - people aren't knocking down the doors to work for you! He was quite pretentious - really a downer and poorly represented Palantir. I left the interviews feeling a little deflated about Palantir. If an offer came - I was prepared to simply max out the salary to an amount I couldn't refuse. For me to leave my current job (Project Manager at a profitable/stable/major NYC company with sweet benefits) would require a huge increase over my current salary to justify the obvious stress and poor management. Later that week - the recruiter was very kind to call me personally to let me know it wasn't a match and gave me some feedback about why - he said the team really liked me overall but two of the interviewers said I tried to drive the conversations too much and that this might not be the right kind of person to put in front of their clients. Palantir - thanks for contacting me - and I'm sorry it didn't work out!
Other Interview Reviews for Palantir Technologies
Site Reliability Operations Analyst InterviewNo OfferPositive ExperienceAverage Interview
I applied through college or university. The process took 3 weeks. I interviewed at Palantir Technologies in September 2013.
Initially talked to a recruiting person at my college's career fair. After a brief talk he asked me a quick on-the-spot computer science question even though I was not applying for a technical position. It was regarding binary search "If you're trying to guess a number that I know and my only responses are yes and no, how do you do it?" Something to that effect. A few weeks later a recruiter from one of the facilities emails me regarding a phone "chat session" (30 min). This is a pre-screen to ask about things on your resume, why you want to work for the company, and why you think you're a good fit. It also double checks your credentials like how many years of experience you have, where you worked, and where you went to school (even though it's on your resume). If you seem like a fit, the recruiter sets up another phone interview (1 hr) with an actual Site Reliability Operations Analyst (SRO). The SRO continues to explain more details about the job and company, in addition to asking you questions. For this position, I was asked quite a few questions regarding how you interact with clients: how you generally deal with clients, how you deal with client pushback, how you deal with difficult or stubborn clients, how you express an unpopular opinion to a client. I thought I nailed the SRO interview because the conversation was very engaging, I had good examples/stories to back up my claims, and the interviewer went on much detail when answering my questions. Suddenly, it came to an end and I knew I didn't make it to the on-site interview. After I was done asking questions there was a pause, so I told him those were all the questions I had. Before being able to say anything else, the interviewer concluded the interview and we said our goodbyes. The tone was very rushed and different from the rest of the interview. I never received any feedback as to why I was rejected. Overall, the response time was very fast. The recruiters were friendly. The questions seemed customized to my situation and my position I was applying for. Good experience, but I just wish I could get some feedback on my performance.
- How do you tell a client that the solution we have arrived at best solves their problem even if they don't like the idea? Answer Question
Site Reliability Operations Analyst InterviewNo OfferPositive ExperienceEasy Interview
I applied through a recruiter. The process took 3 weeks. I interviewed at Palantir Technologies (McLean, VA) in July 2013.
I was sent a request via Linked-in to chat with a recruiter about Palantir. After responding, it took a couple of days of rescheduling before actually talking with the recruiter. After discussion my experience, she suggested I would fit in the Site Reliability Operations Analyst position. I had a phone interview with one of the current employees in the SROA position . The interview was short, approximately 15 minutes. I was asked general questions about my current position and what interested me in Palantir. Two days later I was set up for a second phone interview. The interview lasted about the same time. Same general questions. Next day received rejection letter mentioning my skills did not match.
Site Reliability Operations Analyst InterviewNo OfferNegative ExperienceAverage Interview
I applied online. The process took 1+ week. I interviewed at Palantir Technologies (McLean, VA).
After two phone interviews with very friendly individuals at the Palo Alto office I did my third interview (for a separate position than initially interviewed for) with someone at the McLean, VA office. Let me start by saying that the first two interviews were very straight forward and very nice. A few technical questions that were pretty easy to field followed by questions based around my work ethic and working as a party of a team. This was very encouraging because I am looking for a position that is geared more toward good work environment and good products, rather than politics and pay. The Palo Alto office seems like a very enjoyable place to work that is focused on its most important assets, its employees. The third interview with a McLean representative was quite the opposite. There were no technical questions and the interviewer seemed to have a very elitist personality. The interviewer had very little structure, he seemed to ask random questions but did not know what answers he wanted, and every question had a response of "Can you elaborate?" no matter how in depth I went. The few questions I asked were not answered such as, Q:“How is the office environment in McLean as opposed to Palo Alto?” A:“It’s an office environment.” After six minutes the interviewer abruptly stated that he had to go and hung up on me. Honestly, I would not want to work in that office after that interaction. But should I relocate to CA again one day I would definitely try for a job at the Palo Alto office. I honestly believe that Palantir has a great product and in general has a good work ethic based on the research I conducted while interviewing. Palantir is going places and would be a fantastic place to work… with the exception of those that are full of themselves.
Site Reliability Operation Analyst InterviewNo OfferNeutral Experience
I applied through a recruiter. I interviewed at Palantir Technologies (London, England (UK)) in July 2014.
Like a few others on here I have been approached by a recruiter at Palantir Technologies via LinkedIn, via a private message even though they weren't an existing contact for a particular role - Site Reliability Operation Analyst. At first I was quite excited but after I saw the job spec realised that I wasn't a good match for the role. I also did a lot of researching into the company, including reviews on this site, and I really didn't like what I found e.g. cult-ish culture, living facilities on site (poor work life balance), unfavourable press about the "weirdness" of the CEO, not a great regard for the for non-techie roles, etc.
- None as such as I cancelled the interviewed after my research - which was taken in kind and professionally. I was surprised though to be even considered for the role as I didn't feel my profile qualified to raise even the initial interest - I am a project manager who mainly worked on Web and IT projects, but am not technical myself and yet the role asked for some heavy duty technical skills, albeit desirable (but you'd need them if you were to solving problems of your software users). Answer Question
Is this helpful? The community relies on everyone sharing – Add Anonymous Interview Review