Research and discovery
Interviews, usability testing and analysis of what people currently do. Used to settle disagreements with evidence rather than to decorate a deck.
Product and interface design
Hire UI/UX Designers
Designers who work close enough to engineering that what they hand over can actually be built. Research when the answer is not known, and states, edge cases and specifications when it is.
What our UI/UX Designers do
The reason to hire a UI/UX designer through an engineering team rather than a design studio is what happens at handover. A file full of beautiful screens that nobody costed is where most redesigns quietly die.
Our designers work close enough to engineering that what they hand over can be built as drawn. That means the unglamorous states are drawn too: empty, loading, error, text three times longer than the mock, and the mobile version of every layout rather than the desktop one alone.
They also work in your tools and your sprints. If a design system is the actual need, that is a build with components and documentation rather than a page of colour swatches, and it is worth scoping as one.
What they build
The work this role actually does here, on client products that are live.
Design systems
Components, tokens and the rules for using them, built in Figma to match how the front end is actually structured. One source both sides work from.
Interface design
Screens with their empty, loading, error and overflow states designed rather than discovered during the build.
Accessibility
Contrast, focus order, keyboard paths and screen reader behaviour designed in. Retro-fitting WCAG compliance costs several times more than including it.
What they know
Named rather than implied, so you can check it against your own job description before we talk.
Design
- Figma
- Auto layout and variables
- Design tokens
- Prototyping
- Design systems
Research
- Usability testing
- Interviews
- Journey mapping
- Card sorting
- Analytics review
Standards
- WCAG 2.2
- ARIA patterns
- Responsive and mobile-first
- Inclusive design
Handover
- Figma dev mode
- Storybook
- Specification writing
- Working with engineers directly
Is this the right way to buy?
Hire this way when
- Engineers are making design decisions because nobody else is
- The product has grown and every screen now looks slightly different
- Users are dropping out of a flow and nobody knows at which step
- An accessibility audit is coming and the interface will not pass
Look elsewhere when
- You need a logo and brand identity, which is a different discipline
- You want screens drawn with no access to users or data, since that is guesswork
- The build starts next week, because good design work does not compress that far
- Nobody has authority to decide, which turns every review into another round
How hiring runs
-
Tell us the gap
What the team is building, what is missing, and how long you expect to need it. A rough answer is enough to start.
-
Profiles within a week
You get a shortlist of engineers who are actually free, with the work they have shipped here. Not a database of people we would have to recruit first.
-
You interview them
Technical interview, pair programming, take-home, whatever your normal process is. You decide, not us. Nobody joins your team without your yes.
-
They start inside your process
Your repository, your board, your standups, your review standards. We do not run a parallel process alongside yours.
Agreed before anyone starts
Written into the contract rather than promised on a call. These are the terms people forget to ask about until they need them.
You interview and approve every engineer before they start
One month notice either way, so neither side is trapped
A replacement at our cost if someone is not working out in the first month
Code, accounts and credentials are yours from the first commit
An NDA before any of your systems are discussed, not after
No recruitment fee if you later hire someone permanently
Questions we get asked
Do they work with our engineers?
Directly. A designer working in isolation produces something beautiful and unbuildable. Ours sit in the same standups and answer questions during the build, not only before it.
Will they redesign everything?
Only if that is what you asked for. Usually the higher-value work is fixing the specific flow that is losing people and building the system that stops the drift returning.
Do you do user research?
Yes, and we push for it when a decision is being made on opinion. If there is genuinely no research budget we say which decisions are now guesses, so nobody is surprised later.
What do we actually receive?
A Figma file with components and states, a written specification for anything ambiguous, and the designer available during the build. Not a folder of images.
Tell us what your team is missing.
Send the role, the stack and how long you expect to need it. You get profiles of engineers who are actually free, not a sales call.