Vanguard software engineer candidates describe an online assessment, recruiter or HR screens, and a final super day or panel. The technical bar is often described as light, with heavy behavioral emphasis.
$108K
Avg. Base Comp
$130K
Avg. Total Comp
3-4 rounds
Typical Rounds
Not reported
Process Length
Candidates who interviewed for Vanguard software engineer roles describe a process that is more behavioral and conversational than a typical big-tech coding loop. Several report an online assessment first, usually HackerRank-style data structures and algorithms. One candidate called it basic, another described LeetCode easy-to-medium problems, and one internship-level candidate described much harder dynamic programming problems. Expect the difficulty to vary.
Recruiter or HR screens follow. In the reports for this role, these are typically short and focus on your background, your interest in the role, and logistics. One candidate said that stating a preference for machine learning over general software engineering probably hurt their chances, so be clear about why you want this track.
The final stage is often described as a super day or a set of virtual rounds. Candidates report simple coding questions such as FizzBuzz, easy LeetCode-style problems, high-level system design discussions (one was a library management system), and fundamentals such as OOP, stack versus queue, Java, AWS, and Python tuples versus arrays. Another candidate was asked about sequence and ER diagrams and past projects, with little live coding. Have STAR stories ready, because behavioral questions came up repeatedly and one candidate said the interviewers circled back to similar prompts.
Timelines and communication are mixed. Some candidates described a supportive, well-communicated process and others described slow follow-up. One candidate reported a process that ran over two months and included an unplanned extra onsite step, so it is worth asking the recruiter what the next step is after each round.
Synthesized from 20 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 Vanguard 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 Vanguard
Design an automated pipeline for building, training, and deploying image classification models using S3 and EKS.
| Question | |
|---|---|
| Client Solution Pushback | |
| Index Fund Return | |
| Your Strengths and Weaknesses | |
| Choosing Between Python and SQL | |
| 2nd Highest Salary | |
| Employee Salaries | |
| Merge Sorted Lists | |
| Subscription Overlap | |
| Closest SAT Scores | |
| Empty Neighborhoods | |
| Top Three Salaries | |
| Monthly Customer Report | |
| Rolling Bank Transactions | |
| Find the Missing Number | |
| Maximum Profit | |
| Bagging vs Boosting | |
| String Shift | |
| Prime to N | |
| Comments Histogram | |
| Top 5 Turnover Risk | |
| Like Tracker | |
| Find the First Non-Repeating Character in a String | |
| Size of Joins | |
| Total Spent on Products | |
| Google Maps Improvement | |
| Rectangle Overlap | |
| P-value to a Layman | |
| Cumulative Distribution | |
| Top 3 Users |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report an online assessment as the first step, typically HackerRank-style data structures and algorithms under a time limit. Difficulty is described differently across reports, from basic to easy-to-medium, while one internship candidate faced much harder dynamic programming. One software engineer candidate also mentioned Java, AWS and OOP topics. Practice timed fundamentals rather than assuming a single difficulty level.
Candidates typically describe a recruiter or HR conversation after the assessment, and some report both. These calls focus on your background, what you have built, and why you are interested in the role and Vanguard. One candidate says that expressing interest in a different track, such as machine learning, may have worked against them. One phone screen also included a few basic technical questions, such as stack versus queue, SDLC and version control.
Several candidates report technical discussions that lean on fundamentals and past work rather than hard algorithms. Examples include Python mutability, tuples versus arrays, OOP concepts, Java experience, and sequence or ER diagrams. A few mention an easy coding problem or a high-level system design question. Prepare to explain what you built and why you made your technical choices.
The final stage is often described as a super day or a series of virtual or panel interviews that may mix an easy coding problem, system design, a case study and behavioral questions. Candidates mention STAR-style prompts, emerging technology, teamwork, and why Vanguard. Formats differ by candidate, and one reported a three-hour structure with a one-hour technical and a one-hour behavioral interview.
Outcomes in the reports are mixed, including offers, rejections, and candidates who declined. Some candidates describe clear communication, while others report silence or delays, and one reported an additional onsite step that was not in the original outline. Ask the recruiter about next steps after each round and plan for the timeline to possibly run longer than quoted.
