Each skill is a few short lessons, then practice. You rate yourself at the start and again at the end.
Core to the job
Chapter 2
Front-end engineering craft
Build a page that resizes cleanly and code a button
What you'll learn
Semantic HTML
Responsive layout rules
Component boundaries
Pull request review
AI code checks
Practice
Spot What's Wrong with This HTML Before It Ships15 min
Convert a Pixel-Pushed Layout into a CSS Grid20 min
Chapter 2
Coded design systems
Store repeated colours as variables, then build a documented component
What you'll learn
Design tokens
Component contract
Component states
Library drift
Practice
Turn Five Design Decisions into CSS Custom Properties15 min
Chapter 4
Visual design fundamentals
Design a layout so people read the main message first
What you'll learn
Visual hierarchy
Type scale
Spacing system
Contrast and grouping
Practice
Compare Visual Hierarchy in Two Competing Apps15 min
Chapter 4
Interface animation
Compare how animations speed up and slow, then tune timing
What you'll learn
Easing curves
Timing by purpose
Spring physics
Motion order
Reduced-motion path
Practice
Compare Three Easing Curves on the Same Button15 min
Choreograph a Three-Step Form Transition, and Make It Work Without Motion20 min
Chapter 6
Accessibility
Check a design for accessibility barriers and list practical fixes
What you'll learn
POUR principles
Colour contrast
Keyboard focus
Meaningful labels
Practice
Audit a Sign-Up Form for Accessibility Issues10 min
Chapter 6
Design handoff
Write build notes for a screen's images, interactions and errors
What you'll learn
Component states
Design tokens
Developer-ready spec
Shippable deviation
Practice
Spec one screen for engineering handoff30 min
6 more in the plan
Using AIReword a weak question and check AI's answer against sourcesCh 2
What you'll learn
Say what you want
Confident and wrong
What never goes in
Check by cost
The right job
CommunicationRewrite an update for two different readers, cutting extra linesCh 7
What you'll learn
Lead with the point
Match detail to the reader
Said versus heard
Specific feedback
Practice
Write a Six-Line Delay Message10 min
PortfolioWrite a case study explaining why you made major choicesCh 7
What you'll learn
Case study spine
Recruiter scan
Show tradeoffs
Clear case headline
Practice
Critique a Published Case Study and Rewrite Its Problem Statement30 min
Working with othersContribute to group work, ask for help and credit teammatesCh 8
What you'll learn
Early team friction
Clear ownership
Challenge ideas, not people
Lead or follow
Practice
Navigate a Disagreement Without Damaging the Relationship20 min
Problem solvingTest each possible cause of a problem instead of guessingCh 8
What you'll learn
Problem vs symptom
Clean problem splits
Root cause
Deciding under uncertainty
Practice
Separate the Problem from the Symptom10 min
Adapting to changeTry a new tool and describe how you handled changeCh 8
What you'll learn
Change vs your response
The messy in-between
Not there yet
Real change vs a feeling
Your plan
Chapter by chapter.
12 chapters, in this order. Chapter 1 is free.
1~2 wks
See the work of a Design engineer
StartFree
2~2 wks
Build interfaces in code from shared components
Skills
3~2 wks
Audit a public site for accessibility
Project
4~2 wks
Design interfaces with strong visuals and motion
Skills
51–2 wks
Talk to two working design engineers
People
6~2 wks
Hand over accessible designs ready to build
Skills
7~2 wks
Build case studies that get you hired
Skills
8~2 wks
Solve problems together when plans change
Skills
9~2 wks
Capstone: ship a polished site or interaction live
Project
101–2 wks
Answer the questions interviewers ask
Interview
111–2 wks
Decide how you will get in
Decide
12on your timeline
Send your first applications
Apply
The job
What a Design Engineer does
Works in both design files and code. Turns designs into polished, working interfaces without a slow handoff between teams. Owns the details that make products feel great: motion, micro-interactions (small animations that respond to a tap or click), and accessibility.
The work
Design interface components in Figma, then build them in React and TypeScript
Build and maintain the design system in code so components stay consistent
Prototype new features in production-quality code instead of static mockups (pictures of the design)
Add motion, transitions, and micro-interactions that make products feel responsive
Test interfaces for accessibility so people using screen readers can navigate
Use AI code tools like v0 and Cursor to turn designs into working UI fast
Bridge designers and developers by translating design intent into exact code
Polish shipped screens by fixing spacing, states, and small visual bugs
A typical day
Review open pull requests (proposed code changes) on design system components
Pair with a designer to turn a new Figma flow into a coded prototype
Build a component in React, adding keyboard support and screen reader labels
Tune an animation's timing until the interaction feels smooth and natural
Demo the working prototype to product and engineering for quick decisions
Log polish fixes and update design system documentation before closing the day
How long does it take to become a design engineer with Welica?
The plan is 12 chapters, 4–5 months at 15 to 30 minutes a day. You can go faster or slower; the plan moves with you.
Do I need a degree?
Not always. Common routes are bachelor degree in computer science, interaction design, or digital media, degree in graphic or product design plus self-taught front end coding, front end or full stack bootcamp combined with a strong design portfolio, self-taught route: online courses in React plus design fundamentals and projects, or related degree in HCI (human-computer interaction) covering both design and code.
What is free?
Chapter 1, See the work of a Design engineer, is free for good. Premium unlocks the rest of the plan.