What is a typical working day like at Capital One?

Pros

Good salary, that's literally it

Cons

Job has been made permanent WFH so social aspect and perks are lost, terrible hours on rotating shift pattern, low morale and high turnover, nitpicky feedback, toxic culture amongst some associates

Advice to Management

Standardise hours, no need for rotating shift pattern or late finishes and weekends when other phone departments don't work those hours

Pros

Great benefits, great day shift schedules

Cons

There is No room for advancement

Pros

Great salary and great management processes Work from home permanently

Cons

Shift work between 8:30 and 9pm and weekend work

Advice to Management

Half days on weekends and varying shifts each day of the week rather than a whole week of each shift

Pros

You can learn a lot and grow your career in AWS Cloud technology. PTO package is good, pay is great, and people are awesome.

Cons

Depending on team you work with, late night code deployments and weekend support is not uncommon. Performance expectations with one team can significantly change with another team. While it's good to keep on the edge of technology, just when you get used to something they decide to change direction.

Pros

Terrific benefits Great atmosphere In a safe work environment Central location

Cons

Shift work Working weekends Hardly ever offered a 9 - 5 shift

Advice to Management

Listen more to what employees need to make them satisfied

Pros

good chance to learn experts in BAU

Cons

12 h/day shift in some of production support roles

Pros

True customer focus through all levels of management. Everyone is collaborating with the customers' best interests at heart. As a product manager I got to partner with designers, business analysts, data engineers, and of course my tech teams of 4-7 software engineers. Auto loans is organized into "experiences," each focused on a different phase of the customer's journey, and product managers get a high level of autonomy to develop new features and improve processes. My projects were engaging. People across job families were engaged in their work, smart, collaborative, and really nice. Also we're a good mix of a tech company and a bank: product and technology are at the focus of the company, but you still get banking holidays and log out at 5pm every day. I was in auto loans in the Plano campus.

Cons

There is a high level of change: I had 5 managers in the last 12 months. That's higher than average, but everyone seems to change managers at least once a year if not twice; either because the manager gets moved to a different team or because you do. My projects tended to get changed frequently as well: partway through a project, leadership would change the objective and ask us to focus on a different goal, abruptly stopping a 6- or 12-month project halfway through without us delivering anything. That happened enough to my projects and other product managers' to become a pattern. This all combines to a frustrating level of change when you have really interesting projects and would love to get them out to customers. My advice would be to start coding an MVP as quickly as possible so you can at least deliver something before priorities shift.