Product Manager applicants have rated the interview process at Salesforce with 3.2 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 69% positive. To compare, the company-average is 79.5% positive. This is according to Glassdoor user ratings.
Candidates applying for Product Manager roles take an average of 35 days to get hired, when considering 73 user submitted interviews for this role. To compare, the hiring process at Salesforce overall takes an average of 34 days.
Common stages of the interview process at Salesforce as a Product Manager according to 73 Glassdoor interviews include:
Phone interview: 28%
One on one interview: 24%
Group panel interview: 17%
Background check: 10%
Presentation: 9%
Drug test: 6%
Skills test: 3%
Personality test: 2%
IQ intelligence test: 1%
Other: 1%
Here are the most commonly searched roles for interview reports -
I applied through an employee referral. The process took 1+ week. I interviewed at Salesforce (San Francisco, CA) in Jan 2011
Interview
The initial referral was from someone working in product management; my own background is in protocol engineering and engineering management. We talked via email, and he forwarded one set of discussions to a senior person in their team; the senior person asked for an interview to be scheduled. The phone interview was quick, not highly technical and resulted in a scheduled one on one interview.
That revealed something fairly interesting. Salesforce has trouble dealing with highly technical people who are not currently coders. Their engineering managers & CTOs are all coders (or at least, they represent themselves that way). Someone who had designed and deployed large scale systems but hadn't coded in production environments in years was hard to fit into their world view. After the interview, it was clear that I was far too much on the technical side to fit their product management team. They went off to think about how to fit me in, but came back a week or so later saying "we'd like to find something that works, but we can't".
I suspect that had I said "of course I code" (and I certainly have done production-level code in the past), the result would have been a second set of interviews which might have gone further. I wouldn't encourage anyone to lie about their skills, but salesforce.com's view of engineering management as dependent on coding skills would certainly suggest not minimizing any skills you have there, should you be looking for engineering management jobs there.
Spent 1 month doing interviews with them only for them to tell me the role no longer exists and wasted my time.
It was about an interview every week, HR, technical, another technical then nothing until I followed up
Straightforward, standard questions by the book, nothing special or out of the ordinary. Classical PM questions, some were related to usage of AI in the daily work and to team management
I had a 30 minute phone screening with recruiter and then a 45 minute interview with the hiring manager. After that, I was told they would be in touch with next steps. 2 weeks later I received a rejection email.
Interview questions [1]
Question 1
What project management methodologies are you familiar with?