Salesforce interview notes, page 12 of 13

“Nailed this one, follow-ups included.” The rest of the author's notes on Software Engineer interview at Salesforce, Technical Phone Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“The example they gave was s = 'abcdefgh' and k = 'fha', answer being 'fgha'.” The rest of the author's notes on Software Engineer interview at Salesforce, Technical Phone Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“My first instinct was greedy and it was wrong.” The rest of the author's notes on Software Engineer interview at Salesforce, Technical Phone Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“Thought I had this cold but partway through my answer I realized I was just describing caching at a high level and hadn't touched on edge nodes, origin pull vs push, or how routing decisions actually get made.” The rest of the author's notes on Software Engineer interview at Salesforce, Technical Phone Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“My first instinct was greedy, just keep subtracting the largest power of 2 that fits.” The rest of the author's notes on Software Engineer interview at Salesforce, Technical Phone Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“I knew the high-level idea but the O(1) constraint is where it gets painful.” The rest of the author's notes on Software Engineer interview at Salesforce, Technical Phone Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“This felt like a warm-up but I over-explained it.” The rest of the author's notes on Machine Learning Engineer interview at Salesforce, Onsite - Multi Round round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“I started with the sort-each-word approach and got through it fine, O(n * m log m) and all that.” The rest of the author's notes on Software Engineer interview at Salesforce, Technical Phone Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“Spent the first few minutes just listing classes out loud, ElevatorCar, FloorRequest, Dispatcher, Door, that kind of thing.” The rest of the author's notes on Backend Engineer interview at Salesforce, Onsite - System Design / Architecture round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“Started with the API contract and worked outward, which felt right.” The rest of the author's notes on Software Engineer interview at Salesforce, Onsite - System Design / Architecture round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.