Pros: Aside from the product owners, the engineering group was very professional, easy to work with, and had some definite talent.

Cons: The management structure is very dated. Essentially all engineering teams are run by a Product Owner. The product owners sit in meetings and groom backlogs; they're not capable of contributing meaningfully to technical discussions. Some have a technical background, but within a few months, they're completely out of date on any given stack and are functionally unable to manage an engineering team. At that point, there's a real problem: software decision-making is entirely driven by non-technical staff. This, of course, is a perverse incentive. Instead of an engineer driving technical decisions, designing software, and innovating, the engineers have to effectively beg product owners for tasking (e.g., "Please let me solve this issue the right way"). Any incentive an engineer had to excel in their trade will quickly be exhausted by this poor organizational structure.

Pros: That amazing place where you can grow.

Cons: Nothing bad can be said about them.

Pros: C1 is fully in the cloud (AWS), so you may get to work with the latest technologies. There are pockets that push for the highest standards for engineering. Most teams offer stress-free, low-hour work.

Cons: Regulation stifles innovation, and this is strongly felt at even more tech-driven banks like C1. Typical pains of a large company. Change management teams and cybersecurity teams have too much authority. Obviously, a lot of great folks are there, but quite a few incompetent ones as well, sadly. This leads to a lot of extra, redundant, and tedious work to avoid escalations with management. Getting exceptions often requires VP approval, and many managers are afraid of doing this, probably due to the authority of these regulatory teams at C1.