Skip to main content

What to expect from a software development interview at DocuSign


As some of you might know I handle the partner integration products at DocuSign.  Over last several years my team has grown quite a bit with folks that want to learn cutting edge business systems. The projects are generally around the same theme – how do we take an old process of printing and faxing and replace it with a cloud based process of DocuSigning.

We have been very lucky to get some sharp and passionate engineers that literally move mountains and we’d like to keep the bar high.  A bad engineer on the team not only is a bad producer, this person also often times takes other resources offline. How do we make sure that every new hire accelerates the speed of innovation instead of slowing it down?

Number one thing we test are coding skills.  If one can’t solve a simple algorithm like FizzBuzz it’s an immediate ejection.  There is no point in talking to a developer who can’t write simple algorithms.  Even someone who just graduated from college with a Computer Science degree should be able to write out a 5-10 line of code algorithm on the board.

Next thing we generally try to find out about that person’s exposure to architecture and patterns.  A junior hacker can write simple algorithms, but to be an engineer in charge of a system with millions of users one must know how to create factories, write unit tests, how to load balance, how to use processes, threads, daemons and asynchronous calls.

After we verify that a developer is technically competent we start probing into exposure to project management and working with other disciplines.  Does the person know how to work with bugs?  Is Scrum a new concept?  What’s the engineering approach to estimating and mitigating scheduling risks?

Last but not least we talk to the candidate about the opportunity.  Excitement and energy make up for lack of experience in certain areas.  This is a company with a huge opportunity and a history of doubling revenue and staff every 12-18 months – there is no room for resting and vesting.  I am a big believer that bad energy slows down the entire team.  We want a good culture fit and we currently have a team of doers.

In closing I’d like to add a little sales pitch: if you think you got what it takes to work at a company that’s reimagining the way people are going to be doing business in the future - let me know! The best way is to introduce yourself via Twitter - @mikebz

Post a Comment

Popular posts from this blog

Lessons from my 9 Year Journey with DocuSign

After over 9 years at DocuSign I am taking on a new challenge.  It’s been phenomenal seeing the
company grow from from 25 to 2000 employees.  DocuSign has changed the way the people do business and I am proud of it.  The next chapter is going to be heading up software development at Tempo Automation - a 25 person startup that is changing the way people produce electronics.  While I am extremely excited about the future, this is a good time to reflect on my journey and share the things that contributed to the success and things that I will do differently next time around.
1: Focus on the Customer One of the key things that contributed to the success of DocuSign and my personal career is relentless focus on the customer success.  From the very beginning our CTO has taken meetings, listened and prioritized requests and feedback coming from customers.  People who could not be bothered by customer requests didn’t last long.  As a result over time our engineering team retained and reward…

Highly Effective Software Teams

A few weeks ago our Board of Directors asked me to present my assessment of the state of software.
 I was hired to organize and grow the software team and the directors wanted to know what kind of a team we needed to build.  I was hoping that I can just reference an article somewhere that would give me the answer, unfortunately I didn’t find anything suitable. During my research I did find some great material that will be helpful if your job is to put together a highly effective software team.
A highly effective software team has the following key characteristics: dependable, committed to shared goals, passionate about technology, respectful and compassionate.  These are not limited to technology industry, it can easily apply to finance, medicine, or sports as well.  Below is the summary and references that I found. Dependable If you are creating a software product, you need to deliver your software to your users.  Your users need to know that you are able to solve their problems on …

SDET / QA Engineer Interview Checklist

After interviewing and hiring hundreds of engineers over the past 12+  years I have come up with a few checklists.  I wanted to share one of those with you so you could conduct comprehensive interviews of QA Engineers for your team.

I use this checklist when I review incoming resumes and during the interview.  It keeps me from missing areas that ensure a good team and technology fit.  I hope you make good use of them.  If you think there are good questions or topics that I have missed - get in touch with me!


SDE/T or QA Engineer interview checklist from Mike Borozdin
If you like this checklist you might want to check out these posts:
Emotional Intelligence in Software Teams  and Good-bye manual tester, hello crowdsourcing!