Reverse Apply

Roadmap

What may be added next. Nothing here is promised or dated: it is a list of ideas, and your votes and messages decide what comes first.

New features

Only items marked Available are built

  • Check your own CV against a posting Available

    Paste a CV and a job posting and get the same report, follow-up chat and cover letter for that pair. You choose whether it is deleted when you are done or kept for 30 days.

    Makes the tool useful to anyone applying. It is for your own CV only: please do not upload anyone else's. Available now on the Check your CV page.

    0 people
  • A JSON API Planned

    Create a report, read it, ask a follow-up question and request a letter from your own code, with a token per client.

    Lets other tools and scripts use the match without the web page. Rate limits and spend caps apply per token.

    0 people
  • An MCP server Planned

    The same operations as tools an AI agent can call: check a match, read a report, ask about it, draft a letter.

    An agent that already works with your CV or a job board can use the match directly.

    0 people
  • Agent to agent Exploring

    An agent acting for a candidate and an agent acting for a hiring team exchange a posting, a CV and a match report in a machine-readable form, with a person approving what is shared.

    Screening is mostly two documents being compared. Letting software do the first pass, in the open, is the idea behind the whole site.

    0 people
  • A candidate pool Exploring

    Opt-in only: a candidate can keep their CV and report so that the owner and the owner's agents can find them for a role.

    Needs a ranked shortlist before any model scoring, and clear rules on consent, who can search and how long data is kept. A system that ranks candidates for recruitment counts as high-risk under the EU AI Act, so that is assessed before anything is built.

    0 people
  • Best candidates first Exploring

    Rank a pool of CVs against a posting cheaply (which requirements each CV has strong evidence for), then run the full report on the top few.

    Scoring every CV with a model costs too much. A shortlist stage makes a large pool affordable. Like the pool, it would need the EU AI Act assessment for recruitment systems first.

    0 people
  • A public accuracy page Idea

    Show how the reports score against hand-checked cases, and how each model compares on quality and cost.

    A verdict is a model's reading. Publishing how often it is right is the honest way to show it.

    0 people
  • Interview prep from the gaps Idea

    Turn the overall reading's gaps and the points the CV only suggests into a short list of questions to prepare or to ask.

    The report already says what is not on record. This turns it into something to do next.

    0 people
  • Compare two postings Idea

    Put two postings side by side against the same CV and see where they differ.

    Useful when choosing between roles.

    0 people
  • Reports in more languages Idea

    Read postings and write reports and letters in German, Italian and others.

    Many postings are not in English.

    0 people

Making it sturdier

Security, reliability and privacy work, not new features

  • A job queue Planned

    Reports, chat answers and letters run through a queue instead of threads inside the web process, so work survives a restart and a burst of requests waits its turn.

    Today a restart cuts off a report being written and parallel jobs compete inside one process. A queue also lets the site run on more than one server.

    0 people
  • Storage away from the web server Planned

    Reports and uploaded CVs live in a managed database outside the web server, with encrypted, tested backups and deletion that reaches them.

    The database sits on the same small server as the app. A separate store means a rebuilt server loses nothing and backups follow the same deletion rules as the data.

    0 people
  • Two-factor login for the admin Planned

    The administrator signs in with a password and a second factor.

    The admin can read every report and CV, so it deserves more than a password.

    0 people
  • Abuse protection at the edge Exploring

    A bot check and request limits in front of the app, so one source cannot use up the daily budget that is shared by everyone.

    The limits per visitor are kept in the app. A shared budget can still be drained by many sources, which blocks real visitors.

    0 people
  • Locked and signed builds Exploring

    Dependencies locked with hashes, base images pinned, builds reproducible, and automatic alerts for known vulnerabilities.

    Today new builds pick up the latest compatible versions. Locking them makes a build repeatable and a supply-chain surprise less likely.

    0 people

Tell Karsten Rieke what is missing

Read by a person. Stored with your email if you give one, until it is deleted on request: write to jdtocv2026@gmail.com. Please do not put a CV or other personal details in it. Privacy