There are a ton of awesome and really smart people at Capital One.
Generally, there is good work-life balance. If you like to coast and work 35-40 hours a week, you'll be able to find a team to accommodate.
Management makes it really hard to get things done as a software engineer. There are seemingly endless hoops to jump through to meet compliance standards. Often, the compliance standards aren't well thought out and are not flexible enough to meet the needs of the diverse set of applications being developed at the company.
Every tech project essentially becomes waterfall as a result due to an insistence on project timelines, complicated compliance processes that become blockers, and endless business justification for even small decisions.
Reorgs are frequent, and political battles between senior management lead to major consequences for associates. Because of this, it can be hard to develop relationships with direct reports and managers.
My only other gripe is that performance management isn't an intelligent process. Essentially, every team under a director is forced to rate their employees on a bell curve; the top x% get promotions, and the bottom y% get bad reviews.
This system incentivizes team members on good/productive teams to transfer to unproductive/poor teams if they want to get a promotion. You could have a team of rockstar engineers delivering awesome applications, and only one will get a single promotion, while another team that can't put a simple data pipeline together will get the same amount.
Move away from the stack rank, emphasize delivery and team success over individual bell curve ratings (bonuses and promotions for delivery).
Compliance processes should empower engineering teams to build great products, not restrict them. Don't just pay lip service to agile; commit to it. Change the business's mindset from timelines and planning to prioritization and delivery. Most importantly, accept failure as a possibility and enable teams to take on big, scary ideas.
The interview process involved several stages: * An initial screening call. * A timed coding assessment completed via an online platform. * More contact with the recruiter/liaison to discuss prep materials and strategy. * Finally, a series o
The process started with a recruiter screening call and a code test. The next step was a one-day interview at the office, meeting with hiring managers. The interview felt depersonalized and did not allow for the interviewee to talk with potential co
The HackerRank test was extremely easy. You had a choice of language to code solutions for three problems in two hours. This was followed by a half-day of in-person interviews. Be confident and ready to do some serious brown-nosing.
The interview process involved several stages: * An initial screening call. * A timed coding assessment completed via an online platform. * More contact with the recruiter/liaison to discuss prep materials and strategy. * Finally, a series o
The process started with a recruiter screening call and a code test. The next step was a one-day interview at the office, meeting with hiring managers. The interview felt depersonalized and did not allow for the interviewee to talk with potential co
The HackerRank test was extremely easy. You had a choice of language to code solutions for three problems in two hours. This was followed by a half-day of in-person interviews. Be confident and ready to do some serious brown-nosing.