Ir para o conteúdoIr para a pasta
  • Vagas
  • Empresas
  • Salários
  • Para empresas

      Avance em sua carreira

      Descubra qual pode ser seu salário, conquiste a vaga dos seus sonhos e compartilhe insights de qualidade de vida com sigilo.

      employer cover photo
      employer logo
      employer logo

      Palantir Technologies

      Essa empresa é sua?

      Sobre
      Avaliações
      Remuneração e benefícios
      Vagas
      Entrevistas
      Entrevistas
      Buscas relacionadas: Avaliações da empresa Palantir Technologies | Vagas da empresa Palantir Technologies | Salários da empresa Palantir Technologies | Benefícios da empresa Palantir Technologies
      Entrevistas da empresa Palantir TechnologiesEntrevistas do cargo de Software Engineer da empresa Palantir TechnologiesEntrevista da empresa Palantir Technologies


      Glassdoor

      • Sobre
      • Prêmios
      • Blog
      • Fale conosco

      Empresas

      • Conta gratuita de empresa
      • Área da empresa
      • Blog para empresas

      Informações

      • Ajuda
      • Regras da Comunidade
      • Termos de Uso
      • Privacidade e opções de anúncios
      • Não venda nem compartilhe minhas informações
      • Ferramenta de consentimento de uso de cookies

      Trabalhe conosco

      • Anunciantes
      • Carreiras
      Baixe o aplicativo:

      • Busque por:
      • Empresas
      • Vagas
      • Localizações

      Copyright © 2008-2026. Indeed, Inc. “Glassdoor”, “Worklife Pro”, “Bowls” e o logotipo do Glassdoor são marcas comerciais pertencentes à Indeed, Inc.

      Empresas seguidas

      Fique por dentro de todas as oportunidades e dicas internas seguindo as empresas de seus sonhos.

      Buscas de vagas

      Comece a buscar vagas para receber atualizações e recomendações personalizadas.

      Entrevista para Software Engineer

      7 de mar. de 2013
      Candidato(a) sigiloso(a) à entrevista
      Nenhuma oferta
      Experiência neutra
      Entrevista difícil

      Candidatura

      Candidatei-me por meio de uma faculdade ou universidade. O processo levou 1 dia. Fui entrevistado pela Palantir Technologies em fev. de 2013

      Entrevista

      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.

      Perguntas de entrevista [1]

      Pergunta 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 respostas
      9

      Outras avaliações de entrevista de vagas de Software Engineer da empresa Palantir Technologies

      Entrevista para Software Engineer

      3 de jun. de 2026
      Funcionário(a) sigiloso(a)
      Miami, FL
      Oferta aceita
      Experiência positiva
      Entrevista com nível médio de dificuldade

      Candidatura

      Fui entrevistado pela Palantir Technologies (Miami, FL) em jun. de 2026

      Entrevista

      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

      Perguntas de entrevista [1]

      Pergunta 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.
      Responder à pergunta

      Entrevista para Software Engineer

      24 de jun. de 2026
      Funcionário(a) sigiloso(a)
      Palo Alto, CA
      Oferta aceita
      Experiência positiva
      Entrevista difícil

      Candidatura

      Candidatei-me por meio de recrutador(a). Fui entrevistado pela Palantir Technologies (Palo Alto, CA) em jun. de 2026

      Entrevista

      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.

      Perguntas de entrevista [1]

      Pergunta 1

      Why palantir over any other company?
      Responder à pergunta

      Entrevista para Software Engineer

      15 de mai. de 2026
      Funcionário(a) sigiloso(a)
      New York, NY
      Oferta aceita
      Experiência positiva
      Entrevista com nível médio de dificuldade

      Candidatura

      Fiz uma entrevista na empresa Palantir Technologies (New York, NY).

      Entrevista

      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.

      Perguntas de entrevista [1]

      Pergunta 1

      Why do you want to work here? What are you looking for in your next role.
      Responder à pergunta
      1