Taro Logo

Cloud Engineer Interview Experience - Palo Alto, California

June 1, 2020
Positive ExperienceNo Offer

Process

The interview process involved several rounds:

  • First round: An interview with a current engineer, featuring a practical coding exercise. This wasn't an algorithmic problem, but rather scenario-based coding questions.
  • Second round: A three-part interview, with each part conducted by a different engineer from the team. Each section focused on a specific area: Infrastructure as Code, Programming, and Debugging in the AWS console.
  • Third round: A deep-dive, conversational interview with the team manager. This session explored past roles extensively, inquiring about reasons for leaving, lessons learned, and potential areas for improvement.

The interview process itself was positive. The recruiters were highly responsive, provided clear explanations before each round, and even offered resources to learn more about the company.

However, the decision-making process took over two weeks. This was particularly concerning as I was informed I would receive a prompt answer, especially since I had another offer pending. I experienced a lack of communication, being ignored until I called and emailed multiple times before finally receiving the rejection email.

Questions

There is a web service on AWS that is not working. What steps would you take to debug and get the application working again?

Was this helpful?

Interview Statistics

The following metrics were computed from 1 interview experience for the Palantir Cloud Engineer role in Palo Alto, California.

Success Rate

0%
Pass Rate

Palantir's interview process for their Cloud Engineer roles in Palo Alto, California is extremely selective, failing the vast majority of engineers.

Experience Rating

Positive100%
Neutral0%
Negative0%

Candidates reported having very good feelings for Palantir's Cloud Engineer interview process in Palo Alto, California.

Palantir Work Experiences