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

Comments

Popular posts from this blog

Quality of Code is Quality of Life

About 20 years ago when I started working in technology companies I remember “the best” engineers had similar patterns:
-They worked crazy hours
-They knew the systems no one else knew
-They could react and deliver something faster than anyone else
You could always hear other employees say: “Bob is really smart, no one knows how to get anything done in system X besides him!”

This reinforced optimization around being the only person who knew how to do something in some part of the code.  That in turn reinforced job security and bargaining for those engineers, but also chained them to a particular system.  We had big code bases of C++ or Java code where some “Bob” hacked up features as soon as he possibly could.  “Bob” would have occasional nuclear disasters where he’d sleep in the office or through the weekend and then everyone would thank him for how he “saved the day.”  “Bob” sacrificed his quality of life to get praise when he hacked stuff up quickly and then the second time when n…

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!

Code versus Configuration

At Ethos we are building a distributed mortgage origination system and in mortgage there is a lot of
different user types with processes that vary depending on geography.  One of our ongoing discussions is about how much of the logic resides in code vs. being in a workflow system or configuration.  After researching this topic for a bit, I have arrived at a conclusion that the logic should live outside of code very infrequently, which might come as a surprise to a lot of enterprise software engineers.

Costs of configuration files and workflow engines First thing that I assume is true is that having any logic outside of the code has costs associated with it.  Debugging highly configurable system involves not only getting the appropriate branch from source control, you also need to make sure that the right configuration values or the database.  In most cases this is harder for programmers to deal with.  In many FinTech companies where the production data is not made readily accessible…