Web design split into two disciplines over the past decade: people who design for screens and people who build websites. If you need someone to create the visual design and user experience before anything gets built, you're hiring a web designer, not a developer. And in 2026, that means hiring someone who works in Figma or Adobe XD.
Figma has won the market. Adobe XD is still used but declining — Adobe stopped developing new features for it in 2024. Understanding what these tools do and how to evaluate designers who use them is the difference between hiring someone who can design a website and hiring someone who can design a website your developer can actually implement.
Why the Tool Matters
Both Figma and Adobe XD are interface design platforms. They let designers create pixel-perfect mockups, interactive prototypes, and component-based design systems that developers can build from. They replaced older tools like Photoshop and Sketch for web and app work.
Figma is the current standard. Browser-based, collaborative, with better developer handoff features than any alternative. Most modern design teams work in Figma. Developers can inspect designs, extract CSS, and grab assets without asking for files.
Adobe XD was Adobe's answer to Figma. It's still used by designers invested in the Adobe ecosystem. But Figma won the market share battle decisively.
When hiring, look for proficiency in Figma. If they only know Adobe XD, they're either behind on industry trends or working in a very specific context where XD is required.
Reading a Portfolio
Look for web and app work specifically. A designer with a strong print or branding portfolio is not automatically a strong web designer. Web design involves different constraints — responsive layouts, interactive states, accessibility, how designs translate to code.
Check whether designs were built. Portfolio pieces showing only static mockups might never have been implemented. Designs that link to live websites prove the designer understands how their work becomes reality. Ask for live links.
Evaluate component thinking. Modern web design uses component systems. A designer showing you 50 unique screens probably designed inefficiently. A designer showing a small set of reusable components used across many screens understands how developers work.
Look at responsive design. Web designs need to work on desktop, tablet, and mobile. A portfolio showing only desktop mockups is incomplete.
Check for design system work. Strong web designers think in systems — color palettes, typography scales, spacing systems, component libraries. If their portfolio includes documentation or style guides, that's meaningful.
Notice prototypes. Figma and Adobe XD let designers create interactive prototypes. A designer who shows clickable prototypes with transitions and interactive states is thinking beyond static visuals.
Pay attention to constraints. The best portfolios include case studies explaining the problem, the constraints (budget, timeline, technical limits), and how the design addressed them. "I designed a beautiful interface" is less useful than "I redesigned checkout to reduce cart abandonment by 30% within these constraints."
Finding Them on Upwork
Search "Figma web designer," "UI/UX designer Figma," "Web design Figma," or "Product designer Figma" — not just "web designer."
Filter by Job Success Score (90%+), listed skills (Figma or Adobe XD), and whether they've uploaded portfolio samples.
Read profiles for specifics. "I design modern websites in Figma with focus on user experience" is more useful than "experienced web designer with Adobe Creative Suite."
Look for designers who mention design systems, responsive web design, prototyping, interaction design, and developer handoff.
What It Costs in 2026
Hourly Rates
| Experience Level | Hourly Rate (USD) |
|---|---|
| Entry-level (0–2 years) | $25–$50 |
| Mid-level (2–5 years) | $50–$100 |
| Senior (5–10 years) | $90–$160 |
| Expert / Specialized | $150–$250+ |
Project Pricing
Most web design is priced per project:
Landing Page (single page)
- Entry-level: $300–$800
- Mid-level: $700–$2,000
- Senior: $1,800–$5,000
Marketing Website (5–8 pages)
- Entry-level: $1,000–$3,000
- Mid-level: $2,500–$8,000
- Senior: $7,000–$15,000+
Web App UI (10–20 screens)
- Mid-level: $3,000–$10,000
- Senior: $8,000–$25,000+
Mobile App Design
- Mid-level: $2,500–$8,000
- Senior: $7,000–$20,000+
Design System / Component Library
- Mid-level: $2,000–$6,000
- Senior: $5,000–$15,000+
UI Redesign (existing product)
- Mid-level: $2,000–$8,000
- Senior: $6,000–$20,000+
Writing the Job Post
Include type of project (marketing site, web app, mobile app, redesign), number of pages or screens, whether you have wireframes, whether you have brand identity, target audience and goals, reference sites you like (be specific), file deliverables needed, timeline, and whether you need interactive prototypes.
Filter question: Ask applicants to link to one similar project and briefly explain their design process for it. Template proposals disappear.
Screening Questions
"Walk me through your process from brief to handoff." Look for discovery and research, wireframing, visual design iterations, prototyping, and developer handoff. A designer who jumps straight to high-fidelity mockups is skipping steps.
"Show me a component library you've built." Modern web design is component-based. A designer who hasn't built reusable systems creates more work for developers.
"How do you approach responsive design?" The answer should include designing for multiple breakpoints, mobile-first vs desktop-first considerations, and how designs adapt across screens. "I design for desktop and let developers handle mobile" is concerning.
"What's your handoff process?" Good answers: organized Figma files with named layers and components, annotations for interactions and edge cases, assets exported in correct formats, availability for developer questions. "I send them the Figma link" is incomplete.
"Tell me about a design that didn't work. What did you learn?" This shows whether they iterate based on feedback and metrics, or design in isolation.
"Do you conduct user research or testing?" For complex projects, research matters. A designer who's never done this is designing on assumptions about user behavior.
Red Flags
Portfolio with no web work. If it's logos, brochures, and social media graphics, they're a graphic designer, not a web designer.
Only showing final polish, never process. Might be good at making things look nice but weak at problem-solving.
Designs that look identical across projects. A rigid style means you'll get a variation of what they always do regardless of brief.
No mention of developer collaboration. If they've never worked with a dev team, their designs may be difficult or impossible to build.
Can't explain design decisions. If they can't tell you why they chose a specific layout or interaction pattern, they're designing on intuition alone.
Unrealistic timelines. "I can design your 10-page website in 3 days" is either false or means templates with minimal customization.
Figma vs. Adobe XD
In 2026, Figma is the clear choice. Browser-based, real-time collaboration, better developer handoff, larger community and plugin ecosystem, more companies using it.
Adobe XD integrates with other Adobe tools if your team already uses Creative Cloud. That's the main advantage left.
If starting fresh, request Figma. If you already have work in Adobe XD, you can continue but finding proficient designers will get harder over time.
Fixed-Price vs. Hourly
Web design almost always works better as fixed-price with defined deliverables. Predictable cost, clear scope, no incentive to work slowly, easy to budget.
A good contract lists deliverables (wireframes, mockups, prototype, design system), number of design concepts (typically 2-3), revision rounds (typically 2-3), file formats, timeline with milestones, and what's excluded.
Hourly makes sense for ongoing work where scope changes frequently or long-term product relationships.
The Test Project
For significant projects, consider a paid test before committing. Ask the designer to create 1-2 key screens based on your brief. Pay $200-$500 depending on complexity. Evaluate their process: questions asked, interpretation of brief, revisions needed.
You're testing communication, process, and how they handle feedback — not just visual output.
Working With Your Designer
Provide clear references. Don't say "modern and clean." Show them websites you like and explain specifically what appeals to you about each.
Share brand assets early. Logos, colors, fonts, existing guidelines — get these to the designer at the start.
Be specific about functionality. If a feature needs to work a certain way, explain it.
Give structured feedback. "I don't like it" is not useful. "The hierarchy feels off — the secondary CTA is competing with the primary one" is actionable.
Expect iterations. The first concept is rarely final. Budget for 2-3 revision rounds.
Involve developers early. If your developer sees designs only at the end, you might discover they're impractical to build.
Developer Handoff
Your designer should deliver more than mockups. Proper handoff includes organized Figma files with clear naming, design system documentation (colors, typography, spacing, components), annotations for interactions and responsive behavior, edge cases documented (loading states, errors, empty states), asset exports in correct formats, and availability for developer questions.
Mistakes to Avoid
Confusing designers with developers. Designers create mockups. Developers turn them into working websites. These are different jobs.
Not defining responsive requirements upfront. Specify if you need mobile designs or you might only get desktop mockups.
Skipping wireframes. Jumping to high-fidelity design is faster but often creates structural problems expensive to fix later.
Unlimited revisions. Every contract should specify revision rounds. Otherwise the engagement never closes.
Judging only on aesthetics. A beautiful design that's difficult to use or impossible to build is worse than a plain design that works.
