DocuSign interview notes, page 1 of 2

“I went straight to supply and demand sides, which felt right, but I spent too long on the developer onboarding piece and kind of glossed over discovery and trust signals for buyers.” The rest of the author's notes on Product Manager interview at DocuSign, Onsite - Product Sense / Strategy round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“I knew union-find was the right tool pretty quickly but fumbled the bookkeeping.” The rest of the author's notes on Software Engineer interview at DocuSign, Technical Phone Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“Pretty standard stuff.” The rest of the author's notes on Software Engineer interview at DocuSign, 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 API layer because that felt most natural, but I think that was a mistake.” The rest of the author's notes on Software Engineer interview at DocuSign, Onsite - System Design / Architecture round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“I started by reaching for a basic map from role to a list of jobs and sorting on the fly, which the interviewer let me finish before asking what happens at scale.” The rest of the author's notes on Software Engineer interview at DocuSign, 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 where I spent most of the interview and also where I embarrassed myself a little.” The rest of the author's notes on Software Engineer interview at DocuSign, Onsite - System Design / Architecture round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“Seemed easy at first and I jumped straight into coding without clarifying the expected return behavior.” The rest of the author's notes on Software Engineer interview at DocuSign, Technical Phone Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“I jumped straight into token bucket and felt pretty good about it, but then they started asking about distributed state and I realized I'd been designing for a single node the whole time.” The rest of the author's notes on Software Engineer interview at DocuSign, Onsite - System Design / Architecture round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“I went with a hash map immediately, which I think was fine, but then they pushed me on whether I'd considered ordered access patterns and I kind of fumbled.” The rest of the author's notes on Software Engineer interview at DocuSign, Onsite - System Design / Architecture round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.

“Knew it was topological sort pretty fast, the dependency framing makes it obvious.” The rest of the author's notes on Software Engineer interview at DocuSign, Technical Phone Screen round, covers how they worked through the question, what the panel pushed back on, and what they would do differently.