Wells Fargo reviews

You are on the bottom of a toxic chain of micromanagement. You are not there to help customers. You are there to convince customers to sit down with bankers so they can bring in more money. Due to the scandal, Wells Fargo is very strict about the verbiage used to accomplish this. You will be coached on every interaction with every customer and have daily one on one meetings with your supervisor about why you are not meeting expectations. The branches are audited more often than necessary and you will be constantly quizzed about policies and procedures. Wells Fargo hires "behavior influencers" (yes that is a real job that people get paid six figure incomes for) who come into the branches to police bankers and tellers alike. Unrealistic expectations up the wazoo, results are expected within a week. Exempt employees are being told they are not entitled to a lunch (not true). Aside from referring customers to bankers, what they want most from you as a teller is to divert customers to the ATM or the app. Some banks are already going teller-less. This trend will spread until human tellers are a thing of the past.

- Leaving misleading positive reviews to fool prospective employees. - Waterfall disguised as Agile. They're not fooling anybody. - Awful code quality process. There's a checklist of requirements that changes constantly for reasons nobody can specify. Things don't get deployed until the entire application is completely finished, which in software engineering means never. Nothing is ever finished. This results in deployments of massive chunks of code, which we all know is more risky than deploying completed bits and pieces. - Forcing employees to come into the office when the teams they work on are spread across the globe. So employees go into the office for "face time" on Skype and Teams. A stated reason for making everyone go back into the office was so we can chit chat and build professional relationships with people not on our team, but of course nobody's given the time to do that. You're booked constantly with meetings so every bit of non meeting time you get you dedicate to doing your work. Also not everybody is interested in chit chatting with people they don't work with. In short they only want you back into the office because, unlike smart managers, they care about the time your butt is in the seat not the work you get done. - extremely unstable development environments. - Excessive amount of documentation, duplicate documentation, and out of date documentation - 200 hour SLAs. Really? SLA? There's no reason to have this anymore. And did I mention 200 hours?! Just get the ticket and work on it! Most of the "engineers" that pick up these tickets are off shore, and on multiple occasions they waited until the 200 hours is almost up to start work on the ticket, but they don't know what to do so they "work" on it and then immediately mark it as done thereby resetting the 200 hours. Of course they aren't real developers so they don't know what to do, but now they're given an additional 200 hours to complete their work. They do all of this without once reaching out to the person who made the request. Very unprofessional. - Dev teams are told we MUST do agile (even though it's not agile) so we're all working on 2 week sprints, yet every little thing we want to do outside of our local machine requires a 200 hour SLA ticket to be submitted. I'm not that good at math, but 200 hours is way longer than 2 weeks. - Everything requires a stupid ticket, which has a 200 hour SLA attached to it. And the "developers" that pick up these tickets have no idea what they're doing. You need to call them and walk them through exactly what to do or else they won't know, but you're not allowed to do it yourself. Not even in the dev environment. This is how I had to instruct one of the "devs", "You need to go to this URL. Ok, now click on login. You need to enter your credentials. No I can't see what your password is so you can go ahead and type it in the password input field." I wish this is a joke, but it is not. And what did this "developer" need to do that I had to give such detailed basic instructions? He needed to update environment variables, which should've taken no longer than 5 minutes, but they took the entire 200 hour SLA to complete this task... It's sad. -