Salesforce reviews

These cons are related to the Site Reliability structure. Some other structures may have similar issues. To begin with there is actually no SRE job per se, It's actually a NOC position. Originally Salesforce had a NOC to handle incidents etc but under new management the goal of the team changed. The new goal was to automate their way out of trouble. Unfortunately this got as far as changing the name of the team to Site Reliability but not much else. When I interviewed (a lengthy process indeed) I was under the impression that the majority of the work would be engineering and analysis with firefighting and root cause analysis thrown in. This piqued my interest but when I actually joined the actual job was very different. Picture this: You are one of a team of 4 or 5 "SRE" (I emphasize the quotes) and each of you handle a different role each day (10 hour days x 4 days a week....weekend work also which sucks the life out of you). The first role which is the worst is the console operator. You are made to watch a console with many different alerts coming in from thousands of systems. It's your job to watch this for 10 hours, click and confirm each alert[hundreds in a day) and create tickets and escalate as necessary. If you miss an alert which escalates to an issue be prepared to be chewed out by your manager and anyone else who wants to blame you. Nevermind the fact that you were staring at several hundred alerts for the past 5 hours and just slightly tired! The second role does the same as above but stares at email and the chatrooms for any engineers who want to execute a chance (SRE don't execute changes, they're the gatekeepers). Super boring! The third/fourth/fifth roles handles escalations from the others although if it involves networks or databases they go straight to different teams. The most complex issue you would probably investigate is a server falling over. There is little time for actual software engineering as much of the time you will be closing the many many many many silly tickets that were opened. If you do get to carry out some scripting, be prepared to get pulled off to cover for incidents (of which there are plenty), time off or go through hoops to get your change implemented. If you get to do this role then you will probably spend most of your time looking at jobsites. Plus Salesforce is so big someone is probably working on your idea. Want to fix monitoring? There's a team for that (M&M). Want to build automation? There's a team for that (DCA). Want to build tools for your team? There's a team for that (SRE Tools). All that is left is incident management which itself deserves an entire post. I realized my mistake in joining the team after 2 months. It took me a long time to get out as I had lost valuable skills while there. If you want to join Salesforce then I would recommend the Operations Engineering division.

There is no culture at all. Ohana, VTO, Customer Success... They are just words. In my team, we were obliged to work on bank holidays and not allowed to take the day back off when it was BH in the country we covered. There is no flexibility in WFH. But what's really the worst is the management. In Salesforce there are no leaders, just poor managers. It all works around internal politics and friendships with people crossing borders continuously. Also, those "managers" text you after working hours and have no respect of your personal life. There is no interest in who you are as a person or your background, just how much you're closing. It's the least human company in tech I have ever witnessed and keeps losing talent year over year. I had a burnout and had my manager talk poorly and joking about me with team members and peers. Just one last thing, AEs are pushed to always complain about business partners (Solution Engineers, Sales Dev and Customer Success) when they really are the only ones to make the job qualitative and worth it.