Great benefits.
Great remote flexibility for the engineering side of the house.
Decent work-life balance (assuming you don't have a bad manager).
Looks great on a resume.
A career dead-end for an engineer. This is not a place to learn and grow your technical skills.
Prepare to spend about 70% of your time dealing with corporate bureaucracy and maybe 30% doing real engineering work.
The organization as a whole is extremely close-minded and not open to new ideas, contrary to the value of "innovation".
Start treating your engineers like people and not resources. Do not assume that simply working for Salesforce is the only thing everyone at the company is interested in. People have career goals, aspirations, and interests beyond just the brand. Failure to acknowledge that is driving attrition. Most importantly, don't assume that you can hire managers with a "technical background" and use them to replace the expertise of your Principal Engineers, Architects, etc. Listen to your technical experts instead of ignoring them and pushing them out the door.
1. Phone screen with HR. 2. Phone screen with the hiring manager. 3. 1.5-hour coding test with 2 questions. 4. 5-hour onsite interview: 4 were 1-on-1, and the last was with a couple of team members.
I received a Java coding test with a single problem to solve. There was a countdown timer for three hours. I don't like coding tests with countdown timers, but the problem was an interesting one to solve, so I didn't mind it this time. The recruite
I applied online for the position. I was contacted by the recruiter and completed a HackerRank assessment. After that, I had a phone interview with one of the engineers. Proceeding that, I had an onsite interview with a mix of behavioral and technica
1. Phone screen with HR. 2. Phone screen with the hiring manager. 3. 1.5-hour coding test with 2 questions. 4. 5-hour onsite interview: 4 were 1-on-1, and the last was with a couple of team members.
I received a Java coding test with a single problem to solve. There was a countdown timer for three hours. I don't like coding tests with countdown timers, but the problem was an interesting one to solve, so I didn't mind it this time. The recruite
I applied online for the position. I was contacted by the recruiter and completed a HackerRank assessment. After that, I had a phone interview with one of the engineers. Proceeding that, I had an onsite interview with a mix of behavioral and technica