Docusign Software Engineer interviews typically include a recruiter screen, DSA-heavy coding rounds, a system design discussion, and behavioral or hiring-manager conversations, with candidates reporting roughly five to seven interviews and one loop taking close to two months.
$140K
Avg. Base Comp
$233K
Avg. Total Comp
5-7 rounds
Typical Rounds
2 months
Process Length
Docusign's Software Engineer process is multi-stage: candidates describe totals of roughly five to seven interviews, and one candidate said the full loop took close to two months. It usually opens with a recruiter or HR screen on background and the role. The technical core is heavily DSA-focused, with LeetCode-style problems that candidates rate from medium to hard: a monotonic stack question, a heap-and-greedy problem, a Minesweeper implementation, a Two Sum existence check, a sliding-window problem, a nested-box tree traversal in Python, and a three-lane racing-game problem about minimizing sideways moves. One candidate received a one-line prompt for a structure that supports insert, get, and get-random in constant time, then had to define classes and constraints from scratch and handle follow-ups on concurrency and making it generic. Expect to code live and talk through your approach, since some rounds are conversational with frequent interruptions.
System design comes up repeatedly. Candidates mention CAP tradeoffs, a prompt that drifted into a pub/sub design with scalability follow-ups, a Wordle-style solver, and broader discussions of microservices, high availability, data security, and automated testing. Behavioral rounds use STAR-style prompts about ownership and cross-team collaboration. Several candidates also describe a hiring-manager, director, or team conversation alongside a project deep dive, such as walking through past performance-optimization work. A few reports mention unclear prompts or underprepared interviewers, so restate the problem and ask clarifying questions before committing to a solution. Most outcomes in these reports were not offers, so treat this as a map of format and depth rather than a predictor of results.
Synthesized from 21 candidate reports by our editorial team.
Had an interview recently?
Share your experience. Unlock the full guide.
Real interview reports from people who went through the Docusign process.
Share your own interview experience to unlock all reports, or subscribe for full access.
Sourced from candidate reports and verified by our team.
Topics based on recent interview experiences.
Featured question at Docusign
This problem involves identifying duplicate numbers in a list of integers. The function should return a list of the duplicate numbers.
| Question | |
|---|---|
| Client Solution Pushback | |
| Shortest Path Algorithms | |
| Swipe Payment API | |
| Your Strengths and Weaknesses | |
| LRU Cache 1 | |
| Tic-Tac-Toe Outcome | |
| 2nd Highest Salary | |
| Top Three Salaries | |
| Merge Sorted Lists | |
| Empty Neighborhoods | |
| Closest SAT Scores | |
| Subscription Overlap | |
| Top 3 Users | |
| Random SQL Sample | |
| Upsell Transactions | |
| Find the Missing Number | |
| Monthly Customer Report | |
| Rolling Bank Transactions | |
| Largest Salary by Department | |
| Size of Joins | |
| Scrambled Tickets | |
| Prime to N | |
| String Shift | |
| Duplicate Rows | |
| Find Bigrams | |
| Comments Histogram | |
| Last Transaction | |
| Longest Streak Users | |
| Minimum Change |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report an initial recruiter or HR call covering their background, the team, and the role. This screen is typically short and non-technical.
Candidates describe one to three coding interviews, often about an hour each, with LeetCode-style problems rated medium to hard. Reported problems include a monotonic stack question, a heap-and-greedy problem, Minesweeper, a Two Sum existence check, a sliding-window problem, a nested-box tree traversal, a three-lane racing-game problem, and an insert/get/get-random structure in constant time with concurrency follow-ups. Interviewers may expect you to code live and explain your approach as you go.
A system design round appears in several reports. Topics include CAP tradeoffs, pub/sub and scalability follow-ups, a Wordle-style solver, microservice architecture, and high availability. One candidate said a round meant to assess DSA turned into a design discussion, so be ready for coding prompts to expand into scalability questions.
Behavioral rounds typically ask about past projects, ownership, and cross-team collaboration, often in a STAR format. Several candidates describe a separate hiring-manager conversation and a project deep dive, such as walking through past performance-optimization work.
Some candidates went through additional rounds, including a team interview that went deeper on a recent project, a technical session with three developers, or a final conversation with a director. These rounds are not universal, which is why reported totals range from about five to seven interviews.
