Pros: Work/life balance is the best I've ever had. Deadlines are generally pretty lenient as well.

Cons: The annual review process uses stack ranking, which I think is the root cause of one of the most passively toxic work cultures I've been a part of. Teams put forward a great front of working together to solve problems, but once the review cycle hits, it all boils down to how much your manager likes you as a person. Innovative engineering and extra effort spanning the whole year take a back seat to how much you've stroked your upper management's ego over the year. I've seen fantastic engineers get poor ratings due to not flashing their accomplishments, while subpar engineers get promotions from knowing how to run their mouths about doing the most trivial tasks to seem impressive to management. Overall, it's an incredibly stressful environment for employees who care about improvement rather than boot-licking.

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: Great for work-life balance.

Cons: It's a job, I guess.