Pros
In Support tribe, overall a good culture, helpful co-workers and understanding and qualified management. Tasks are up for the qualification. - Fairly unstressful corporative celebrations. - Good hardware for employees, comparing to companies I've worked at before. - Good WLB. Overworking is discouraged for non-management.
Cons
- You'll wave any rights for all code you develop while work contract with MTS is singed, even in your spare time. There are cases employees had to remove their personal githubs, in fear of a lawsuit. - OSS is out of corporate culture, and basically ignored by policies. There were some movements towards open source, but they are sparse and not noticeable. You can use free software as a tool, you can't use any free code officially (unless specifically approved, which rarely happens), even if MTS does not need to publish product code, for example, for internally used tools never published outside. - A lot of bicycles invented there. Mostly with square wheels and other rough edges. - Remote working is limited. Upper management's "one fit for all" solution is - 2 days at office, 3 days from home, weekly (which is combination of worst from both normal options). - Long approval chains without a reason. Upper management just clicks thorough approvals without reading, but if they are doing something else, approvals stop going. For middle managers, approvals is like a second job. - A lot of write-only documentation and reports. - "product culture" causes mistakes during planning to stay, poisoning life of everyone working on the product, and are rarely being fixed (because fixing them requires product re-approval) - Infrastructure is slow (heavy underprovisioning for servers, local AV and DLP for employee's PCs causing i7s to work like i3s at best) and isolated (from the Internet) - Employee's workstations settings provisioning is fear-based, bad both for security and productivity. - Because of the above, a lot of legacy and outdated software, both in working and for development - While network security is a requirement, product Security is an add-on, not a requirement. - Using security tools is denied, it's security officers' privilege. But their reports are lagging and outdated. - Security top management is out of touch. If you talk to them, they impose impossible and unreasonable requirements, like splitting repositories for dev and production environments (but never enforce them, so it's just imagination).