RepostedVanguard logo

Vanguard · OA → Phone screen

In process

Vanguard Tech and Risk Older OAs: 12 Experiences (Part 3 of 3)

Software engineer · InternshipNov 2019
Shared byjanebeingjane

Vanguard tech and risk internship and new grad reports from 2019–2020: 12 older OAs with string tasks and C# items, plus two quant-style risk interviews.

At a glance

  • Process (older format): an OA of about three easy coding tasks plus four multiple-choice concept items (H27, H28, H29, H31) → a 30-minute phone screen, often behavioral (H31, H34) → onsite (H31, H34, H37).
  • Asked in this period: string and anagram tasks (H27, H28, H31, H32), resume and "why computer science" questions (H31, H34), and for risk roles, regression and option-pricing theory (H30, H36).
  • Difficulty: candidates called the OA easy (H26, H27, H28, H29, H37); one could not get past O(N^3) on the anagram task (H32).
  • Note: every report here is from 2019–2020, so the whole part sits under History and outside current counts. For current reports, see Part 1.

Coverage: 12 Vanguard applicants (entries H26–H37), reports from March 2019 to October 2020: software interns (Application Development, College to Corporate technology, a software development co-op), SDE and entry-level developer new grads, and two risk-department candidates (H30, H36) whose interviews were regression, portfolio-risk and option-pricing questions.

In this series

  • Part 1: the OA question index for all 37 accounts and timelines 01–12.
  • Part 2: timelines 13–25, with a circular-array task, phone screens and a SuperDay.
  • Part 3 (current): H26–H37, the 2019–2020 reports.

History (before Nov 2023)

These 12 reports describe Vanguard's earlier process. Their questions stay inside each entry.

H26: Three theory items and two coding tasks

Report date: October 12, 2020 · Stage: OA · Role: Not stated

  1. The commenter called the assessment easy.
  2. Three theory questions: time complexity, sorting, and one they no longer remembered. Two coding tasks, easy to maybe medium, not named.

H27: A warm-up, two string tasks and four C# items

Report date: September 23, 2020 · Role: SDE, new grad · Stage: OA

  1. Three coding tasks: a warm-up, then two string-manipulation tasks. Some test cases were visible.
  2. Four concept questions written in C#.
  3. The candidate found it easier than bigger tech companies' tests. The tasks were not described further.

H28: Modulo, a hash table and anagrams

Report date: July 31, 2020 · Role: Application Development intern · Stage: OA

  1. Four multiple-choice questions and three easy coding tasks.
  2. Task one used modulo with an O(1) solution, task two a hash table, task three string anagrams. None were trees or graphs.

H29: Three plus four, again

Report date: July 30, 2020 · Role: Application Development intern · Stage: OA

  1. Three easy coding tasks and four multiple-choice questions, not named.

H30: A risk phone interview on OLS and portfolio risk

Interview: early April 2020 · Report date: April 22, 2020 · Role: Risk, new grad · Stage: Technical phone

  1. A resume walkthrough, then an internship project and what was hard about it.
  2. Regression: the assumptions, how ordinary least squares works, the formula for the coefficients, and what happens when assumptions break.
  3. How to evaluate a portfolio's risk: which dimensions, why, and how to calculate them.
  4. Factor and optimization questions also came up; their wording was not kept.

H31: A fast OA, then a 30-minute phone screen

OA: November 19, 2019 · Phone: November 26, 2019 · Role: Developer, entry level (new grad)

  1. OA: four basic Java items and three coding tasks: Water Hole, Username System and Group Anagrams. The candidate finished in about 13 minutes. They said the first two were basic course material with no matching LeetCode number, but did not describe them.
  2. The phone invite came November 25. The 30-minute call covered a resume walkthrough, why computer science, salary expectations and why Vanguard.
  3. They were invited to an onsite, which they did not describe.

H32: Remove later anagrams

Report date: September 16, 2019 · Stage: OA · Role: Not stated

  1. Keep the first word of each anagram set and remove the later ones. Example: ["code", "edoc", "doce", "ant"] returned ["ant", "code"].
  2. The candidate's pairwise approach, marking removed words as empty strings, was O(N^3), and they could not optimize it. The full sorting rules and limits were not shared.

H33: Alternating strings, an abstract car and high scores

Report date: September 15, 2019 · Stage: OA · Role: Not stated

  1. Three tasks: Alternating Strings, an abstract Car class, and High Scores, described as comparing counts.
  2. The string operation, the Car API and the High Scores output were not shared; the linked versions are practice adaptations.

H34: A C2C technology intern with a behavioral phone screen

Phone: August 15, 2019 · Role: 2020 College to Corporate technology intern

  1. After passing the coding challenge (not described), the phone screen was all behavioral: leadership experience and interest in computer science.
  2. The next invite went straight to an onsite, whose format they did not know yet.

H35: One task locked to C# or C++

Report date: July 24, 2019 · Role: Software development co-op · Stage: OA

  1. One task allowed only C# or C++; the others let candidates choose. The tasks were not shared.

H36: A risk interview on Black–Scholes and rates

Report date: March 2, 2019 · Role: Risk department · Stage: Technical phone · Result: No reply afterwards

  1. Black–Scholes: its conditions and variables, how the PDE is derived, and what delta is (the candidate first thought of delta hedging, then answered the derivative of option value with respect to the underlying price).
  2. How they think about volatility, including the volatility smile and what happens as time to maturity goes to zero.
  3. American vs European options, with the no-dividend caveat for an American call.
  4. A question about an "index" that turned out to be about rate concepts such as the short rate; the exact term stayed unclear. The interviewer suggested CFA study.

H37: Some failed tests, still through to the onsite

Interview: 2019 · Report date: July 30, 2020 · Role: Application Development intern · Result: Rejected after onsite

  1. The assessment was easy, though some tests failed. A phone interview and an onsite followed, then a rejection. No tasks were shared.

Patterns across the reports

  1. Three coding tasks plus four concept items. H27, H28, H29 and H31 all describe that OA shape; H26 instead listed three theory items and two coding tasks.
  2. Anagram tasks. H28, H31 and H32 each had a string-anagram task, in different forms (grouping in H31, removal in H32).
  3. Risk roles were quant theory. Both risk interviews (H30, H36) were regression, portfolio-risk or option-pricing questions, not coding.

Common questions

What was on the Vanguard OA in 2019–2020?

Usually three easy coding tasks plus four multiple-choice concept items in Java or C# (H27, H28, H29, H31).

What does the Vanguard risk interview ask?

Quant theory: OLS assumptions and portfolio risk in H30; Black–Scholes, volatility and American vs European options in H36.

Was the Vanguard phone screen technical?

In H31 and H34 it was resume and behavioral questions; the risk screens (H30, H36) were technical.

Keep practicing

In this series: Part 1 · Part 2 · Part 3 (current)

Sources: Anywhere useful interview info can be found.

0 total reactions. Your reactions: none.
0 comments

Comments

0

No comments yet — be the first to share what you know.