Software Engineer Interview Experience - San Francisco, California
Process
The initial interview was scheduled quickly, almost a week after applying for the job posting on their website.
The interview was performed at a Karat studio.
Since the interviewer did not work at the company, he did not know the job requirements.
In the interview, he asked about two graph problems, which were like easy and medium LeetCode problems. He stated their expectation was only completeness. Finding an efficient solution or considering time and space complexity when implementing a solution were secondary concerns during the interview.
Questions
LeetCode medium-level graph problems similar to Inorder Successor in BST.
Was this helpful?
Interview Statistics
The following metrics were computed from 5 interview experiences for the Palantir Software Engineer role in San Francisco, California.
Success Rate
Palantir's interview process for their Software Engineer roles in San Francisco, California is extremely selective, failing the vast majority of engineers.
Experience Rating
Candidates reported having mixed feelings for Palantir's Software Engineer interview process in San Francisco, California.
Palantir Work Experiences
- 5.0Forward Deployed Software EngineerSoftware Engineer • Current EmployeeSan Francisco, California, United StatesJuly 19, 2023Pros: Nice company to work for. The company is very aggressive on the usage of the latest tools and technologies.Cons: Nice company to work for.
- 4.0Good Pay, Overworked HoursSoftware Engineer • Current EmployeeNew York, New York, United StatesSeptember 18, 2023Pros: Good pay at this company.Cons: A lot of work around the clock.
- 5.0Amazing people, great tech, long hoursSoftware Engineer • Former EmployeeJune 12, 2021Pros: People are amazing; the hiring quality is out of this world even for the Valley. Projects can be extremely interesting. Tech stack (especially on the Foundry side) is modern and fun to use. The software is real and works unlike most enterprise technology Palantir competes against.Cons: Work/life balance is highly project dependent. Long hours trend towards brutal if your project is fast-paced or the customer is overly demanding. Your project may not be all that interesting, and you'll hear about everyone else doing world-changing tech. If your project is uninteresting and has long hours, you can burn out fast. Some of the Gotham codebase is archaic and hard to understand. Palantir changes over time, and you'll need to adapt or reinvent yourself if you stay longer than two years. This can be fun but stressful, and the pace never slows down.
Palantir Interview Questions
