Aller au contenuAller au pied de page
  • Emplois
  • Entreprises
  • Salaires
  • Pour les employeurs

      Boostez votre carrière

      Découvrez votre salaire potentiel, décrochez des emplois de rêve et partagez vos témoignages de manière anonyme.

      employer cover photo
      employer logo
      employer logo

      Palantir Technologies

      Est-ce votre entreprise ?

      À propos
      Avis
      Salaires et avantages
      Emplois
      Entretiens
      Entretiens
      Recherches associées: Avis sur Palantir Technologies | Offres d’emploi chez Palantir Technologies | Salaires chez Palantir Technologies | Avantages sociaux chez Palantir Technologies
      Entretiens chez Palantir TechnologiesEntretiens d’embauche pour Software Engineer chez Palantir TechnologiesEntretien chez Palantir Technologies


      Glassdoor

      • À propos
      • Récompenses
      • Blog
      • Nous contacter
      • Guides

      Employeurs

      • Compte employeur gratuit
      • Centre employeur
      • Blog pour les employeurs

      Informations

      • Aide
      • Règles de la communauté
      • Conditions d'utilisation
      • Confidentialité et choix publicitaires
      • Ne pas vendre ni partager mes informations
      • Outil de consentement aux cookies

      Travailler avec nous

      • Annonceurs
      • Carrières
      Télécharger l'application

      • Parcourir par :
      • Entreprises
      • Emplois
      • Lieux

      Copyright © 2008-2026. Glassdoor LLC. « Glassdoor », son logo, « Worklife Pro » et « Bowls » sont des marques déposées de Glassdoor LLC.

      Entreprises suivies

      Tenez-vous au courant des dernières opportunités et profitez de conseils d’initiés en suivant les entreprises de vos rêves.

      Recherche d’emplois

      Obtenez des recommandations et des mises à jour personnalisées en démarrant vos recherches.

      Entretien pour Software Engineer

      7 mars 2013
      Candidat à l'entretien anonyme
      Aucune offre
      Expérience neutre
      Entretien difficile

      Candidature

      J'ai postulé via un établissement d'enseignement supérieur ou universitaire. Le processus a pris 1 jour. J'ai passé un entretien chez Palantir Technologies en févr. 2013

      Entretien

      An email with a coding challenge link are sent to the mailbox. This is the first stage to get a potential interview. Unfortunately I stopped at the very beginning. I did not pass the code challenge.

      Questions d'entretien [1]

      Question 1

      There is only one coding problem given 100min. The problem is as below: A group of farmers has some elevation data, and we’re going to help them understand how rainfall flows over their farmland. We’ll represent the land as a two-dimensional array of altitudes and use the following model, based on the idea that water flows downhill: If a cell’s four neighboring cells all have higher altitudes, we call this cell a sink; water collects in sinks. Otherwise, water will flow to the neighboring cell with the lowest altitude. If a cell is not a sink, you may assume it has a unique lowest neighbor and that this neighbor will be lower than the cell. Cells that drain into the same sink – directly or indirectly – are said to be part of the same basin. Your challenge is to partition the map into basins. In particular, given a map of elevations, your code should partition the map into basins and output the sizes of the basins, in descending order. Assume the elevation maps are square. Input will begin with a line with one integer, S, the height (and width) of the map. The next S lines will each contain a row of the map, each with S integers – the elevations of the S cells in the row. Some farmers have small land plots such as the examples below, while some have larger plots. However, in no case will a farmer have a plot of land larger than S = 1000. Note: The input uses unix line endings (\n). If you try to view the sample inputs on a windows machine with a program that does not convert line endings (like Notepad), you will see the input appear all on a single line. Your code should output a space-separated list of the basin sizes, in descending order. (Trailing spaces are ignored.) While correctness and performance are the most important parts of this problem, a human will be reading your solution, so please make an effort to submit clean, readable code. In particular, do not write code as if you were solving a problem for a competition. A few examples are below. Input: 3 1 5 2 2 4 7 3 6 9 Output: 7 2 The basins, labeled with A’s and B’s, are: A A B A A B A A A Input: 1 10 Output: 1 There is only one basin in this case. Input: 5 1 0 2 5 8 2 3 4 7 9 3 5 7 8 9 1 2 5 4 3 3 3 5 2 1 Output: 11 7 7 The basins, labeled with A’s, B’s, and C’s, are: A A A A A A A A A A B B A C C B B B C C B B C C C Input: 4 0 2 1 3 2 1 0 4 3 3 3 3 5 5 2 1 Output: 7 5 4 The basins, labeled with A’s, B’s, and C’s, are: A A B B A B B B A B B C A C C C
      5 réponse(s)
      9

      Autres retours d’entretien d’embauche pour un poste comme Software Engineer chez Palantir Technologies

      Entretien pour Software Engineer

      3 juin 2026
      Employé (anonyme)
      Miami, FL
      Offre acceptée
      Expérience positive
      Entretien moyen

      Candidature

      J'ai passé un entretien chez Palantir Technologies (Miami, FL) en juin 2026

      Entretien

      Started with a recruiter screen where the whole point is just checking if you actually care about their mission and the real-world impact of their software, rather than just wanting a cool tech job. After that was a 90 minute hackerrank OA that felt more like an implementation mini-project with SQL and Python instead of abstract algorithms. The onsite was a 4-round loop chosen from decomp, re-engineering, learning, coding, and sys design. Decomp is the most important one - they give you a super vague prompt like designing a chess game or tracking a disease from scratch, and you have to map out the inputs and logic out loud. Re-engineering gives you around 1000 lines of code with a very subtle logical bug to fix, and the learning round drops you into a random API with barely any documentation to see how fast you pick it up lol. Coding was standard LC mediums but they squeeze a 20-minute behavioral chat right into the middle of it, and sys design was heavy on data governance and fault tolerance. The final chat with the hiring manager is pretty intense too ngl. They will actually make you redo parts of the onsite you struggled with. For prep, don't just mindlessly grind LeetCode. Practice reading other people's code fast and structuring ambiguous problems. I got a really good Palantir coach on Prepfully who helped a lot to catch my blind spots and get a reality check before the actual loop. Overall, not very easy though

      Questions d'entretien [1]

      Question 1

      A payment processing module has a race condition that produces incorrect totals under concurrent writes. Walk through how you would identify the root cause and propose a fix.
      Répondre à cette question

      Entretien pour Software Engineer

      24 juin 2026
      Employé (anonyme)
      Palo Alto, CA
      Offre acceptée
      Expérience positive
      Entretien difficile

      Candidature

      J'ai postulé via un recruteur. J'ai passé un entretien chez Palantir Technologies (Palo Alto, CA) en juin 2026

      Entretien

      Standard interview similar to their new grad. Recruiter, two technicals decomp and learning, and then hiring manager half behavioral half technical leetcode style. Really focused on why palantir, mission alignment, and role alignment.

      Questions d'entretien [1]

      Question 1

      Why palantir over any other company?
      Répondre à cette question

      Entretien pour Software Engineer

      15 mai 2026
      Employé (anonyme)
      New York, NY
      Offre acceptée
      Expérience positive
      Entretien moyen

      Candidature

      J'ai passé un entretien chez Palantir Technologies (New York, NY)

      Entretien

      Great interview process - 1. Recruiter call 2. Leetcode style technical 3. Scoping style (decomp) interview 4. Frontend coding 5. Another scoping (decomp round). Interviewers were fun and engaging, and I felt challenged in a positive way.

      Questions d'entretien [1]

      Question 1

      Why do you want to work here? What are you looking for in your next role.
      Répondre à cette question
      1