I had two 1-hour interviews. The first was with a team manager, and the second was with an engineer on the team.
Interview 1: We mostly went over my resume, and the manager asked me specific questions about my previous internship experiences. He went into detail about the projects I worked on and my day-to-day responsibilities. He got a little technical, but that was alright. My recommendation is to know everything on your resume inside and out. Make sure you understand what you've written clearly, as they might ask very specific questions.
Interview 2: This was a technical round. The engineer was very interested in my resume, so for the first 20 minutes, we went over my resume and projects. He asked me specific questions about them too. Then, we moved into the technical portion. Since this team is a front-end team, he sent me JavaScript code and asked me to analyze it and predict the output. It took me a while, but I was able to explain my thought process, and he asked why I was thinking a certain way. If you're able to keep the conversation going, they'll enjoy that. It's important to keep the conversation engaging; it shows you have good communication skills, which are necessary to be part of any team. He asked me a few more theoretical questions about Big O notation and linked lists regarding the code he'd provided. We had a long discussion about those as well.
Within two days, I received my offer, and apparently, both my interviews were very successful. I think it was because I kept my thought process out in the open.
Why do you want to work for us?
The following metrics were computed from 2 interview experiences for the Salesforce Software Engineer (Internship) role in Seattle, Washington.
Salesforce's interview process for their Software Engineer (Internship) roles in Seattle, Washington is incredibly easy as the vast majority of engineers get an offer after going through it.
Candidates reported having very good feelings for Salesforce's Software Engineer (Internship) interview process in Seattle, Washington.