Taro Logo

Member of Technical Staff (Software Engineer) Interview Experience - San Francisco, California

January 1, 2017
Positive ExperienceGot Offer

Process

The interview process took a couple of months to complete. The process consisted of an hour-long phone screen, followed by a two-hour remote programming test (RPT) assessment, and ended with a five-hour on-site interview. My process took a couple of months because we were trying to figure out a schedule that could work for both of us. In addition, they had to reschedule the RPT because the engineer was pulled into a critical issue, pushing the RPT back by two to three months. I had the on-site interview three weeks after my RPT and received the offer the next day.

For the on-site interview, each session consisted of two engineers (one QA and one Dev). The first 30-40 minutes of each interview focused on design and algorithm questions, and the last 10-15 minutes were dedicated to QA questions regarding the designs I had proposed. Salesforce has recently combined the QA and Dev roles into one, calling it the 'hybrid' system, thus each interview consisted of an engineer from QA and Dev.

In the end, it was a great experience, although the process was a bit long.

Questions

Design a library catalog.

Was this helpful?

Interview Statistics

The following metrics were computed from 4 interview experiences for the Salesforce Member of Technical Staff (Software Engineer) role in San Francisco, California.

Success Rate

75%
Pass Rate

Salesforce's interview process for their Member of Technical Staff (Software Engineer) roles in San Francisco, California is incredibly easy as the vast majority of engineers get an offer after going through it.

Experience Rating

Positive50%
Neutral25%
Negative25%

Candidates reported having very good feelings for Salesforce's Member of Technical Staff (Software Engineer) interview process in San Francisco, California.

Salesforce Work Experiences