DocuSign SWE Intern Interviews: 27 Experiences (Part 2 of 2)

Shared by janebeingjane ·
Company
DocuSign
Reports
27 interview reports
Level
Internship
Stages
Phone screen

DocuSign SWE intern interviews in 2024–2026 were usually one coding round after the OA, then an HR or manager round; older loops had three short sessions.

At a glance

  • Process: after the online test, one technical round (27, 30, 31, 33, 34), then HR or a manager (27, 30, 34). Some candidates had a recruiter or HR call first (33, 35, 36). Candidate 29, who was referred, had no test: a phone screen, a 30-minute technical with the team's director, and an offer within two weeks.
  • Asked recently: Trapping Rain Water with a 2D follow-up (30), two array problems in one round (32), a hashing-and-strings problem (31), and Two Sum with FizzBuzz (36). Design questions joined the coding in 30 and 34, and project questions came up in 30, 32 and 34.
  • Difficulty: candidate 34 listed two easy questions and one medium; 30 found the design questions needed more structure than the coding. One interview was behavioral only (28).
  • Practise first: Rain Kept Between Walls, Three-Part Splits With a Light Middle, Most Transactions Kept Without Going Negative and Two Positions That Add Up to a Target.

Coverage: 27 DocuSign software engineering intern candidates who reached a live interview, each in one entry with their test and their interviews. Ten are current (2024–2026): India, California and one remote U.S. intern where a place is given. The other 17 (2018–2022, U.S.) are history. Test-only reports and the overview tables for the whole series are in Part 1.

In this series

  • Part 1: online test and overview — the process, question tables for all 28 current reports, and 26 test-only reports
  • Part 2 (current): interviews, 27 candidates

What came up

In the 10 current reports, coding came first in every technical round that was described (30, 31, 32, 36), and six candidates also talked about projects or behavioral questions (28, 30, 32, 33, 34, 36). The current questions are in Part 1's tables; the older ones are indexed at the start of History below.

10 candidate timelines from 2024–2026

27: Campus drive: three-question test with a hard SQL query, then two interviews

Report date: Jul 2026 · Role: Software Engineer (Internship) · Location: Jamshedpur, India · Result: No offer

  1. Applied through the university as part of an on-campus drive. The whole process took about three weeks: resume screening, the test, a technical interview, and an HR interview. One student from the drive got selected.
  2. Online test: a BFS problem, about LeetCode Medium; a 2D dynamic programming problem, Medium to Hard; and a SQL query the candidate called very difficult.
  3. Technical and HR interviews: the candidate didn't describe the questions.

28: A behavioral-only interview, rescheduled

Report date: May 2026 · Role: Software Engineer (Internship) · Result: No offer

  1. The time was pushed back from the original slot.
  2. Behavioral questions only, with no coding.
  3. The candidate said the interviewer seemed uninterested.

29: Referral, phone screen, then a 30-minute technical with the director

Report date: Apr 2026 · Role: Software Engineer (Internship) · Location: California · Result: Offer

  1. Applied through an employee referral. The process took two weeks.
  2. A phone screening first.
  3. Then a 30-minute technical screen with the director of the team the role was on.
  4. HR steps after that, and that was the whole process.

30: A 90-minute test, Trapping Rain Water, then the hiring manager

Interview date: Mar 2026 (test before Mar 12) · Role: Software Engineering Intern · Location: India · Result: No offer

Online test (HackerRank, 90 minutes)

  1. Two data-structures-and-algorithms problems and one SQL problem. The candidate fully solved the two coding problems; the SQL problem was harder for them.

Technical round (Zoom + HackerRank, 60 minutes)

  1. Trapping Rain Water. They started with brute force, then moved to a two-pointer solution with no stack.
  2. Edge cases, and how the same idea would work on a 2D grid.
  3. Some basic low-level design and high-level system design questions. The candidate found these needed more structure than the coding part.

Hiring manager round (Zoom, 30 minutes)

  1. Walkthroughs of their projects: a UPI fraud-detection ML project and a backend project.
  2. Their previous internship at a telecom company, including LTE and radio access network basics.
  3. Where a company like Amazon would use SQL versus NoSQL. The candidate felt this answer wasn't strong.

31: Campus: about 400 down to 15, then a hashing-and-strings problem

Report date: Mar 2026 · Role: SDE Intern (on-campus) · Result: Rejected after the final round

  1. Online test: two DSA problems and one SQL query. The candidate fully solved one coding problem, partly solved the other, and didn't finish the SQL. About 400 students took it and 15 were shortlisted.
  2. Technical interview: a live DSA problem built on hashing and strings.
  3. Final round: four candidates reached it. This candidate was rejected after it.

32: A wheels puzzle and a grid path in the test, two array problems live

Report date: May 2025 · Role: Software Engineer Intern (Summer 2025) · Type: On-site internship, stipend quoted in Indian rupees

Online test (HackerRank)

  1. Given the total number of wheels n, count how many different mixes of 4-wheelers and 2-wheelers use exactly n wheels.
  2. A SQL question based on joins.
  3. A grid of empty and blocked cells. Find a path whose closest approach to any blocked cell is as far away as possible, and return that distance.

Interview round 1

  1. Count the ways to split an array into three non-empty consecutive parts so that the middle sum is at most the left sum plus the right sum.
  2. Given a list of transactions, find the longest subsequence you can apply in order without the balance ever going negative.

Interview round 2

  1. Projects and behavioral questions.

A later commenter on the same post said they went through the same process in 2026, without more detail.


33: A recruiter call the day after the test, a technical a week later

Report date: May 2025 · Role: SWE Intern

  1. Applied in mid-April and got the test link at the end of the month. Finished it the next night.
  2. The recruiter call came the day after, with a few easy behavioral questions.
  3. An hour after that call, an email asked for technical-interview availability. The technical round happened about a week later.

34: Test in 40 minutes, technical and HR on back-to-back days

Report date: Apr 2025 · Role: Software intern (2026 graduating class)

  1. Took the test on April 5 and finished every question in about 40 minutes.
  2. Technical round on April 15 and HR round on April 16.
  3. The candidate listed two easy and one medium DSA question, object-oriented design, and questions about their projects. They didn't say which came in the test and which in the technical round.

35: HackerRank, then 30 minutes with HR

Report date: Apr 2025 · Role: SWE Intern

  1. Took the HackerRank test.
  2. Invited to a 30-minute interview with an HR person. The candidate expected it to be a phone call before a technical round and a hiring-manager round.

36: U.S. remote: a one-problem DP test, then Two Sum and FizzBuzz

Report date: about 2024 · Role: Software Engineer Intern · Location: United States, remote · Result: Offer

  1. Online test: a single LeetCode Medium dynamic programming problem.
  2. Recruiter call and hiring manager call: tell me about yourself.
  3. Two coding interviews: Two Sum and FizzBuzz.

The whole process took about three weeks.


History (before 2023)

Seventeen reports from 2018 to 2022, mostly U.S. Many went straight from a test, take-home or career fair to a loop of short interviews.

Questions in these older reports

The Reports column names the entries. Counts cover these 17 reports only.

Coding: strings and words

Question Reports Last seen
Exact Palindrome Check 3: 37, 45, 52 Apr 2022 (report date)
Reverse a string: Reverse the Characters of a Text 2: 37, 52 Apr 2022 (report date)
Paired Words That Share a Substring 1: 37 Apr 2022 (report date)
Are All Words Anagrams? 1: 40 May 2020 (report date)
Alphabetize a Word List 1: 40 May 2020 (report date)
List Each Name Once, Alphabetically 1: 49 Nov 2018 (report date)
A trie question (no details) 1: 50 Oct 2018 (report date)
Find the Words for Each Prefix (talk only) 1: 51 Sep 2018 (report date)
Distinct Letter Arrangements 1: 53 Aug 2018 (report date)

Coding: arrays, lists and other

Question Reports Last seen
Two Sum: Two Positions That Add Up to a Target 2: 48, 49 Mar 2019 (report date)
Combine Two Sorted Lists Into One 1: 37 Apr 2022 (report date)
Number Digits Backward 1: 40 May 2020 (report date)
Smallest and Second-Smallest Distinct Values 1: 42 Feb 2020 (report date)
LeetCode 206 style, Reverse the Order of a Linked List 1: 42 Feb 2020 (report date)
Busiest Station on a Grid 1: 44 Dec 2019 (report date)
Stretch Each Number Into Two Halves 1: 44 Dec 2019 (report date)
Pre-screen: measure your internet bandwidth 1: 46 Apr 2019 (report date)
LeetCode 332 style, Rebuild a Trip From Flight Tickets 1: 47 Apr 2019
Take-home, LeetCode 528 style: Size-Weighted Random Server Picks 1: 48 Mar 2019 (report date)
Second-Smallest Distinct Value in a Min-Heap Tree 1: 48 Mar 2019 (report date)
How Many Primes Are Below n (talk only) 1: 51 Sep 2018 (report date)

Behavioral (BQ), asked more than once

Question Reports Last seen
Most challenging project, or the one hardest to leave 4: 37, 44, 48, 49 Apr 2022 (report date)
What should I have asked you? 3: 44, 48, 49 Dec 2019 (report date)
What programming languages are you comfortable in? 2: 37, 39 Apr 2022 (report date)
Where do you see yourself in five years? (42: three years) 2: 37, 42 Apr 2022 (report date)

Behavioral (BQ), asked once

Question Reports Last seen
Tell me about yourself 1: 37 Apr 2022 (report date)
Why did you switch into tech? 1: 37 Apr 2022 (report date)
Are you a fast learner? 1: 37 Apr 2022 (report date)
What do you do when stuck on a project? 1: 37 Apr 2022 (report date)
What would you build with unlimited resources? 1: 37 Apr 2022 (report date)
What do you think DocuSign does? 1: 37 Apr 2022 (report date)
What do you want to learn here? 1: 37 Apr 2022 (report date)
A conflict on your team 1: 37 Apr 2022 (report date)
Hardest part of a past internship 1: 37 Apr 2022 (report date)
Who you like to work with, and teammates who don't do their part 1: 42 Feb 2020 (report date)
A time you couldn't explain something well 1: 44 Dec 2019 (report date)
Why do you want to work at DocuSign? 1: 45 Oct 2019 (report date)
Biggest weakness (is "none" a good answer?) 1: 48 Mar 2019 (report date)

Concepts

Question Reports Last seen
Edge cases to test in a deposit and withdraw program 1: 37 Apr 2022 (report date)
Asynchronous programming and programming paradigms (JavaScript) 1: 52 Sep 2018 (report date)

37: A very simple test, then a superday for three roles (2022)

Report date: Apr 2022 · Role: Software Engineer Intern · Result: Offer

The candidate first applied to a test-team intern role. The recruiter then had them interview for software engineering and information architect too. Each track was one very simple online test, which the candidate didn't describe, and then a superday.

Software engineering superday

  1. A senior engineer on the Android team went deep on their resume, then asked them to reverse a string. They swapped characters with two pointers in Python, were asked not to use another data structure, then used slicing and couldn't explain how it works. Time and space complexity came last.
  2. Another engineer on the same team asked about a project, then palindrome and its time complexity, and whether it could beat O(n).
  3. Then: given two arrays of strings a and b of the same length, print YES for each pair a[i], b[i] that shares a substring, and NO otherwise. They used a hash map in O(n·k). Last came design patterns, Java and Kotlin.
  4. The recruiter called the next day with an offer.

Test-team superday (not selected)

  1. The team manager asked them to introduce themselves and why they switched to tech, then asked them to merge two sorted arrays. They gave only the naive approach.
  2. A senior engineer asked about projects, then to reverse a string. Behavioral questions followed: languages, the most challenging project, whether they learn fast, and what they would do when stuck on a project, asked again and again.
  3. Another senior engineer asked them to check a palindrome, then about testing experience: which edge cases they would test in a deposit and withdraw program.

Information architect (hiring manager, behavioral only)

  1. What app would you build with unlimited resources? Where do you see yourself in five years? What does DocuSign do? What do you want to learn here? A team conflict, and the hardest part of a past internship.

38: Recruiter interview, then a five-question test with SQL (U.S., 2022)

Report date: Feb 2022 · Role: SWE Intern · Location: United States · Result: No offer

  1. A recruiter interview came first, asking about experience and projects.
  2. Then a coding assessment of about five questions. One was a SQL query-writing question, which surprised the candidate.

39: A background chat before the coding link (New York, 2022)

Interview date: Jan 2022 · Role: Software Engineer (Internship) · Location: New York, NY · Result: No offer

  1. Applied through the university. The process took about four weeks.
  2. A first conversation about their background, projects, programming languages, and the company and its culture. One question: what programming languages are you comfortable in?
  3. Then a coding assessment link. They didn't make it past that.

40: Referral, a simple pre-screen, then a Zoom "on-site" (2020)

Report date: May 2020 · Role: SWE Intern · Location: United States · Result: Offer

  1. Applied with a referral from a friend in sales and heard back within a few weeks.
  2. A "pre-phone screen" with a very simple coding problem, a recruiter call the day after, then a Zoom "on-site" with three developers the day after that.
  3. Questions across the process: reverse the digits of a number (123 → 321), check whether a set of words are anagrams of each other, and turn a large set of words into an alphabetized file in any language. The report doesn't say which question came in which step.

41: Seattle, 2020: take-home, then three 45-minute interviews

Report date: Mar 2020 · Role: Software Engineer Intern · Location: Seattle, WA · Result: Offer

  1. Applied on the portal and received a take-home exercise, submitted to the recruiter.
  2. Three back-to-back 45-minute interviews: two LeetCode Medium problems and one Easy. The candidate found the interviewers friendly.

42: Career fair, then three 30-minute sessions (2019)

Report date: Feb 2020 (interviews late 2019) · Role: Software Engineer Intern (career fair, bachelor's) · Result: Offer

  1. Technical: find the smallest and the second smallest element in an unsorted array.
  2. Behavioral: project experience, what kind of person they like to work with, what happens if teammates don't do their work, how to measure effectiveness, and their three-year plan.
  3. Technical: reverse a linked list.
  4. The candidate called the questions easy to medium and the interviewers friendly. The offer came in January.

43: A recruiter's coding challenge, then a straightforward phone screen (2020)

Report date: Feb 2020 · Role: Software Engineer (Internship) · Location: United States · Result: No offer

  1. A recruiter reached out with a coding challenge.
  2. A phone screen followed, with technical questions and questions about the candidate. They found it straightforward.

44: Busiest station and a "stretch" array (2019)

Report date: Dec 2019 · Role: Software Engineer Intern (career fair, bachelor's) · Result: Offer

Three sessions back to back in an hour and a half:

  1. Given a width, a height and the coordinates of stations, every grid position uses its nearest station. Find the busiest station. They built a count map and took the largest count.
  2. Behavioral: the project that was hardest to leave, the most technically challenging project, a time they couldn't explain something well, and what they would ask if they were the interviewer.
  3. "Stretch" an array so each number becomes two halves: [14, 0, -5] becomes [7, 7, 0, 0, -2, -3]. Follow-ups asked about the array and the time complexity.

The year before, this candidate had failed the same onsite on the behavioral round. This time they got the same strict interviewer and passed.


45: 30 minutes on a whiteboard: palindrome check (Orlando, 2019)

Report date: Oct 2019 · Role: Software Engineer (Internship) · Location: Orlando, FL · Result: No offer

  1. A 30-minute technical interview on a whiteboard.
  2. A few behavioral questions first, like why they wanted to work at DocuSign.
  3. Then the coding question: check whether a string is a palindrome.

46: Measure your bandwidth, then three in-person interviews (Seattle, 2019)

Report date: Apr 2019 · Role: Software Engineer (Internship) · Location: Seattle, WA · Result: No offer

  1. An online coding question as a pre-screen: write a program that measures your internet bandwidth.
  2. Then three one-on-one technical interviews in person. The candidate didn't describe the questions.

47: 30-minute Zoom: reconstruct the itinerary (2019)

Interview date: Apr 2019 · Role: Software Engineer (Internship) · Location: United States · Result: No offer

  1. Applied through the university.
  2. A 30-minute Zoom call with one coding problem: given a set of flight tickets, reconstruct the itinerary.
  3. The candidate felt the interviewer was checking email and not engaged.

48: A weighted-random take-home, then Two Sum in a story and a heap (2019)

Report date: Mar 2019 (onsite March 11) · Role: Software Engineer Intern (Summer 2019, master's) · Result: Offer, later declined

  1. The school's career office passed the candidate's resume along. They applied on January 9 and got a take-home on January 29: a reworded version of LeetCode 528, random pick with weight. They sent it back on February 3 and heard back on February 22.

Onsite: three 30-minute rounds

  1. Behavioral only: resume, a project, the project that was hardest to leave, the most challenging project, what internship they want, and what they think the interviewer should have asked. They were also asked whether "no weaknesses" is a good answer.
  2. Two Sum, wrapped in a long story: a builder cuts rafters at different angles and needs two that together form a fixed ridge angle. Design an app that records every cut angle and finds such a pair.
  3. A min-heap stored as a binary tree, with possible duplicate values: find the second smallest value. They didn't find a good approach in time.

HR gave a verbal offer two days later and the written offer came on March 19. A clash with another internship made them decline.


49: Career-fair onsite: distinct names and a Two Sum variant (2018)

Report date: Nov 2018 · Role: Software Engineer Intern (career fair, bachelor's) · Result: Rejected

Three 30-minute interviews, one behavioral and two technical:

  1. Behavioral: the project that was hardest to leave, the most challenging project, what internship they want, and what they think should have been asked.
  2. Print every distinct name in a string array. First with a hash set, then with no extra memory, which they did by sorting the array first.
  3. A variant of Two Sum.

50: Forty-five minutes on a trie (2018)

Report date: Oct 2018 · Role: Software Engineer Intern (career fair, bachelor's) · Result: Rejected

  1. One coding question about a trie. The candidate hadn't prepared it and was stuck for 45 minutes. No other details.

51: HR call, then a talk-only phone screen (2018)

Report date: Sep 2018 · Role: Software Engineer Intern (bachelor's)

  1. An email from HR, then a call about their background, then a phone interview the next week.
  2. The phone interview started with past projects, then two questions answered aloud with no code.
  3. Given an array of words and a prefix, how do you quickly find every word that starts with the prefix?
  4. Given n, how do you quickly find every prime less than n?

52: A 30-minute phone screen with a frontend engineer (2018)

Report date: Sep 2018 · Role: Software Engineer Intern (bachelor's) · Result: Passed to the onsite

  1. JavaScript concepts first: asynchronous programming and programming paradigms. The recruiter hadn't said which team it was for.
  2. Then reverse a string, with a follow-up: use it to check whether a string is a palindrome. They suggested comparing with the original, or two pointers.
  3. Four minutes were left for their questions. They felt the interviewer was rushing. Two days later they were invited to an onsite at a conference career fair.

53: A take-home, then an hour on the phone (2018)

Report date: Aug 2018 · Role: Software Engineer (Internship) · Location: United States · Result: Offer

  1. Applied by emailing the recruiter. The first round was a take-home coding challenge.
  2. Then one hour on the phone: 30 minutes behavioral and 30 minutes technical. The question: find duplicate permutations in a string.

Patterns across the reports

  1. A short call before the technical round. Eight candidates had a recruiter, HR, phone or background call first: 29, 33, 35 and 36 recently, and 38, 39, 40 and 51 before 2023.
  2. Thirty-minute rounds. The technical screen in 29, the HR call in 35 and the hiring-manager round in 30 each ran 30 minutes. Before 2023, 45, 47 and 52 had 30-minute screens, and 42, 48 and 49 had three 30-minute sessions in a row.
  3. The same behavioral questions, year after year. The most challenging project and the project hardest to leave came up in 37, 44, 48 and 49; "what should I have asked you?" in 44, 48 and 49.
  4. Classic warm-ups. Reverse a string or check a palindrome in 37, 45 and 52; Two Sum or a Two Sum story in 36, 48 and 49.
  5. An interviewer who seemed checked out. Candidates 28 and 47, seven years apart, both said their interviewer didn't seem engaged, and 52 felt rushed.

Common questions

How many interview rounds come after the DocuSign OA?

Usually two in recent reports: a technical round and an HR or hiring-manager round (27, 30, 34). Candidate 32 also had two rounds, and 36 had a recruiter call, a hiring-manager call and two coding interviews.

What does the DocuSign technical round ask?

Coding first. Recent rounds named Trapping Rain Water with a 2D follow-up (30), two array problems (32), a hashing-and-strings problem (31), and Two Sum and FizzBuzz (36). Design questions sometimes followed (30, 34).

How hard is the DocuSign intern interview?

Candidates who rated it said easy to medium: two easy and one medium (34), two LeetCode Medium and one Easy (41), easy to medium (42).

How long does the DocuSign intern process take?

About two to three weeks in recent reports (27, 29, 36). Before 2023, offers sometimes came fast: the next day after a superday (37) or two days after an onsite (48).

Keep practicing

In this series

Sources: Anywhere useful interview info can be found.

0 total reactions. Your reactions: none.

Comments

0

No comments yet — be the first to share what you know.