How to save a job posting before it disappears

Why did a save-anything app make the news this week?

On 2 October 2026, TechCrunch covered the launch of a new app from Laytr built on one simple idea: save anything you find online, not just articles. Recipes, screenshots, videos, PDFs — the pitch is a private archive that syncs across your Apple devices instead of yet another read-later list. That framing matters far beyond bookmarking. The reason people keep reinventing the save button is that the web keeps deleting things, and a saved link is a promise the internet refuses to keep. Job seekers feel this more sharply than almost anyone, because the single page your whole application depends on is also one of the most short-lived pages online.

Think about what a job posting actually is. It's a temporary marketing page, hosted by a company or a job board, kept up only as long as the role is open. The moment a hiring manager fills the seat, pauses the budget or restructures the team, that page goes. Sometimes it vanishes within hours of you spotting it. You're left with a URL in your browser history, a vague memory of the responsibilities, and no way to recover the exact wording that would have told you what to write on your CV. The archive-everything idea is the right instinct applied to the wrong file type.

So take the news story's logic and point it at your job search. The useful version of "save anything" for an applicant isn't a bookmark folder — it's a capture habit that grabs the words. Every posting you care about should end up as plain text you own, stored somewhere you control, with enough context around it that it still makes sense in three weeks. That sounds fussy until the first time a recruiter emails you about a role whose description you can no longer read. Then it stops feeling fussy and starts feeling like basic hygiene.

What happens when a job posting is deleted before you apply?

When a posting is deleted, you lose the only document that tells you how to tailor your application — and you can't get it back from the link. Deleted job pages typically redirect to a generic "this job is no longer available" screen or a 404, and job boards rarely keep a public copy of the original text. Your browser history preserves the address, not the content. If you saved a link instead of the words, you've effectively saved nothing useful, because every downstream task in your application depends on the wording: the keywords, the seniority signals, the must-haves versus nice-to-haves.

The damage shows up in stages. First you can't tailor your CV, so you fall back on a generic version and your bullets stop echoing the language the employer used. Next the cover letter goes vague — you end up writing about the company rather than about the role, which reads like you applied on autopilot. Then, if you do land a screening call, you walk in without the brief. You can't quote the responsibilities back to the interviewer, you can't rehearse against their stated requirements, and you can't tell whether the job they're describing on the phone has quietly drifted from the one you applied to.

There's a second, less obvious loss: evidence. A saved description is your record of what was promised — scope, reporting line, location policy, salary band if one was published. Postings get edited silently. Remote turns into hybrid, the salary range moves, the title drops a level. If you only ever saw the live page, you have no way to notice the change or to raise it politely in negotiation. Keeping the original text costs you ten seconds and occasionally saves you an uncomfortable surprise at offer stage.

Why can't AI tools just fetch the job posting URL?

Because the biggest job boards block automated fetching. LinkedIn and Indeed both put job pages behind bot detection, login walls and anti-scraping measures, so when you hand an AI assistant or a CV tool a link to one, it usually comes back with an error, a login page, or — worse — a plausible-sounding guess assembled from the URL and whatever it half-remembers about the company. That last failure mode is the dangerous one, because a confident hallucinated job description will happily send you off tailoring your CV to requirements nobody ever wrote down.

This is why every serious workflow tells you to paste the text. HRLens accepts a job description either as a pasted URL or as pasted text, and the honest guidance is the same one we'd give a friend: for LinkedIn and Indeed, paste the text, because those sites block fetching. Once the description is in as text, the free CV analysis can read it properly — scoring your CV out of 100 across experience, tech stack, impact and ownership, clarity and structure, and ATS compatibility, and listing the skills the posting asks for that your CV doesn't mention.

It also explains why your capture routine isn't busywork. Keyword matching and CV tailoring run on the posting's actual words, so the text you saved is the raw material for everything that follows. No text, no tailoring — just a generic CV and a hope. Treat the paste as the real save action and the URL as a nice-to-have breadcrumb. One more practical note: grab the text while you're logged in and looking at the full posting, not from a search-results snippet, which usually truncates the requirements section exactly where the useful keywords live.

How do you build a capture routine that takes ten seconds?

The routine is simple: select all, copy, paste into one running document, and add four lines of context — company, exact role title, date found, and the application deadline or "rolling" if none is stated. That's it. Do it the moment the posting catches your eye, before you've decided whether to apply, because the decision takes longer than the capture and the posting doesn't wait for you. Anything that adds steps will get skipped on a tired Tuesday evening, and a routine you skip is worse than no routine because it leaves you falsely confident that the role is "saved somewhere".

Where you put it matters less than the fact that it's text you own. A plain notes app, a single long document, a spreadsheet with one row per application, or a save-anything archive like the one in the news — all fine. What you want is searchable text, offline access and no dependency on the original page staying up. Add the posting's URL at the bottom for reference and a screenshot if the page has a published salary band or a design-heavy layout worth remembering. Avoid relying on a board's own "saved jobs" tab: it keeps a pointer to the listing, and when the listing dies, so does your save.

Build in one habit beyond the copy. After pasting, highlight or bold the five or six requirements that read like must-haves — the tools, the years, the certifications, the specific domain. You'll do this scan anyway when you write the application, and doing it at capture time means your future self opens the note already knowing where to aim. If you use a tracker, add a status column with four values: found, applied, screening, closed. Four is enough. Elaborate pipelines are how job-search organisation quietly becomes procrastination.

How do you use the saved description weeks later?

A saved description is a three-stage asset: it tailors your CV, drafts your cover letter, and briefs you for the interview — in that order, often weeks apart. Start by pasting the text into a CV analysis so you can see concretely which of the posting's requirements your CV doesn't currently evidence. Then rewrite your bullets in the employer's vocabulary, matching their terms rather than your internal job titles. Every HRLens analysis also generates ATS-friendly rewritten CVs in six templates that mirror the job's keywords, which saves you the fiddly work of rebuilding a document by hand for every single role.

The cover letter comes next, and the saved text keeps it specific. Pull the two or three responsibilities that genuinely match your track record, then write to those with numbers attached — team sizes, budgets, cycle times, percentages. If you'd rather start from a draft, HRLens writes cover letters too, with the CV-aware version living on the analysis results page. A letter built from the posting's own priorities reads as though you thought about the job, because you did. One written from memory of a page you skimmed a fortnight ago reads exactly like what it is.

Interview prep is where the habit pays off most and almost nobody does it. Two days before a screening call, reopen the saved description and build answers against the requirements you highlighted at capture time. If the posting asked for stakeholder management across three regions, have that story ready with names of functions and outcomes. Compare the saved original with whatever the recruiter now says the role involves; the gaps are your best questions. Candidates who can quote the job description back accurately come across as prepared, and they're usually just organised. Build the tailored CV from the same saved text and the whole application stays consistent.

Here's the contrarian bit: saving fewer postings, more thoroughly, beats hoarding a hundred links. A folder of fifty bookmarked jobs is a to-do list that generates guilt and no applications. Ten properly captured descriptions — text, context, highlighted must-haves — will produce more interviews than fifty saved links ever will, because each one is actually actionable. Volume without the source text is just volume.

Frequently asked questions