Pros
- When you aren't working nights and weekends, good work/life balance. - Allowed for some of the internal tools we built to be open source. - Pretty open to new technology given it has a reason to use it. Open to be able to test it out as well if you see fit.
Cons
- Revolving door of requirement changes. Product Managers without a clear idea of what they want built. - Very frequent and disruptive requirements changes without extending or changing deadlines. - Drastically under market pay for expected work. - Severe lack of growth potential. No process at all around this and it's really just at the whim of the office director. No transparency at all and you only have one chance in a year to get a raise/promotion. - Work/life balance is never stable. Sometimes its fine, other times you have many months of very little work/life balance. To be fair, this seems to be improving. - Any sort of valid criticism to code or architectural decisions is seen as "complaining". - Engineering is not included in meetings that determine how long a particular feature or product will take to build. Yet, you are forced to meet deadlines regardless, even if that means your nights and weekends. - Toxic culture. The culture here has drastically changed under new leadership, the prior leadership was under the helm of Brandon, which was much better. - PR/code standards at this office are grossly unequal. - Really poor leadership. - Not enough senior developers to truly mentor and help grow the big number of junior developers. Also lack of leadership hurts juniors as well.
