Me postulé a través de un reclutador. El proceso tomó 4 semanas. Acudí a una entrevista en SailPoint Technologies
Entrevista
Interview Experience – Extremely Unprofessional and Disorganized
If you're considering interviewing with this company, make sure you have at least 4–5 other processes running in parallel. SailPoint India wasted over a month of my time — after clearing two technical rounds, they suddenly responded with "we don’t have openings for your experience." This, despite the fact that they had personally approached me for the role.
Here’s what you should know:
HR communication is pathetic — no updates unless you follow up multiple times.
They are clueless about what they’re hiring for — roles seem to change mid-process.
Extremely unprofessional — zero respect for candidates’ time and effort.
The whole experience reflects a serious lack of internal coordination.
My honest advice: Stay away. Don't waste your energy here — there are far better companies out there.
4
Otras evaluaciones sobre las entrevistas para el cargo de Senior Software Engineer en SailPoint Technologies
Acudí a una entrevista en SailPoint Technologies (Ciudad de México)
Entrevista
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
Me postulé a través de un reclutador. El proceso tomó 2 meses. Acudí a una entrevista en SailPoint Technologies
Entrevista
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
Preguntas de entrevista [1]
Pregunta 1
Project , and coding solutions which is oerr coding