I joined right out of college in 2010, and it was a good decision. The stable salary, benefits, and work helped me get my footing, and get experience in the industry. Working in finance also taught me a lot.
As a large corporation whose industry is not technical, Vanguard does not fully understand what role it wants for its full-time devs.
Vanguard's position in the industry is, simply, "to be the Wal-Mart of investing": high-value (though low costs and consistent returns), accessible to the public, and very efficient in operation. As of this review, they are succeeding wildly, with trillions of dollars in investments. This model is based on being conservative with money and not taking risks, which means that Vanguard tends to follow other companies only after success has been proven.
If you work in tech at Vanguard, you will likely be working on either their Java-based web servers, or their COBOL and SQL based data center. There are rare occasions where a project works with new tech. The tech direction is primarily maintenance and stability for the existing codebases.
On a personal note, I left Vanguard because my roles had started to shift away from software development and into project management for other divisions in the company and its outsourced teams. I had a bad experience where a simple project (roughly 1,000 lines of Java midtier code) was outsourced, and took 4 months to complete with the additional overhead.
Take a serious look at how IT is managed. The heads of the IT branches may have IT experience, but they all felt out-of-touch with both current technologies as well as Vanguard's current codebase. Trust your professional FTEs to make technical decisions without being vetoed by the business side of the company. Invest in transitioning to new technologies, especially in your ledger and data storage.
I know that there is no incentive right now to change, but fostering an experienced and satisfied in-house team will pay for itself if a catastrophe were to ever strike. It is very difficult to both save costs by outsourcing while simultaneously having employees with a deep technical understanding of Vanguard's codebase and domain.
The interview process was very informal. Make sure you study up on OOP. You will not have a successful interview if you don't know what OOP is. Understand the 4 pillars and be able to discuss them.
After applying there were two interviews and one coding challenge. One interview was to get to know the applicants personality and conversation skills. The second interview was a tech interview in order for the company to test your knowledge, progra
Solid, flew me out to interview in person, multiple rounds, everyone was very friendly and open, nothing technical, just basic structure questions and answers about programming strategies and fundamentals. Ended up declining but that was purely locat
The interview process was very informal. Make sure you study up on OOP. You will not have a successful interview if you don't know what OOP is. Understand the 4 pillars and be able to discuss them.
After applying there were two interviews and one coding challenge. One interview was to get to know the applicants personality and conversation skills. The second interview was a tech interview in order for the company to test your knowledge, progra
Solid, flew me out to interview in person, multiple rounds, everyone was very friendly and open, nothing technical, just basic structure questions and answers about programming strategies and fundamentals. Ended up declining but that was purely locat