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.

Comments

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!

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 acce

Intuitive Programming - Comments

Comments are a topic of vibrant discussion.  Ever since programmers could leave some text in the program that was ignored by the machine the debate started: “what’s a good comment, what’s a bad comment, why comment?” There are endless instructions to programmers that say many of the following things: 1) Describe your function! 2) Don’t write in the comment what you wrote in the code. 3) Tell people why you are doing what you are doing. What I think has been missing from this discourse is the audience for comments and through those audiences there is intent.  The code is being read, skimmed or analyzed by people and tools.  So what are the audiences and reading modes? 1) Maintaining and enhancing the code 2) Skimming through the entire module or file to figure out what the overall structure is 3) Reviewing the test files to check out the test coverage and edge cases 4) Seeing the docstrings of functions while being in a separate file altogether 5) Reviewi