Watches people use the current thing
Six sessions is usually enough to find the real problem, and it is usually not the one in the brief.
A designer who watches people use the thing before redrawing it. Research, flows, interface design and a component library the engineers can actually build from, rather than a beautiful file that has to be reinterpreted.
Shortlist within 24 hours · You interview every candidate · Flat monthly rate
Most redesign briefs describe a symptom. Watching six people attempt the task usually reveals a different problem than the one you were asked to solve.
Six sessions is usually enough to find the real problem, and it is usually not the one in the brief.
Empty, loading, error, too much data, name too long. These are most of the real screens and they are what gets skipped.
So the twentieth screen costs an hour rather than a day, and so two engineers building different pages produce the same interface.
Button labels, error messages and empty states are design. Leaving them to engineers produces "An error occurred".
Not at the end as an audit. While designing, because retrofitting accessibility costs several times more.
Nobody on the bench knows all of this. We shortlist against what your problem actually needs, and tell you where the gaps are.
You make the decision at every step. We do the searching, the vetting and the paperwork.
Thirty minutes on the constraint you are working against and what finished looks like. No job specification needed.
Engineers already vetted for this role, with where each one is strong and where each one is weaker.
Your questions, your decision. The interview signals further down this page are yours to use.
In your repository and your tools, on a flat monthly rate. If the fit is wrong, we replace them and do not bill the second ramp-up.
No algorithm puzzles. Every exercise below is a task this role does in a normal week, and we watch the method more than the answer.
A live product with genuine problems. We want specific, prioritised observations, not "it feels dated".
Given a happy-path screen, produce the empty, loading, error and overflow variants. This is the fastest signal of production experience.
Three components with real variants and tokens in Figma. We check whether an engineer could build from it without asking questions.
We push back on a choice. We want reasoning, not deference and not defensiveness.
You interview every candidate we put forward, so these are yours to use. They separate somebody who has run this in production from somebody who interviews well.
Names a measured behaviour: task completion, time to first action, support tickets about a specific screen. Compares before and after.
Says stakeholders liked it, or that it is cleaner. Neither is evidence, and both are compatible with the product having got worse.
Has several, and talks about what the message tells the user to do next. Treats the copy as part of the design.
Only has happy paths in the portfolio. That is a portfolio of demos, and the missing screens are most of the real work.
Components with variants and named tokens, plus a conversation about what is feasible before the design is finished rather than after.
Exports images and annotates them. The engineers then make a hundred small decisions the designer did not, and the result does not match.
Contrast checked as part of choosing colours, keyboard order designed rather than inherited, and focus states drawn explicitly.
Treats it as a compliance pass at the end. That is when it is most expensive and least likely to actually happen.
Courses, products, coaching and memberships sold from one login, with an AI offer writer.
Read the case study → EducationGenerates practice material and scores writing and speaking against real examiner marks.
Read the case study → HealthcareClinical notes written live during a consultation, with no patient data kept on its servers. Running in Norway.
Read the case study →“Each developer I had worked with from Zeki Experts was talented, efficient, communicative, and self-starting.
“Zeki Experts’ team was exceptional: talented, efficient, communicative, and self-starting.
Some do, to component level, and it makes handover noticeably smoother. It is not the default, and a designer who codes a little is more useful than one who codes badly.
Yes, and it is usually the better brief. Extending a system you already have costs a fraction of replacing it and keeps everything built so far consistent.
For most product decisions, five or six sessions with real users. Past that the findings repeat. Large research programmes are occasionally justified and usually a way of postponing a decision.
Thirty minutes, and a shortlist within a day. If a ui/ux designer is the wrong hire for what you described, you will hear that instead.
Either one reaches the Zeki team directly. No forms sitting in a queue.