The interview panel was pretty chill and they really asked very good questions. There was a single coding question and most of the questions were on my previous work experience. It started with submitting my application, and after about a week, a recruiter reached out to schedule a quick introductory call. That first call was mostly non-technical — the recruiter asked me about my current role, experience with data pipelines and cloud tools, why I was interested in the position, and what my notice period and salary expectations were. It was fairly straightforward and relaxed.
After that, I was invited to take a technical screening. This was a live coding session over a shared editor and lasted about an hour. I had to solve a couple of SQL problems, including writing queries with joins and window functions, and then there was a Python task where I had to parse and clean a JSON dataset. They were looking for how well I handled edge cases and how readable and efficient my code was.
Once I passed the screening, I moved on to the technical interview rounds. The first one focused on SQL and data modeling. I was given a scenario about an e-commerce system and asked to design the schema for tracking orders, customers, and products. Then I had to write some queries to answer business questions based on that schema. It was challenging but manageable.
Write a query to find the top 3 products by sales in the last 30 days.
Given a table of customer orders, identify customers who have made repeat purchases within 7 days.
The following metrics were computed from 1 interview experience for the Vanguard Data Engineer role in Penn, Pennsylvania.
Vanguard's interview process for their Data Engineer roles in Penn, Pennsylvania is extremely selective, failing the vast majority of engineers.
Candidates reported having mixed feelings for Vanguard's Data Engineer interview process in Penn, Pennsylvania.