Skip to main content

CloudStock Recap

Cloudstock was a very special event. I hope that salesforce.com puts one together next year. DocuSign team did extremely well. We have had several hundred conversations with cool developers and hosted three sessions on Cloud computing and the eSignature API.

Several things that I thought were interesting:
1) It's amazing how many of the cloud developers have their sights on international solutions. I talked to a guy who was doing loan servicing in France. There was a group of consultants that were doing a supply agreement application for a Chinese partner. There were many other people who are taking their US based solutions world wide. This is great!

2) Mobile is entering enterprise computing. I talked to a developer who is doing a medical records system that will need to be rendered on the iPhone and iPad. Fields sales organizations are now getting connected to the cloud. The trend is undeniable.

Overall there is another big shift that is happening - people are creating apps faster and getting feedback from customers faster. I talked to a great cloud billing company and we agreed to do a prototype together. Our estimate is that we can put something together in half a day. That's right - half a day. In half a day people didn't even put requirements together in the past.

The success of CloudStock proves that our decision to go all in to the Cloud in 2003 was the right one!

-mb

PS: Don't forget that we are hosting a developer meetup in Seattle on 12/15. Register here: https://www.developerforce.com/events/seattle_developer_meetup/registration.php?d=70130000000Fkg2
1 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!

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…

Chief Collaboration Officer

When you search for the word “collaboration” on the Internet, the top hits are mostly software packages you can buy.  Software can facilitate collaboration, but it doesn’t make people collaborate on its own.

One of the key functions of a technical leader is to bring a team together, help people share ideas, and facilitate team members helping each other.  When a software leader overlooks this key function, you end up with a group of individual contributing engineers instead of a cohesive team.
Before we get into tactics, we should ask “Why is collaboration important for an engineering team?” 
It’s critical to examine your assumptions, so here are my reasons for why a group of engineers working on their own are worse than a team working together: Smart people learn from each other.Getting your plans and designs reviewed by other people allows you to leverage their experience and check your assumptions.Collaboration produces artifacts that stay after collaboration has taken place (such…