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!

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…

Pull Requests and Code Reviews

Software development involves a great deal of collaboration.  One of the most basic blocks of collaboration on a software development team is a code review.  There have been many different ways of doing code reviews over time, some of this has been dictated by the tools available.  Git and online source collaboration tools created a set of best practices that are worthwhile of adopting on any team.

About a month ago I have looked at various articles about how to best create a Pull Request (PR) and do a code review and the attached presentation is the result of this research.  The presentation can help you guide your team and develop a set of collaboration practices that works for your particular situation.

It’s good to start out with why to seek a code review.  Having clarity about your intentions helps you guide the person helping you with code reviews and also to manage your expectations about you can get out of the code review.  The reasons for seeking a code review are generally …