Roadmap 04final

Student / Graduate→UX Engineer

For students and recent graduates starting from scratch: HTML, CSS and JavaScript, a design eye, one real project, a portfolio of details and open-source contribution.

Time9–18 months
Phases5
Lessons13
Written bySidhanshu Monga
What you bring
  • Time and energy to practise
  • Willingness to learn in public
  • Fresh eyes on existing products
What’s new
  • Solid frontend fundamentals
  • A trained visual eye
  • Experience shipping something real
  • A portfolio that shows how you think

Who this is for

You are studying, recently graduated or teaching yourself. You don't have years of experience in engineering or design yet. Maybe you have built a few projects and noticed that you care more about how they feel than most of your classmates do. That is a good sign.

Your advantage is time and a blank slate. You don't have habits to unlearn, and you can build both the engineering and the design skills together from the start. You can also learn in public without much risk.

The honest gap is that you have no moat. Without work experience, your portfolio carries all the weight. That is why this is the longest path. You need real fundamentals, a trained eye and proof that you can ship something people use. There are no shortcuts here, only taste and reps.

How the work changes

At school, work is usually graded on whether it meets the brief. In UX engineering, work is judged by how it feels to the people using it. That means caring about the parts no assignment asks for: the empty state, the slow network, the keyboard user, the error message.

Your learning also changes shape. Instead of finishing a course and moving on, you build, show, take feedback and rebuild. Small projects done carefully teach more than big projects done quickly.

Expect to work in two modes. Some days you will focus on engineering fundamentals. Other days you will study interfaces, copy them and train your eye. Both matter, and the role sits where they meet.

You will also learn to work with other people's code and opinions. That is why the last phase is open source. A merged pull request shows that you can read an unfamiliar codebase, follow its conventions and take review well. Those are the same habits a team will look for on your first day.

Finally, keep a simple log of what you build and what you learn each week. It helps you see progress on slow weeks, and it becomes raw material for your portfolio write-ups later. Short notes are enough: what you tried, what surprised you and what you would change next time.

  1. Phase 1wk 1–120/4 done

    HTML, CSS, JS

    You can build a responsive, accessible page and add behaviour to it with JavaScript.

    Ship it

    A small set of pages on a public URL, each one responsive and keyboard friendly.

  2. Phase 2wk 13–240/4 done

    A design eye

    You can explain why one interface feels better than another and apply that to your own work.

    Ship it

    A before-and-after redesign of one of your own pages, with a note on each change.

  3. Phase 3wk 25–400/4 done

    One real project

    You can take one product from idea to shipped, for real users, and keep improving it.

    Ship it

    A live product that real people use, with a short write-up of what you learned from them.

  4. Phase 4wk 41–560/3 done

    A portfolio of details

    You can show the small interaction details that separate polished work from working work.

    Ship it

    A portfolio site with three playable interaction studies and your one real project.

  5. Phase 5wk 57+0/3 done

    Open-source contribution

    You can work in someone else's codebase, take review and land changes.

    Ship it

    At least one merged pull request to an open-source UI project, linked from your portfolio.

Common traps

  • Tutorial loops. Following tutorials feels like progress, but building your own things is where you learn. After each tutorial, build something different without it.
  • Too many shallow projects. Ten half-finished apps say less than three careful ones. Go deep on fewer things.
  • Ignoring design. Strong code with weak visual judgement is not enough for this role. Practise your eye on purpose.
  • Waiting until you feel ready. Share work early. Feedback is how you improve, and nobody feels ready.
  • Chasing every new tool. The fundamentals last. Learn HTML, CSS, JavaScript and accessibility well before collecting frameworks.

How to show it

Your portfolio is everything, so make it playable. Every project should have a live demo or a short recording, and the code should be public.

Use the structure in A UXE portfolio: the interaction, the constraint and the decision. A strong graduate portfolio usually has one real project that people use, three small interaction studies that show care for detail, and a link to at least one open-source contribution. The breakdowns, such as easing curves, hover intent and fuzzy search, are good models for small, deep studies.

In interviews, talk about what you learned and changed, not just what you built. Explain a decision you made, what you tried first and why you changed it. Show that you take feedback well. Curiosity and care are what make a junior candidate stand out.

The other roadmaps and the resources list are there when you want more.

Edit this roadmap on GitHub·Updated ·Shared under CC BY-SA 4.0·A guide, not a contract — adjust it to your life