Skip to main content

Are you in Software Design or IT?

Different engineers have different calling, some create mass-market products and some create local solutions.  There is a problem when you use the wrong personality for a wrong project.  More specifically if you apply “solution mindset” to a product problem you end up getting crap.

I love opening up Apple packages.  Over the years I’ve been spoiled by Steve Jobs’s drive to deliver amazing out of box experience and intuitive interfaces.  I open up the box, the device is most likely going to be charged and within minutes will start making my life better and more fun.

I also like putting stuff together.  I learn new computer languages, model airplanes, do-it-yourself electronics kits.  It’s really awesome to pick up a new language, start playing around with tools and let my creative side go nuts.

My suspicion is that I am not alone.  Most of the people have two modes – have fun because things are intuitive and easy, and have fun because things are flexible and powerful.

In my engineering and design I have always tried to be mindful of those two sides.  Things have to be fun because they are intuitive or they have to be fun because they are powerful.   Creating the right products and the right designs is what gives someone a title of “Software Design Engineer” (feel free to add whatever hierarchy prefix you want – director/manager/VP).  Software Design Engineers create mass market products and platforms.

There is also another type of engineer out there.  This type of engineer is more responsive, more accessible and is good at putting together solutions. This engineer is no more or less important than the software design engineer but his tasks are about a deep dive into a particular problem and coming up with a solution.  The solution engineer shines in IT.  You love having those guys that put together products, processes and make the Legos fit together.

The danger lies when you get the “solution guys” into the product business.  What happens is they start solving every customer’s problem with adding small features that address every single edge case.  The solution guys want to make sure that they solve a particular problem and the product starts having a bunch of different personalities.  Those personalities start growing without any rhyme or reason and sooner or later you get a monster with a bunch of heads.  The new customers are intimidated and their experience sucks.

Thankfully with modern software you can address this issue.   In todays applications you can create easy and intuitive user experience and then supplement it with a powerful API.  This is the best of both worlds design.  It gives people what they want without creating a monster.

Your Enterprise customers are probably going to complain – “but why don’t you put a button in your software that solves a problem for my department of 50 sales reps” The answer is to challenge this request and figure out if that same button can be useful to 5,000,000 sales reps.  Don’t let your product lose it’s personality and let the solution engineers take your API and solve the edge cases.
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!

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…

Ego in Your Decision Making

Oxford dictionary defines Ego as: “a person's sense of self-esteem or self-importance”. It says that it is “responsible for reality testing and a sense of personal identity.” For a lot of us techies those were really important functions that probably served us very well early in our career.  We had to be assertive, we had to choose a coding style guide, pick our frameworks and “be decisive”.  However when it comes to engineering management the same things that used to help might be turning into a liability.

When my job changed from writing code to creating an environment where the best code is written - it took me a while to understand how my ego was holding me back.  I kept applying the old tricks - defining the architecture, the final design and task priority.  What ended up happening is those things led me to turn off a lot of the best and brightest people on my early teams.

I remember the feelings of being aggravated when I had to go over an explain my decisions and get buy …