Skip to main content

Join my team - we are hiring a Technical Evangelist

This is really a dream job for a technology enthusiast. Send your resume or LinkedIn profile to me here - http://www.linkedin.com/in/mikebz or @mikebz on twitter

Technical Evangelist Job Description

Location: Seattle, WA or San Fancisco, CA
Travel Time: 25%

DocuSign is looking for a technical visionary to join our Technical Evangelism Team.

The mission of a Technical Evangelist (TE) is to win adoption of DocuSign technologies through talks, articles, blogging, user demonstrations and creation of sample projects. TE is involved in mutually beneficial alliances that drive revenue growth and expand DocuSign usage in partners offerings.

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) Passion for learning new technologies in various technology stacks: Windows, Linux, iPhone, Android and others.
2) Existing knowledge of how to create solution in 2 or more of the technology stacks using various programming languages such as: C#, VB.NET, PHP, Java, JavaScript, Apex Code and Ruby on Rails
3) Communication experience needs to include public speaking, writing and social media
4) Personality: positive attitude, ability to energize software developers and IT professionals, fair and balanced approach to technology.
5) Education: Bachelor of Science in Computer Science or Computer Engineering is required. Graduate degree in business or computer science is a plus.
6) Language: Must be fluent in English both verbal and written.
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!

There are Only Two Ways to Treat Your Team

There are only two ways to treat your team: take care of them or let them go.  Early in my management career there have been times when someone has been underperforming on the team.  Before I knew better I let my emotions get the best of me: I’d give them the cold shoulder, avoid including them in conversations and look like I was upset with them. Thankfully with some good mentorship I came up with a simple rule: we are helping each other or you are off the team.

One of the biggest mistakes that folks make a lot of times is letting people linger on for too long.  Hiring good engineers is hard and getting new folks up to speed is hard.  You feel like you are going to miss your product delivery plan if you let someone go.

Letting folks linger when you are unhappy with each other creates a toxic environment.  This toxic environment is generally contagious and brings the entire organization down.  Of course you can’t have a constant state of euphoria on your team, but if a productive and…

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 …