I can't imagine much better work life balance.
Benefits are good, and it is the best 401k plan I've ever seen if you stay until it vests.
People are generally very nice.
Because of the first con I listed, moving up is pretty easy (at least to a certain extent), and it's pretty easy to stand out here.
Generally, I think everybody here believes in what they do and are aligned to the company's values.
If you're looking to settle down and just coast into retirement, this is a great place to be a developer.
Too many people here are very bad at their jobs, during my time here I worked with the worst developers I've ever worked with. There are some really great developers here, to be sure, but a lot of very bad ones too.
You don't actually get to work on much. Separate teams own nearly every part of your stack. This may sound good on paper, you're only responsible for your application code, but the mandated infrastructure can be sub-optimal/unstable/poor-fit and finding issues is a nightmare when things go wrong.
Way too much of a focus on education. There are some teams (particularly more in the research space) that will only recruit at Ivy League schools and because of it we'd get bottom of the barrel candidates (we cannot compete with hedge funds/ big tech for that top talent). Anybody who places such a high focus on where you went to school, and not what a candidate can actually do, clearly doesn't know how to actually judge talent.
Many senior leaders don't have a background in engineering. Obviously only a problem for those leading engineering teams, but it is alarming. There are exceptions, and some come from more of the IT side (meaning technology but not developing), but Vanguard has this weird philosophy where they seem to think any senior leader can lead any team. If you don't understand what you're leading, you are probably a terrible leader. Even those with IT backgrounds, many think, "oh I did IT for 2 years so I know what I'm doing", sure, but 2 is not much experience. I once overheard a senior leader say to a lead dev on my team, "It's not my job to understand what you do, it's your job to teach me", massive red flag.
Enterprise architects often decide how we should build things despite not having built real software for 10+ years in many cases. They don't always understand the intricacies of what is required and it leads to a lot of sub-optimal solutions. This is not an issue on all projects, and mainly seems to affect projects led by long time Vanguard vets (see next point). Whenever I worked on projects like this, I often found myself speaking up a lot more to try to steer the ship in a different direction.
Things are done "the Vanguard way". There are a lot of people in high roles in technology who have been at Vanguard for 20+ years and they only know what they've done at Vanguard. You have to push hard for change. This also leads to them not understanding more modern technology, even at a basic level. Specifically things like cloud security, etc.
Everything needs multiple layers of approvals and reviews, not a bad thing in and of itself, but it brings development to a snail's pace. Deploying a simple app or API will take a month or more instead of a few days at other places. Leads to lots of doing nothing waiting for approvals to happen.
Success theater is rampant. A lot of folks here think they are doing ground breaking work and love patting themselves on the back but it is still not keeping up with industry trends (the mobile app for example is laughable).
Base comp is on the low side of average for the area. Part of that is made up for with the 2 bonus system and they do have good benefits. Personally I would rather just have higher base comp though.
Get real engineers in the door to actually lead engineering. MBAs with backgrounds in finance are not the people to lead software developers.
Vanguard is obviously a well respected financial company, but hiring for developers needs a complete overhaul if you want to propel Vanguard into more of a digital finance company. We are behind our competitors (Fidelity, Schwab, etc.) in the space when it comes to technology and I don't see us closing that gap if we continue on the current path.
The format was face-to-face in a roundtable. There were multiple questions from the group. It lasted about 30 minutes. The tone was formal, and I was dressed in a suit and tie. They asked general questions about development within the platforms with
Very basic. You will be called to come on campus for a quick interview. First round will cover behavioral questions. The second round (on the same day) will be with a technical manager. He/She will basically ask all textbook questions (including some
In person, most of the questions are related to core Java and they are very basic. You should be able to explain your experience well. They will ask you questions about standard Java practices.
The format was face-to-face in a roundtable. There were multiple questions from the group. It lasted about 30 minutes. The tone was formal, and I was dressed in a suit and tie. They asked general questions about development within the platforms with
Very basic. You will be called to come on campus for a quick interview. First round will cover behavioral questions. The second round (on the same day) will be with a technical manager. He/She will basically ask all textbook questions (including some
In person, most of the questions are related to core Java and they are very basic. You should be able to explain your experience well. They will ask you questions about standard Java practices.