DocuSign provides a lot of great perks for their employees and regularly solicits feedback to raise the bar. They offer:
The positive impact on the environment from the software, along with DocuSign's additional efforts in protecting the environment, is inspiring.
Employee Resource Groups and DocuSign's efforts to promote diversity in both leadership and non-leadership positions are great. I have a ton of respect for the way Tom Casey, our SVP of Engineering, dives into a lot of challenging conversations and is willing to change his thinking when challenged.
DocuSign really does care a lot about trust, security, and respecting our users' privacy. I respect that I have not had to implement any features that are user-unfriendly or hostile. People actually care.
I would not recommend DocuSign as a place to start one's career as a software engineer. Depending on your team, you might often work on code that is quite dated.
While it is a good place to work, at some point, you'll probably want to move on, and the experience you'll have gained here might not be ideal for moving on to that next position.
Engineering feels fragmented. Questions that feel like they should have a general, company-wide answer sometimes require going from team to team to get an answer.
Our process for planning and delivering new features is not agile at all. DocuSign is so focused on protecting its core business and maintaining its SLAs that new development can often be hindered as a result. I think there's potential to create more efficient paths forward for smaller products.
Deadlines can be aggressive. I don't feel overworked, but I do feel a general sense of disappointment from often not measuring up to what DocuSign wants us to accomplish.
Career advancement can depend on the visibility and success of your project.
My advice will generally be around engineering. Focus on unifying everyone, regardless of where we were acquired from.
It'd be great if more contributions and collaboration happened across different products, maybe even shuffling teams. I'm sure it'd be awful initially, but I think we could all learn a lot from each other by working in uncomfortable positions.
Along those same lines, just developing consistency around simple things, like say, shared StyleCop or ESLint configurations, would do a lot to improve working across teams. I know these sorts of things can often be considered a waste of time for little benefit, but I think at the scale DocuSign is at, it'd help us all work together with less friction.
2 phone screens, a take-home coding exercise, and 3 hours of in-person interviews. The first hour is coding. The second hour is whiteboarding system architecture questions. The third hour is application architecture questions.
The interview process is smooth, with 5/6 rounds of interviews. The questions are similar to those at any other tech company. You must prepare well to crack the interview. Ensure that you review your basics, like algorithms and system design question
The interview process included: * A basic recruiter call. * LeetCode questions. * System design. * A hiring manager interview. The LeetCode questions were of medium difficulty. The system design discussion seemed relevant to the business, w
2 phone screens, a take-home coding exercise, and 3 hours of in-person interviews. The first hour is coding. The second hour is whiteboarding system architecture questions. The third hour is application architecture questions.
The interview process is smooth, with 5/6 rounds of interviews. The questions are similar to those at any other tech company. You must prepare well to crack the interview. Ensure that you review your basics, like algorithms and system design question
The interview process included: * A basic recruiter call. * LeetCode questions. * System design. * A hiring manager interview. The LeetCode questions were of medium difficulty. The system design discussion seemed relevant to the business, w