Salesforce interview notes, page 5 of 13

“This one made me slow down because the no-third-party constraint is the whole point.” 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.

“My first instinct was to use ladders on the biggest jumps, which is kind of right but you don't know which jumps are biggest until you've already passed them.” 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 sliding window approach going in but fumbled the shrink logic under pressure.” 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.

“Pretty much just exponential growth.” 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 one sprawled.” 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.

“Started fine, got the recursive case working pretty quickly.” 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 is the kind of question where you think you know it cold and then you start talking and realize you're hand-waving through half of it.” 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.

“The subsequence vs substring split is what makes this tricky.” 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 one genuinely stressed me out.” 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 substring constraint is what makes this non-trivial.” 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.