October 17, 2026
Positive ExperienceNo Offer
A recruiter reached out to me on LinkedIn telling me to apply. I did, and I had a 30-min phone screening with that recruiter which led to a 30-min technical screening (pretty basic practical scenario question), which I also passed.
I then got invited to DC for a day for onsite stuff (from what I've seen online, this means multiple hour-long interviews and meeting people). Haven't had the onsite yet.
The following metrics were computed from 16 interview experiences for the Palantir Forward Deployed Software Engineer role in Washington, District of Columbia.
0%
Pass Rate
Palantir's interview process for their Forward Deployed Software Engineer roles in Washington, District of Columbia is extremely selective, failing the vast majority of engineers.
Positive56%
Neutral25%
Negative19%
Candidates reported having very good feelings for Palantir's Forward Deployed Software Engineer interview process in Washington, District of Columbia.
3.0
Software Engineers - pay attention!
Forward Deployed Software Engineer • Former Employee
Washington, District of Columbia, United States
September 19, 2016
Pros: Some (but not all) of the work the company does is incredibly exciting and impactful to real-world problems. Your co-workers will be smart, hard-working, and motivated. There's a very small number of companies in the DC area that offer catered food 3 times a day and have a speakeasy. The perks are real, and while they shouldn't be a deciding factor, they're definitely nice.
Cons: I was hired as a "Forward Deployed SOFTWARE Engineer". During the interview process, I asked what the difference was between this and a normal software engineering position, and was told "there's basically no difference". That response was untrue. I was further misled at least twice during the interview process, and one of my interviewers apologized for lying to me during interviews after we both had left the company. Any type of forward deployed position at Palantir bears very little resemblance to a normal "software engineering" position. Some people like the differences and others don't. Forward deployed engineering involves mostly deploying other people's code of varying quality and trying to shoehorn it into a place to solve a problem, then struggling desperately to keep it running. Also, trying to keep other people's earlier shoehorned solutions running. As of my departure in summer 2016, the DC office still has no real SE positions, though it does list them as openings. Be very cautious applying for one of these positions. I recommend asking every single person you talk to the following questions: * If hired, what PRODUCT will I be working on? (They will probably try not to answer - you can interpret that response however you like) * How many products are developed in this office, and where are they used? How big are the development teams? * How many product managers are in the office? * What does the development/release cycle look like for the product I will be working on? * Will I be working on a client site? OR What are the travel requirements for this position? Basically, try to ask very SE-specific questions about the job you're applying for. Be critical when analyzing the responses. But seriously, if you want to do software engineering, do yourself a favor and don't go to work at Palantir in DC. London, New York, and Palo Alto all have supported and stable engineering teams as of summer 2016. The company also suffers from systemic poor leadership, which creates a political, distrusting environment that said leadership refuses to believe exists. This isn't necessarily a dealbreaker though, just something to be aware of. I ranked culture & values low, because while Palantir has a great cultural manifesto, it's almost 100% not reflective of conditions inside the company. Palantir has a culture of disrespecting customers, which made me uncomfortable. Finally, there's definitely a subculture of people expecting employees to be in the office a lot. I think even people who are on site all the time suffer from a public perception that they're not "spending enough time in the office".
4.0
Smart People, Very Political
July 26, 2024
Pros: - Super smart people. - Good culture. - Reasonably good benefits, in-office meals, etc.
Cons: Highly political; you need to be good with people and technology to be successful. Bad work-life balance. A lot of great people will leave to start their own businesses. A tad culty at times.
Interesting Problems, Stressful Times
Forward Deployed Software Engineer • Current Employee
November 25, 2025
Pros: FDSE solves lots of interesting problems.
Cons: Can be a bit stressful at times.
- 3.0Software Engineers - pay attention!Forward Deployed Software Engineer • Former EmployeeWashington, District of Columbia, United StatesSeptember 19, 2016Pros: Some (but not all) of the work the company does is incredibly exciting and impactful to real-world problems. Your co-workers will be smart, hard-working, and motivated. There's a very small number of companies in the DC area that offer catered food 3 times a day and have a speakeasy. The perks are real, and while they shouldn't be a deciding factor, they're definitely nice.Cons: I was hired as a "Forward Deployed SOFTWARE Engineer". During the interview process, I asked what the difference was between this and a normal software engineering position, and was told "there's basically no difference". That response was untrue. I was further misled at least twice during the interview process, and one of my interviewers apologized for lying to me during interviews after we both had left the company. Any type of forward deployed position at Palantir bears very little resemblance to a normal "software engineering" position. Some people like the differences and others don't. Forward deployed engineering involves mostly deploying other people's code of varying quality and trying to shoehorn it into a place to solve a problem, then struggling desperately to keep it running. Also, trying to keep other people's earlier shoehorned solutions running. As of my departure in summer 2016, the DC office still has no real SE positions, though it does list them as openings. Be very cautious applying for one of these positions. I recommend asking every single person you talk to the following questions: * If hired, what PRODUCT will I be working on? (They will probably try not to answer - you can interpret that response however you like) * How many products are developed in this office, and where are they used? How big are the development teams? * How many product managers are in the office? * What does the development/release cycle look like for the product I will be working on? * Will I be working on a client site? OR What are the travel requirements for this position? Basically, try to ask very SE-specific questions about the job you're applying for. Be critical when analyzing the responses. But seriously, if you want to do software engineering, do yourself a favor and don't go to work at Palantir in DC. London, New York, and Palo Alto all have supported and stable engineering teams as of summer 2016. The company also suffers from systemic poor leadership, which creates a political, distrusting environment that said leadership refuses to believe exists. This isn't necessarily a dealbreaker though, just something to be aware of. I ranked culture & values low, because while Palantir has a great cultural manifesto, it's almost 100% not reflective of conditions inside the company. Palantir has a culture of disrespecting customers, which made me uncomfortable. Finally, there's definitely a subculture of people expecting employees to be in the office a lot. I think even people who are on site all the time suffer from a public perception that they're not "spending enough time in the office".
- 4.0Smart People, Very PoliticalForward Deployed Software Engineer • Former EmployeeWashington, District of Columbia, United StatesJuly 26, 2024Pros: - Super smart people. - Good culture. - Reasonably good benefits, in-office meals, etc.Cons: Highly political; you need to be good with people and technology to be successful. Bad work-life balance. A lot of great people will leave to start their own businesses. A tad culty at times.
- 4.0Interesting Problems, Stressful TimesForward Deployed Software Engineer • Current EmployeeWashington, District of Columbia, United StatesNovember 25, 2025Pros: FDSE solves lots of interesting problems.Cons: Can be a bit stressful at times.
Explore Interview QuestionsTaro 75Google Interview QuestionsMeta Interview QuestionsAmazon Interview QuestionsApple Interview QuestionsNetflix Interview Questions
Explore Interview ExperiencesOpenAI Interview ExperiencesAnthropic Interview ExperiencesPerplexity Interview ExperiencesWindsurf Interview ExperiencesMistral AI Interview Experiences