DocuSign SWE Intern OA Questions: 53 Experiences (Part 1 of 2)

Shared by janebeingjane ·
Company
DocuSign
Reports
26 interview reports
Level
Internship
Stages
OA → Phone screen

DocuSign SWE intern OAs in 2025–2026 usually had three questions, two coding problems and one SQL query, and the SQL was often the hardest part.

At a glance

  • Process: an online test (HackerRank in five reports; 90 minutes in 30), sometimes a short recruiter or HR call (33, 35), a technical interview (60 minutes in 30), then an HR or hiring-manager round (27, 30, 34). One campus drive went from about 400 test-takers to 15 interviews (31).
  • Asked recently: every recent test that listed all its questions had one SQL query (7 reports). The coding side leaned on graph or grid search (5 of 28) and dynamic programming (4). The live rounds named Trapping Rain Water (30), two array problems (32), and Two Sum with FizzBuzz (36).
  • Difficulty: three candidates called the SQL their hardest OA question (01, 27, 30) and a fourth didn't finish it (31). Candidate 02 disagreed: their SQL was medium and the last coding problem was hard. Several finished the whole test in 30 to 45 minutes (03, 04, 12, 34).
  • Practise first: Max Sum With No Two Adjacent Picks, Grid Path With the Most Clearance, Rain Kept Between Walls (Trapping Rain Water) and Beautiful Number Orderings.

Coverage: 53 DocuSign software engineering intern reports (Software Engineer Intern, SWE Intern, SDE Intern). 28 are current, from 2024 to 2026: 18 test-only reports in this part, and 10 reports with live interviews in Part 2. Where a place is given they are mostly from India (campus and off-campus drives), plus California and one remote U.S. intern. The other 25 (2018–2022, mostly U.S.) are history at the end of each part and stay out of the counts. Each candidate appears once: a candidate who reached the interviews is in Part 2, with their test there too.

In this series

  • Part 1 (current): overview, question tables, and 26 test-only reports
  • Part 2: interviews — 27 candidates who reached live rounds, each with their test and interviews in one place

What came up

SQL is the thread that ties the recent tests together, and graph or grid search is the most common coding topic. The table counts the 28 current candidates in both parts.

Topic Reports Last seen
SQL query in the test 7 of 28 Jul 2026 (report date)
Behavioral or project questions in a live round 6 of 28 May 2026 (report date)
Graph or grid search 5 of 28 Jul 2026 (report date)
Dynamic programming 4 of 28 Jul 2026 (report date)
Array problems in a live round 3 of 28 Mar 2026
Design (low-level, high-level or object-oriented) 2 of 28 Mar 2026
Counting and combinatorics 2 of 28 Feb 2026 (report date)
Hashing and strings 1 of 28 Mar 2026 (report date)

Rows: SQL 01, 02, 15, 27, 30, 31, 32; behavioral 28, 30, 32, 33, 34, 36; graph 01, 09, 15, 27, 32; DP 01, 15, 27, 36; arrays 30, 32, 36; design 30, 34; counting 02, 32; hashing 31.

Questions we found

These tables cover the 28 current reports. Nobody shared a SQL schema or the exact ask, so the SQL questions stay in the topic table. Older questions are in each part's History.

Algorithms: online test

Question Reports Last seen
House Robber I and II style: in a line and in a circle 1: 01 Apr 2026 (report date)
LeetCode 526 style, Beautiful Number Orderings 1: 02 Feb 2026 (report date)
Vehicle Mixes for a Wheel Total 1: 32 May 2025 (report date)
Grid Path With the Most Clearance 1: 32 May 2025 (report date)
Reach node n−1 in at most k edges, smallest largest edge 1: 09 Apr 2025 (report date)

Algorithms: live interviews

Question Reports Last seen
LeetCode 42 style, Rain Kept Between Walls 1: 30 Mar 2026
Three-Part Splits With a Light Middle 1: 32 May 2025 (report date)
Most Transactions Kept Without Going Negative 1: 32 May 2025 (report date)
LeetCode 1 style, Two Positions That Add Up to a Target 1: 36 about 2024
LeetCode 412 style, Fizz and Buzz Words From 1 to n 1: 36 about 2024

Behavioral (BQ)

Question Reports Last seen
Tell me about yourself 1: 36 about 2024

Concepts

Question Reports Last seen
Where would a company like Amazon use SQL, and where NoSQL? 1: 30 Mar 2026

18 test-only reports from 2025–2026

These candidates shared their test and, at most, whether a call followed. Entries 03 to 12 and 16 to 18 come from one spring 2025 wave, when many applicants took the test within a few weeks and compared notes.

01: Off-campus test with two linked DP problems and a joins query

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

  1. Two closely related coding problems. The candidate compared them to House Robber I and II, the "take or skip, but never two neighbors" problem, first in a line and then in a circle. They also described the pair as graph problems.
  2. One DBMS question, which they found trickier: a SQL query with joins and aggregate functions.

02: Campus test of rising difficulty, done in one day

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

  1. Applied through the university. The whole process took one day.
  2. Three questions, each harder than the last: an easy-to-medium coding problem, a medium SQL problem, and a hard coding problem.
  3. The one problem the candidate named: count the permutations of 1..n where, at every position i, either i divides the number placed there or that number divides i. This is the "Beautiful Arrangement" problem.

03: Finished in 37 minutes

Report date: Apr 22, 2025

Solved it in about 37 minutes, with over an hour left. No reply a week later.


04: Three questions in 30 to 40 minutes

Report date: Apr 21, 2025

Three questions, done in 30 to 40 minutes. No second-round invite yet.


05: All three, with time to spare

Report date: Apr 17, 2025

All three solved with 40 to 45 minutes left. No next-round email a week later.


06: Shortlisted a week out

Report date: Apr 15, 2025

Submitted with about an hour to spare and was shortlisted for an interview a week later.


07: All solved, still waiting

Report date: Apr 15, 2025

All three solved. Still waiting for an email.


08: Two full solutions and a partial

Report date: Apr 10, 2025

Two full solutions and a few failed test cases on the third. No email.


09: Two and a half solved, then a rejection

Report date: Apr 10, 2025 · Result: Rejected

  1. About two and a half questions solved.
  2. The third question: an undirected graph where you must reach node n−1 using at most k edges, so that the largest edge on the path is as small as possible. Another candidate described a similar version framed around servers.

10: All three solved, no invite yet

Report date: Apr 9, 2025

All three solved. No interview email at that point.


11: Every test case passed

Test date: Apr 6, 2025

HackerRank, three questions, every test case passed. No response yet.


12: Three in 45 minutes, then a long wait

Test date: Apr 4, 2025 · Role: 2026 graduating class

All three in 45 minutes. Still no email by Apr 21.


13: Two solved, still rejected

Report date: Apr 2025 · Role: Software Intern · Location: India · Result: Rejected after the OA

  1. The candidate fully solved two of the OA questions.
  2. A rejection email came anyway.

14: Test link the day after applying

Report date: Apr 2025 · Role: Software Engineer Intern

  1. Applied on April 4 and got the OA link on April 5.
  2. The link was valid until 11:00 AM on April 7.

15: DP, graphs and SQL, 14 of 15 tests on the last one

Report date: Apr 2025 · Role: Software Intern

  1. The candidate called the OA medium to hard, with DP and graph problems.
  2. The test was HackerRank: two DSA problems and one SQL query.
  3. They fully solved one coding problem and the SQL question. The other coding problem passed 14 of its 15 test cases.

16: All three solved (2025 class)

Report date: Apr 2025 · Role: 2025 graduating class

All three solved. Waiting to hear back.


17: All three solved (2026 class)

Report date: Apr 2025 · Role: 2026 graduating class

All three solved. No interview email.


18: Two questions, 15 of 15 on both

Test date: Mar 30, 2025

Two questions, 15 of 15 test cases on both. Waiting to hear about an interview.


History (before 2023)

Eight test-only reports from 2019 to 2021, when the first step was a two-question HackerRank test, a short pre-screen program, or a take-home.

19: Wrong sale prices and non-overlapping intervals (2021)

Report date: Feb 2021 · Role: Software Engineer Intern (master's, applied online)

  1. Given four lists (product names, the correct prices, the products sold, and the prices they sold for), count how many sales used the wrong price.
  2. Given a list of start times and a list of durations, find the largest number of intervals that don't overlap.

20: HackerRank: Stay Positive and Activate Fountain (2021)

Report date: Feb 2021 · Role: Software Engineer Intern (master's, applied online)

  1. Stay Positive. Start from a value x and add each array element in turn. Find the smallest x that keeps every running sum at 1 or more. For [-4, 3, 2, 1] the answer is 5. Practice this problem
  2. Activate Fountain. A garden of length n has a fountain at every position i, and fountain i waters from i − locations[i] to i + locations[i], clipped to the garden. Find the fewest fountains to turn on so the whole garden gets water. The candidate called this one dynamic programming. Practice this problem

They said the test seemed to change between candidates and wasn't hard. Afterwards an email said the internship didn't support CPT or OPT.


21: Wrong sale prices again, plus minimum taps (2021)

Report date: Feb 2021 · Role: Software Engineer Intern (master's, applied online) · Result: Rejected

  1. An easy question about finding the goods sold at the wrong price, solved with a map.
  2. LeetCode 1326, the minimum number of taps to open to water a garden.
  3. They were rejected right away.

22: Two-question HackerRank test, then silence (2021)

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

  1. Invited to a HackerRank online test with two questions.
  2. An email said they passed and that DocuSign would reach out in early January. Nobody did, and a follow-up to the recruiter went unanswered.

23: Fall 2020 HackerRank: Group Division and Number of Moves

Report date: Nov 2020 · Role: Software Engineer Intern (Summer 2021, bachelor's) · Result: Rejected after the test

  1. The candidate noted that earlier years had a take-home, and this year it was HackerRank.
  2. Group Division. Given student levels and a maximum allowed gap k, split the students into the fewest groups so no two students in a group differ by more than k. Example: [4, 1, 5, 8] with k = 3. Practice this problem
  3. Number of Moves. The candidate gave only the title and pointed to another post.

24: A basic command-line program, scored and rejected (2019)

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

  1. A simple "pre-phone screen" coding challenge: write a program that takes command-line arguments and does something basic.
  2. The candidate sent it back within an hour.
  3. Over a month later, a rejection said their score did not qualify. They asked what was scored, since their program worked, and never got an answer.

25: Take-home: assign jobs to servers by size (2019)

Report date: Jan 2019 · Role: Software Engineer Intern (career fair, master's) · Result: Rejected

  1. HR emailed the take-home three days after the career fair and asked for it back soon.
  2. The task: servers come in different sizes, and each job goes to a random server, weighted by size. A server three times as big should get jobs three times as often, so 75% against 25%. With X:4 and Y:1 the output should look like XYXXX. The order doesn't matter, only the proportions.
  3. The candidate's own lessons: their Python file had too few comments, no lint pass, no README and too few tests, and it wasn't executable. They were rejected.

26: A PDF coding challenge under NDA (2019)

Report date: Jan 2019 · Role: Software Engineer Intern (career fair, master's) · Result: Rejected

  1. Met DocuSign at a career fair and applied for the internship.
  2. Got a PDF coding challenge, which they called "a simple, common medium problem". It was under NDA, so no details.
  3. Rejected. They think it was because they sent it back a week late.

Patterns across the reports

  1. A clean score didn't guarantee a call in spring 2025. Many candidates who finished every question were still waiting when they posted (04, 05, 07, 10, 11, 12, 16, 17). Others moved quickly: 06 was shortlisted within a week, and in Part 2, 33 had a recruiter call the day after the test and 34 had interviews ten days later.
  2. Partial scores went both ways. Candidates 09 and 13 were rejected after solving two or two and a half questions; 08 and 15 had partial scores and hadn't heard either way.

Common questions

How many questions are on the DocuSign intern OA?

Three in 2025–2026: two coding problems and one SQL query in every test that listed all of them (01, 02, 15, 27, 30, 31, 32). One wave candidate reported only two (18). The 2020–2021 tests had two questions (20–23).

How long is the DocuSign OA?

Candidate 30's HackerRank test ran 90 minutes. Several candidates finished in 30 to 45 minutes (03, 04, 12, 34).

Is there SQL on the DocuSign SWE intern OA?

Yes, in every recent test that listed its questions. Candidates 01 and 32 said it was about joins, and 01 added aggregate functions. A U.S. intern in 2022 also got a SQL question in their coding test (38, Part 2).

How soon does the DocuSign OA link come?

Fast for some: candidate 14 got it the day after applying, with three days to finish. Candidate 33 waited about two weeks.

How long until DocuSign replies after the OA?

Anywhere from a day to never. Candidate 33 had a recruiter call the next day and 06 an interview a week out, while many in the spring 2025 wave were still waiting a week or more later (see the first pattern).

What to practise

  • SQL with joins and aggregates. It was in all 7 recent tests that listed their questions (01, 02, 15, 27, 30, 31, 32), and three candidates found it the hardest part while a fourth didn't finish it. No reporter shared a schema, so there is no SQL problem to link yet.
  • Max Sum With No Two Adjacent Picks and its circle version. The named DP pair from an Apr 2026 test (01); DP came up in 4 of 28 current reports.
  • Grid Path With the Most Clearance. Graph or grid search came up in 5 of 28 current reports; this is the named grid task (32, May 2025).
  • Rain Kept Between Walls. Trapping Rain Water, the most recent named live-round problem, with a 2D follow-up (30, Mar 2026).

Keep practicing

In this series

Sources: Anywhere useful interview info can be found.

Next in this seriesDocuSign SWE Intern Interviews: 27 Experiences (Part 2 of 2)
0 total reactions. Your reactions: none.

Comments

0

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