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

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!

Chief Collaboration Officer

When you search for the word “collaboration” on the Internet, the top hits are mostly software packages you can buy.  Software can facilitate collaboration, but it doesn’t make people collaborate on its own.

One of the key functions of a technical leader is to bring a team together, help people share ideas, and facilitate team members helping each other.  When a software leader overlooks this key function, you end up with a group of individual contributing engineers instead of a cohesive team.
Before we get into tactics, we should ask “Why is collaboration important for an engineering team?” 
It’s critical to examine your assumptions, so here are my reasons for why a group of engineers working on their own are worse than a team working together: Smart people learn from each other.Getting your plans and designs reviewed by other people allows you to leverage their experience and check your assumptions.Collaboration produces artifacts that stay after collaboration has taken place (such…

Hire Fast, Fire Fast? Not so Fast.

Silicon Valley is full of advice and it frequently comes from people who have little experience on the subject matter.  A popular topic surrounds hiring and terminations with the king catch phrase being: “Hire Fast, Fire Fast.”  To me, what that usually means is lack of diligence, thought, communication and courage.

When hiring people love going with their gut feel, often with disastrous results.  There is an obvious subject of diversity of thought, appearance and background.  When thinking “fast” you are probably hiring people like yourself because humans quickly react to people who they believe are in their tribe.

A startup that lacks the resources of a big company often becomes so desperate to get technical staff that when a decent candidate comes along, excitement ensues and the employer doesn't slow down to put them through a more rigorous hiring process.

I highly encourage technical founders and engineering executives to write out their precise hiring process.  Of course, y…