CFO
Selected
Chief Financial Officer
Executive · Finance
Leads financial strategy, planning and reporting.
View details
Selected
As a Senior UX Designer, I work directly with a vice president and engineers on the tools recruiters use to choose job profiles and manage candidate progress.
I design the screens, interactive prototypes and reusable Figma components, including AI-assisted updates that recruiters can edit and confirm before saving.
Example: choosing a job profile
Fictional example: a recruiter searches for a finance role, reads the descriptions and confirms a job profile. Client screens and data are not shown.
From the first questions to build review. I review the existing steps with product managers and engineers. I map the full task, design the screens, and make a prototype we can click through. I revise the designs with their feedback and check the build with engineers.
Shared components the team can reuse. I create and update shared buttons, cards, and layouts in Figma. I show how these parts should work so the team can use them across the software.
What stays private. Client screens and data stay private. The examples use fictional roles and candidate information to explain my design decisions.
My role
One part helps recruiters choose a profile that describes a job. The other keeps candidate activity, notes and follow-up work together. Korn Ferry calls these tools Success Profile Selection and SearchFlow.
The examples use fictional content. Client screens, data and research records stay private.
01 · Candidate progress
SearchFlow is where recruiters keep a record of each candidate’s progress. They log calls, add notes, arrange interviews and track follow-up work.
I designed a candidate workspace that brings the current stage, activity history and open tasks into one view. I explored two layouts: separate cards for tasks and the timeline, and a stacked version with tasks above the activity history.
I also designed an AI-assisted update flow. A recruiter can describe a resume review and an interview request in one message. The prototype presents two separate updates so the recruiter can check, edit and confirm them before saving.
Working prototype
Try it. Select an open task, or choose “See proposed updates” to try both. Edit a draft, confirm it, and see the timeline update.
Example candidate · Finance leadership role
Candidate context stays visible while the update is prepared.
Ready to prepare an update for Alex
Review the two proposed updates
Reviewing with team
Resume reviewed with the team.
To be scheduled · Jordan
Interview requested. No calendar invite sent.
The recruiter reviews the records before saving.
See the timeline updateSwitch between “Separate cards” and “Stacked layout.” The information stays the same; the arrangement changes.
Try the layout switch
02 · Choose a job profile
Recruiters choose a job profile, called a Success Profile in the software, for the role they’re hiring for. They search by job title, review the profile’s description, level and function, then confirm their choice.
I worked on the search, profile details and selection flow. Following team feedback, I clarified the labels and added sorting by Best Match or Title (A–Z). I also designed the loading, cancellation, no-results and error states.
Making the labels clearer. “Job title” says what to search for. “Scope” describes the role’s responsibility level, rather than a candidate’s work experience.
Working prototype
Try it. Open Finance Director’s description. CFO stays selected until you choose another role. Select Finance Director, then choose “Use selected profile.”
Compare each role’s description, level and job function.
Example results 3 job profiles
Leads financial strategy, planning and reporting across the company. Works with the executive team on financial decisions.
Leads budgeting, forecasting and financial planning for a team or business area.
Oversees accounting operations, financial records and the preparation of financial reports.
Open another description or choose a different profile.
Show that the search is still running and offer a way to cancel.
Confirm the search stopped and let the recruiter try again.
Explain that there are no matches and suggest adjusting the search.
Explain that something went wrong and provide a retry action.
03 · Compare profiles
Recruiters can read another job profile before deciding whether to switch. I kept reading the description separate from selecting the profile.
CFO stays selected while the recruiter reads Finance Director. To use Finance Director instead, they select it, then choose “Use selected profile” to confirm.
04 · Reuse the design
I create and maintain shared Figma components for buttons, profile cards and layouts. The team reuses them across job-profile selection and candidate workflows.
When a design changes, I update the shared library and review the behavior with engineers, including what happens when someone opens details, selects a profile or confirms a choice.
Interactive component example
Try the shared buttons. Highlight them to see the reused design, then try either action. Each confirms its own fictional example.
One primary button design. The label changes with the action.
Job title: Chief Financial Officer
Candidate: Alex Morgan
Illustrated profile change
Reading keeps CFO selected. Selecting Finance Director changes the choice; the confirmation button applies it.
Explore the selected states, inline descriptions and confirmation button in the CFO example.
Highlight its place in the example screen.
Reading Finance Director leaves this choice in place.
Expand the description while CFO stays selected.
Leads budgeting and financial planning for a business area.
“Use selected profile” confirms CFO in this example.
Fictional component examples.
The components in one screen
Leads financial strategy, planning and reporting.
Leads budgeting and financial planning for a business area.
Selection: CFO stays selected while Finance Director is read.
Working with engineering
I review prototypes, component behavior and build requirements with engineers. This diagram illustrates that process.
Build checks and accessibility
These sample checks cover screen states, keyboard use and readable controls. They are not client test results.
| State | What someone needs to know | What the design needs to do |
|---|---|---|
| Loading | Whether the software is working | Show progress and keep the person’s place. |
| Empty | Why no results appeared | Explain why and offer a next step. |
| Selected | Which profile is selected | Keep the chosen profile marked while details are open. |
| Changed | What changed on the screen | Update the right part without resetting the page. |
| Error | How to try again | Keep the person’s choice where possible. |
| Success | Whether the action worked | Confirm what happened and show the next step. |
05 · Approved + in use
I’m continuing to refine the job-profile and candidate workflows with product managers and engineers. The shared Figma components are also being reused across the recruiting software.
The examples include prototypes and layout alternatives. Approval and use refer to the first design version.
The team approved and began using that version.
Approval + useThe prototype covers search, descriptions, selection, confirmation, refresh and cancellation.
Clickable prototypeI maintain the Figma library used across the internal system and update it with the screens.
Parts the team can reuseI use feedback to revise the steps and screens with the team.
Work with product and engineeringWhat I would measure next
I would compare similar tasks before and after the change, checking completion, median time to confirm a profile, selection errors and returns to earlier steps.
Reflection
I ask what needs to change and why.
A clickable prototype gives us something to review together. When feedback changes the design, I update the screens and components.
I review the working software with engineers during the build.
Client screens, research records, internal data, and private technical details stay confidential.
More selected work
A wildlife planner I built and a website I redesigned for a software company.
I designed and built a wildlife planner for Yellowstone and Grand Teton. The work includes the website, checkout, member access, saved route PDFs, and field guides.
Read case study →I designed and built the website to help buyers understand the software and choose a free trial or demo.
Read case study →I’m looking for a full-time senior UX, product, or web design role. I bring 15+ years of design experience and hands-on coding skills. I work closely with product managers and engineers.