Web
Designer
UI design and responsive builds in your stack — from $14/hr + GST.
What a Web Designer does
A web designer turns ideas into interfaces — UI design and responsive builds that look right and work everywhere, in your platform.
Every StaffingSolutions.io web designer is recruited, hired and managed by us — reference-checked for your tools, working your business hours, and backed by our zero-risk promise: no placement fee, money-back first week, and a free replacement if the fit isn't right.
What they handle
- UI design — to your brand.
- Responsive builds — every screen.
- Landing pages — fast and clean.
- CMS work — WordPress, Webflow and more.
- Design systems — consistent.
- Handoff — dev-ready.
A week in the role
Design that ends in a build, not a mood board. The work is Figma files a developer can implement — components with variants, layouts that hold at every breakpoint, the states nobody remembers to draw — plus the ongoing page and campaign assets your marketing team needs between projects.
Lays out desktop, tablet and mobile frames on the agreed column grid using auto layout and constraints, so the developer can see what stretches, what wraps and what stacks, instead of interpolating between two static comps.
Draws the states most briefs skip: empty search results, inline form validation messages, disabled and loading buttons, skeleton placeholders, and the confirmation screen — so the build does not stall while someone invents them in code.
Keeps the Figma library as the single source: buttons with size and state variants, form fields, cards, navigation, and tokens for colour, type scale and spacing — publishing updates with notes so linked files pick up the change.
Tests text and interface colour pairs against WCAG AA contrast ratios, sizes touch targets for thumbs rather than cursors, and specifies the visible focus style on every interactive component so accessibility is not retrofitted after launch.
Annotates the file in Figma Dev Mode: which library component each element maps to, hover and active behaviour, what happens at each breakpoint, image crop rules and link destinations — then answers build questions in file comments as work proceeds.
Art-directs and sources photography, crops to consistent ratios across card and hero placements, exports at the required densities in WebP and SVG, and names files to the convention the developer's asset folder already uses.
Turns the campaign brief into a landing page that matches the ad creative, with form layout, social proof block and a mobile hierarchy built around the offer, then produces the variants being split-tested.
Designs email layouts within the real constraints of Klaviyo, Mailchimp or Campaign Monitor — single-column mobile fallback, web-safe type stack, and a design that still reads when images are blocked by default in Outlook.
Compares the staging build against the design at each breakpoint and logs discrepancies as specific tickets — wrong spacing step, substituted font weight, missing hover state, hero cropped off-centre on mobile — rather than a vague complaint.
Works up low-fidelity structure for new pages and flows first, gets content order and hierarchy agreed with the stakeholder, and heads off the rework that comes from arguing about colour before anyone has agreed what the page says.
Wires frames into a Figma prototype so stakeholders click the actual journey, which surfaces dead ends, missing back-steps and unclear next actions during review instead of halfway through the development sprint.
Applies brand guidelines across new templates, pitch decks and social assets, flags the situations the guidelines have no answer for, and maintains the shared asset library so the team stops rebuilding the same header from scratch.