Skip to main content

Hiring: Technical Evangelist in San Francisco / Bay Area

Technical Evangelist

DocuSign, Inc.
San Francisco, CA, United States
Full-Time

A successful TE would be able to articulate the benefits of DocuSign service to a wide variety of audiences from CTO to an individual Software Engineer. Internally TE’s responsibility would be to influence DocuSign product strategy through knowledge of software vendors, system integrators and technological landscape.

The position will be measured by:
1) DocuSign API and protocol adoption in the marketplace
2) DocuSign service awareness among outside software developers
3) Partner satisfaction
4) Revenue resulting from integrated solutions

Position Requirements:

1) Self-direction and proven ability to identify technical trends.
2) Passion for learning new technologies in various technology stacks: Linux, Force.com, iPhone, Android and others.
3) Existing knowledge of how to create a solution in 2 or more of the technology stacks using various programming languages such as: PHP, Python, Ruby, Java and Apex Code.
4) At least 3 years of commercial experience as a Software Engineer, Product Manager or Program Manager.
5) Communication experience with a record of public speaking, writing, Facebook, twitter and blogging on technical topics.
6) Personality: positive attitude, ability to energize software developers and IT professionals, fair and balanced approach to technology.
7) Education: Bachelor of Science in Computer Science or Computer Engineering is required. Graduate degree in business or computer science is a plus.
8) Language: Must be fluent in English both verbal and written.

http://jobvite.com/m?3AIf1fwi
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!

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 …

Two Critical Questions for Your Next Interview

I’ve interviewed probably over 500 engineering and management candidates over the last several years.  There have been a lot of really smart people who have applied at DocuSign, Microsoft and Tempo Automation. A surprising number of them didn’t have a clear answer to these two essential questions:

Why are you interested in joining our team?Why should we be interested in you? 
If you are an applicant, having a prepared answer for these questions is critical.  If you are a hiring manager, you should ask them and have a clear answer to these questions at the end of the first interaction with your future team mate.

In a field where work is somewhat predictable and static, those questions are less critical, but in software development perseverance, ingenuity and focus make all the difference. These are the two main questions that will separate a subpar and a superb hire.

When I discuss those two questions with an applicant I try to go below the surface.  Generic answers like “it says you ar…