A prompt in a design tool can now produce a tidy dashboard layout in under a minute, complete with sensible spacing and placeholder charts. That has taken much of the value out of polished screens as evidence of skill, since anyone can make one. What a generated layout cannot do is find out why people abandon a flow, decide what to leave out or write an error message that helps someone fix the problem. At the same time, design and code have moved closer through tokens, Dev Mode and shared component libraries. UI/UX designer skills have shifted towards research, judgement and systems, and they are harder to see in a portfolio than they used to be.
Use this post to see which eight core skills to look for and how to check each, which working habits count, what has become more and less important, how skills grow by level and how to assess a designer with more than a look through their case studies.
Core skills for a UI/UX designer
Information architecture and flows
Before any screen exists, someone must decide how a product is organised and what labels users will recognise. Good designers think in structures and journeys, and they test those structures with methods such as card sorting and tree testing. How to check it: show a muddled settings menu with overlapping labels and ask how they would reorganise it. Then ask how they would know the new structure works before building it. A strong answer involves real users finding items in a plain text tree, with no visual design involved.
Moderating a usability test
Running a session looks easy, yet one leading question can spoil it. Good moderators give a task and stay quiet, ask what the user expected, and never explain the interface. How to check it: share a short transcript in which the moderator asks “Did you find that button easy to use?” and steps in to help. Ask the candidate to mark what went wrong and rewrite the prompts. People who have moderated will spot the problem at once and offer task-based wording.
Making sense of evidence
Designers must weigh small numbers of observations alongside analytics, and know what each can and cannot show. A handful of sessions can reveal why something fails, though it cannot tell you how often that happens. How to check it: say a few test users struggled at a step, while analytics show few people leaving there. Ask what they would conclude and do next. Good candidates ask whether the test users match real customers, and look for other explanations before redesigning anything.
Interface writing
Words carry much of an interface, and in smaller teams nobody else will write them. Strong designers write labels and error messages that tell people what happened and what to do. For Indian products they also allow for longer strings and for users reading in a second language. How to check it: show a KYC screen that says “Invalid input” and “Error 403”, and ask for better versions. Then ask what would change if the same screen appeared in Hindi or Tamil. Look for plain wording and layouts that can stretch.
Visual hierarchy
Strong UI work comes from control of space, type and contrast. Colour and decoration come later. A designer with this skill can make a dense screen readable with few tools, and can apply Material Design and Apple’s Human Interface Guidelines without copying either blindly. How to check it: give a crowded data table screen and ask them to improve it using only spacing, type size and weight, with no new colours.
Design systems and tokens
Mature teams work from shared components, and Figma variables have made tokens an everyday tool. Good designers understand the difference between a raw value and a semantic token such as “surface error”, and they know how those map to code. How to check it: open a small component set and ask how they would add dark mode, or a second brand, without redrawing each screen. Strong answers restructure tokens, and mention working with frontend engineers and checking the components in Storybook.
Designing accessibility in
WCAG 2.2 gives a sound baseline. Designers decide much of what later succeeds or fails: focus order, target size, heading structure and whether colour is the only signal. How to check it: show a status table that marks passed and failed items only in green and red, with small icon buttons alongside. Ask what they would change, and how they would record reading order and focus behaviour for developers. Designers who think about this annotate their files, leaving nothing to be guessed at during the build.
Metrics and experiments
Designers increasingly share responsibility for outcomes, and that takes some comfort with funnels, A/B tests and their limits. Knowing what to measure, including what might get worse, is the core of it. How to check it: say a redesign lifted sign-ups while support tickets from new users also rose, and ask whether it succeeded. Good candidates look at retention and the content of those tickets, instead of celebrating the first number or defending the design.
Working skills that separate good from average
- Giving and taking critique. Strong designers invite criticism early and respond to the problem raised, without defending the pixels. They also give useful feedback to others, based on goals and not on taste.
- Trading off with product managers. When a release date tightens, good designers propose what can be simplified without harming the user, so scope cuts are not left to chance.
- Staying with the build. They review staging builds, answer developers’ questions quickly and accept sensible changes. The design is finished when the product ships, which is later than the Figma file suggests.
- Working with thin research. Few teams get ideal access to users. Resourceful designers use support calls, sales notes and a few quick sessions, and they say how confident they are in what they found.
Skills rising and falling in value in 2026
Mattering more. Editing is now a major part of the craft. When AI tools produce many options quickly, the value lies in picking the right one, recognising generic results and fixing what they miss. Designing AI features has become a skill of its own, covering how to show uncertainty, let people correct a wrong answer and keep users in control. Fluency with tokens, Dev Mode and code-connected components matters more as the distance between design files and production shrinks. Accessibility has also gained commercial weight, with the European Accessibility Act now applying to many digital services sold into the EU.
Mattering less. Drawing every screen at high fidelity is less necessary where a design system covers most patterns. Writing long redline specifications has largely gone, since developers can inspect files directly. Adobe XD is no longer under active development, so experience in it matters mainly as history. Persona decks that nobody reopens are losing ground to direct evidence from users.
UI/UX designer skills matrix by level
| Skill area | Junior | Mid-level | Senior |
|---|---|---|---|
| Flows and structure | Maps a defined flow | Structures a whole journey | Shapes navigation across products |
| Research | Assists and takes notes | Plans and moderates own tests | Sets research priorities with product |
| Interface writing | Writes clear labels with review | Handles errors and edge states | Sets voice and terminology |
| Visual craft | Applies type, spacing and grid well | Creates hierarchy on complex screens | Sets the visual direction |
| Design systems | Uses components correctly | Extends components with tokens | Governs the system with engineering |
| Accessibility | Checks contrast and target size | Annotates focus and reading order | Builds it into team standards |
| Metrics | Understands the funnel for a feature | Defines success measures and reads tests | Links design work to business outcomes |
| Collaboration | Takes feedback well | Negotiates scope with product and engineers | Influences what gets built next |
How to assess UI/UX skills in a hiring process
Since generated screens have made portfolios easier to polish, build the process around conversation and live reasoning. The UI/UX designer job description should already say which side leans heavier, and these steps can be weighted to match.
- Critique a third-party app. Pick an app the candidate does not work on, such as a bank or food delivery app, and ask for a live critique of one journey.
- Put a developer on the panel. Ask an engineer to take one case study and question how it was built. The conversation shows how the designer explains decisions and whether they know what happened in the build.
- Pair on a constraint. Spend a short session adapting an existing screen for a narrow phone or a new user type, sharing the screen in Figma.
- Test ownership of the work. Ask which decisions in a case study were theirs and which belonged to others. Then ask if AI tools were used and how.
Red flags on a CV or portfolio: concept redesigns of famous apps with no real users; identical process diagrams in each case study; conversion gains with no baseline or method; personas with stock photos and no source; and no mention of a developer, a product manager or any constraint.
Frequently asked questions
Do UI/UX designers need a design degree?
No. Many strong designers come from psychology, engineering, journalism or graphic design. Formal training can help with visual foundations, but judge the work and the reasoning behind it, whatever route someone took to get there.
How should we assess designers whose work is under NDA?
Ask for a walkthrough with sensitive details hidden, or a live conversation in place of a shared file. They can usually describe the problem, process and result in general terms. Respect the NDA, and be wary of anyone willing to show confidential screens freely.
Should designers use AI tools in their work?
Yes, for exploring options, drafting copy and summarising research notes, as long as the designer checks the result. Ask how they use these tools and where they stop. Treating raw output as finished work is the concern, and summaries of research still need checking against the source.
How do we hire a first designer when nobody on the team can judge design?
Borrow a reviewer. A design lead from your network or a trusted external adviser can assess portfolios. Otherwise, focus on how candidates explain problems and on what the developers and product managers who will work with them think after meeting them.
When the search is ready to start, Zilo AI can help you hire UI/UX designers in India on contract, contract-to-hire or permanent terms, including product designers and UX researchers, with portfolios reviewed for problem framing, research, iteration and developer handoff. Developers to work alongside them can be found through our IT talent page. Tell us about your product and which side of the slash it needs most.