Overview

Problem statement

Handshake created a feature that digitalised the career fairs for students and alumi’s, creating a network around multiple users like undergoing students, alumi’s, recruiters and hiring managers.

Users and audience

a — Hiring managers b — recruiters c — Alumi (or graduates) d — students

Roles and responsibilities

On this project

1. Scope and constraints
2. Process and what you did

1. Outcomes and lessons

Overview

Fierce created a great team in early 2022 in order to reimagine the mobile and web experience for Handshake, a recruitment platform with a set of swiss army knife like features for graduate students.

But in order to do that it required to think a multi user level experience across our 3 personas

Career Fair Video Conference Sessions

EMP CRM

Integration

During The Fair

Filter Sessions

Search

Reassigning a

Changing a Group Session Time

See Other Companies

More Options

Conflictiong Times

Communication

In order to drive value to the product and differetiate from competitors communication was a key part of the new features. Our focus was to seek the best way to integrate Group sessions, where one or two hosts will present of talk to up to 50 participants and 1:1 Sessions that will be act more like a video call.

Differentiation

Even if at the core they are pretty similar and share lots of components the Group session is time based while the 1:1 Sessions start and end from messages section as they are an extension of it.

Group Sessions [STU x Mobile]

Group sessions are a big part of the Handshake experience, as it marks the core feature of the digital career fairs and the part that adds human connection and thus value to the product.

Structure wise a group session will feature a presentation that will be turned on and off by the hosts while the other sections like Participants, Chat and Details will be always on

Lobby Screen is used in the edge case when the hosts are late and tge session didn’t started yet we will feature a waiting screen for a while. The participants can see each other as they start to join but the main audio-video channels will not be available .

Because we prioritise the presentation we first tried to create a 3 tab toggle with the addition option to swipe through as a heuristic gesture.

Model A - Tab version

Unfortunately that means the menu will change if a person is sharing a presentation and this might be confusing. Also from our user interviews we learned that users want more options and they might want to explore the chat for example while watching the presentation, and this wouldn’t be possible with the tab version.

Model B - Split portrait view

A solution was to rely on a split screen and have the fullscreen option in landscape view. The nav will be composed still by the two (Participants & Chat) sections and the advantage is that if no one shares a presentation the space will be saved.

In the Participants Section students have the option to quickly preview the hosts and fellow students.

Different concept ideas

Details Page will come either as an overlay modal, or a page and will feature everything that we had in the schedule section

Functions

STU Join / Interact in Group Sessions (Participants and Chat)

STU raise hand

1:1 Sessions

Normally you would downscale the group version, remove a couple of items and you will get a 1:1 session. But instead we tried a diferent approach, group sessions started from the premise they are a streaming event with options to speak up and interact, while 1:1 sessions are an extension of a call that starts from messages.

We tracked how users start the video calls and surprisingly 60% jumped on a call from mesages opoed to the rest that schedule an event in the calendar. Jumping on a video call was an experience that most got familirised and can happen instantly, aditionaly to the schedule option that can be mised, not synched and people running late.

Calls can start from the calendar or from a messaging threads

One experimental feature was to create a call widget for the message thread, in this situation the Recruiter can start a session and invite to join rather than an intrusive call that may be missed, cancel, etc

Booking a 1:1 Session (Visual UI)

Employer CRM

We took into consideration when designing the persona that will use interphase on a daily basis, in constrast to most of average users that focus on entertainment or facilitation. This brings a few key achievement points:

• Automation focus — figure out useless repetitive points on the flow
• A clear structured taxonomy
• Avoid clutter, prioritise what is used and tuck away anwanted items
• Focus on a perfect integration with the current structure
• Test and learn by doing rapid prototyping