---

Introduction to the Problem

At a recent matching team meeting, one of the developers noted, "We cannot ignore that users are getting lost in long job lists." This sparked a discussion on how to improve the user experience on the platform. While many of us focused on adding new filters, such as a salary filter, we decided to consider a simpler solution — the "Save Search" button.

Why This Matters

The issue of users getting lost was pressing for many of us. We received feedback from candidates who could not remember what searches they had conducted and wasted time trying again. This affected not only their experience but also the overall efficiency of the platform. A high bounce rate on the job listing page indicated that something needed to change.

Details of the Problem

One user searching for a marketing job wrote to support: "Every time I refresh the page, I lose all my filter settings and have to start over." This created frustration, leading users to close the tab more often than continue their search. We realized that the problem was not just a lack of filters but also that users could not save their preferences.

Initial Attempts at a Solution

Initially, we proposed a more complex filtering system, including a salary filter, to give users more options for customizing their searches. However, after several iterations and tests, we found that this solution complicated the interface and did not address the core issue — saving searches. We abandoned this idea and began exploring other approaches.

Technical Solution

After discussions with the team, we decided to add a "Save Search" button. This allowed users to save their current filter settings and return to them later. Here’s an example of code that illustrates the functionality of the button:

function saveSearch(searchParams) {
  // Save search parameters
  localStorage.setItem('savedSearch', JSON.stringify(searchParams));
}

This command saves the search parameters in local storage, enabling users to easily return to them. We also added the option to receive notifications about new job postings that match the saved search.

What Changed in the Product

After implementing the "Save Search" button, we noticed a significant improvement in user experience. The bounce rate on the job listing page decreased, and users began returning to their saved queries more frequently. This change also impacted sections like /jobs and /for-candidates, where users could now find relevant job listings more efficiently.

Lessons Learned

• Simplicity can be more effective than complex filters.
• Users appreciate customization options, but only if it does not complicate the interface.
• It is important to regularly gather feedback and make changes based on real user needs.
• Saving settings can significantly enhance interaction with the platform.

What This Means for Candidates

For candidates, this means they can now save their search queries and avoid wasting time on repeated searches. This improves their chances of finding suitable job openings and allows for more efficient time management.

What This Means for Recruiters

Recruiters can now expect users to be more engaged in the search process and, consequently, to return to the platform more often. This could lead to an increase in the number of quality candidates for open positions.

Next Steps

Although the "Save Search" button has brought noticeable improvements, we continue to monitor how users interact with this feature. We are considering adding a feature to automatically refresh search results based on saved parameters. If we could go back, we might have started with this feature to avoid unnecessary iterations with filters. However, overall, this solution has been a positive step forward for our product. ---