Salesforce reviews

-Director is not technical which means he will only judge you on how much you can flatter him/ He is very rude and manipulates our personal space. -They will tell people to bring expensive gifts and don't return the money. - Director firstly takes people who are not good in english and then insults them in public - Time schedule is 9-6 where reaching on 9 is compulsory but they try to make you work at late night/ Salesforce gives time to work for NGO but director plans it in a way that its on weekend to ruin your weekend. - HR (Hyderabad and Bangalore) is his friend so no complain can goes beyond these people. - They harassed people way too much (insulting in front of everyone, pressurized for exams, Community work, attending trainings, making PPT for director/managers work, etc all together. - Director has divided his task to all team members and watches videos in office - Director and manager with his HR friends are always out for lunch (which I feel was our team's budget) and take us out once or twice to a really cheap place, infact we are not allowed to go out for lunch because according to director it is waste of time. - If you are away from your desk for more than 15 min, you will get messages and calls asking where are you and come back soon. -Get leaves approved by director is such a pain, he converts your sick leave into annual. - Recently they started dutching money everyweekend and take people for pubbing where they drink alot and half of the team doesn't drink, so they drink from employees money -If you think you can get transfer within salesforce to another team, it will take you minimum 2 years and only if you can flatter the Director by giving details of employees which he can use against each of the member of the team when he wants to, come by 9 to office, do his PPT, keep notes of everybody's time, and all demoralizing stuff only then transfer can start. There are so many things, in short Director is psycho and wants to control everything, he shows things differently to Tod(manipulates content).

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.