Pros: A few great co-workers (others just stab you in the back). Some great technologies you can learn for a short term.

Cons: 1. Lots of stress. 2. No work/life balance. 3. You should be your manager's pet!!! 4. Lots of talk about the company's culture, but nothing in fact. What you hear is not true, and what management asks you to do, you should NOT do (such as be vocal, do the right thing, speak up, and etc.). 5. Lots of betrayals. In fact, Capital One encourages this kind of behavior. 6. Performance reviews are done based on your commits' amount! (Lots of experienced people are overusing this by creating a huge amount of fake commits and contributions). 7. Support for other OS's such as Linux or Windows is a lie; only OSX is supported for development. 8. Huge dependency on the US team. Most of the time, you can't even contribute, change, or deploy code without US approvals. 9. Lots of delays in review processes from the US side. 10. Management has its own favorite people in teams and they listen only to them while they are talking about the flat team structure. 11. There is a huge difference between Senior and Principal roles, and Capital One's HR team can trick you with it. Don't fall into this. Renegotiate your salary if they change your title just before your start date, and expect that leads will expect a lot more from you when you are a "Principal." (And don't expect that someone will explain this to you on the first day). 12. Lots of micromanagement. They count your breaks and ask you to take fewer breaks, but at the same time, they expect you to be on call 24/7! 13. Canada's Software studio tends to follow the US almost everywhere. Lots of in-house frameworks (built in the US) on top of famous frameworks, which prevent you from gaining some fundamental knowledge.

Pros: To be brief: I’m working in the data outcome team. Pros: * Good atmosphere. * Lots of in-team and outcome team and enterprise activities. * Average standard perks, like private pension and private insurance (no dental). * People are nice; the culture is not toxic at all. * Quite flexible working time.

Cons: - Salary is quite low compared to the leading market. - Performance review sessions are not quite fair, as managers can be biased and misjudge people's performance. It is not about competency, but more about visibility. - Unfortunately, people who are decision-makers are not quite competent. - Knowledge is institutionalized in this environment, so they stick with internal standards rather than software engineering normal patterns or standards. - They say we care about delivery and quality at the same time. But in practice, delivery is all that matters. - As a Principal Software Engineer, you don’t have much control over the product or system you are designing. Policies are pushed on engineers. In other words, engineers up to the principal level are more coders rather than designers. - Developing in C1 is a pain for devs, as there are lots of controls and constraints, and paperwork is in place even for dev and sandbox environments. - As visibility is a key game-changer in getting promotion, people figure this out after a while and they try to focus on this side rather than getting the job done. Hence, not real healthy teamwork takes place in this environment. - Lack of correct processes is all over the place. - Disjointed connections are all over the enterprise.

Pros: Good benefits. Generous pay. Better work-life balance than FAANG.

Cons: Stack ranking Hybrid (3 days in office a week - could be a pro if you like going into office)