
SailPoint engineering candidates report an HR or recruiter screen, manager conversations, and technical rounds on Java, OOP, SQL and coding, with frequent complaints about slow or missing feedback.
$135K
Avg. Base Comp
$170K
Avg. Total Comp
2-5 rounds
Typical Rounds
Not reported
Process Length
Candidates who interviewed at SailPoint for engineering roles describe a process that usually opens with an HR or recruiter conversation, moves to a hiring manager, and then reaches one or more technical rounds. The reports come from different titles, including senior, backend, UI and developer roles, so expect the loop to vary by team and level.
The technical content leans toward Java and object-oriented fundamentals. One candidate had a roughly twenty-minute round covering Java, OOP, data structures, exception handling and SQL. A senior candidate described medium LeetCode-style coding in a 45 to 60 minute session, a business-related system design interview of similar length, and "guess the output" Java questions touching on binary trees, arrays, exception handling and the difference between factory method and abstract factory. A backend candidate wrote a program to solve a fairly simple problem and also answered an exam-style set of about ten questions. A Staff UI candidate was asked about XSS and Angular after a technical assessment that ran over three hours.
Behavioral conversations cover your background, why you want to change jobs and how you would fit the team. The bigger complaint is communication: several candidates, across different roles, described long gaps, unanswered requests for feedback, or a rejection with no explanation. Ask about timing at the end of each stage, and practice talking through Java behavior out loud.
Synthesized from 8 candidate reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Sailpoint technologies process.
The process started with a 30-minute HR call where they got a feel for my background and interests. After about two and a half weeks of waiting, I had a conversation with the hiring manager. They asked me about a project I was most proud of, which felt pretty straightforward—they wanted to understand my experience and what I'd actually built. I tried to give a solid answer, but the whole thing felt rushed. Then I waited another three weeks before getting rejected. The timeline was frustrating, and honestly, the entire process felt disorganized. I wish they'd moved faster or given clearer feedback earlier rather than stringing things out. The questions themselves weren't particularly challenging—mostly behavioral stuff focused on my past work—but the lack of communication and the long gaps between rounds made it hard to stay engaged. It felt like they could have made a decision much sooner instead of letting it drag on.
Prep tip from this candidate
Be ready to articulate specific projects with concrete impact and scaling considerations, but also be prepared for a potentially slow and unclear feedback process—follow up proactively if you don't hear back within a week.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Sailpoint technologies
How would you scale training this recommender system to millions of movies and users
| Question | |
|---|---|
| 2nd Highest Salary | |
| Empty Neighborhoods | |
| Closest SAT Scores | |
| Top Three Salaries | |
| Merge Sorted Lists | |
| Random SQL Sample | |
| Subscription Overlap | |
| Raining in Seattle | |
| Monthly Customer Report | |
| Top 3 Users | |
| Find Bigrams | |
| N-gram Dictionary | |
| Upsell Transactions | |
| Longest Streak Users | |
| Find the First Non-Repeating Character in a String | |
| Size of Joins | |
| Customer Orders | |
| String Shift | |
| Rolling Bank Transactions | |
| Find the Missing Number | |
| Scrambled Tickets | |
| P-value to a Layman | |
| Comments Histogram | |
| Get Top N Frequent Words | |
| Last Transaction | |
| Duplicate Rows | |
| Minimum Change | |
| Bagging vs Boosting | |
| Employee Salaries (ETL Error) |
Synthesized from candidate reports. Individual experiences may vary.
Candidates describe starting with a conversation with HR or a recruiter, in one case a Teams call. It is a fairly standard screen on your background and why you are looking to move. One senior candidate said an early interview was rescheduled and the role was briefly described as closed before they were redirected to another hiring manager.
Several candidates describe a manager-level conversation. A senior candidate found it pleasant and focused on background, reasons for changing jobs and team fit. A backend candidate had two manager-level interviews before the technical round. A Staff UI candidate was asked why they wanted the role and how they would approach team management.
Formats differ by role. One candidate had a 20-minute round on Java, OOP, data structures, exception handling and SQL. A senior candidate had a 45 to 60 minute medium-difficulty coding round, a similar-length business-related system design round, and Java output-prediction and design pattern questions. A backend candidate wrote a program for a simple problem and answered about ten exam-style questions.
A developer candidate completed a technical test in a few days and was then rejected before it was reviewed. A Staff UI candidate sat a technical assessment of over three hours, followed by a technical and a cultural interview.
Several candidates reported little or no feedback after finishing. One waited about a week and a half after a test, another had to chase the recruiter after three rounds, and a Staff UI candidate heard nothing after the final interview. Another candidate said follow-up between rounds was good, so ask about next steps and timing at each stage.