How it works

Updated 10 October 2026.

RoleInbox gets new jobs from company career pages, not LinkedIn or Indeed. It rules out the jobs you could not take. For each job, it tailors your resume using only facts you approved, and drafts answers from them. By default, anything they don’t cover comes to you, and nothing is sent until you approve it. Auto, which sends for you, is off until you switch it on.

Where the jobs come from, and where it can submit

It reads company career pages hosted on Greenhouse and Workday — the company’s own page, not a reseller’s copy of it. It does not ingest job aggregators, and it does not buy or scrape profile data about you. That is a decision, not a gap.

It submits to Greenhouse. A Workday role still appears in your feed with a link to the posting, because RoleInbox reads that board without writing to it. When a posting sits on a board it cannot fill, it says so and sends you to the employer’s own form instead of trying.

The three apply modes

You pick one of three rungs, and you can change it whenever your week changes. They differ in how much is drafted for you and who presses submit.

Self serve. The agent proposes nothing. It lays the form out and every box is yours to fill. Nothing is drafted for you at this rung.

AI assist is the default and the recommended rung. It pre-fills what it can from facts you approved, you read the result and press send. A question no approved fact covers is put to you, and your answer is kept for the next application that asks it.

Auto. The agent fills what it can and sends an application you opened, without a review step. At this rung a question no fact of yours covers is answered by the model rather than put to you, and every such answer is marked on the receipt as one you did not supply.

Auto is off by default and turns on only after you acknowledge, in as many words, that it sends answers you have not read. The server rejects the switch without that acknowledgement, so a client that skips the dialog cannot skip the acknowledgement.

Needs you, proposed, filled

Every prepared application sorts its answers into three groups, always in this order. Needs you comes first: questions the agent will not answer for you. Proposed comes next: answers it drafted but will not commit on its own. Filled comes last: answers it commits on its own. In Auto, that includes answers the model wrote where you had no fact.

Needs you is short and open on the screen. Proposed stays open too. Filled is the long group, collapsed to its count, because a list of forty correct answers is not what you came to read.

What it refuses to do

An answer that contradicts a limit you entered is never committed, at any rung. It can only be offered to you, and it must state the contradiction when it is. That rule lives in the database, not in a setting you can turn off.

A form known to be broken refuses, and so does a board it has no write adapter for. That stop is recorded against the particular form variant, never against a whole employer domain, so one bad form does not silently condemn every other form on the same host.

Two more checks run on every send, with nobody able to wave them through. The application carries a fingerprint of the form it was prepared against, and if the form changed underneath it the send refuses. The executor then reads every value back off the page after typing it, and refuses if a required question did not take the value. Both happen before any receipt is written.

Where a posting does not say, the answer is “unknown” and you are asked. Missing text is never converted into a pass or a fail.

How matching works

Your hard rules run first. A role that misses one is dropped before any paid model call is made about it, and before it reaches you at all. Nothing is spent, and nothing is shown, on a job you could not take.

Once your hard rules have cleared a role, an AI judge scores how well your approved facts fit it. That run happens when you open your dashboard, and the best matches are listed first. The score itself isn’t shown — it only decides the order, never whether you are eligible, which stays the hard filters’ job on every role.

Receipts

Every application sent in your name leaves a receipt: when it went, to which employer, and what was submitted. Receipts are added to, never rewritten. If you ask us to erase your account we export your receipts to you and redact the personal content, keeping only a stub so the record cannot be quietly changed after the fact.

Pricing · Chrome extension · About · Home