I had a person reach out from Sailpoint after applying for a backend role. Come interview time, he immediately asks me really odd questions and is hostile/rude without even greeting me. His first question is who the mascot of my university, seven years ago, was. Then he asked me random things about where I used to live. He confesses that he didn't believe I was a real candidate and thought I was "AI".
I thought maybe he'd be less rude now that he sees I'm a real person but come time for compensation, he asks me for an exact number and when I ask what the range is for the role he sighs and yells "THAT'S NOT WHAT I ASKED YOU. ANSWER ME FIRST!". Really odd screening experience. He says relay this over to the hiring manager.
A few days go by and he emails me that the hiring manager thinks he can get by with a junior hire instead of a senior who will accept $90k. Then why post a senior role and interview for it? Is this a tactic to get candidates to accept a lower pay and title? Either this company uses shady tactics with rude recruiters to hire people OR the recruiter thought I was not real and just wanted to try and expose me but ended up wasting my time.
I interviewed at SailPoint Technologies (Ciudad de Mexico)
Interview
Long process, ghosted by the Recruiter. Won’t recommend, looks like a nice company but the Recruiter assigned to Mexico is not professional at all. Improve you process. Not a good experience for anyone
I applied through a recruiter. The process took 2 months. I interviewed at SailPoint Technologies
Interview
Extremely disorganized hiring process. I was initially contacted by a recruiter about a Go position, which was then closed, but then a Java position was opened, but then it became a Go position with an India-based team, but then on the interview itself I was asked to write in Java.
When I found out I was interviewing with an India-based team, I was asked to be more flexible with my schedule given the timezone difference. On the interview itself I wasn't even interviewed by that team, so I could've had a much easier time scheduling.
The CoderPad screener asked me to hit a mock API and return the lowest price for a Source+Destination+Airline, which is trivial, but the team added artificial constraints to runtime (including API "response" time) implying they want you to pre-cache the pricing data, I was also told several times by the interviewer that I should cache the data - data that I haven't pulled yet from the API. It could be me misunderstanding the intended solution, but I feel if there's an API to hit, you should use the data from the API.
I was told that they decided to go with another candidate, but maybe if it didn't take them well over a month to schedule the first screener with me, I would've had a fairer shot.
3 rounds of interview coding round design round and manager round coding was lru cache implementation where as designing is designing web hooks and other stuff.
Managerial round was more about project and solution design
Interview questions [1]
Question 1
Project , and coding solutions which is oerr coding
