How I Became A Self Taught UI/UX Designer

Oct 27, 2021

How I Became A Self Taught UI/UX Designer

My journey to becoming a self-taught designer has been one filled with learning new interesting things. Here are some tips and tricks that you can adopt if you're doing the same!

Author

Rati Agarwal
Rati AgarwalUI & UX Designer

Hello 👋

I am Rati, and I joined GeekyAnts as a Junior UI/UX Designer. I am happy to be here surrounded by talented, like-minded people. I enjoy creating simple and intuitive interfaces for landing pages, online stores, mobile apps, and meeting new people. Did I mention my love for ice cream? 😛

I have tried to document my journey of becoming a UI/UX designer. Everyone’s journey and learning process are different but you may find some tips that may work for you as well. Who knows? So, here we go:

Made Myself Acquainted With Basics

1. Understood the UX design process: Like common UX design process, called, Design Thinking. The Stanford Design School (d.school) formulated and open-sourced their famous 5 stage process attached below:

2. Learned the UI Principles: Typography, contrast, white space, working with color combinations, different kinds of grids, layouts, shadows, designing buttons, Composition & Balance, etc. Udemy and Uxcel make it easy for beginners.

Imitated Works Of More Skilled And Experienced Designers

1. Polished my design skills: Observed and trained my eye to see good design and bad design, paid attention to every detail, got familiar with design patterns. Got creative inspiration, and followed designers I admired. I mostly looked for designs at:

Confucius said, “I hear and I forget. I see and I remember. I do and I understand”.

2. Here is what I did:

  • Copied and recreated other designers to sharpen my design muscles (Only for learning purposes!)
  • Imitated but not blindly- observed spacings, usage of colors, the structure and layout, fonts selection.


Below is an email redesign which I imitated for learning purposes by designer- Nevil Suresh

Few extensions which help in the process are:

This process enhanced my creativity and developed an understanding of what a good design looks like.

Always ask "Why?" when you're designing or replicating something.

Enhanced My Knowledge

1. Read about design every day: Started reading books, articles, listened to podcasts, watched videos, took online classes and tutorials.

Elon Musk once said- "You can literally learn any skill you want for free on youtube. You can become a person of value in a matter of months. Just a few years ago this wasn't possible. If you were lucky enough to be born in this era, take full advantage of it."

Here I have jotted a quick list of few helpful resources:

Books:

YouTube channels:

2. Practiced more than I read: Used the acquired knowledge for my design. I tried learning and working hard every single day as that’s the only way one can improve. Tried to become one percent better every day.

It’s all about dedication, hard work, a lot of patience, and practice.

Learned The Latest UI Design Tools

I started learning the basics of Figma and began designing using it. If you learn the basics of one tool then you can easily use other tools as well. Few tools beginners should give a try: Adobe XD, Figma, and Sketch

There’s no one right tool for UI/UX designers. It’s really up to you to decide which software feels most user-friendly and unchallenging to you.

Started Working On Dummy/Concept Projects

1. Welcomed challenges: Subscribed to DailyUI.co, they send small interface design challenges daily and also tried Sharpen- a free design challenge generator. This helped me to build my portfolio and get future projects/opportunities. Post them online for feedback to further improve.

2. Joined communities and got involved: The only way to begin is to, well, begin!

I didn't wait for my best work to share in the community but in fact, built my online presence. Like every other design project, it gets better the more you practice and hone your skills so I uploaded all of my work and have not deleted/archived any of them in my design portfolios as it is an iterative process. Also, I checked design groups, discord, or social media to receive objective critiques of my design with constructive feedback.

Learned From Design Systems:

Observed and studied popular design systems as well:

Found a mentor

1. Found someone to mentor in the community: I fortunately found Sarvottam Ghosh for mentorship. I followed his tips, work, portfolio links, and Instagram page. This helped me in finding the flaws in my designs, improving my skills easily, and learning UI/UX quickly.

2. Applied for internships: When I got aware of what’s new in the industry and have built my portfolio (by practicing dummy projects, creating free designs/prototypes for friends with product ideas), I started applying for internships.

Conclusion

When you have more things to show, more opportunities will be open for you.

After training for months, my learning led to to find awesome opportunities and internships which have helped me to expand my horizons. Interning and working in the industry provided me with an environment where I can build connections, collaborate, share ideas, learn and grow under the guidance of experienced designers present there. While my journey to being a UI/UX designer has been a roller coaster ride in itself, I can't wait to explore the various opportunities out there by constantly learning and honing my skills

This has been my journey, I hope you've found it interesting and inspired you to try out new things!

Subscribe to Our Newsletter

More from the engineering frontline.

Dive deep into our research and insights on design, development, and the impact of various trends to businesses.
Insight
Why Legacy Systems Make Business Growth More Expensive: Navigate A Smarter Path to Legacy Modernization
Sep 23, 2026

Why Legacy Systems Make Business Growth More Expensive: Navigate A Smarter Path to Legacy Modernization

Learn how legacy systems make business growth more expensive and how edge-first modernization can remove constraints without replacing the existing system.

Insight
SSO, Audit Logs and RBAC: The Enterprise Features AI Prototyping Tools Do Not Cover | Sarika Gautam
Sep 23, 2026

SSO, Audit Logs and RBAC: The Enterprise Features AI Prototyping Tools Do Not Cover | Sarika Gautam

Why AI-generated prototypes fail enterprise review: the context behind SSO, the cost of skipping audit logs, and how role explosion makes RBAC a product of its own.

Insight
Feature Flags as Technical Debt: The Cleanup Nobody Schedules
Sep 21, 2026

Feature Flags as Technical Debt: The Cleanup Nobody Schedules

This blog explains how unmanaged feature flags create technical debt and how teams can detect, manage, and remove them safely.

Insight
Building AI-First Enterprises: Why System Design Matters More Than AI Adoption
Sep 21, 2026

Building AI-First Enterprises: Why System Design Matters More Than AI Adoption

This blog explores how system design, architecture, and validation shape AI-first enterprises, while examining AI’s impact on software engineering and human decision-making.

Insight
The Product Studio in the AI Era: What Actually Changes | Sarika Gautam
Sep 21, 2026

The Product Studio in the AI Era: What Actually Changes | Sarika Gautam

What changes in product development when AI writes the code: the shift to architecture, the token cost of unplanned builds, and why juniors still matter.

Insight
AI and the Future of Digital Customer Experience: Where Technology Meets Human Creativity
Sep 18, 2026

AI and the Future of Digital Customer Experience: Where Technology Meets Human Creativity

A discussion on how AI, human creativity, research, and cross-functional collaboration are shaping the future of digital customer experience.

Insight
Scaling Down Before Scaling Up: Why Bigger Servers Don’t Fix Bad Architecture
Sep 17, 2026

Scaling Down Before Scaling Up: Why Bigger Servers Don’t Fix Bad Architecture

This blog explores how inefficient backend architecture can cause performance issues even under low traffic, covering practical ways to reduce database load, API latency, and resource usage before scaling infrastructure.

The Right Conversation Can

Save You Six Months.

Book a call