← Back to Directory

DocuSign

Large Enterprises

Screna has 13 DocuSign interview write-ups. The most reported round is the system design round (5).

13 interview notes · updated Jul 2026

DocuSign·Software Engineer·Technical Phone Screen

Jul 2026
DocuSign SWE interview with a grid/island problem that kept growing new requirements as you went. Started simple enough but by the fourth variant I was definitely second-guessing my BFS setup.
  • You're given an m×n grid where 0 is water and any nonzero value is land. Connected land cells (4-directional) form an island. Find the maximum sum of cell values across all islands.
  • Now restrict valid islands to those where every cell has a non-negative value. Islands containing any negative cell are completely ignored. Recompute the maximum sum under this rule.
  • For whichever island has the maximum sum, also return the index (row, column) of any one cell belonging to that island.
  • Instead of any cell index, return specifically the last cell of the winning island in row-major order, meaning the lexicographically largest (r, c) pair by row first then column. If multiple islands tie on sum, break the tie by choosing the island whose last row-major cell is largest.
  • Walk through your algorithm design for all the above variants and analyze the time and space complexity.

“Classic flood fill setup.”

View Post

DocuSign·Product Manager·Recruiter / HR Screen

Jul 2026
Short PM screen at DocuSign, basically just one question about motivation. Not much to report.
  • Why do you want to work at DocuSign?

“Standard opener.”

View Post

DocuSign·Software Engineer·Onsite - System Design / Architecture

Jun 2026
System design round at DocuSign for a software engineer role. The problem was a multi-level parking lot which sounds straightforward but there's a lot of surface area once you start pulling on the thread of vehicles that span multiple spots.
  • Design a multi-level parking system that tracks floors, spots, and vehicle types, where some vehicles may occupy multiple adjacent spots. Define the core data models and APIs for vehicle entry and exit, spot allocation and release, and queries like available spots by type or by floor.

“I started with the data model which felt right, floors containing rows of spots, each spot having a type and an availability flag.”

View Post

DocuSign·Software Engineer·Technical Phone Screen

Jun 2026
DocuSign software engineer interview with a graph problem centered on cloud resource initialization order. Pretty standard topological sort territory but they added a cycle detection requirement which is where things get interesting.
  • Given a set of cloud resources with initialization dependencies between them, find a valid order to initialize all resources. If a cycle exists in the dependencies, report it as unsatisfiable.

“Knew it was topological sort pretty fast, the dependency framing makes it obvious.”

View Post

DocuSign·Software Engineer·Onsite - System Design / Architecture

Jun 2026
DocuSign software engineer interview that leaned heavily on system design fundamentals. The main problem was building an in-memory key-value store from scratch, which sounds straightforward until you have to justify every decision out loud.
  • Design and implement an in-memory key-value store with put, get, update, delete, and exists operations. Justify your choice of underlying data structure, analyze the time and space complexity, and walk through edge cases like duplicate keys and missing key lookups.

“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.”

View Post

DocuSign·Software Engineer·Onsite - System Design / Architecture

May 2026
DocuSign SWE system design round, just one question the whole time. Pretty focused session, no fluff.
  • Design a rate limiter for a microservices API.

“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.”

View Post

DocuSign·Software Engineer·Technical Phone Screen

May 2026
Interviewed for a SWE role at DocuSign and got a pretty straightforward array manipulation question. Nothing wild, but it's the kind of thing that trips you up if you're not careful about edge cases.
  • Given an array, implement add, remove, and update operations and return the modified array after each operation.

“Seemed easy at first and I jumped straight into coding without clarifying the expected return behavior.”

View Post

DocuSign·Software Engineer·Onsite - System Design / Architecture

May 2026
DocuSign full-stack round that was basically one long system design question about pagination. Seemed straightforward at first but they kept pushing on edge cases until I ran out of confident answers.
  • Design and implement a paginated list feature for a web page, covering both the backend API shape and the underlying data model. Walk through your choices around cursor-based vs offset/limit pagination, whether to return a total count or a has_more flag, and how you'd handle edge cases like empty results, partial last pages, items being inserted or deleted between requests, deep pagination performance, and stable ordering.
  • How would your pagination design handle items being inserted or removed between page requests, and what guarantees can you realistically offer to the user?
  • What are the performance implications of deep pagination and how would you address them at the data layer?

“This is where I spent most of the interview and also where I embarrassed myself a little.”

View Post

DocuSign·Software Engineer·Technical Phone Screen

Apr 2026
DocuSign SWE interview with a design-your-own-system coding question. The problem was more involved than I expected for a phone screen, felt like it was testing both data structure knowledge and API design at the same time.
  • Design a system with three operations: createUser(userName, role), postJob(jobId, role, salary), and topKJobsForUser(userName, k). The last one should return the top K highest-salary jobs a user is eligible to see based on their role. What data structures would you use to make topK fast?

“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.”

View Post

DocuSign·Software Engineer·Onsite - System Design / Architecture

Apr 2026
DocuSign system design round for a software engineer role, focused entirely on building a paginated list feature end to end. The scope was broader than I expected, covering frontend, API design, data modeling, and database indexing all in one question.
  • Design a paginated list feature for a web app, covering the frontend UI, backend API, data model, and database indexing strategy.
  • What are the tradeoffs between offset-based and cursor-based pagination, and when would you choose one over the other?
  • How would you handle items being inserted or deleted while a user is actively paginating through results?
  • What metadata should the API response include to support the pagination UI, and how do you handle the 'is there a next page' problem efficiently without counting all rows?
  • What database indexes would you create to support efficient newest-first pagination with stable ordering?

“I started with the API layer because that felt most natural, but I think that was a mistake.”

View Post