Now

Five fixes went out this week, from the order of your Boolean search results to a scrollbar you can drag again.

For companies

• Boolean searches that rank by relevance: With the Recommended sort, a Boolean decided who appeared but not in what order, so a search for "AEM" put popular engineers with one passing mention above genuine specialists. The candidates who match your Boolean best now come first. Popularity and recent activity still count, but they can no longer lift a weak match above a much stronger one.

• No more crashing position pages: A position crashed instead of loading if a hidden account was on its hiring team. Up to 45 live positions across 14 companies were affected, and they all open now.

For job seekers

• Keyword searches from discover now work for everyone: If you had no saved searches, a keyword search typed from Discover lost its keyword on the way to the results. The page showed your search as its title, then listed all 19,107 positions. It now shows only the matching roles, with the keyword as a filter you can remove.

• A scrollbar you can drag: When you opened a role from a results list, dragging the scrollbar or clicking its track did nothing. It scrolls now, which matters if you use a touchscreen or a mouse without a wheel.

For everyone

• Hiring Leaders rankings: The Summer '25 and Spring '25 rankings crashed instead of opening when a company in them had no record for that season. They load now, and season names no longer carry a month range after them.

Intros used to be a page of its own, with a dropdown to switch between roles. It now sits on each position as a tab, next to everything else you do on that role, and every set is twice the size.

Additional Features

• Intros on the position page: Each position now has its own header and tabs, with Intros next to the position's analytics and settings. You switch roles from the sidebar rather than a dropdown.

• Ten intros per set: Each set now brings you 10 candidates instead of 5. The same person can no longer turn up twice in one set.

• Start a position's intros yourself: A new position used to wait for the overnight run, and that doesn't run at weekends. If you're on the hiring team and a position has no intros yet, you can now start them from the position page.

• Analytics for one position: The Analytics tab shows views, requests sent and received, how fast you reply and conversations started, for that position alone, from the day it was posted.

Improvements

• Candidates matched to the job description: About 90% of live positions had no qualities set, so a new role had little to rank candidates against. cord now reads them from the job description.

• Saved and Not right per position: Both lists now belong to the position they came from, and they stay after the role is filled. A closed position's intros are read-only.

• A wider pool: Intros can now reach passive candidates and people with adjacent skills, who were left out before.

Fixes

• Unreviewed intros stay in play: Every candidate you'd been shown was kept out of later sets, including the ones you never got to. Now only the candidates you acted on are left out.

• Passive candidates stay in your lists: When a candidate went passive, they were removed from intros on every position, and your saves and messages went with them. That no longer happens.

Your recommended jobs were ranked almost entirely on skills and job title, so a junior engineer could open the page and find it full of senior and lead roles. Seniority now counts, and a fault that left some people with an empty page is fixed.

Improvements

• Roles at your level: Seniority carried one of the lightest weights in how recommended jobs were ranked, so it barely changed what you saw. Recommended jobs now only show roles within one level of yours, so someone at junior sees entry, junior and mid roles. If you've picked more than one level, you see exactly those. Roles with no level set still show, and if the filter would leave you with nothing, you get the wider list instead of an empty page.

Fixes

• Recommended jobs no longer come up empty: If part of your profile was missing, such as your secondary skills or the region behind your location, the page could fail and show "No relevant positions found" even when roles matched. One person had around 1,372 matching listings and saw none. A missing detail is now skipped and matching carries on with everything else.

Four smaller fixes went out this week, from the location filter in candidate search to what you see when a password is turned down.

For companies

• Cities now return correctly in the location filter: Typing "Berlin" into the Current location filter offered "Berlin Road" and "Berliner Strasse 12", never Berlin itself, so there was no way to pick the place you meant. The filter now offers cities and countries, in candidate search and in streams.

• No more broken candidate profile photos: Photos brought in from LinkedIn were saved as links that LinkedIn expires, so after a while they turned into broken images. cord now keeps its own copy of a photo when it comes in.

For everyone

• US locations now read properly: A location saved as just "United States" showed as "United States, undefined, USA", and Texas showed as "Texas, Texas, USA". They now read "USA" and "Texas, USA". Before the fix, 767 US profiles had "undefined" in their location.

• Password errors are now visible: When company signup or a password reset turned a password down, the form showed nothing, so it just looked broken. The reason now appears on the form. Every signup and reset also refuses passwords that have turned up in known data breaches, where before only two of the five places you can set a password checked.

The Declined tab was ordering itself by the wrong date, which made a request you had just lost very hard to find.

When a request you sent goes 14 days without an answer, cord closes it. It kept the date of your original message though, so it dropped into the Declined tab as if nothing had changed and sat wherever it had always sat. One person had four expire inside two days and could not find any of them. The expiry date now drives the order, so the ones that just lapsed are at the top.

Your experience goes stale the moment you stop editing it, and most people stop editing it. cord can now keep that section current from your LinkedIn profile, and there is a switch in Settings if you would rather it did not. Two fixes to your profile page went out alongside it.

Additional Features

• Choose whether cord refreshes your profile: There is a new card in Settings called "Keep my profile up to date". If your profile has a LinkedIn URL on it, cord uses that to refresh your experience from time to time. It only adds and updates, and never removes anything you have written yourself. It starts on, and the toggle turns it off.

Fixes

• Current roles no longer flagged as a date error: A role you are still in showed a red "Incorrect date period. Please edit and fix." where its length should have been. An open end date was read as the year -1, so every ongoing role looked like it had finished before it started. Current roles now show how long you have been there, on your experience and on your projects.

• Your location shows on your profile: If your city had been saved as plain text with no matching place record behind it, your profile showed no location at all. Saving your city now matches it to a real place, so it appears where it should.

Writing a detailed job description and hitting save returned "an error occurred" with nothing to act on, so people rewrote the post, tried again, and gave up. One company tried 21 times in under a minute. Descriptions past roughly 8,000 characters of formatted text were quietly hitting a limit in how the change was published behind the scenes. Length is no longer a limit, and saving works the same whether you make the edit or cord's team does.

A position posted on a Friday afternoon had no intros until Tuesday morning. Fixing that turned up four more paths where a position quietly ended up with no intros at all, or with intros for a role that was no longer live.

Improvements

• First intros on the day you post: Creating a position saved the role and then waited for the overnight run to fill it, so a role posted on a Friday afternoon had nothing to look at until Tuesday morning, around 66 hours later. Intros are now generated as soon as the position is created. The daily refresh covers every day of the week too, where Saturday and Sunday used to be skipped.

Fixes

• Resuming a position brings its intros back: Resuming a paused position said it worked and then did nothing. The step that should have rebuilt the intros failed on a malformed query and the error was swallowed, so the role came back live with an empty Intros page. Resuming now restores them.

• Joining a hiring team gets you your own intros: Joining a position from the hiring team is the quickest way onto a role, and it was the one route that created no intros at all. Joining now generates them, and leaving clears them.

• No intros for positions you have closed: Intros stayed on positions that had been archived, paused or deleted, and messaging anyone on that list failed. Intros now show only for positions that are still live, and archiving or pausing a role clears them.

• External roles no longer generate intros: A position that sends people to another system to apply cannot be actioned on cord, so building an intro list for it spent a search and a ranking pass on people nobody could message. Those are skipped now.

• Core skills weighted in the order you ranked them: The ranking read your core skills back to front, so the skill you listed first, the one that matters most, carried the least weight and the last one carried the most. The order now counts the way you set it. The weighting no longer depends on how many skills you list either, so a position with more than five core skills ranks like the rest.

Three things that were going wrong quietly. The largest was a filter panel building itself before anyone had opened it, which is what locked up Discover on load for some users.

For everyone

• Tabs that pick up the latest version: A tab left open kept running whichever version of cord it loaded with, until you navigated out of the app entirely. One customer sat on a four-day-old build and hit a bug that had been fixed and released days before. cord now checks for a new version every 15 minutes and whenever you come back to the tab. A tab you have not touched for an hour reloads itself quietly, an active one picks the new version up the next time you move between sections, and neither will reload over a position you are part-way through writing.

For job seekers

• Newsletter and events emails you can turn off: Switching "Newsletter and events" off in your email settings said "Saved", then showed the toggle back on the moment you reloaded, and the emails kept arriving. Nothing had been written. It affected everyone verified before February 2024, because that setting only got a record at verification and older accounts never had one. Turning it off now creates the record on the spot, and the emails stop straight away rather than up to an hour later.

For companies

• Company feeds that respond straight away: Opening a company feed under Discover looked ready, then locked up for a few seconds if you clicked a filter, scrolled, or switched job role, sometimes far enough for Chrome to offer "Page Unresponsive". The filter panel was building 2,065 checkboxes and around 10,500 page elements before you had opened it, 1,726 of them the 863-item skills list rendered twice, once for Core skills and once for All skills. Each panel now builds its options when you open it, so landing on a feed with the filters closed builds none of them instead of 2,062, and a saved feed still loads with its filters applied.

A position that had never produced a single intro said "Ready for more intros?", and pressing Generate escalated that to "You've actioned all your intros! Great job."

Both credited you with work you hadn't done, and neither told you the one thing worth knowing: whether anybody matches the role.

Improvements

• Why there are no intros: An empty list now says nothing matches this position yet, and names the two things that usually change that, work type and salary range, with a link straight to the position. Of 908 positions running an intro agent, 854 have live intros, 53 have never produced one and exactly one had genuinely been worked through. The old copy was wrong for 53 of those 54 empty cases.

• Generating the first set: A position's first list only appeared once the overnight job reached it, and that job doesn't run at weekends. 72 live positions were sitting in that state. Generate intros is now the main button on the empty state and runs there and then.

Fixes

• A page that loads: A single position pointing at a listing cord couldn't resolve took the whole Intros page down, on every reload, which left the account with nothing to work from. The page now renders and the problem position is logged instead.

• Long position names: A long position title spilled out of the selector and over the buttons beside it. The selector is capped and long titles truncate. The empty state was also rendering behind the top navigation with its illustration cut off, and now clears it.