Pros: Management is great. The team is great. The pay is great, and the benefits are great. Just great.

Cons: I like it here; no cons at the moment.

Pros: * Decent salary * Health insurance * Nice equipment * Good outings

Cons: 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 handles 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. Never mind 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 change (SRE don't execute changes; they're the gatekeepers). Super boring! The third, fourth, and fifth roles handle 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 job sites. 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.

Pros: - Team (the peers on my team were awesome, but all management was awful) - Compensation (you end up paying for it in the long run) - Benefits (comparable to other large companies) - ESPP was nice - Snacks (yay?) - Swag (if you enjoy being a walking advertisement)

Cons: - Work-life balance is terrible. - They took the alcohol away because they hire alcoholics. - Everything is a snowflake and not scalable (they will eventually figure this out, and it will hurt when it matters). - Incompetent management (mid and senior level - how are these people getting hired/promoted?). - Too much management, so nothing actually gets done. - CAB/change management is incompetent. - Dev does not seem to know how to make their products stable or supportable. - Infrastructure does not seem to know how to make their environments stable. - Meetings (let's have a meeting about a meeting, and we will schedule a meeting to discuss the meeting). - Internal Salesforce recruiting/hiring is worthless. - Indy Tower move provides no benefit to employees and worsens work-life balance. - Commute worse now since the move to the ivory tower. - Pay for your own parking (penalized for not living in the city). - No real room for growth within Marketing Cloud for SREs. - Worst career decision I have made from a skill set perspective (no marketable skill set growth outside of the company). - Company liberal agenda constantly shoved down your throat. - Employees placed into a silo. - Mandatory holiday work for Marketing Cloud so other companies can send more spam to people who do not want it. - SRE team mandatory weekly on-call rotation recently went from 4 weeks/year to 15 weeks/year (yes, seriously, and that is the main reason I quit Salesforce for a real #dreamjob elsewhere). - The company itself provides no real benefit to society, so they allow employees to volunteer to feel fulfilled on the inside, but really, it is a thinly veiled attempt at marketing and promotion of the company. - Stressful workplace. - Job titles are made up. - Open office concept is detrimental to productivity and health in general. - Cult feeling with all the internal lingo. - Ridiculous amount of money spent on unnecessary things, but then they take away the small amount of money they contributed to parking costs, which is a necessity. - Giant corporation now... culture cannot keep up with acquisitions. News flash: people are different in different parts of the country and the rest of the world. Company needs to just admit they are the same as other giant corporations. - No longer feels like an innovative/entrepreneurial/start-up company (Now we just buy those kinds of companies, even if it doesn't make sense. I'm looking at you, Quip.). - The company has never told a customer no, even when they needed to do so, and the company is feeling it. - Company seems to reward bad client behavior instead of correcting it. - I am tired of typing, but there are definitely more cons than pros.