📋 Loop 8 ‘24
19/04/24
New updates and improvements.
Loop 8: releases, improvements and fixes
🎉 Releases
📈 Improvements
Improvements to search and relevance logic for candidates:
- Enhanced filtering for non-tech job titles: We've changed our approach to creating the base dataset for searches by non-tech job titles. Now, when a user searches for non-tech positions, they will be presented with a list of all positions within the non-tech categories. These results are then sorted by ranked relevance by default, ensuring that the most relevant matches, including job titles, are displayed at the top of the list. We will closely monitor the performance of this change to determine if further refinement is necessary, particularly as our database of non-tech positions expands in the future.
- Minimum salary adjustment: To provide more accurate search results, we've updated the minimum salary parameter to reflect the actual minimum salary for each job listing.
- Increased weight for job titles: Recognising the importance of job titles in searches, we've increased the weight of job titles to be equivalent to the weight of core skills when sorting by ranked relevance. This adjustment ensures that job titles are given appropriate emphasis in the search algorithm, leading to more relevant results.
- Skill tag inclusion for non-tech users: For non-tech users, searches are now built based on their job title, incorporating all skill tags instead of core skill tags. This change allows the search algorithm to utilise the
orSkill
parameters effectively. Additionally, we've expanded the inclusion of core and candidate-preferred skills within theorSkill
tag, further refining the search criteria to better match candidate preferences.
- Default sorting for user's job title: Searches created based on a user's job title will now default to sorting by
ranked_relevance
. This default sorting method ensures that the most relevant opportunities are displayed first.
- “Exclude positions without salary filter”: 33% of direct positions don’t disclose salary, so we have removed “Exclude positions without salary filter” from default searches so that users see more positions in their saved searches.
Other improvements:
- Updated reactivation pathways so that they are always correct for companies reactivating their account
- Added Microsoft Power Platform to the skills list, along with Power BI, Power Automate, Power Apps and Power Pages
- Agency customer stories are no longer shown on the cord.co/stories page
- Agency testimonials are shown on the cord.co/agencies page
- Changed candidate's search limit from 10 to 12 so that FE can fit 3 or 4 blocks in a row for search results
Internal:
- Implemented design tokens so that engineers have single source of truth when building features
- Refreshed Sales demo stats every 30 days
- Added detection of default company saved search
- Reorganised database indexes
- Removed Slack notifications for local environments
- Added
companyType
toapi/v2/account/candidate/shortlist
response so that FE wouldn't need to map the result again
🔧 Fixes
- Solved issue where users were not able to message about a position because they are on public search. We now redirect them to logged in search so messaging is as frictionless as possible.
- Fixed issue where the salary tool wasn’t appearing for any user
- Fixed visibility issue in dark mode - use rgb value for a colour used in rgba function
- Removed the ‘new’ label by ‘View Profile’ on candidate accounts
Did this answer your question?
😞
😐
🤩