India version. Written for design hiring in India: GIGW 3.0 accessibility (WCAG 2.1 AA) for government work, lakh and crore number formats, and mobile payment flows in design tasks. US version

UI/UX Designer Interview Prep (India)

Prepare for UI/UX design interviews in India: portfolio reviews, design tasks, GIGW 3.0 and WCAG 2.1 AA, rupee and lakh formatting and mobile-first payment flows.

The interactive tool loads here when JavaScript runs.

About this tool

What is UI/UX Designer Interview Prep?

Design interviews in India usually have a portfolio round, a design task (often a take-home with a day or two to submit, sometimes a live exercise) and a discussion with a product or design lead. Freshers from design schools and bootcamps face the same structure, with more weight on the task because their portfolio is thinner. The task brief is often a flow Indian users know well: paying a bill, booking a train or bus ticket, ordering groceries or checking an exam result.

Two local topics come up again and again. The first is the Guidelines for Indian Government Websites and apps (GIGW 3.0), which any agency or consultancy building for a ministry, PSU or state department works to. The GIGW portal says the current version conforms to WCAG 2.1 Level AA, adds 17 success criteria over GIGW 2.0, and includes a cybersecurity chapter written with CERT-In. The second is formatting for Indian readers: rupee amounts with the ₹ sign and Indian digit grouping, dates as day, month, year, and screens that hold up in Hindi or a regional language as well as English.

Use the tabs as normal: rehearse the frameworks, tick the skills your portfolio proves, run a timed challenge and test each case study against the review questions. This version adds the checks an Indian panel is likely to probe.

  • Four design process frameworks
  • 32 core design skills with progress tracking
  • Four design challenges with a 40 to 60 minute phased plan
  • Portfolio case study structure and 24 review questions
  • Inputs and progress saved in your browser
Read the guide: Engineering Manager, ML Engineer and Designer Interviews Explained

Updated

How to use UI/UX Designer Interview Prep

  1. Open each framework on the Design Frameworks tab with View Process.
  2. Tick the skills on the Core Skills tab that you can show in your portfolio; the header percentage tracks coverage.
  3. On Design Challenges, choose a prompt in Select Design Challenge and enter extra constraints in Additional Requirements, such as "first-time users, one-handed use".
  4. Click Generate Design Approach, set a timer for the total shown, and work through each phase on paper or in your design tool.
  5. Rehearse your case studies against the questions on the Portfolio Questions tab.

Worked examples

Orange "Pay now" button with white text

Input

Button #F57C00 with white label; alternatives #E65100 and #BF360C

Output

#F57C00: 2.70:1 (fails); #E65100: 3.79:1 (passes only for large text); #BF360C: 5.60:1 (passes AA)

WCAG 2.1 AA, the GIGW level, needs 4.5:1 for normal text and 3:1 for large text (18 pt, or 14 pt bold). A bright orange brand colour often fails with white text, so keep the brand colour for the shape and use a darker shade, or dark text, for the label.

Amounts in a payments history screen

Input

A design task shows a monthly spend of 1234567.5 rupees

Output

Indian format: ₹12,34,567.50 (about ₹12.3 lakh); US-style format: ₹1,234,567.50

Panels notice the grouping. Show the full amount in the transaction detail and a short form ("₹12.3 lakh") only where space is tight, never "1.2M".

A 45-minute task with local constraints

Input

Select Design Challenge: Mobile App Design. Additional Requirements: "book a seat at a coaching centre; low-end Android phone, patchy 4G, Hindi and English"

Output

The five timed phases from the tool, with the requirements carried into the plan

Use the clarifying phase to ask about payment (UPI or card), language switching and offline states. Then design the core flow with its loading, failed-payment and pending-payment states, which is where real Indian payment flows get complicated.

Background and insight

GIGW 3.0 is based on ISO 23026, WCAG 2.1, the Rights of Persons with Disabilities Act, 2016 and the Information Technology Act, 2000, according to its own scope page. Note the version: WCAG 2.1, not 2.2. Under 2.1 the only target size criterion (2.5.5) is level AAA at 44 by 44 CSS pixels, so it is not required for AA; WCAG 2.2 added a level AA minimum of 24 by 24. If you design to 2.2 AA you meet the 2.1 AA bar as well, which is a good line to use in an interview.

Number formats are a quick way to show attention to detail. Indian English groups digits as 12,34,567 (three, then twos), and large amounts read as lakh and crore: ₹12,34,567 is about ₹12.3 lakh. A dashboard mock-up that shows "₹1,234,567" or "1.2M" to an Indian user reads as a foreign template. Browsers format this correctly with Intl.NumberFormat("en-IN"), so the fix is cheap.

Common use cases

  • Rehearsing whiteboard challenges

    Run each of the four prompts against the timed plan until you consistently reach a finished core flow.

  • Preparing a portfolio presentation

    Restructure each case study into context, process, decisions and results, and test it against the 24 questions.

  • Spotting skill gaps

    Unticked skills in the Core Skills list show which areas your portfolio does not yet demonstrate.

  • Running design interviews

    Use the challenges and portfolio questions as a consistent set for every candidate.

Tips and limitations

  • For a take-home task, state your assumptions on the first slide and keep to the time the company suggests; panels compare candidates on similar effort.
  • Show a failed or pending payment state in any checkout task. A payment that is debited but not confirmed is a common real case and a good talking point.
  • Test every screen with real Hindi or regional-language strings, not lorem ipsum, and check that buttons and tabs still fit.
  • If the role involves government work, read the GIGW 3.0 accessibility guidelines before the interview and mention the WCAG 2.1 AA baseline.
  • Put your portfolio link at the top of your CV and keep each case study readable on a phone, because many reviewers open links on mobile first.

Sources and further reading

  1. New features of GIGW 3.0, Guidelines for Indian Government Websites and apps (Government of India). Conformity with WCAG 2.1 Level AA, 17 new success criteria and the CERT-In cybersecurity chapter.
  2. Scope and objective of GIGW 3.0, Guidelines for Indian Government Websites and apps (Government of India). Basis in ISO 23026, WCAG 2.1, the RPwD Act 2016 and the IT Act 2000.
  3. Web Content Accessibility Guidelines (WCAG) 2.1, W3C. Contrast (1.4.3) and target size (2.5.5, AAA) criteria.
  4. Web Content Accessibility Guidelines (WCAG) 2.2, W3C. Target size (minimum) at level AA.
  5. Unicode CLDR Project, Unicode Consortium. The en-IN number format used by browsers.

Frequently asked questions

Which accessibility standard do Indian government websites and apps follow?

The Guidelines for Indian Government Websites and apps, version 3.0 (GIGW 3.0). Its portal says the current version ensures conformity with Level AA of WCAG 2.1 and added 17 new success criteria over GIGW 2.0, which followed WCAG 2.0. It also has a cybersecurity chapter written with CERT-In.

Is GIGW based on WCAG 2.1 or 2.2?

WCAG 2.1. WCAG 2.2 became a W3C Recommendation in October 2023 and added criteria such as a 24 by 24 pixel minimum target size and focus not being hidden. Designing to 2.2 AA also meets 2.1 AA, so mention both if the panel works for government and private clients.

What kind of design task do Indian companies give UI/UX candidates?

Usually a take-home brief or a live exercise around a familiar flow, such as bill payment, ticket booking, food or grocery ordering, or onboarding for a learning app. Ask how long you have, what format they want (Figma file, slides or both) and whether you will present it. Then use the challenge planner here to time-box your work.

How should rupee amounts appear in a UI design for India?

With the ₹ sign before the number and Indian digit grouping: ₹12,34,567.50. Large figures are read as lakh and crore, so a short form such as "₹12.3 lakh" fits Indian readers better than "1.2M". Intl.NumberFormat with the en-IN locale produces the grouping.

How do I show accessibility in a portfolio if my projects never tested it?

Run a quick audit on one shipped screen: contrast for text and controls, focus order, labels on form fields and text size. Show what failed, what you would change and how it affects the layout. A short, honest audit is more convincing than a claim that everything was accessible.

How many case studies should a design portfolio presentation include?

Two or three in depth for a 45 to 60 minute slot. Freshers can include one academic or self-initiated project if it shows research with real users and iteration after testing.

Is there an in-depth guide to UI/UX Designer Interview Prep?

Yes. “Engineering Manager, ML Engineer and Designer Interviews Explained” covers the background, how it works, common pitfalls and worked examples. Read the full guide.