Morgan Stanley

Many things are done well at Shareworks:

1. As far as local talent goes (Calgary, AB), I think Shareworks probably has some of the most talented and intelligent developers in the city.

2. Developers can take on as much responsibility as they want. It can be a 9-to-5 job if you want it to be. It can also be a round-the-clock job if you want it to be. There's no lack of problems to be solved or improvements to be made. The people who have an impact on the organization are rewarded.

3. Leadership is dedicated to improvement and fairly transparent about what they want to improve and what will stay the same in a given timeline.

4. Learning and code quality are valued. Though this can be team-dependent, my experience has been that code reviews are thorough and time is given to devs to refactor and build a good solution.

5. There is a strong focus on sustainable workload. Management does a good job of ensuring the team isn't getting burnt out. They encourage taking PTO and actually unplugging during that time. This promotes a sustainable pace of work, etc.

6. You absolutely will learn at Shareworks. With such a large (and battle-tested) codebase, you'll learn about patterns that scale well and patterns that don't. You'll learn about the importance of tests and clean code. You'll learn about the importance of clear requirements. I don't care what point you are in your career; you'll learn something new here.

1. It would seem that the company likes to think it's hype-agile. To me, it seems there is a lack of a common product vision. Every few months, the top priority changes.

2. The tech stack is old. Shareworks is a monolithic application where the majority of the front end is written in GWT (a technology that Google EOL-ed in 2012).

3. There are a lot of manual processes that should be automated.

4. There is a serious lack of documentation on the product. Every time you need to do something new, you need to reverse engineer that part of the codebase.