Sefism is free for learners. We are here to help you grow, one step at a time.Join for free
Sefism.
Product engineeringProduct company

Docusign

Builds electronic signature and agreement management software that businesses use to prepare, sign and manage contracts.

Not known4 stage process documentedFounded 2003
Headquarters

San Francisco, California, United States

Headcount

5,000 and up

5,000 or more people
Work model

Not known

Hiring

Not known

Not enough signal to say. Check the careers page directly.
Where to apply

No careers page on file yet. Try their LinkedIn or the job boards below.

Website

Ask for a referral to Docusign

A referral only means something if the person giving it can actually speak to your work. I will refer you where I know someone on the inside and your profile genuinely fits the role, and I will tell you plainly when I cannot. Either way you get an answer, and a straight one.

  • I read every request. A reply takes a few days, sometimes longer.
  • I will not refer someone for a role their profile does not fit. It wastes your time and costs me the contact.
  • Where I cannot refer you, I will say why, and point you at the way in that does work.
  • Nothing you send here is shared with anyone without you agreeing to it first.

If you found the opening, paste it. It tells me which team you mean.

A Drive, Dropbox or personal-site link is fine. Make sure it opens without a request for access, or I cannot read it.

At least a short paragraph. This is what I would be putting my name behind, so specifics beat adjectives.

Comma separated, up to six. Things you would be happy to be tested on.

How they hire

Docusign says the process usually takes three to four weeks from the first recruiter call, with a decision within seven business days of the final interview. The official description is written for students and new graduates; experienced hires report a similar shape.

  1. 1

    Recruiter screening call

    Official +1
    Recruiter screenRemote

    Reported to be about 30 minutes on your background, interest and logistics.

  2. 2

    Technical screen

    Reported +1
    Live codingRemote

    Candidates describe a remote session of 60 to 90 minutes over Zoom and HackerRank covering data structures and algorithms, basic API design and sometimes SQL.

    Data structuresAPI designSQL
  3. 3

    One to one with the hiring manager

    Official
    Hiring manager
  4. 4

    Series of team interviews

    Official +1
    Panel interviewRemote

    Docusign describes a series of interviews with members of the team. Candidates report four to five virtual rounds covering coding, system design and behavioural questions.

What comes up

Recurring themes from candidate accounts, not a question bank. Nobody is served by leaked question lists, least of all you in the interview.

  • Correct, careful code

    Reported

    Reported coding questions reward clean implementation and edge case handling over clever algorithms.

  • Multi-tenant system design

    Reported

    Design rounds reportedly touch on multi-tenant architecture, sharding and API design.

  • Ownership stories

    Reported

    Behavioural questions on ownership, production incidents and technical disagreements.

Worth reading before you apply

From the Sefism resource library, matched to the rounds above.

Roadmap
Coding Interview Playbook

A structured learning path through coding interview preparation that brings together data structures and algorithms fundamentals, recursion and the pattern-based approach to coding questions in one order. It totals 77 chapters and 1,054 lessons, with quizzes, flashcards and a certificate. Use it when you have plenty of material but no clear plan for what to study first.

  • Job search
  • DSA
  • Career
Design Gurus · Interview Prep · 3 to 6 months
SubscriptionDetails
Roadmap
FAANG Coding Interview Roadmap

A bundle of five company-specific question courses covering the problems most often reported from Meta, Microsoft, Amazon, Google and Oracle coding rounds, each split into easy, medium and hard sets with worked solutions. It suits candidates who already know the core patterns and have a loop booked at one of these companies, and want to rehearse on the questions those interviewers are known to ask.

  • Job search
  • DSA
  • Career
Design Gurus · Interview Prep · 3 to 4 months · Advanced
SubscriptionDetails
Roadmap
System Design Interview Playbook

A learning path that bundles five courses into one sequence for system design preparation: System Design Fundamentals, Grokking the System Design Interview, Advanced System Design Interview Volume II, Grokking Microservices Design Patterns and Grokking Design Patterns for Engineers and Managers. Together they add up to 76 chapters and 666 lessons. It suits engineers who want a complete, ordered curriculum instead of assembling one from scattered posts.

  • System design
  • Job search
  • Career
Design Gurus · System Design · 2 to 4 months
SubscriptionDetails
Course
Grokking Tech Salary Negotiations

A practical course on negotiating compensation in tech, from preparing and building a strategy to specific tactics, the full package beyond base salary, handling multiple offers and asking for a raise. It has tailored sections for fresh graduates and experienced engineers. It suits anyone with an offer coming, and anyone who has ever accepted the first number out of discomfort.

  • Career
  • Job search
Design Gurus · Career Growth · 1 week
SubscriptionDetails
Course
ByteByteGo

The paid learning platform from Alex Xu and co-authors, built on their System Design Interview books. It offers text-based courses with detailed diagrams on system design, machine learning and generative AI system design, mobile system design, coding interviews and more. It suits engineers preparing for technical interviews who learn best from visual explanations and want worked designs in one place rather than scattered posts.

  • System design
  • Backend
  • Job search
Alex Xu · System Design · 2 to 3 months · Intermediate
Subscription, about $16/mo billed annuallyDetails
Cheat sheet
Sefism University to Job-Ready Cheat Sheet

The quick-revision companion to the University to job-ready roadmap: OOP, Git and engineering practice, data structures, DBMS, operating systems and networks, then projects, choosing a direction, getting experience and the hiring process. It has editions for first or second year, third year, and final year. Revise a chapter a week alongside your courses and before assessments.

  • Career
  • Job search
  • CS fundamentals
  • DSA
Sefism · Career Growth · Reference · Beginner
Browse the whole library

What it pays

Nothing collected for this company yet, and nothing worth guessing at. A made-up range is worse than no range because people negotiate against it.

Add to the Docusign page

This library is only as good as what people who have been through it are willing to share. Most of these companies have no hiring process documented anywhere, and one account of what the rounds actually were is worth more than anything I can research from the outside.

What are you adding?

This decides how the claim is labelled on the page. Only someone representing the company can produce an “official” label, and I check that separately.

Year and month.

Comma separated topics, not the questions themselves.

Round by round is ideal: what each one was, how long, remote or in person, and what it covered.


Credit

Anonymous is the default. If you keep it anonymous, nothing identifying you reaches the page: it is published as a candidate account and your name stays with me. Never send anything covered by an NDA, and never send a take-home or a question paper.

Universities they recruit from

No sourced university links yet. A campus drive, a career fair appearance or an internship partnership is what puts a university here.

Add to the Docusign page

This library is only as good as what people who have been through it are willing to share. Most of these companies have no hiring process documented anywhere, and one account of what the rounds actually were is worth more than anything I can research from the outside.

What are you adding?

This decides how the claim is labelled on the page. Only someone representing the company can produce an “official” label, and I check that separately.

Year and month.

Comma separated topics, not the questions themselves.

Round by round is ideal: what each one was, how long, remote or in person, and what it covered.


Credit

Anonymous is the default. If you keep it anonymous, nothing identifying you reaches the page: it is published as a candidate account and your name stays with me. Never send anything covered by an NDA, and never send a take-home or a question paper.

How to actually get seen

Expect questions that reward reliability and edge case handling, since the product handles legal agreements. Have a production incident story ready for the behavioural round.

Sources

Whole profile last checked 2026-09-22.

Interviewed at Docusign? Fill in what changed.

Processes change, rounds get added, tests get replaced. If what you went through was different from what is on this page, tell me and I will update it.

Want me to refer you here?

Send me the role, your CV and a few honest paragraphs on why you fit it. Where I know someone inside and your profile matches, I will make the introduction. Where I cannot, I will tell you why and point you at the route that does work. You get an answer either way.

Ask for a referral to Docusign

A referral only means something if the person giving it can actually speak to your work. I will refer you where I know someone on the inside and your profile genuinely fits the role, and I will tell you plainly when I cannot. Either way you get an answer, and a straight one.

  • I read every request. A reply takes a few days, sometimes longer.
  • I will not refer someone for a role their profile does not fit. It wastes your time and costs me the contact.
  • Where I cannot refer you, I will say why, and point you at the way in that does work.
  • Nothing you send here is shared with anyone without you agreeing to it first.

If you found the opening, paste it. It tells me which team you mean.

A Drive, Dropbox or personal-site link is fine. Make sure it opens without a request for access, or I cannot read it.

At least a short paragraph. This is what I would be putting my name behind, so specifics beat adjectives.

Comma separated, up to six. Things you would be happy to be tested on.

Add to the Docusign page

This library is only as good as what people who have been through it are willing to share. Most of these companies have no hiring process documented anywhere, and one account of what the rounds actually were is worth more than anything I can research from the outside.

What are you adding?

This decides how the claim is labelled on the page. Only someone representing the company can produce an “official” label, and I check that separately.

Year and month.

Comma separated topics, not the questions themselves.

Round by round is ideal: what each one was, how long, remote or in person, and what it covered.


Credit

Anonymous is the default. If you keep it anonymous, nothing identifying you reaches the page: it is published as a candidate account and your name stays with me. Never send anything covered by an NDA, and never send a take-home or a question paper.

Work with me

Stuck on something specific?

Writing only gets you so far. If you want an answer to your situation rather than the general case, book a session and we will work through it together. Sessions are free for approved Sefism members, and a few slots open each week.