What is typically worn or allowed to be worn at work at USAA?

Opportunity for performance bonuses. Good benefits. Relaxed work attire.

Favoritism is rife within management. KPIs continually shifting. Employees demotivated. Focused primarily on the $ and neglects employee wellbeing.

USAA has beautiful facilities with a lot of amenities, include quiet rooms, multiple food shops and relax outdoor areas to work in. As well as good benefits including on site clinics, ample paid time off and a relaxed dress code.

USAA's culture is extremely toxic unless you fit into a very specific personality type and they're very unwelcoming to neurodivergent individuals as well. If you don't fit the expected personality type they'll either beat you into submission or make you so miserable that you quit on your own. Additionally they expect a toxic level of competition between employees, to the point it felt like the hunger games. Lastly they've fully embraced the unassigned open floor plan for the IT staff making focusing on a task very difficult because of the constant noise and interruptions.

Full benefits Decent pay for San Antonio although city is more expensive now Home office is nice and had good food

So much bureaucracy is felt impossible to get code implemented. Never talked to business partners because they were never available or seemed uninterested in IT projects. Every code change had to go through so many hoops that many programmers stopped working altogether and just talked about work making life harder for those who were trying. Implemented agile incorrectly and made developers go to hours of meetings a day. If things weren't going well then the solution was almost always to implement more meetings so even less work got done. Locked down Jira so developers had to follow strict rules when working in Jira tickets otherwise they would be marked as being out of compliance and would be in trouble with management. Locked down all features of new products-like Snowflake-so developers couldn't take advantage of what these products offer. If work didn't get done it was always assumed to be the developers fault and never the fault of the hundreds of managers, project managers, scrum masters, business product owners, architects, and tooling teams that conspired to make it impossible to get any work done. Tried implementing best practices but didn't involve developers so things always got worse and they were never successful removing roadblocks for developers (such as refreshing development databases with good data). Architects, tech leads, and managers would talk about concepts such as AI, streaming, cloud computing, but they had no idea about basic things such as data modeling or whether the data in their database was actually used by anyone or if it was even valid data. When code did get implemented, it would almost always break or get rolled back because automated testing was never implemented and because no one ever talked to their business partners about requirements and often developers barely even looked at the data. Company was always in trouble, and in the news, and getting fined for not following banking and insurance regulations. Although that wasn't surprising since they tracked their employees constantly but didn't track basic things that could have actually helped such as data quality. Company hired too many developers, didn't set them up for success, and then had many rounds of layoffs as a result.