Docusign Software Engineer Tech Phone Screen Experience and Interview Process
Interview Experience
The interview consisted of standard infrastructure questions and some Microsoft technical questions. There was supposed to be a coding session at the end, but they said it was almost over and no codin
Full Details
The interview consisted of standard infrastructure questions and some Microsoft technical questions. There was supposed to be a coding session at the end, but they said it was almost over and no coding was needed, ending half an hour early (the schedule was 1 hour). A week has
passed, and I still don't know the results. The HR person even told me they were in a meeting and urgently needed to hire. A Cisco engineer, an Indian from India, who seems to be a director now, was interviewed by phone. I suspect he was the skip for that position. He previously worked at Walmart. He asked some resume-related questions, but as soon as I started to elaborate, he would interrupt me, say he understood, and then change the subject. He also asked some standard questions, such as how to investigate application latency, whether I knew front-end and back-end concepts, and how to expand on my design. Strangely, if I said I knew, he would change the question; if I said I might know, he would immediately ask specific questions; but if I spoke fluently, he would immediately interrupt and change the subject again.
About Docusign Interview Reports
This question was reported by a candidate who interviewed at Docusign. LeakCode aggregates interview reports from 10+ sources, including 1Point3Acres, Glassdoor, LeetCode Discuss, Blind, Reddit, Indeed, and Nowcoder. Each report is translated where necessary, deduplicated against existing entries, and tagged by company, role, round type, and reporting date.
Use this question as one calibration data point, not a memorization target. Companies typically rotate their question pools every 2-4 months; the exact wording of a 2024 question may differ from what you encounter today. The underlying pattern, difficulty level, and follow-up depth at Docusign are the higher-signal extractions to take from this report.
For broader preparation context, the Docusign interview process typically includes a recruiter screen, one or two technical phone screens, and a 4-5 round on-site loop covering coding, system design (at L4+ levels), and behavioral. Reports tagged on LeakCode show the round-by-round distribution and typical difficulty calibration. To browse questions filtered by round type and seniority, use the company hub linked above.
How To Practice This Type of Question
Solve similar problems on LeetCode under timed conditions (25-35 minutes per medium difficulty). The goal is pattern recognition: recognize the underlying technique (sliding window, two-pointer, BFS, memoized recursion, etc.) within 60-90 seconds of reading. Strong candidates verbalize their hypothesis out loud before coding, then iterate based on feedback. Weak candidates dive into implementation immediately, lose time on the wrong approach, and run out of time for follow-ups.
Companies update their question pools every 2-4 months. The exact wording of any given question may have been retired by the time you interview. Focus your prep on the pattern, not the specific problem. The patterns that appear in Docusign reports consistently are the ones worth investing in; one-off niche problems are not.
During Your Docusign Round
Apply the standard interview round template: clarify requirements (2-3 minutes), state your approach out loud and confirm direction with the interviewer (3-5 minutes), code with narration (15-25 minutes), test with concrete examples including edge cases (5 minutes), discuss optimization or trade-offs if time permits (5 minutes). This template is universally accepted across FAANG and adjacent companies; deviating from it produces weaker interviewer feedback signal.
The single most predictive failure mode in Docusign reports tagged "no hire": not asking clarifying questions. Interviewers are explicitly trained to weight this. Strong candidates ask 3-5 clarifying questions even on problems that look obvious; weak candidates dive into code immediately. The clarifying-question check is often the first signal recorded in the interviewer's written notes.