Pros: Great company and product, but there is a lot of politics.

Cons: Mid Management and Lot of Politics

Pros: Great pay. Great benefits. The entire technical side of the company prioritizes health and wellbeing.

Cons: Tech stack is miserable. New first-party technologies re-invent the wheel at every step of the way, creating bottlenecks for getting work out the door. Corporate bureaucracy completely blocks any kind of innovation or forward progress. Literally more than 80% of development time is spent doing some form of required "paperwork" before being able to complete the actual development work at hand.

Pros: Great day-to-day benefits. * Free onsite coffee shops, * Stocked breakrooms, * Meditation areas. Top-notch desks and workstations.

Cons: Daily work is entirely dependent upon the individual team. You may have a great one; I had the worst experience of my career of over 20 years. Technical knowledge is entry-level. Salesforce has combined the roles of testing and development/engineering. The result is testers are now responsible for learning how to program on their own. I had one gentleman ask me, after 3 months of programming, if methods can be called from other methods. Engineers are now responsible for testing. They don't do it and just sign off because they 'looked at the code.' On two different occasions, engineers repeatedly stated that specific features were tested and verified on test servers. Interestingly enough, those test servers had not yet been deployed. The 'testers' never even logged into the server. Staff compete for jobs unethically. The personal benefits are so good (pay, etc.) that individuals will lie about what has been completed to deflect investigation into other problem areas. The entry-level management are typically developers who have been moved into management with no training. During meetings, they will remote in while working on their own tasks or actually work on their own tasks at the table, often interrupting a meeting to ask a question or give directions about totally unrelated tasks. When asked why they do this, they will respond, "I wasn't running the meeting; it was for you." This often results in missed info and misdirected teams.