There is a moment every job seeker knows. You finish the fourteenth form of the week, you hit submit, the page goes white, and something appears that says Thank you for your interest.
Then nothing. For weeks.
And you cannot tell the difference between they read it and passed, they never opened it, and it never arrived at all. Three completely different situations, one identical experience.
I build a product that applies to jobs on your behalf. So I had to decide what my product is allowed to call sent. That decision turned out to be the entire product.
What everyone counts
Ask any application tool what proof it can show you, and you get some version of this list:
- the fields it filled in
- the answers it gave to the open questions
- the resume and cover letter it attached
- a confirmation it saw on screen
Read that list again. The first three are the tool reading back its own input. It typed a value into a box, then printed the value it typed. That proves the tool has a memory. It proves nothing at all about whether an employer received anything.
We know because we shipped exactly that, and it was confidently wrong.
Our agent once reported a form as fully completed. Seventeen fields written, seventeen confirmed. Zero of those values reached the employer. The fields it was reading were the ones it had just typed into, and the values the form actually submits sat empty underneath. The check could not fail while the typing worked. It was a mirror, not an instrument.
The fourth item, the on-screen confirmation, is better and still not enough. Plenty of forms show a thank-you page and then refuse the submission behind it. We have watched a hiring system return a clean success page and separately record a refusal, on the same request, for the same posting.
What we count instead
An application is sent when the company's own system says something back.
That is a specific, boring, mechanical thing. Every applicant tracking system in wide use sends an automated acknowledgement. It arrives from their domain, or the vendor's, within seconds to a couple of minutes. Something like this:
Thanks for applying to StackAI
Our applications route through an address we own, so that reply comes to us. We classify it, we match it to the application it belongs to, and only then does that application change state. Nothing we observe about our own session can produce that state. Not the click, not the screenshot, not the status code, not our own confidence.
This has a consequence I like more every time I explain it: we cannot fake our own success metric. The one field that matters can only be written by somebody else's mail server.
The three-verb ladder
Once you look at this category with that lens, everything sorts itself by one question: who performs the last verb?
- Some tools stop at you review. They draft, you approve, you submit. The last verb is yours, which means the work is still yours.
- Some tools stop at we submit. The last verb is theirs. Better, and it is still a claim about their own behaviour.
- We stop at they confirm. The last verb belongs to the employer.
That is not a feature comparison. It is a standard. If your application tool cannot show you something the employer produced, you are being shown a receipt the shop wrote for itself.
What it changes for you, concretely
When the only thing that counts is an outside confirmation, four things follow.
You know where you stand. Not "submitted" as a hopeful noun. Confirmed, or not yet confirmed, per application, with the timestamp of the reply.
Silence becomes information. These acknowledgements arrive fast. When one has not arrived in a few minutes, that is a signal about the submission, and it can be retried while it still matters, rather than discovered in three weeks when you wonder why nobody called.
You stop paying for nothing. A submission the company never confirmed does not count against your plan. That rule only exists because the confirmation exists. You cannot build that pricing on top of your own click.
Ghost postings stop being invisible. A listing that never acknowledges anything, from a company still posting it every three weeks, is telling you something. You just have to be counting the right thing to hear it.
The part I would tell my competitors
I am not writing this to say we are cleverer. Our first version had the same defect as everyone else's, and it took a production run where seventeen out of seventeen fields were empty to make us look properly.
The defect is seductive because the code is easier, the tests are green, and the dashboard is full. Reading your own input always succeeds. That is exactly why it tells you nothing.
If you build anything that hands work to somebody else's system, an application, a payment, a webhook, an upload, ask one question of every check you have written:
Would this read differently if the other side had failed?
If the answer is no, you do not have a check. You have a mirror.
I am Ava Bagherzadeh. I build AI Applyd, which scores, tailors and submits applications on the company's own hiring system across the twelve platforms most companies actually use. Interviews on your calendar, not rejection emails in your inbox.
Top comments (1)
This is the right standard for agentic work, and it is stricter than most dashboards want to admit. A self-observed click is only operational telemetry. The employer acknowledgement is counterparty evidence. That distinction matters because it changes the loss function from looked completed to can be reconciled later.