CareerForge is in closed beta. This is the whole picture: the finished parts, the unfinished ones, and the things we have decided against on purpose.
Closed beta: you need an invite code to make an account. Join the waitlist to get one.
Working now, for testers with an invite code.
Underway right now.
Decided on, designed, and waiting their turn.
Built means it works today, for testers who have a code. It does not mean you can sign up yet: the waitlist is how you will hear when that changes.
Everything you write is locked in your browser first, with a key made from your password that never leaves your device. What reaches our servers is a sealed envelope we have no way to open.
Ask where a setting lives, why the app did something, or how to run a search here, whether that is one CV per job or a handful you reuse and where a cover letter fits, and it answers from how CareerForge actually works, then offers a button that takes you to the exact control it just described and lights it up, the same way the AI review points at a line of your CV. It is free, it never sees anything from your vault, and it will not pretend to review your CV.
You get a recovery code the moment your account is made, because a password reset we could perform would mean we could have read your CV all along. Lose both and the vault stays shut for good, which is why we say so at every step that can lead there.
Write a CV, watch it lay itself out as you type, and download exactly what is on the screen. The preview and the download are the same file, so they cannot quietly drift apart.
Your details follow you between devices as sealed envelopes. Our servers store them, keep them in order and hand them back, and cannot read a word of them.
CareerForge is open to invited testers. An invite code is the only way in, and that is the point: it keeps the group small enough to fix what they find before anybody else meets it.
Every role, project, qualification, skill and well-written bullet is saved as its own sealed record, so your career follows you instead of living on whichever device you happened to type it into.
Mark a CV as a base and start new ones from it, so applying for two different sorts of role does not mean building each one from nothing. Copying a CV asks what should come across, and leaves the last job ad behind unless you say otherwise.
A way in from this site, sign-in screens worth the front door, and a pass you can see without going hunting for it.
Paste a job ad and have the right material pulled out of your vault and reworded to match, or just reviewed against it, with no API key of your own to arrange. Start a new CV that way too, and it arrives already cut down to what the ad asks for. It will also read your vault itself and say where the wording is weak, asking you for the number it is missing rather than inventing one. Every rewording waits for you to accept it. It reads only what you send it, answers, and keeps nothing.
A board for the whole search: every application, the stage it has reached, and the exact CV you sent frozen against it. Free, and locked like everything else. What it tells you about how your search is going, it tells only you.
What we are in the middle of.
A browser add-on that captures an advert from the page you found it on, instead of copying it across a tab at a time. It lands on your board as a card, cleaned up and ready to write against. The add-on sends nothing anywhere at all: the advert waits in your browser until the next time you open CareerForge.
What has to be true before CareerForge can open to everybody rather than to a list.
A pass that simply runs out, and a yearly plan that cancels in a click. No cheap trial that quietly turns into a monthly charge.
Score a CV against the screening software before a person ever reads it. No upload, no account, no email address. It is already written, and it opens with the app.
Everything on this site about encryption is a claim until somebody outside can read the code. We will publish that part so security researchers can check it does what we say.
Decided on and designed, waiting their turn. We intend to build every one of them, and a position on this list is only about when.
Passkeys, so the thing that unlocks your vault can be the device in your hand rather than one more thing to remember.
Written from your vault and the job ad, with every line tracing back to something you really did. Anything it cannot stand behind gets flagged rather than sent.
Small notes as the year happens, so the next CV is written from a record instead of from memory.
A roadmap that lists only what a company plans to build is half a roadmap. This is the other half: what we have been asked for, or expect to be asked for, and have turned down. They are commitments too, and we would rather you held us to them.
We could not do this if we wanted to. A server cannot lay out a document it cannot read, and it cannot read yours. Every page is drawn on your own device. That is why the rest of this page can describe how the product is built, and not just what our policy happens to say today.
Your password is what the key to your vault is made from, so there is nowhere for a sign-in button to fit: it would put another company between you and your own files. It would also put a company you may be applying away from in the middle of your job hunt.
This has been proposed, and it will be proposed again, because turning it off would make several hard things easy. A switch that turns the encryption off is a switch that is off for somebody, and once that is true the promise on our front page has quietly become a default instead.
None on this page, none in the app. People pay us once, and that is the only arrangement we know of that never develops an appetite for the thing we have gone to all this trouble not to be able to read.