How did MST transition from having smart, hardworking folks about a decade ago to the s**thole it is today...quality of engineers has gone to dust and the current crop is unwilling to problem solve
3 replies (most recent on top)
The entire QCT test management org is circles within circles within circles. If your code passes your unit test, you need to get it validated. You go to a different manager to get the code integrated. Then a different group comes in and does an integration test. Then a different group comes in and does a product level test. Then a different group does a subsystem test (like MST does, as the name suggests, Modem Test). Do you realize the hoops you gotta jump to dispatch one bug fix? The worst experience is with MST. You need to do a function validation, there is a director who passes it on to a senior staff, and so on an eventually a contractor in QIPL will execute it. Then if you need performance validated you need a different director. If you make a mistake and address it to static performance director instead of dynamic performance director, it goes into a black hole. Worst case is customer validation. As MPSS dev team, you keep taking hits from CE, customer, internally within MPSS, etc and finally MST.
DEI is also a factor. Pushing hiring based on skin color rather than merit. Q deserves to go down for being woke (Su-king that Blackrock and Vanguard zio d!ck)
A decade ago, QCA already had many senior directors, directors, and principals. Management only hired people who are also from their own countries or regions, assigning over 90% of the workload to a single employee. Meanwhile, the remaining team members—often over ten people—would mock and bully the overburdened engineer. During performance reviews, they lied about employees' contributions and capabilities. Personal errands were frequently run during work hours. Don't even mention the slew of supposedly zero-tolerance behaviors that were routinely ignored within the team.