JobBank Resume Editor optomizing
Constantly iterate and try to create a simpler, more convenient and flexible resume filling experience.
In 3 major iterations, each included countless optimization attempts. The main goal is to allow users to have a "what you see is what you get" resume creation experience.
Role & key partners
Me- Product designer / manager- Sr. Product designer
/ PM & SA / Supervisor- Design director
Collaboration
ver.1~2- design independently, discuss with PM & PO.
ver.3- coop. with manager, discuss with PM & SA.
Responsible
Comparative analysis & UI mockup & Hi-fi prototype for presentation.
Intensively discuss with partners.
(Initiative) Documenting record of discussion details to leave proof of decision.
Intro of fill-in flow (v.3)
Background
As the most important service on a job search website, resume-editing optimization is the main task of our team. As the main projects, resume revision in April were already in progress before I joined.
After I joined, I immediately started discussing the process experience and making prototypes.
Challenge
However, due to years of accumulated habits and technical problems, it is necessary to constantly find a compromise between innovative solutions, no changes, and restrictions.
The main difficulty is that I need to understand a very large amounts of different filling mechanisms and data modes and limitations while doing it at full speed.
Intro of fill-in sections & properties (v.3)
Problem
The original redesigned resume completed by the outsourcing team, but internal engineering and PM discovered so many problems so that it was necessary to lock down the development, prioritize the problems, and solve them one by one. At the same time, we discussed how to find the shortest path to catch up the launch DDL.
After the fail of launched of the original reversion in April (I don’t know the reason), Ver.2 & 3 redesign start immediately, the main purpose is to link the originally redesign back to the old version of the website, and continue to optimize the resume editing experience during it.
Goal
For Ver.1, we optimized the editing flow mainly by visualizing the steps and status clearly to let user know exactly where they are and what is next.
For Ver.2, we were promoting the service of "Editing CV first for quick apply, then continue to finish the whole resume", focusing on simplifying and minimizing the steps and fill-in forms.
For Ver.3, aiming to modularly display categories of forms at once and hierarchically, let user can quickly switch between preview and filling mode to help improve efficiency and reduce uncertainty.
Variables setting
for Type, State, Status and Size
When there are many types and states of interaction, using Figma's variable function to set the properties is necessary.
The image below is the whole picture of all properties of info fill-in forms.
CV editor- Official released & Handoff
The images above is the online version, and the images below is the ver.2 Handoff.
(the redesign of CV editor was based on modal for easily switching.)
New feature: Apply previously filled data
Intro of component annotations
Resume design reversion in April- Ver.1
Resume design revision in April- Ver.2
- Data editing changed to Modal
Resume design revision in April- Ver.3
- Main process of mobile version
Tablet main screens
Learning
Don’t discuss without pictures
There are old versions as reference, but when there is a lack of specification documents and wireframes from PO&PM, the designer should quickly produce wireframes so that the effective communication can start.
Train a brain with extremely clear, logical and strong memory.
The real situation is usually that the requirements are confusing, there are frequent modifications, additions and deletions, so I learn to clearly record discussions and decisions. (I was jokingly called the little secretary because I took the initiative to take notes.)
Be brave to let my solutions be heard, discussed and implemented.
Team often in a situation where it was difficult to decide or find solutions. Although I am still a rookie, I still actively express and visualize the solutions I think are possible, and they have been successfully accepted and implemented many times.

























































