software developers vs web developers vs interactive developers
i’ve interviewed a lot of people for webdev positions in the past few years, mainly from recruiters and open job postings. invariably, the majority of folks who sit before me end up being software developers. what’s the difference?
a software developer…
- tends to think user interface is the least important issue
- is usually surprised by last-minute changes
- is used to working as a member of a large team
- probably has a CS degree and takes it very very seriously
- considers the marketing department to be a waste of good desks
not that there’s anything wrong with that.
then you’ve got typical web developers. regardless of language, they’re writing code that is meant for the web from day one.
a web developer…
- tends to think that user interface is the second-least important issue
- is used to last-minute changes but pushes back whenever possible
- is used to working with relatively small teams
- has learned everything on his own thanks to The Google
- thinks marketing is maybe the third-least important issue
not that there’s anything wrong with any of that, either.
a web developer in advertising — an interactive developer — is a different breed. interactive developers (should, anyway) eat, sleep, and breathe communication. everything we do has an overall objective: increase the client’s brand equity.
the ideal interactive developer…
- understands that creative is the key, and that no user ever got excited by a singleton
- expects last-minute changes
- thrives under the pressure of completely ridiculous deadlines
- is used to working with small teams, but understands each role is vital
- has an actual interest in advertising, communication, and cultural expression
seems that there aren’t many interactive developers around. maybe they already have jobs. the folks i have hired in the past few years are absolutely brilliant programmers, but they are also brilliant communicators. and, at the end of the day, that’s what we get paid to do.
