← Back to Directory

DocuSign

Large Enterprises

Screna has 5 DocuSign interview write-ups. The most reported round is the technical phone screen (3).

5 interview notes · updated Jun 2026

DocuSign·Software Engineer·Onsite - Multi Round

Jun 2026
DocuSign software engineer round that mixed behavioral questions with a project walkthrough, then pivoted into designing a user-facing JSON structure for a feature and iterating on it live with the interviewer. The JSON design portion was the real meat of the session.
  • Walk us through a past project you worked on and the decisions you made along the way.
  • Design a JSON structure for a user-facing feature. Then iterate on it with us, considering versioning, optional fields, backward compatibility, naming conventions, and how clients will consume it.
  • How would you ensure backward compatibility as the JSON structure evolves over time?

“Pretty standard stuff.”

View Post

DocuSign·Software Engineer·Onsite - System Design / Architecture

Jun 2026
DocuSign full-stack round focused entirely on pagination, which sounds narrow until you're 20 minutes in and realize how many layers there are to it. Solid technical depth required, less about coding and more about design decisions and tradeoffs.
  • Design and implement a paginated list feature for a web page, covering both the backend API shape and the data model that supports it. Walk through your choices around cursor-based vs offset/limit pagination, whether to return a total count or just a has_more flag, and how you'd handle corner cases like empty results, partial last pages, items changing between requests, deep pagination performance, and stable ordering.

“This was a lot to hold in your head at once.”

View Post

DocuSign·Software Engineer·Technical Phone Screen

May 2026
DocuSign SWE interview with a graph problem that's essentially the classic course scheduling question dressed up in cloud infrastructure clothing. Pretty standard if you've done LC 207/210 before, less fun if you haven't.
  • Given a set of cloud resources with initialization dependencies between them, find a valid order to initialize all resources. If a circular dependency exists, report it as unsatisfiable.

“It's basically topological sort with a cloud theme slapped on it.”

View Post

DocuSign·Software Engineer·Technical Phone Screen

May 2026
DocuSign software engineer interview, got a graph/union-find problem that I'd seen variants of before but still had to think through carefully. Nothing too surprising about the format.
  • You're given a list of accounts, each with a username and a set of email addresses. Merge any accounts that share at least one email address, since they belong to the same person. Return the merged accounts with emails sorted and the username attached.

“I knew union-find was the right move pretty quickly, map every email to a parent, union them when they appear under the same account, then group by root and slap the username back on.”

View Post

DocuSign·Software Engineer·Technical Phone Screen

May 2026
DocuSign software engineer round that was basically one meaty design-your-own-mini-system question. The problem had three parts and the real challenge was picking the right data structures, not just getting something that works.
  • Design a system with three operations: createUser (assigns a user a role), postJob (adds a job with a role requirement and salary), and topKJobsForUser (returns the K highest-paying jobs a given user is eligible to see based on their role). What data structures would you use to make topK queries fast?

“My first instinct was just a list per role and sort on demand.”

View Post