Reading a listing
The full description, the skills we pulled out of it, where it came from, and a direct link to the employer's own posting.
Click any row to open it. On a wide screen the detail opens beside the list, so you keep your place. On a phone it opens as a full-screen sheet you can swipe away.
- The full description is fetched when you open the job, rather than the shortened version the list needed.
- Key skills are extracted from the whole posting and offered as one-click filters for the rest of your results.
- The board it came from is named on the row and in the panel. If several carried it, the row says how many.
- Similar jobs sit at the bottom, matched on what the role actually involves rather than on title text. When a posting is too new to have been indexed that way, the heading says so and falls back to matching by employer and title.
- Apply goes straight to the original posting on the board that carried it. We are never in the middle of an application.
- Rows you have opened are dimmed so you can see where you got to. That is stored in your browser as one-way hashes rather than as addresses, and never leaves the device.
Where it stops: About half of all postings arrive already truncated by the board that published them, some at a few hundred characters and some at a few thousand. We cannot recover text the source never sent, which is also why a match score against a short posting is treated with less confidence than one against a full description.
Related
- Why the same job appears onceA role carried by several boards collapses into one row marked with how many others had it, and the employer's own link wins where there is one.
- Why a job shows no match scoreBecause the posting names too few skills to judge. A confident 0% would be a much stronger claim than the truth, which is that we cannot tell.
- Whether a posting is still openWe spot-check listings against the board that carried them and remove the ones that answer as gone. Most rows have not been checked, and say nothing.
Did this answer your question?
Still stuck? Ask us directly, and mention this article so we know where to start.