The company treats interns well. The perks are good (food, housing, laundry, gym, etc.), and the salary is very high for software engineers. Engineers are, on average, very smart and think/code fast.
If you are inexperienced, you will probably have a very short time at the company, even if you do your best to adapt. They put interns in ongoing projects which are often changing and blame you if you perform poorly or don't keep up. They are unwilling to inform you about technologies you should know upon arrival and will just kick you out of a project if you don't speed up within a couple of days. They expect amazing results in a matter of weeks, even if you are still in college.
Even though they have weekly intern/mentor feedback, the feedback is poor. You pretty much have to read the minds of project leads, most of whom, by the way, are often rude to you and usually too busy to answer any inquiries or questions you may have. They will blame you for wasting their time if you even try.
Palantir is also ethically dubious, as they have multiple concurrent banks to whom they work and keep secret from one another. They often urge interns and full-time software engineers to post positive reviews on Glassdoor.
Don't treat interns as garbage from day 1.
Had a recruiter call covering general questions, followed by a phone screen. The screen featured a LeetCode-type problem: compute the price of a stock portfolio for every day it remains active.
The recruiter initially scheduled and conducted my first interview. This was a phone-based behavioral interview where we discussed my background, experiences, and potential fit for the role.
One phone screen. It included generic behavioral questions, followed by a technical assessment. The technical portion involved parsing data and efficiently storing and manipulating it to create an output. This required knowledge of hash maps and sor
Had a recruiter call covering general questions, followed by a phone screen. The screen featured a LeetCode-type problem: compute the price of a stock portfolio for every day it remains active.
The recruiter initially scheduled and conducted my first interview. This was a phone-based behavioral interview where we discussed my background, experiences, and potential fit for the role.
One phone screen. It included generic behavioral questions, followed by a technical assessment. The technical portion involved parsing data and efficiently storing and manipulating it to create an output. This required knowledge of hash maps and sor