Skip to content

Design system · Theming · B2B SaaS · Visual design · Freelance

Four job-portal products, one design system, one switch between them.

A job portal with a separate product for each side of hiring. As the only designer, I redesigned two products, designed two from scratch, and built one system under all four, so a candidate screen and an admin screen differ in hue and nothing else.

Role
Freelance product designer. Owner of the design system
Team
Solo designer, with the client's product team and developers
Timeline
2 months, 2026
Status
Handed off to development

The client. The client runs a job portal with four products across seven apps: Candidate and Employer on web and mobile, Admin on web and mobile, and Super admin on web. Each product had been built on its own, so every new screen started as a copy, and the products no longer looked like one company.

In short. I audited the early build's styles first, then rebuilt from the foundation: colours named by their job, a brand switch that turns candidate purple into internal blue, and one library of masters for mobile and web.

277 tokens, 82 component sets and about 600 screens, redesigned or new, in two months.

design system behind four products
1
colour themes from one component set
4
screens redesigned or built new on it
~600
01Why it kept drifting

A redesign with nothing to build on.

An agency designed the first Candidate and Admin products. The client brought me in to redesign both, design Employer and Super admin from scratch, and give his developers a system to build from.

What I heard

  1. The look wasn't rightClientThe client didn't like how the agency's design looked, on any of the products.
  2. Two brands, two modesClientPurple for candidates and blue for the internal teams, each in light and dark.
  3. Devs complainedClientWith no design system behind the screens, every build problem ended up with him.
  4. No rules to build fromDevelopersThey wanted proper guidelines for every basic component and for spacing. Without them, each screen was hard to build.

So before redesigning a single screen, I went through what the early build actually contained.

The candidate dashboard in the early build: four stat cards, an empty recommended jobs panel and a list of recent applications.
The candidate dashboard in the early buildBefore · Candidate web · dashboard
02What the audit found

Nothing in the early build was shared.

I went through the old styles and screens before designing anything. Eight problems stood out, ranked here by how much damage they did.

8

problems, ranked by damage

From the early build's styles and screens, before I designed anything.

ProblemIn the early buildWhat it cost
No one owned the qualityNew components kept going into the system, but no one checked that each was built properlyNothing stopped the problems below from spreading
Four copies of one paletteColours, spacing and radius saved four times. The colour sets held 8, 8, 5 and 8 valuesA fix in one copy never reached the other three
Same name, different colour"Neutral 4" was grey #989997 in one copy and beige #C9B49A in anotherPicking a colour by its name could give you the wrong one
Look-alike valuesBackground #FDFCFB against #FCFCFB, accent #B69978 against #B69977Nobody could say which one was right
Icons that never sat rightEach icon carried its own paddingTwo icons at the same size looked like different sizes
Missing rolesOnly one copy had a secondary text colourGrey text was picked by eye, screen by screen
Raw values onlyEvery colour and size was a raw value. None was named by its job, and there were no modesA new brand or a dark theme meant editing every screen
Wireframes for consolesAdmin and super admin web started as 153 screens of wireframesThe internal products had no visual language to build on

If something looks wrong in blue, the fix is a token, not a new component.

That one rule, written into the file, kept four products on one system.

03How I fixed it

Colours named by their job, so one switch can retheme a product.

I built the tokens first, then the mobile and web libraries on top, then rebuilt every product on them.

Same components · one switch

Candidate brand, light mode. Purple for the candidate products.

Candidate brand, dark mode. The same screens; only the Theme layer changes.

Internal brand, light mode. Blue for the admin, employer and super admin products.

Internal brand, dark mode. Two switches, two values each: four themes.

The candidate dashboard and My Jobs phone screen in the purple Candidate brand, light mode.

System. From raw values to seven apps, in five steps

A token is a named setting a component reads instead of a raw colour. Here is the whole chain, from raw values to the products.

The token chain in five steps: 142 foundation tokens, 30 brand tokens, 89 theme tokens, 82 component sets and 7 apps. Below, one token, action/primary-bg, resolves to four colours across the two brands and two modes.
Two switches, two values each: that is where the four colour themes come from. Every product follows the same rule.

Light and dark. Dark mode is a column of links, not a second palette

64 of the 89 named colours change in dark. The other 25, like white text on brand buttons, stay put. Dark mode is a second column of links, not a second set of colours.

The Theme collection in Figma: surface colours like canvas, raised and brand, each with a Light and a Dark value linked to brand and ink steps.

Brands. Purple to blue is one setting

Flip the Brand layer from Candidate to Internal and 38 of 89 colours change. The other 51 stay, including every success, warning, danger and border colour, so a status means the same thing in both brands.

The Brand collection in Figma: brand steps 50 to 950 point to purple in the Candidate column and to cobalt in the Internal column.

Layout. One shell, four breakpoints

The web shell reads its grid, padding and panel sizes from one collection with four breakpoint modes.

The Layout collection in Figma: values like nav rail, columns, gutter and modal width across Desktop 1440, Laptop 1280, Compact 1024 and Mobile.
The Layout collection. The nav rail goes 256, 256, 88, then 0 on mobile. Columns go 12, 12, 8, 4.

Library. Every component is a master, every use a variant

The web button is one master with 45 variants: 5 types, 3 sizes, 3 states. One side nav serves all four roles through a Role property. The eight boards are built from the live components.

Eight boards from the component library: colour palette, buttons, controls, inputs, typography, iconography, navigation and feedback.
Built from the live library. The Internal button row is the same component in the other brand mode.
3

smaller calls that kept it honest

Each one is small. Together they're why the library stayed in one piece.

  1. Two shadow sets, one per platformPhones got five levels, from card to bottom bar. Web got three: nav, popover and modal.
  2. Icons picked, not drawn75 icons from Iconsax, wrapped in one Icon component, out of about 2,000 in the set.
  3. A weekly check with developersEvery week we went through what had been built, so Figma and the build stayed the same.
4

rules, written where developers would see them

They sit on the How to apply board, next to the brand modes.

  1. Bind to jobs, not coloursNever a primitive, never a raw hex.
  2. Never copy for a platformIf it looks wrong in blue, fix the token.
  3. Keep the blue on 600It's the step contrast was checked at, in both themes.
  4. No new mode per productA new internal product points its page at Internal.

I owned the system for all four products.

04What changed

From 95 loose values to one system of 277.

The redesign is with the developers, so these numbers come from the design file, not the build.

The numbers

tokens in five layers, up from 95 raw values
277
component sets, with 534 variants
82
component instances in the screens
17,705
of web component fills read a token
92%

Every product, redesigned on one system

Purple tiles run in Candidate mode, blue tiles in Internal. Nothing was redrawn per product.

Redesigned screens from every product: candidate web and app, admin web and app, super admin web, and an assessment screen, purple in Candidate mode and blue in Internal.

What I'd do differently.

  1. 01Test every component in all four themesDark mode passed on web and broke on mobile: the tab bar turned white and its labels disappeared. A four-theme check per component would have caught it early.
  2. 02Check contrast on the quiet colours tooGrey secondary text sits at 3.88:1 on white, under the 4.5:1 minimum for body text. I'd move it a step darker before handoff.
  3. 03Check each screen's bindings before handoffA few mobile screens still had typed-in colours.

Still open: how fully the developers use the tokens in code, and whether dark mode ships.

The project, at a glance.

  1. ClientA job portal, name withheld. Freelance project.
  2. ToolsFigma variables, modes and component properties for the system. Iconsax for the icon set.

Next case study

Karnataka BankRebuilding a 100-year-old bank's app customers called undependable.

Ask-bidyut · tty1

BIDYUT-OS 1.0 · PORTFOLIO ASSISTANT

(c) 2026 Bidyut Bera

Hi, I'm AI Bidyut. I answer from my portfolio, so I may get things wrong. Pick a question or type your own.

Chats are processed by an AI provider. Don't share sensitive info.