The robot that applies to jobs: how it really works
“A robot that applies to jobs for you” became a headline in 2026, and the article ends at the click. The work starts there: where the robot gets stuck, how it fills a Gupy form, and how anyone proves the employer received it.
Autofill is not an application
An extension fills what is on the screen. A robot decides before there is a screen: is this posting still open, is there an account here, is that session still valid, does this question have a truthful answer in your data. Not one of them has a field next to it.
Finding the posting is cheap: Gupy, the platform behind most large Brazilian employers, has a public search that answers with structured JSON, no login and no browser, checked on 13 August 2026. The wall arrives late, and that is what fools people: the posting is public when you are signed out, and the demand for an account only shows up at the moment of sending.
How a robot fills a Gupy form, field by field
The first layer is the registration: country, tax number, email, full name, mobile and date of birth. The last two fields are where automation dies in silence. The mobile has to go in as eleven Brazilian digits with no country code and no dashes; the date as day/month/year. Anything else and the Continue button does nothing, and the page never says why.
The second layer is that employer's questions, which arrive inside the HTML of their own careers page. A page that could not be read looks exactly like a posting that asks nothing, so the code refuses to send rather than submitting everything blank.
| Short text and long text | filled |
| Single choice and multiple choice | filled |
| Per-question attachment | goes to the browser |
| Conditional question | goes to the browser |
| Résumé on the account | checked first |
| Question with no truthful answer | goes to the browser |
The proof that the application went out
Once created, Gupy answers 201, created. That is a fact about a request, not about an application: the code goes back and reads the application out of your own list on Gupy, and if it is not there it is forbidden from saying it was sent. On an ordinary form the witness is the network, or a confirmation written on the page. The auto-apply page shows the screenshot and the log of every field.
How many a day makes sense, and why 10 not 1,000
In four days of a real search we read 360 postings across eleven job sites: 47 matched and nine became applications. On the accounts we run today the number of roles a day genuinely worth someone's name lands between one and eight. The ceiling is one a day on the free start and ten a day with credits, one credit an application, and it is a ceiling, never a target. A thousand a day means not reading: a hundred applications from one person in one morning shows up to a recruiter, and hiring software already treats that pattern as possible fraud.
What it never answers for you
- Tax number, phone and date of birth are never invented. With none on the profile, that is a clean stop naming the missing fact. Guessing would be fraud.
- Work authorization and visa get the conservative answer. It is the one field where a wrong answer is a lie rather than a typo.
- Your LinkedIn account is not touched. We only read the postings.
On Gupy there is one account per national tax number, checked on 21 August 2026: anyone who has applied through it already has the only account that number will have, and the dashboard asks for that login once. More in auto apply vs autofill, prices on Plans and pricing, the rest on the FAQ. Create an account and paste one job link.