SAS software engineer candidates describe a HireVue video screen followed by conversation-heavy rounds: a project presentation, a hiring manager chat, a take-home review, or a team panel.
$118K
Avg. Base Comp
$151K
Avg. Total Comp
2-3 rounds
Typical Rounds
Not reported
Process Length
Candidates describe SAS interviews as conversational, with a HireVue one-way video screen as the most common first gate. Three of the five reports begin there, with questions about why you fit the role, teamwork, conflict and learning something new.
The one candidate who applied as a software engineer was asked to prepare a 15-minute presentation on a project of their choice after the HireVue. They felt the feedback praised their storytelling, but the interviewers asked few technical follow-ups, and they did not advance. Their advice was to bring the harder technical decisions and trade-offs, not only the narrative arc.
A software developer who received an offer described three virtual rounds: a short HR phone screen, an hour with the hiring manager on Teams that included why strings are immutable in Java, and a two-hour Teams session presenting a week-long coding exercise. Two internship candidates went from HireVue to a relaxed panel with the team. One described the panel as an hour with three people focused on resume experience, with no coding challenge.
Overall timing varied. One candidate heard back after about a week and a half, and another described roughly a month from application to decision. Be ready to walk through a past project in depth, review core language fundamentals, and prepare specific stories from your resume.
Synthesized from 5 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 Sas institute inc process.
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 Sas institute inc
Select the 2nd highest salary in the engineering department
| Question | |
|---|---|
| Merge Sorted Lists | |
| Closest SAT Scores | |
| Subscription Overlap | |
| Empty Neighborhoods | |
| Top Three Salaries | |
| Monthly Customer Report | |
| String Shift | |
| Random SQL Sample | |
| Comments Histogram | |
| Minimum Change | |
| Raining in Seattle | |
| Top 5 Turnover Risk | |
| Rolling Bank Transactions | |
| Customer Orders | |
| Prime to N | |
| Upsell Transactions | |
| Top 3 Users | |
| Find the Missing Number | |
| The Brackets Problem | |
| Find the First Non-Repeating Character in a String | |
| Bagging vs Boosting | |
| Rectangle Overlap | |
| Largest Salary by Department | |
| Scrambled Tickets | |
| First Touch Attribution | |
| Flight Records | |
| Level Of Rain Water In 2D Terrain | |
| Job Recommendation | |
| Project Pairs |
Synthesized from candidate reports. Individual experiences may vary.
Several candidates report a one-way HireVue recording as the first stage. Questions were behavioral or reflective: why you would fit the role, teamwork, conflict with a peer, and learning something new. One candidate said they could re-record answers, so read the instructions you receive carefully.
The software developer who received an offer had a short HR phone screen about their background and the role. A week later came an hour-long Teams meeting with the hiring manager. It covered their work experience in depth, with some technical questions such as why strings are immutable in Java. They described the tone as curious rather than adversarial.
The software engineer candidate gave a 15-minute project presentation and was not advanced, feeling the discussion stayed surface-level. The software developer worked on a moderately complex coding exercise for a week, then presented it in a two-hour Teams session with follow-ups and a behavioral question. Prepare to explain your technical decisions and trade-offs.
Two internship candidates describe a live panel after the HireVue. One had a one-hour online session with three team members who asked detailed questions about resume experiences and described their day-to-day work, with no formal coding challenge. The other met the manager and team and found it natural. Bring concrete examples and questions about the team's work.
