Turn any job posting into a tailored CV from the tab you found it in
Reads the job description off whatever board you found it on, shows you the text before anything leaves the browser, and opens a tailored CV in a new tab — without the copy-paste round trip that stops most people tailoring by the fifth application.
Tailoring per application is obviously correct and almost nobody sustains it. The reason is friction, and the friction is mostly clerical: find the posting, select the description without the sidebar and the cookie banner, copy, switch tabs, paste, name the thing, start the run. Twelve seconds, forty times, at the end of a working day.
This removes that round trip. Open the popup on the posting you are reading, check the text it pulled, press send.
Deliberately thin
The extension does almost nothing, and that is the design rather than an unfinished state.
It runs Mozilla Readability — the library reader modes are built on — against the page in your active tab to pull out the job description, and shows you the result. You edit or trim it if it grabbed a footer. You press send. A background worker posts that text to the same endpoint the web app uses, and opens a SiviGen tab on the new application.
Everything that requires judgement happens on the server: what the title is, which company it is, what the requirements are. The extension never structures or interprets anything, which means it cannot drift from the web app’s behaviour, and a change to how postings are parsed does not need a new extension release.
No per-site selectors. Selector-based extensions work perfectly on the four boards their developer tested and return nothing — or a cookie banner — on the fifth. Readability is less precise on a heavily templated board and works on the small company careers page where the job you actually want is posted. Since you see and can edit the text before it sends, imprecision costs you a second rather than a bad run.
What it does with your browsing
Worth being specific, because “an extension that reads the page” deserves better than reassurance.
It reads the text of the active tab only, and only when you open the popup and it asks for it. Nothing is transmitted until you press send. The request carries the job description text you approved — not the URL, not the page title, not a record of anywhere else you have been. Closing the browser clears its per-tab state.
Authentication reuses the session cookie you already have from the web app. No second login, no API key, no new credential to leak.
The popup remembers what happened
A small thing that is disproportionately annoying when it is missing: the popup keeps a per-tab record of the send. Close it mid-run, open it again, and it shows the real state — sending, created with a link into the app, or needs-attention — rather than a fresh blank button that leaves you unsure whether you already sent it. Records clear when the tab navigates elsewhere or closes.
Where it lands you
In the tailoring pipeline, on a new application, with the audit already running. The extension is a faster front door, not a different product — and specifically not a “one-click apply” tool. It gets the posting in front of the machinery; reading the result is still on you, which is rather the point of a document you have to defend out loud.
The honest limitation
It is not on the Chrome Web Store yet. Today it installs as an unpacked extension from a built folder, which means enabling developer mode in Chrome. That is a genuine barrier, it is on the list, and implying a one-click install that does not exist would be a strange thing to do on a site about not overstating things.
Questions
- Does the extension read every page I visit?
- No. It reads the text of the page in the active tab, and only when you open the popup and it asks for it. Nothing is transmitted until you press send, and the send request contains the job description text you approved — not the URL, not the page title, not any record of other pages. Closing the browser clears its per-tab state entirely.
- Which job boards does it work on?
- Any page with a readable job description, because it does not use per-site selectors. It runs Mozilla Readability — the same article-extraction library reader modes use — against whatever page you are on. Selector-based extensions work beautifully on the three or four boards the developer tested and produce nothing on the fifth; this trades a little precision on the big boards for working everywhere, and you see and can trim the text before it sends.
- Is it on the Chrome Web Store?
- Not yet. It currently installs as an unpacked extension from a built folder, which means you need developer mode switched on in Chrome. That is a real limitation and worth saying plainly rather than implying a one-click install that does not exist.
- Do I have to log in again in the extension?
- No. It reuses the session cookie you already have from the web app, so if you are signed in to SiviGen in that browser, the extension is signed in too. There is no separate extension password and no API key to paste.
- What happens after I press send?
- The job text goes to the same endpoint the web app uses, and the tailoring runs server-side — the extension does not structure or interpret anything. A SiviGen tab opens on the new application, and the popup keeps a per-tab record of what happened, so closing and reopening it shows sending, created, or needs-attention rather than resetting to a blank button.