About
Robert Half is the world's first and largest specialized talent solutions firm that connects highly skilled job seekers with companies. These positions range in fields such as finance, law, technology & more. They have been in business for more than 75 years and are the leader in staffing solutions.
Candidate Scheduling
Read time: 9 min
Role: Sr. Product Designer
Tools used:
Business Goals
Create a solution to allow appointment scheduling between Talent Solutions ProfessionaIs (TSP) and vetted candidates (two-sided market). These goals are outlined below in detail.
- Streamline the process for TSPs to schedule multiple meetings on their calendars with Shortlisted(vetted) candidates via Salesforce.
- Allow invited job-seeking candidates to schedule and view an appointment with a TSP via RH’s website portal.
Teams Involved
- User Research
- Legal
- Copy
- Product Managers (Web/Salesforce)
- Development
- Marketing
Current Problem
The current scheduling between prospective candidates and TSPs was limited to email, text, and phone call communications. This experience has cost the business revenue due to long times to hire, inefficient internal candidate vetting, and overall job placement rates.
Alignment
In order to kick off the project I facilitated a series of alignment sessions to begin gathering the information and planning of work needed from the TSPs, PM (Salesforce), and UX Research teams.
Research
Key Learning Objectives Gain a rich understanding of experiences and motivations related to the job-seeking and hiring process.
Insights
- I need an easier way to initialize communication of vetted candidates
- I would like to spend less time with back-and-forth scheduling
- I want to reach out to multiple candidates to maximize my time with candidates later in the hiring funnel
- I expect working with recruiters to be fast and easy
- I value responsiveness as time is of the essence
- I talk with multiple recruiters because I want to cover my bases
Since this project was intended to be an end-to-end solution for candidate scheduling, I wanted to begin shifting focus on the talent solutions professional experience. This entails communication with prospective candidates and sending over the appropriate information from Salesforce (CRM) to begin the candidate scheduling web experience.
Current Salesforce Experience
What you are seeing above is an example job record and the actions a TSP can take after the system identifies quality candidates by leveraging Robert Half’s proprietary AI model. During this time there were considerations made to leverage a 3rd party vendor to integrate into RH’s Salesforce environment. Essentially this tool would be providing an API to handle time slots for booking, invite additional attendees, auto-create Salesforce objects…and more.
Wireflows
Lo-Fidelity Mockups
Above are the lo-fidelity mockups for the TSP experience.
Within the Salesforce environment, many of the designs were leveraging a mixture of Salesforce classic and orphan SLDS components. Moving forward with this project I realized that the team would benefit from a shared SLDS library to pull from for designers working on Salesforce projects.
Hi-Fidelity Mockups
After stakeholder's approval, I moved straight into prototyping the TSP experience in Figma🧑🏽💻
TSP - Salesforce Experience
Candidate Scheduling Experience
After finalizing the TSP experience, I shifted focus to the Candidate web experience flows. The above image was a collective effort with PMs (Web Candidate) and UX team to understand how candidates would navigate through the scheduling experience.
Prototype
Metrics
Recap
One of the challenges that I hadn’t considered was that sometimes out-of-the-box solutions are not always the easiest to implement. In this case, there was a development issue using an SLDS date picker component that was intended to span between two selected dates when a TSP is creating their availability. This out-of-the-box component shows the functionality from a design standpoint on SLDS’s design system documentation but when collaborating with the development team proved a challenge since it would impact the product feature release deadline due to the customizations needed. As an alternative to the intended design, we came to a solution where the system would auto-prompt an end date after the selection of the initial date. This ensured that we can keep close to the development bandwidth and still provide a working solution by release. Overall, this was quite a large project and enjoyed the challenges that came with it. I had the opportunity to learn more about how our users(internal/external) interact with our product and how we can create an experience for both sides that helps solve their problems.