Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

How do you hire a designer? #82

Closed
nathanpalmer opened this Issue Nov 14, 2011 · 1 comment

Comments

Projects
None yet
2 participants

I'm not sure if you are the correct person to answer this question (if not, would love to get in touch with that person.)

What do you look for in a designer?
What are a designer's responsibilities?
Are they responsible for just the "design" or are they actively working in html/css?
Are they also responsible for user interface related javascript?
We've touched on this before, but they are tightly integrated in the dev process correct? Their input to some degree drives the feature development.

Thanks.

Owner

holman commented Nov 14, 2011

What do you look for in a designer?

Lots of qualities- a number of them similar to how we hire for other roles in GitHub, too. One of the more important ones (particular for designers we hire) is to be independent. We put a lot of faith into designers that they can manage their own workload, go out of their way to work on things that need work, and to identify places in the site that needs improvement.

What are a designer's responsibilities?

Make things look good. That's the gist of it. We don't really have firm job titles or anything; if a frontend developer wants to change something on the backend they're more than welcome to (provided they know what they're doing).

Are they responsible for just the "design" or are they actively working in html/css?

We don't hire any pure, abstract designers that can't put their ideas into code. I think eventually we may get to that point, but early on when you're smaller it's just more cost-effective to hire someone that can build out practical designs and then push out the code to do so. You spend less time pushing back on impossible idealized designs and more time implementing real shit.

Are they also responsible for user interface related javascript?

Yup. That's sort of the glue between backend and frontend, but we'll have both sides help out with it.

We've touched on this before, but they are tightly integrated in the dev process correct? Their input to some degree drives the feature development.

Absolutely. Designers are expected to be involved in developer Pull Requests and vice versa. Pull Requests are expected to be double checked-off: to get something shipped, a developer needs to sign off on a designer's backend changes, and a designer needs to sign off on a developer's changes to the frontend. We go through a lot of back-and-forth in Campfire, too; developers can pop into the design room and ask for feedback (and designers can pop into various rooms for developer feedback, too).

@holman holman closed this Nov 14, 2011

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment