Docusign software engineer candidates report recruiter and manager conversations alongside live coding, system design, and behavioral interviews. Prepare for DSA depth, tradeoff discussions, and concrete project examples.
$170K
Avg. Base Comp
$262K
Avg. Total Comp
6-7 rounds
Typical Rounds
1-2 months
Process Length
Docusign software engineer candidates describe a process that mixes recruiter or HR conversations with coding, system design, behavioral, manager, and team discussions. Reported totals vary: one candidate completed six interviews, while another described about seven rounds. Other reports only name a few stages, so the exact sequence can differ by team and level.
Live coding is the most consistently detailed technical theme. Candidates encountered medium-to-hard DSA prompts involving trees and recursion, arrays and queues, monotonic stacks, heaps with greedy reasoning, and sliding windows. Specific exercises included modeling nested boxes, a three-lane obstacle problem, a Two Sum existence variant, and a prompt to implement Minesweeper. Practice explaining assumptions, runtime, memory use, and changes prompted by follow-up questions rather than coding silently.
System-design discussions may test how you reason through tradeoffs. Candidates reported CAP tradeoffs, distributed systems, microservices, high availability, security, testing, scalability, consistency, and service communication. One candidate found an initially ambiguous DSA prompt shifted toward a pub/sub and scalability discussion, making clarification early in the conversation especially valuable.
Behavioral and project conversations also matter. Reported topics include collaboration, end-to-end ownership, and performance optimization work. Prepare concise examples that make your own contribution and decisions clear, plus a direct answer about why Docusign. One report described a one-hour Zoom technical interview with two coding questions.
Synthesized from 10 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 | |
|---|---|
| Shortest Path Algorithms | |
| Swipe Payment API | |
| Client Solution Pushback | |
| Your Strengths and Weaknesses | |
| LRU Cache 1 | |
| Tic-Tac-Toe Outcome | |
| 2nd Highest Salary | |
| Top Three Salaries | |
| Merge Sorted Lists | |
| Closest SAT Scores | |
| Subscription Overlap | |
| Empty Neighborhoods | |
| Monthly Customer Report | |
| Prime to N | |
| Rolling Bank Transactions | |
| Top 3 Users | |
| Random SQL Sample | |
| String Shift | |
| Comments Histogram | |
| Largest Salary by Department | |
| Upsell Transactions | |
| Raining in Seattle | |
| Find the Missing Number | |
| Minimum Change | |
| Customer Orders | |
| Bagging vs Boosting | |
| Find the First Non-Repeating Character in a String | |
| Scrambled Tickets | |
| Weighted Keys |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report an initial recruiter or HR call covering their background, the role, and sometimes behavioral questions. This stage may be brief, but some candidates also encountered a question about what they like about Docusign.
Candidates report live or HackerRank-based coding, sometimes in one-hour sessions and sometimes with two questions in an hour. Reported prompts span trees, recursion, graphs, arrays and queues, sliding windows, caching, and game-style implementations; follow-up discussion may probe complexity or concurrency.
Candidates report design conversations on distributed systems, microservices, payments, scalability, consistency, failures, and CAP tradeoffs. Prompts may evolve through follow-ups, so explicitly confirming the problem scope and explaining tradeoffs can be important.
Candidates report hiring-manager, team, panel, and project-focused conversations. Topics included recent projects, performance optimization, collaboration, ownership, technical decisions, mistakes, and working with incomplete information.
Candidates report STAR-style behavioral questions, sometimes alongside manager or director discussions. Prepare specific examples of cross-team collaboration and end-to-end ownership, and be ready to connect your interest in the company to your engineering experience.
