Company
DocuSign interview questions
5 practice questions in the style of DocuSign's interviews, covering Coding & Algorithms, Software Engineering Fundamentals.
2 easy3 medium0 hard
DocuSign interview questions by the numbers
Last updated
Katkat has 5 DocuSign interview questions. The largest topics are Coding & Algorithms (80%) and Software Engineering Fundamentals (20%). By difficulty: 40% easy and 60% medium. The most common round is Onsite (60%). Frequent concepts include arrays, design, json and oop.
Topics
- Coding & Algorithms80% · 4
Difficulty
- Easy40% · 2
- Medium60% · 3
Interview rounds
- Onsite60% · 3
- Technical Screen40% · 2
Roles
- Software Engineer100% · 5
Frequent concepts
- arrays20% · 1
- design20% · 1
- json20% · 1
- oop20% · 1
- recursion20% · 1
- sorting20% · 1
Showing 1–5 of 5 results
Given a list of lowercase words, repeatedly delete any word that is an anagram of the word immediately before it, and return what remains in its original order. The task tests anagram comparison, reasoning about how repeated deletions interact, and producing a unique, order-preserving result.
DocuSignSoftware EngineerCoding & AlgorithmsTechnical ScreenTests array manipulation, sorting, deduplication, and range-grouping logic to produce a compact string representation of consecutive numbers.
DocuSignSoftware EngineerCoding & AlgorithmsOnsiteDesign and implement a modular JSON schema validator that verifies data against structural schemas, supporting primitive types, nested objects, arrays, regex patterns, numeric ranges, and strict field controls.
DocuSignSoftware EngineerSoftware Engineering FundamentalsOnsiteThis question evaluates grid-based graph traversal and connected-component aggregation skills, including handling positive and negative cell values, tie-breaking by row-major indices, and computing maximum component sums.
DocuSignSoftware EngineerCoding & AlgorithmsTechnical ScreenThis question evaluates understanding of core data structures, API design, complexity analysis, and edge-case handling for an in-memory key–value CRUD store, and falls under the Coding & Algorithms domain while testing both practical implementation skills and conceptual reasoning about time/space trade-offs.
DocuSignSoftware EngineerCoding & AlgorithmsOnsite
DocuSign interview experiences
All 8 →- Docusign Software Engineer interview with a behavioral-only sessionDocusign · Software Engineer · Other · May 2026
I had a lightweight, behavioral-focused experience for a software engineer internship track. Before anything technical happened, the recruiter arranged the process and checked what scheduling worked for me. The logistics felt fairly smooth, and I appreciated that the recruiter stayed in contact and helped map out the timing. When the interview took place, it stayed entirely behavioral. There were…
- Docusign Software Engineer interview with timed DSA and DBMS problemsDocusign · Software Engineer · Online Assessment · Apr 2026Rejected
My process quickly became an assessment-style experience. I completed two closely related DSA problems in a timed format. One seemed to rely on graph-style reasoning. There was also a DBMS question that was trickier than the coding problems. It involved joins and aggregate-style thinking, so I had to slow down and pay close attention to what the question was asking. Recruiting coordination was an…
- Docusign Software Engineer interview: API script and HackerRank-style exercisesDocusign · Software Engineer · HR Screen · Apr 2026
My process was shorter and heavily front-loaded. It began with a quick recruiter screen, then moved into a panel-style technical evaluation. The questions covered coding and system design, and nothing felt wildly unexpected. They were standard areas they wanted to see me handle calmly. The process continued in a way that felt somewhat drawn out but still organized. I had four interviews in total,…
- Docusign Account Executive interview with multiple presentationsDocusign · Account Executive · HR Screen · Mar 2026Rejected
I went through an Account Executive hiring process that felt average to difficult. It dragged on for months, with several rounds, shifting timelines, and a lot of work for the candidate. The early recruiter conversations seemed promising. I then had additional interviews with hiring managers, followed by separate presentations that I had to prepare and deliver. Those presentations took substantia…
- Docusign Software Engineer interview with three LeetCode-style roundsDocusign · Software Engineer · HR Screen · Mar 2026
My process started with a recruiter call about my background, the role, and the team I was targeting. After that, I had three LeetCode-style coding rounds, each lasting about an hour, along with a behavioral interview. The timeline stretched over several weeks, and I waited around three weeks after the final round to hear back. The technical difficulty wasn't the main issue for me. One round felt…
More companies
- Meta666
- Amazon653
- Google486
- OpenAI342
- Capital One268
- Microsoft252
- DoorDash241
- Anthropic225
- Uber217
- Apple177
- TikTok176
- Pinterest161
- ByteDance160
- LinkedIn154
- Stripe139
- Snowflake130
- Databricks122
- Airbnb112
- Rippling106
- Oracle104
- Coinbase99
- Netflix97
- NVIDIA95
- Snapchat94
- Citadel90
- Waymo90
- Instacart87
- Roblox84
- Salesforce77
- Optiver76
- Shopify63
- Robinhood60
- Atlassian55
- Hudson River Trading55
- Two Sigma55
- J.P. Morgan53
- PayPal53
- xAI53
- Lyft52
- Tesla52
