Job application autofiller

Jobless

Jobless fills in job applications for you. You write your details out once and every form after that opens half done. Nothing leaves your computer and it never hits submit.

Year
2026
Stack
Chrome MV3, TypeScript
Status
Live on the Chrome Web Store

Why it exists

I was applying for jobs. Greenhouse, Lever, and whatever portal a company had set up on top. Same name, same links, same work history, typed out again every time. Fifteen minutes gone before I got to a real question.

So I went looking for an extension to speed it up. Most of them are too much. Features I did not ask for, a paywall halfway through, and enough setup that learning the tool becomes another task. Anyone applying for jobs is already worn out. That is a bad moment to hand someone a complicated product.

I built the simple one instead. It does one thing, you can set it up in five minutes, and there is a bit of fun in it, because the rest of the process has none.

That is where the ending came from. Accept an offer and Jobless fires you. It crosses out its own logo, shows you your real numbers, and you are done with it.

How it works

  1. 01

    Fill your details in once

    Eleven short sections, about five minutes. A meter shows what is left and points at whatever you skipped.

  2. 02

    Open an application and hit scan

    Nothing runs in the background. The extension only touches a page when you ask it to, and it attaches your resume as it goes.

  3. 03

    It fills what it knows

    Text boxes and real dropdowns, including the awkward ones that only respond to clicks. Greenhouse and Lever are handled properly, everything else goes through a general matcher.

  4. 04

    It flags what it does not

    Anything it is unsure about turns amber with a short reason. Filled fields turn green. You always know what it touched, and it never presses submit.

  5. 05

    It logs the application

    Company, role, date and the link, saved the moment a fill finishes. No spreadsheet to keep up with.

What's in it

01

It never reads your resume into your profile

Your resume gets attached to applications as a file, but the answers only ever come from what you typed yourself. Nothing gets scraped out of a PDF and filled in behind your back.

02

Markers that stay put

The green and amber badges follow their fields as you scroll and disappear when a popup closes. They sit in their own layer so they cannot break the page underneath.

03

Saved answers

Write an answer once and the next form that asks something similar offers it back in one click, before any AI gets involved. Your applications end up made of your own words.

04

Drafting with your own key

OpenAI, Anthropic, Gemini or DeepSeek. You pick the provider, the model is picked for you, and the only setting is tone. Drafts land in the box for you to edit.

05

A board that keeps itself updated

Applied, interviewing, offer, rejected. Drag things between columns, add notes, export to CSV. One reminder if something has been sitting for a week, and you can turn that off.

06

The firing ceremony

Take an offer and you get your honest totals, confetti, and a card you can post, made on your own machine and uploaded nowhere.

Rules it follows

A wrong answer is worse than a blank one

If it is not sure about a field it leaves it alone and tells you. That single rule is the reason the amber marker exists.

It stays away from demographics

Gender, race, veteran status and disability are only ever filled from answers you saved yourself, matched word for word, and they still get flagged for you to check.

You send it, not the extension

There is no job feed, no suggestions and no auto-apply. You pick the job, you read the form, you click submit. The market has enough automated applications in it already.

It has nowhere to send your data

Everything sits in your browser. No account, no server, no analytics. The only address it can reach is the AI provider you set up, and only when you click draft.

How it was built

I didn't write a line of the code. I made every other decision in it.

Claude wrote the code. I did the rest: what it should do, what it should not do, how each part behaves, how it looks. Then I went through what came back and fixed what was wrong, again and again, until it was the thing I had in my head.

The hardest part was never the filling. It was the writing. Questions like why do you want to work here, or which AI tools do you use, get answered the same way by every tool out there and you can spot it instantly. I kept redoing that piece until the drafts came from your actual resume and profile and sounded like you wrote them.

Product, design, every decision
Me
The code
Claude
Time
About 20 hours
Tokens
About 30M

Where it stands

It is on the Chrome Web Store at version 1.1.2. Manifest V3, TypeScript, no framework, and the Greenhouse and Lever matchers are tested against real saved application pages so an update cannot quietly break them.

Built with AI

JoblessGraphline