Taro Logo

Software Engineer Interview Experience - Seattle, Washington

April 1, 2023
Negative ExperienceNo Offer

Process

The interview process involved:

  • A phone call with the recruiter.
  • A technical phone screening, including coding via a shared document where I explained my thought process.
  • A virtual onsite with three one-hour technical interviews.

I've interviewed candidates myself for software engineer roles and always ensure I'm cognizant of the time so the candidate can clearly convey their thought process. Unfortunately, this wasn't the case with Docusign. In all the rounds, interviewers spent half the time asking me the very same questions that previous interviewers had asked, specifically regarding a project I worked on.

While gaining more insight about a candidate's background is important, it was apparent that the interviewers had not synced up beforehand. This left less time for me to demonstrate my coding and problem-solving abilities. Even though I was able to efficiently solve the coding exercises, I was rejected. I wasn't surprised because I was left with little time to express my thought process clearly.

My advice to the Docusign technical interviewers would be to be mindful of the candidate's time and to collaborate beforehand so interviewers aren't asking the same questions to the candidate every time.

Questions

Signed NDA. However, the questions are pretty standard.

Was this helpful?

Interview Statistics

The following metrics were computed from 16 interview experiences for the Docusign Software Engineer role in Seattle, Washington.

Success Rate

13%
Pass Rate

Docusign's interview process for their Software Engineer roles in Seattle, Washington is extremely selective, failing the vast majority of engineers.

Experience Rating

Positive19%
Neutral38%
Negative44%

Candidates reported having very negative feelings for Docusign's Software Engineer interview process in Seattle, Washington.

Docusign Work Experiences