UI/UX design is unusual among tech careers: nobody will ask for your marks, your degree or your certificate. They will open your portfolio, spend ninety seconds on it, and decide. That's intimidating and it's also the opportunity — it means anyone who can produce genuinely good work can enter, regardless of background.
This guide covers what to learn, how to build a portfolio that gets replies, and what the work pays in India. It follows our Figma UI/UX Design course.
UI, UX and product design: what's the difference?
UX is the thinking: research, user flows, information architecture, wireframes — deciding what should exist and in what order. UI is the making: layout, typography, colour, components, states — deciding how it looks and feels. Product design is both plus business context, and it's what most Indian job titles actually mean when they say "UI/UX designer".
Learn both. A designer who can only make things pretty gets art-directed; a designer who can only research gets ignored. The combination is what gets hired.
UI/UX designer salary in India
- Fresher (0–1 year): ₹3 – ₹6 LPA
- 2–4 years: ₹6 – ₹14 LPA
- 5–8 years: ₹15 – ₹28 LPA
- Lead / design manager: ₹28 – ₹50 LPA
Product companies pay substantially more than agencies, and the gap widens with experience. Freelance UI/UX also has a healthy market in India — small businesses and startups need app and website design constantly.
What to learn, in order
- Design fundamentals. Hierarchy, alignment, contrast, spacing, balance. Unglamorous and the single biggest difference between amateur and professional work.
- Typography. Type scale, line height, pairing, readability. Most beginner designs fail here first.
- Colour. Palettes, semantic colour, and accessible contrast ratios — which is a legal requirement in many markets, not a nicety.
- Layout and grids. Columns, spacing systems, responsive behaviour across breakpoints.
- Figma, properly. Auto layout, constraints, components, variants, styles, and variables. Auto layout is the skill that separates fast designers from slow ones.
- UX research. User interviews, personas, journey maps, competitive analysis — enough to justify your decisions.
- Information architecture and user flows. Sitemaps, task flows, and reducing the number of steps.
- Wireframing. Low fidelity first, always. Deciding structure before visuals saves enormous rework.
- Prototyping. Interactive prototypes, smart animate, micro-interactions.
- Design systems. Reusable components, tokens, documentation. Every serious company works this way.
- Usability testing. Watching five real people use your design, and changing it based on what you see.
- Developer handoff. Specs, assets, naming, and enough HTML and CSS understanding to design things that can actually be built.
The portfolio is the whole job application
Three deep case studies beat thirty dribbble shots. A case study is not a screenshot gallery — it's a story with a decision in it. Structure each one like this:
- The problem. Who has it, and how you know it's real.
- Research. What you did and what surprised you.
- Definition. The specific problem you chose to solve, and what you deliberately excluded.
- Exploration. Wireframes, alternatives you rejected, and why.
- The solution. Final screens with your reasoning attached.
- Testing. What you learned from real users and what you changed.
- Outcome and reflection. What worked, and what you'd do differently.
Good subjects: a redesign of a genuinely frustrating Indian government or utility service, an app for a small local business you actually spoke to, and one end-to-end product with a design system. Avoid redesigning Instagram — every reviewer has seen fifty of them.
Will AI replace UI/UX designers?
AI tools now generate screens and variations quickly, which genuinely reduces demand for people whose only skill is producing layouts. What they cannot do is talk to a user, notice the thing nobody said out loud, choose which problem is worth solving, or defend a trade-off to a product manager. Invest in the research and judgement half of the discipline and the tools become leverage rather than competition.
Learning UI/UX with GeekBase
Our Figma UI/UX Design course runs six weeks live in Tamil and English, covering design fundamentals, typography, colour, Figma including auto layout and components, UX research, wireframing, prototyping, design systems, usability testing and developer handoff — built around producing portfolio case studies rather than exercises.
Design pairs unusually well with front-end skills. If you'd like to build what you design, look at HTML & CSS or full stack development next.
Want a personalised recommendation for your city and goal?
Ask on WhatsAppFrequently asked questions
Do I need to be good at drawing to become a UI/UX designer?
No. UI/UX design is about structure, clarity and problem solving rather than illustration. You will sketch rough boxes and arrows on paper, and nothing more artistic than that. Skills that matter far more are empathy for users, attention to spacing and hierarchy, and the ability to explain why you made a decision.
Can a non-technical or non-design graduate get into UI/UX?
Yes, and this is one of the most background-agnostic careers in tech. Engineers, commerce graduates, teachers, marketers and psychology graduates all move into UI/UX successfully — psychology and marketing backgrounds are genuinely useful for the research half. What is assessed at hiring is your portfolio, not your degree.
Is Figma enough, or do I need Adobe XD and Sketch too?
Figma is the industry standard in India and almost everywhere else, and knowing it well is sufficient. Adobe XD is being wound down and Sketch is Mac-only and largely legacy. Learn Figma deeply — especially auto layout, components and variables — rather than spreading yourself across three tools superficially.
How do I get UI/UX work with no experience?
Build three strong case studies, then take small real projects: a local business's website, an NGO's app, or a redesign done in conversation with actual users. Real constraints and real feedback make a portfolio far more convincing than invented briefs, and small paid projects often become references and repeat work.
Should I learn to code as a UI/UX designer?
You do not need to build production applications, but understanding HTML, CSS and responsive behaviour makes you notably better at the job. It stops you designing things that are impractical to build, improves your handoff to developers, and makes conversations with engineering teams much smoother. A few weeks of HTML and CSS is a good investment.