What the heck is a software designer?

Do you have a job that you have trouble explaining at parties? If so, perhaps you can relate.

 

Understanding what a "Software Designer" is seems to be innate knowledge to a small portion of the population. To the rest of the world, this line of work is a hopeless enigma; even to technology recruiters who repeatedly call me for "Developer" positions.


Designers are not Developers. Not that I don't want to think positively here, but I simply don't know my way around a script the way a developer does. I'm not afraid to get my hands dirty, and can handle code to some extent, but it is not my forte. I attempt to know as much about development as I need to to be a good designer and communicate effectively with developers.

 

To add to the confusion, there is no "correct" way to refer to myself in the field. Very generically speaking, I design software. I design the pages you see on your screen, the navigation of the website or application you may be using. However, the software design field is broken down into people or companies who enjoy categorizing themselves in a variety of ways.

Other names for Software Designers:

UI Designer = User Interface Designers

UE Designer = User Experience Designer

UX Designer = User eXperience Designer

IA = Information Architect

IxD = Interaction Designer

Visual Designer

Web Designer


Articles on these definitions >

Cooper

Boxes and Arrows

Developing a very specific skillset may steer a person into further categorizing themselves. I don't really draw a line, but am all of the above in my work.

 

Some of what I do ›

In the broadest sense, software designers work to make the online tools we use less confusing and simpler to operate for everyone. This can include a variety of tasks, such as creation of

Sketches

Workflows and flowcharts

Storyboards

Wireframes

Interaction specifications or diagrams

Mock-ups

Visual designs

Prototypes

Models for presentation or usability testing

Working code

CSS and style guides

Site standards and patterns

Design specifications

Falling both at the beginning and in the middle of the software development process, Designers must be skilled communicators and be able to speak to both Development and Product teams, Marketing, or the originators of the project. We're in it the whole nine yards, looking out for you, the user, from the project's first blush until final release, when it finally graces your screen.

 

diagram on a coffeehause napkin of the design process

 

Work aside ›

I am not a design robot. I do have a life, quirks and hobbies. Work fascinates me, but I also love sci-fi, horror films, tiling a wall when the mood strikes, a good steak, writing poetry, playing the harmonica, rodents of all shapes and sizes (excepting squirrels), and gardening.