UI/UX, Product design
I implemented general UI and UX improvements related to settings configurations, search and filter capabilities, and navigation in the Mya recruiter portal
5 minutes
My role
As the only designer at Mya, I handled most of the UI and UX development for a the recruiter portal. I would work closely with the PM, engineers, and leadership to define the user experience while simultaneously presenting ideas internally and externally using wireframes and interactive high fidelity prototypes.
Client
Mya Systems
Tools
Sketch, Invision, Balsamiq
Collaborators
Ben Rohrs
Project Manager
Mihail Gumennii
Frontend Engineer
Navigation
Mya is an AI chatbot that recruiters can use for inbound and outbound recruiting. Mya can talk directly to candidates to gather job-related information, gauge interest, answer questions, etc. While Mya may seem fairly autonomous, there is a ton of work going on behind the scenes, especially on the customer's end. To keep Mya running, customers were given access to the Mya Recruiter Portal (MRP).
Our typical user groups in the MRP were recruiters and recruiter admins/hiring managers. Users could do a variety of things, like launching Mya outbound recruiting initiatives, designing Mya's conversations, viewing candidate information collected from a Mya conversation, and much more. Essentially, the MRP was how customers communicated with Mya, the AI.
During my time at Mya, the company was rapidly growing, as was the MRP. I had the chance to contribute to many aspects of the MRP, from huge new features down to small UI updates. Though some of the updates felt small, they improved users' effectiveness with the tool. The following sections will detail UI and UX improvements related to settings configurations, search and filter capabilities, and navigation.
Initially, the search bar in the MRP functioned locally. Search criteria were only applied to the content of the page the user was currently on. If a user was in the Campaigns list view, their search results were tied to Campaigns. We introduced global search and search filters to help our users get around the MRP with more ease.
The filters button surfaces a dropdown with filters that only apply to the page it is on. Each page had a different set of filters, so each filter menu looked slightly different. Some pages didn't even have filters.
As the AI became more robust and Mya conversations improved, we were able to capture and store more candidate information. That information went far beyond the basics of Candidate name, phone number, email, etc. We had information such as a candidate's preferred work location, work availability, experience, desired job factors. Now the challenge was to make that information even more valuable to users.
We decided to introduce advanced filtering for candidates. Users could now generate lists of candidates that meet fairly specific criteria.
Now that users could search by very specific candidate information, we needed a better way for them to view that stored information. Since they would be looking at dozens of candidates at a time, we wanted a way for users to quickly access each candidate's information without overcrowding the page, navigating the user away from the page, or surfacing modals that disable scrolling and requires the user to click to exit.
We decided to display the information in a candidate preview panel that pushed out from the right side of the screen.
The MRP previously did not have any settings configurations beyond managing a users' profile. Everything was configured on the Mya team's side. To reduce the number of interactions between customers and Mya engineers, we decided to build a separate Admin Settings section in the MRP. I developed a general look, architecture, and system of navigating, including a specific design for recruiter calendar management and email settings.
I updated the MRP left-hand nav several times. My final version had some new features to it:
UI/UX, Product design
I implemented general UI and UX improvements related to settings configurations, search and filter capabilities, and navigation in the Mya recruiter portal
Client
Mya Systems
Tools
Sketch, Invision, Balsamiq
Collaborators
Ben Rohrs
Project Manager
Mihail Gumennii
Frontend Engineer
My role
As the only designer at Mya, I handled most of the UI and UX development for a the recruiter portal. I would work closely with the PM, engineers, and leadership to define the user experience while simultaneously presenting ideas internally and externally using wireframes and interactive high fidelity prototypes.
UI/UX, Product design
I implemented general UI and UX improvements related to settings configurations, search and filter capabilities, and navigation in the Mya recruiter portal
5 minutes
My role
As the only designer at Mya, I handled most of the UI and UX development for a the recruiter portal. I would work closely with the PM, engineers, and leadership to define the user experience while simultaneously presenting ideas internally and externally using wireframes and interactive high fidelity prototypes.
Tools
Sketch, Invision, Balsamiq
Collaborators
Project Manager
Frontend Engineer
Mya is an AI chatbot that recruiters can use for inbound and outbound recruiting. Mya can talk directly to candidates to gather job-related information, gauge interest, answer questions, etc. While Mya may seem fairly autonomous, there is a ton of work going on behind the scenes, especially on the customer's end. To keep Mya running, customers were given access to the Mya Recruiter Portal (MRP).
Our typical user groups in the MRP were recruiters and recruiter admins/hiring managers. Users could do a variety of things, like launching Mya outbound recruiting initiatives, designing Mya's conversations, viewing candidate information collected from a Mya conversation, and much more. Essentially, the MRP was how customers communicated with Mya, the AI.
During my time at Mya, the company was rapidly growing, as was the MRP. I had the chance to contribute to many aspects of the MRP, from huge new features down to small UI updates. Though some of the updates felt small, they improved users' effectiveness with the tool. The following sections will detail UI and UX improvements related to settings configurations, search and filter capabilities, and navigation.
Initially, the search bar in the MRP functioned locally. Search criteria were only applied to the content of the page the user was currently on. If a user was in the Campaigns list view, their search results were tied to Campaigns. We introduced global search and search filters to help our users get around the MRP with more ease.
The filters button surfaces a dropdown with filters that only apply to the page it is on. Each page had a different set of filters, so each filter menu looked slightly different. Some pages didn't even have filters.
As the AI became more robust and Mya conversations improved, we were able to capture and store more candidate information. That information went far beyond the basics of Candidate name, phone number, email, etc. We had information such as a candidate's preferred work location, work availability, experience, desired job factors. Now the challenge was to make that information even more valuable to users.
We decided to introduce advanced filtering for candidates. Users could now generate lists of candidates that meet fairly specific criteria.
Now that users could search by very specific candidate information, we needed a better way for them to view that stored information. Since they would be looking at dozens of candidates at a time, we wanted a way for users to quickly access each candidate's information without overcrowding the page, navigating the user away from the page, or surfacing modals that disable scrolling and requires the user to click to exit.
We decided to display the information in a candidate preview panel that pushed out from the right side of the screen.
The MRP previously did not have any settings configurations beyond managing a users' profile. Everything was configured on the Mya team's side. To reduce the number of interactions between customers and Mya engineers, we decided to build a separate Admin Settings section in the MRP. I developed a general look, architecture, and system of navigating, including a specific design for recruiter calendar management and email settings.
I updated the MRP left-hand nav several times. My final version had some new features to it:
UI/UX, Product design
I implemented general UI and UX improvements related to settings configurations, search and filter capabilities, and navigation in the Mya recruiter portal
5 minutes
As the only designer at Mya, I handled most of the UI and UX development for a the recruiter portal. I would work closely with the PM, engineers, and leadership to define the user experience while simultaneously presenting ideas internally and externally using wireframes and interactive high fidelity prototypes.
Tools
Sketch, Invision, Balsamiq
Mya is an AI chatbot that recruiters can use for inbound and outbound recruiting. Mya can talk directly to candidates to gather job-related information, gauge interest, answer questions, etc. While Mya may seem fairly autonomous, there is a ton of work going on behind the scenes, especially on the customer's end. To keep Mya running, customers were given access to the Mya Recruiter Portal (MRP).
Our typical user groups in the MRP were recruiters and recruiter admins/hiring managers. Users could do a variety of things, like launching Mya outbound recruiting initiatives, designing Mya's conversations, viewing candidate information collected from a Mya conversation, and much more. Essentially, the MRP was how customers communicated with Mya, the AI.
During my time at Mya, the company was rapidly growing, as was the MRP. I had the chance to contribute to many aspects of the MRP, from huge new features down to small UI updates. Though some of the updates felt small, they improved users' effectiveness with the tool. The following sections will detail UI and UX improvements related to settings configurations, search and filter capabilities, and navigation.
Initially, the search bar in the MRP functioned locally. Search criteria were only applied to the content of the page the user was currently on. If a user was in the Campaigns list view, their search results were tied to Campaigns. We introduced global search and search filters to help our users get around the MRP with more ease.
The filters button surfaces a dropdown with filters that only apply to the page it is on. Each page had a different set of filters, so each filter menu looked slightly different. Some pages didn't even have filters.
As the AI became more robust and Mya conversations improved, we were able to capture and store more candidate information. That information went far beyond the basics of Candidate name, phone number, email, etc. We had information such as a candidate's preferred work location, work availability, experience, desired job factors. Now the challenge was to make that information even more valuable to users.
We decided to introduce advanced filtering for candidates. Users could now generate lists of candidates that meet fairly specific criteria.
Now that users could search by very specific candidate information, we needed a better way for them to view that stored information. Since they would be looking at dozens of candidates at a time, we wanted a way for users to quickly access each candidate's information without overcrowding the page, navigating the user away from the page, or surfacing modals that disable scrolling and requires the user to click to exit.
We decided to display the information in a candidate preview panel that pushed out from the right side of the screen.
The MRP previously did not have any settings configurations beyond managing a users' profile. Everything was configured on the Mya team's side. To reduce the number of interactions between customers and Mya engineers, we decided to build a separate Admin Settings section in the MRP. I developed a general look, architecture, and system of navigating, including a specific design for recruiter calendar management and email settings.
I updated the MRP left-hand nav several times. My final version had some new features to it: