Docusign Software Engineer candidates report recruiter and manager conversations alongside live coding, system design, and behavioral discussions. Prepare for DSA depth, clear tradeoff reasoning, and concrete project examples.
$170K
Avg. Base Comp
$258K
Avg. Total Comp
6-7 rounds
Typical Rounds
1-2 months
Process Length
Docusign Software Engineer interviews reported here combine recruiter and hiring-manager conversations with live coding, system design, and behavioral or project-focused discussions. The clearest recurring technical theme is interactive problem solving: candidates described medium-level algorithm questions, including dynamic programming, graphs, a Two Sum variation, sliding windows, and a three-lane obstacle problem. Another account described an interviewer-created question where covering corner cases mattered more than recognizing a familiar pattern. Define assumptions, explain your reasoning, and test edge cases aloud.
System design may be a separate conversation or emerge as a follow-up to a coding prompt. Reported discussions covered microservices, high availability, distributed systems, security, automated testing, scalability, and a prompt that shifted from maintaining the latest value for a topic toward pub/sub expectations. Restate your interpretation and ask a focused clarifying question before committing to a design, then explain the tradeoffs behind your choices.
Behavioral preparation should be concrete. Candidates were asked about collaboration, end-to-end ownership, projects, performance optimization, and what they liked about the company. Prepare examples that identify your decision, collaborators, and outcome. The reports show variation in interviewer style and prompt format, so prioritize adaptable reasoning over a fixed question list. Explicitly reported processes took under two months or close to two months, with six or about seven interviews in the longest accounts.
Synthesized from 7 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.
The DocuSign technical interview was both challenging and genuinely valuable because it covered much more than a single coding exercise. The conversation went deep into data structures and algorithms, then broadened into microservice architecture and highly available distributed systems. I was also evaluated on engineering practices around data security, automated testing, and working collaboratively with a team. The interviewers seemed focused on whether I could connect a solution to the company’s broader engineering standards, not just arrive at a technically correct answer.
There was also a question about what I liked about the company, so I would not treat the process as purely technical. Overall, the difficulty came from the breadth of topics and the expectation that I could discuss robust software design alongside core computer-science fundamentals. I did not receive an offer. My advice is to prepare to explain how you would design reliable microservices and high-availability distributed systems while grounding your choices in security, test automation, and maintainable engineering practices.
Prep tip from this candidate
Be ready to discuss microservice architecture and highly available distributed systems in terms of concrete engineering practices, especially data security and automated testing. Also prepare a thoughtful answer for why you like DocuSign.
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 | |
| Your Strengths and Weaknesses | |
| Tic-Tac-Toe Outcome | |
| 2nd Highest Salary | |
| Top Three Salaries | |
| Merge Sorted Lists | |
| Empty Neighborhoods | |
| Closest SAT Scores | |
| Subscription Overlap | |
| Monthly Customer Report | |
| Rolling Bank Transactions | |
| Top 3 Users | |
| Random SQL Sample | |
| Prime to N | |
| Comments Histogram | |
| Upsell Transactions | |
| Raining in Seattle | |
| String Shift | |
| Customer Orders | |
| Bagging vs Boosting | |
| Find the Missing Number | |
| Minimum Change | |
| Weighted Keys | |
| Find the First Non-Repeating Character in a String | |
| The Brackets Problem | |
| Daily Retention Summary | |
| Scrambled Tickets | |
| Largest Salary by Department | |
| Rectangle Overlap |
Synthesized from candidate reports. Individual experiences may vary.
Candidates report an initial recruiter call covering experience, background, and behavioral topics. Some reports also mention role or team discussion; prepare a concise career narrative and examples that connect your work to collaboration and ownership.
Candidates report live algorithmic coding ranging from medium to hard, with trees, recursion, graphs, DP, sliding windows, heaps, stacks, and game-style problems. Prompts may be interviewer-created or incomplete, so clarify constraints and test edge cases aloud.
Candidates report system-design conversations on microservices, high availability, security, testing, CAP tradeoffs, and scalability. A coding discussion may broaden into design, so explain the boundary of your proposed solution before discussing scale.
Candidates report hiring-manager, team, and behavioral conversations focused on project depth, cross-team collaboration, end-to-end ownership, and performance optimization. Use specific examples that show your decisions, stakeholder handling, and outcomes.
