Getting an Interview
Getting an Interview
Interviews for Top Jobs at Salesforce
- Sales Representative (39)
- Account Executive (32)
- Software Engineer (23)
- Sales Engineer (17)
- QA Engineer (16)
- Senior Account Executive (15)
- Senior Software Engineer (15)
- Member of Technical Staff (12)
- Business Development Representative (11)
- Senior Member of Technical Staff (10)
- Enterprise Business Representative (9)
- Sales (8)
- Solution Architect (8)
- Intern (8)
- Lead Member of Technical Staff (7)
- Account Executive - Small/Medium Business (SMB) (7)
- Product Manager (5)
- Marketing Manager (5)
- Customer Success Manager (5)
- Engineering (5)
- Senior Sales Engineer (4)
- Director (4)
- Engineer (4)
- Software QA Engineer (4)
- Sales Support Engineer (4)
- Product Marketing Manager (4)
- Member of Technical Staff (Software Engineer) (3)
- Senior Engineer (3)
- Senior Manager (3)
- Accounts Executive (3)
I applied through college or university. The process took 1 day – interviewed at Salesforce in November 2014.
I was asked to go onsite for the intern interview. The university recruiting took a day, and around 30 students. No tech questions(are you kidding me?). They spent most of the time to split the students into groups to do group exercises. And check if you talk a lot during the process.
They also assign you to different groups and ask you to do presentations on your imaginary products. Then the interviewer asked you questions about your products. One of the interviewer focused on that our product may not make customer happy.. OMG I am not here for sales positions.
I am very curious what the hell are they doing, how can they come out such stupid onsite activities for a software engineer major student. I have other interviews with Google, Facebook, so that day looks like a waste of time.
If the HR or hiring manager could see my post, I just want to ask one thing: you ask nothing about tech questions for a CS major student, but focusing on all other group stupid things, so are you wanting to hire a person that talks a lot but knows little about coding?!!!!!
Before interview, I have a good impression about this company, after the interview, I feel very disappointment and I don't think it's a place for anyone that has passion in technology.
- The most ridiculous and stupid interview I have ever experienced. They are not looking for a tech person, they are looking for a sales person who could talk a lot to make them happy Answer Question
Reasons for Declining
I found the company's culture is so stupid
Other Interview Reviews for Salesforce
Engineering InterviewAccepted OfferPositive ExperienceDifficult Interview
I applied online. The process took 3 days – interviewed at Salesforce (San Francisco, CA) in November 2011.
I had two one hour phone screens followed by an in-person interview. The phone screens were fairly rigorous and included a fizzbuzz. The interviewers were friendly and professional, and they squeezed a lot of questions into the hour. I received feedback within 48 hours of the first interview, and after the second interview I was told they would bring me in for an in-person interview as soon as the hour ended.
Afterwards, they told me that they had high failure rates for the in-person interview, so they instituted a new process of requiring two phone screens instead of one, and shortening the in-person interview from 6 hours to 4. I don't know if this is company-wide, but I like the system.
The in-person interview was a combination of panel interviews (e.g. two engineers asking me questions) and the more senior people did one-on-one. They asked questions specific to the domain knowledge on my resume as well as some general questions specific to their own environment. There were also some algorithm questions/problems. Most of the time I was on my feet at the whiteboard. The interview was very thorough, no inappropriate questions were asked. Some of the questions/puzzles were quite creative and I enjoyed working through them. Had a great time and wished the interview would last a bit longer as the puzzles were interesting and had multiple levels and/or multiple solutions. I think part of the interview process was to see how far you can get in the time allotted.
- route-finding problem for a robot that cannot store internal variables. Answer Question
Engineering InterviewNo OfferPositive ExperienceAverage Interview
I applied through an employee referral. The process took 5 days – interviewed at Salesforce (San Francisco, CA) in August 2010.
Very pleasant actually. Met with multiple groups informally over lunch and a few one on one discussions with group leaders.
Engineer InterviewNo OfferNeutral ExperienceDifficult Interview
The process took 1 day – interviewed at Salesforce (San Francisco, CA) in August 2010.
Engineering InterviewNo OfferNegative ExperienceDifficult Interview
I applied through an employee referral. The process took a week – interviewed at Salesforce in January 2008.
Slow interview process. Interviewers seemed organized but cold.
- Solve a coding problem in Java. You're given a laptop and 2 hours. 2 Answers
Engineer InterviewNo OfferNegative ExperienceAverage Interview
I applied through an employee referral. The process took 1 day – interviewed at Salesforce in September 2010.
At first the hiring manger asked questions from my resume. about the projects and work experience. then he started asking me java and c++ question.
abstract class, templates, exception handling, finally block, what if there is no catch block and there is only finally block.
asked about a testing question. write test cases for a command to find the repeated words in a file. the output should be word, count of the words. if the file is 1GB how will you make sure the result is correct.
question related to sql-> joins, queries
function overloading, over riding,
Engineering InterviewAccepted OfferPositive ExperienceAverage Interview
I applied through a recruiter. The process took 3 days – interviewed at Salesforce in April 2010.
- Given a webservice , how do you go by testing it? Answer Question
You should be really good at negotiating.This is the right time for negotiation.Once after joining, the changes would be very minimal.
Engineer InterviewNo OfferNegative ExperienceDifficult Interview
I applied through a recruiter. The process took 2 weeks – interviewed at Salesforce in October 2009.
I wish I could write good things about this company because I really wanted to like them.
Almost all of my interviews were phone interviews. Everything seemed to be going just fine and we scheduled an in-person interview. I got great feedback from the people who had done the phone interviews. To be fair, it was engineers interviewing other engineers and they did a bad job of it.
Furthermore, the recruiters were sloppy about the scheduling. They made mistakes with several of the dates and left me hanging on more than one occasion. That should have been my first warning.
For one, I got asked a lot of the same questions by interviewers. A lot of the questions were related to whether I could solve (in my head) a problem that had vexed them for some amount of time recently. Many more questions were of the "trivia" variety. Some of the questions were about my particular skills or my background but the interviewers seemed to be doing their best to be "Googley" in their process and try to make the interview about how smart a particular candidate is. I don't particularly like the "battle of wits" style on interview (mainly because it's hard to capture the subtlety of some problems in that environment, and because there is no way to tell someone nicely that they are wrong about a particular answer they think is right) and I guess that put me on a bad footing.
My in-person interview was a disaster. For one, there was no HR rep to greet me. I arrived at their office to find a gang of people hunched over cubicles and staring at screens. It didn't seem to be a great working environment compared to what I've been used to.
I needed to do several interviews with the staff there, one after another, who did the exact same thing from the phone interviews. The process devolved into an oral-exam style of interview and I really began to lose interest in this job.
The final bit was a skills-based interview that consisted of a poorly-constructed set of tasks to perform on a router command line. Never mind that the entire setup was contrived and that the questions were devoid of any context, but the whole thing just made me feel like I was being wrung through a wringer with no clear idea about how any of this related to the job I was interviewing for.
I tried to follow up to see if they would make an offer but the recruiter never returned another email or returned a single phone call. Honestly, this is the first time that a recruiter has ever treated me this way. All in all, I did something like 15 interviews and never got so much as a thank you (but no-thank-you) for going through the process.
I ended up getting a significantly better job than I had (with another company) but I feel that I really wasted a lot of time with these guys. Even if I wasn't a good fit, they should have at least communicated that to me. The un-returned emails after the process ended really left a bad taste in my mouth.
- Why are you looking to leave your current job? Answer Question
Engineer InterviewNo OfferNeutral ExperienceAverage Interview
The process took 6+ weeks – interviewed at Salesforce in December 2008.
Consisted of phone interview. Involved some simple programming, java and sql questions.
- Given some tables and output requirements give the corresponding sql statements. Answer Question
Is this helpful? The community relies on everyone sharing – Add Anonymous Interview Review