July 17, 2008
Interface design
I’m a webdesigner. I do client work most of the time. We have a wide range of clients, varying from small to bigger ones. Sometimes we work for a small lawyer’s office, sometimes we work for a local university. Sometimes we make a website for a small art exposition, and now we’re busy handling the brand new website of my favorite place to go for concerts.
My work is wildly awesome. Solving problems. Designing. And more importantly, making it real. No website ever came from a mockup without getting your hands dirty in the code, because that’s what puts everything together. Webdesigners need to know how to code, not in the pure programmer sense of way, but that’s not today’s subject.
We don’t have official job titles where I work, and we often joke that you can call yourself whatever you want. From an outsider’s point of view, one would definitely call me a webdesigner, but the thing —the one thing— that really makes me tick is designing applications. Interactions. What happens if you do this and this, and how can I make it easy, perhaps almost intuitive, to use an application.
The job title for that would be interaction designer, or user interface architect, or usability engineer, or anything else along that path. I’m looking for people who do exactly the same as what I do. People who install Wordpress 2.6 to figure out what changes Automattic made to the interface. People that open settings panels just to take a look at how they are organized. Those who know wording, writing, is probably the biggest part in any interface. Passion in play. Call me, and we might make something happen.
Like the site. Job titles suck - role definitions are better and then you can be whatever you need to be to suit the challenge.
November 6th, 2008 at 12:59 ∞