Real Interview Experiences
Learn what to expect directly from candidates and interviewers who've been through it.
- 1,323 experiences
- 313 companies
- 37 roles
- +204 added this month
SalesforceSenior Product Manager · L5“One senior director did a surprise case study, and halfway through I realized, oh, you’re basically asking for one of your recent product releases. It felt mildly unfair because I didn’t have the same information they did.”
SalesforceAssociate Product Manager Intern · Intern“Pretty light interview cycle, basic PM prep is needed. More AI heavy and focused on prompt engineering and being able to use AI tools live in an interview, but not too bad overall. Most surprised by the AI heavy cases but recruiter went deep into detail before the interview. ”
SalesforceAssociate Product Manager · L3“The coding problems are pretty easy and straightforward (mainly arrays). The MCQ problems are also pretty straightforward as long as you have experience with AI deployment. Expect standard product questions on AI strategy, products and adoption.”
SalesforceDirector of Product · L8+“It was very unstructured. Most of the questions were about previous experience. Asked about team management. ”
SalesforceSoftware Engineer · L5“The recruiter was helpful but the interview was challenging. Most of my time went in drawing the design on their online IDE. I think they are looking how you can give a structured answer of the system”
SalesforceMember Of technichal staff · L4“Generally salesforce keep interviews in one two days hiring drive where each round eliminating.So i got the interview opportunity via referral so didnt gave OA but scheduled DSA round as very first round where 45 minutes and two medium to hard level questions should be done with almost optimised approach and time complexity explaination.”
SalesforceTechnical Program Manager · L5“The overall interview was over in a week. I think they were looking to quickly to finish the round. It's for Missionforce. The feedback came in positive but for some reasons unknown and not shared they didn't went ahead with me. ”
SalesforceSoftware Engineer · L6“Went well, The interviewer has experience and the questions asked was more systematic aligned to the job posting and tweaked as per the resume submitted ”
SalesforceSoftware Engineer · Intern“This was my first interview ever, and I was nervous. However, the introduction went really well and caught the interviewer’s attention. At the start, I mentioned that my areas of interest were "geopolitics" and "music production". Since many people these days enjoy discussing geopolitics, he followed up by saying he was interested in it too and asked me about recent events I knew about. For the first 10 minutes, we talked about geopolitics, and It was a memorable first 10 minutes in my very first interview. Then we got back to him asking me technical questions. I think i had a good first impression. He first stated with asking general programming questions, about Object oriented programming, Polymorphism. I was good here. Then we got on topic of Database. Here i fumbled big time. First question "what is database?" My nerves answer: a place where we store data. I felt it me fumbling, i was nerves and never practice about database, SQL for this interview. Then here we go another fumble, He asked "What are operators in SQL?" I brain-fogged and said am not aware of this answer, i knew but in moment i did not understand the meaning of "operators", they he clarifies saying addition, subtraction. And it clicked in my mind, but still my answer was in 2 lines: "Plus, minus, subtraction, division, Arithmetic, Logical, Comparison" thats it. I should have expanded on it and explained in little more detail. I think i did this because it was my first interview and in my mind going through was i fumbled very bad and am not gonna be selected i lost my all hopes in between the interview. till now its been in total 20-25 minutes, we switched to last part which was coding part. He said he asked this question to last guy and he did not able to answer this question. I was confident on my problem solving and coding skills, but yeh as you could tell by now i suck at communication. The coding question was: "Given a array on integers return a frequency of each element". I though this is pretty easy and first explain him my first approach to problem, start implementing, code ran and passed on first run. Explain him what approach i used and why everything in detail, with time and space complexities. So the two best parts were long intro and last coding problem. I also asked him at the end what I could improve on, and he mentioned my theoretical knowledge. He explained that interviewers don’t expect you to recite textbook definitions word‑for‑word, but they do expect you to understand and be able to talk about the main ideas or high‑level concepts behind each topic. I somewhere knew that am not getting selected, and i was right.”
Preview full access of other recent interview experiences
AnthropicSoftware Engineer, Safeguards · L5“The weirdest Anthropic round was the company values interview. It was almost like a therapy session, and honestly if you went to a therapist at some point, you will pass that round much more easily.”
NetflixEngineering Manager, Tooling“What was very unusual is they didn’t give me any tooling to draw the system design, so I just sketched it on a piece of paper and talked them through it, then we got into this oddly deep debate about whether hover-over history should count as a recommendation signal.”
