How to Hire a Web Designer

A web designer should help turn business requirements and real content into a clear, usable interface. Hiring decisions should therefore be based on relevant problem-solving, process and handover — not only on whether a portfolio matches your preferred visual style.

Clarify whether you need design only or a supplier who also provides strategy, copywriting, development, migration and ongoing support. “Web designer” is used broadly, and assumptions create expensive gaps.

Define the role before looking for candidates

Possible responsibilities in a website project

Responsibility	Questions to settle
Information architecture	Who plans pages, hierarchy and navigation?
Content	Who writes, edits and approves real copy?
User interface design	Who creates layouts, components and mobile states?
Development	Who builds templates and functionality?
Content entry	Who puts approved content into the site?
Testing	Who checks accessibility, browsers, forms and journeys?
Launch and support	Who handles migration, handover, updates and faults?

Prepare a brief and budget range

Provide the same brief to each shortlisted candidate. Include the website objective, audience, page and function requirements, content position, existing platform, desired launch window, ownership requirements and budget range.

A designer cannot quote reliably from “we need a modern website”.

Review relevant work properly

Ask candidates to explain two or three relevant projects:

• What problem was the client trying to solve?
• What did the designer personally deliver?
• Which constraints shaped the work?
• How were content and mobile layouts handled?
• What changed after testing?
• Is the live result still representative?

Open the live sites on mobile and desktop where possible. A screenshot does not demonstrate navigation, forms, readability or accessibility.

Assess the working process

A controlled process may include:

1. requirements and content review;
2. page structure or wireframes;
3. design direction using representative content;
4. component and template design;
5. mobile and interaction states;
6. review and revision;
7. handover to development or implementation;
8. design quality assurance on the working site.

Ask what the business must supply and approve at each stage.

Discuss content before visual design

Good design depends on real headings, paragraphs, tables, forms, photographs and calls to action. Confirm whether the designer:

• expects approved copy before layouts;
• can work with a copywriter;
• will identify content gaps;
• designs for long and short real examples;
• includes tables, warnings, errors and empty states;
• will avoid using invented testimonials or placeholder claims.

Ask about accessibility and responsive design

Useful questions include:

• How are heading hierarchy and readable text considered?
• How are keyboard focus and interactive states shown?
• How are colour contrast and non-colour cues checked?
• How will forms, errors and validation be designed?
• Which mobile widths and content extremes will be tested?
• How will tables, menus and long titles behave?

“Responsive” should mean more than shrinking the desktop layout.

Clarify deliverables

The agreement should state whether you receive:

• wireframes;
• desktop and mobile designs;
• a component or design system;
• interaction states;
• source files;
• image and font licences;
• developer notes;
• design review after implementation;
• the number and scope of revisions.

Confirm which software is used and whether the business needs a paid account to access editable files.

Check commercial and ownership terms

Review:

• payment stages;
• what triggers approval;
• how additional work is priced;
• what happens if the project pauses;
• ownership and licence terms;
• confidentiality and portfolio use;
• handover if the relationship ends;
• availability for future changes.

Watch for warning signs

• no questions about audience, content or business purpose;
• a promise to start with the home-page visual immediately;
• design based mainly on placeholder text;
• no discussion of mobile, forms or accessibility;
• unclear deliverables and revision limits;
• pressure to copy a competitor;
• claims of guaranteed rankings or sales;
• no written ownership or handover terms.

Use a paid discovery stage when the scope is uncertain

For a complex project, a short paid planning stage can define the sitemap, content requirements, representative wireframes and implementation scope before the full price is agreed. The output should be documented and useful even if a different supplier completes the build.

Make the final decision

Choose the designer who demonstrates relevant judgement, communicates limitations clearly and has a process that fits the business's ability to provide content and decisions. A visually impressive portfolio is valuable, but reliability, clarity and ownership determine whether the project can be completed safely.