Four steps, and one of them is a refusal
-
Tell it about yourself, once
A conversation, not a form. It asks about the roles you have held and the things that actually happened in them, and it keeps two lists of what you can do: what is on your CV, and what is not.
-
Paste a posting
A link or the text. It extracts the requirements and separates the ones a screener can check for from the prose nobody can measure.
-
Read the verdict
Every named requirement lands in one of four places, and the verdict follows from them. If something required is unconfirmed, it stops and asks — nothing is generated until you answer.
-
Then, and only then, it writes
A CV that selects from what you have confirmed — never a rewrite, and never an addition. A cover letter, after asking which experiences should carry it. A short referral message you can send to someone inside.
Questions
Does it write the application for me?
It drafts a CV and a cover letter from material you have confirmed, and asks which of your experiences should carry the letter before writing a word of it. You review, edit, and send.
Does it apply on my behalf?
No. It never submits anything. Tools that auto-apply are one ATS policy change away from burning their users’ reputations, and the applicant is the one who has to explain it.
What if a posting wants something I have not done?
It tells you the odds are long and asks whether you have actually done it. If you say no, it will never appear in anything written for you. If you say yes, it becomes usable material from then on.
Is this only for software roles?
No. The gate works on anything a screener can look for as a token — a tool, a certification, a licence, a language with a level, a named method, a degree. That covers most white-collar postings.