Hi there,

I'm going to be looking for a good graphic web designer who doesn't have to know coding (I already have a website coder), but needs to know site navigation, layout, colour psychology, colour schemes etc.

What questions should I ask them in order to figure out if they know what they are doing?

Thanks


Michelle

Dani AI

Generated

A short, practical add-on to the thread for : 's emphasis on visible work is spot-on, and 's quick-test idea shows the value of seeing thinking in action. The aim below is to go beyond "do they look good?" and give a compact checklist of concrete vetting topics, a lightweight exercise that mirrors real handoff, and a few red flags to avoid.

Useful vetting topics (look for evidence or brief answers, not rehearsed lines):

  • Case studies and role: brief project write-ups that list the problem, constraints, the designer's role, chosen solution and outcome (metrics or client feedback).
  • Design rationale: ability to explain why typography, layout and color were chosen and how those choices support user goals.
  • Deliverables & handoff: what exact files and specs will be provided (layered source or editable file, exported assets, color values, font names, CSS snippets or component specs, and annotated responsive breakpoints).
  • Accessibility & performance awareness: basic checks for contrast, keyboard/focus states, image optimization and how designs adapt on slow connections.
  • System thinking: presence of a style guide or component list that ensures consistency as the site grows.
  • Validation: examples of usability testing, A/Bs, or analytics-driven changes.
  • Legal/ownership: fonts, stock images and final copyright/usage terms.

A practical exercise (paid, short): a one-screen micro-brief that requests an annotated mockup (desktop + one breakpoint), a short justification paragraph, and an asset bundle. This shows process, deliverables and estimate accuracy without a big time sink.

Red flags: vague answers about deliverables, refusal to supply source or specs, no mention of accessibility/responsive behavior, reliance on generic templates with no explanation, or inability to name licensing for assets. A clear brief and a short contract that lists deliverables, ownership and rounds of revision avoids most surprises.

Recommended Answers

All 3 Replies

Obviously you can look at their own sites/portfolio to see if they have a good eye for colour, but you could ask:
- how they would improve the site structure
- how that would make it easier for people to find things
and umm I've run out of ideas!

edit: also could ask what software they use - do they use the professional stuff like Photoshop and Dreamweaver, or something else - however that won't tell you much about their abilities. You can only tell that by looking at their past work or samples.

I think what software they use is important and it is very important that they know how to make your site easier to use.

Just and idea:

Show them your site, leave them for five minutes and tell them to look at it and decide five things they would change to make it look better and easier for the user. I think this will give you a good idea of how good they are and what they are capable of doing because they are unlinkely to say somehting they can't do!

But as I said that's just an idea, maybe it is a bit harsh on the Web Designer but they want to work for you!

I think what software they use is important

At the end of the day their ability with that software is far more important than the software itself. The decision has to rely on the visible skills and natural talent they have with the tools. After all, it doesn't matter if your door locks were fitted with a chisel or a router, but the skills of the person using it will affect how well it works for you.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.