# Marking Ghost Jobs Instead of Boosting Them: A Reply-Time Model

Job boards reward posting, not replying, so dead listings stay visible. PeshaMitra instead measures how employers actually respond and shows it as a seal, which changes what the board optimises for.

By Cloud Technopix · Published 20 July 2026 · 11 min read

ON THIS PAGE

- The problem: listings that never answer

- The idea: measure behaviour, not claims

- How a seal model works

- Make the employer promise something

- A status trail instead of silence

- Engineering notes

- What we took from it

- Related reading and services

## The problem: listings that never answer

Anyone who has applied for jobs online knows the experience: you send an application, and nothing comes back. Sometimes the role was filled long ago. Sometimes it was never going to be filled, and the listing exists to collect résumés or to look busy. These are often called ghost jobs, and they waste the one thing applicants cannot get back, which is time and hope.

Job boards rarely fix this because their incentives point the other way. A board is usually rewarded for the number of listings and applications, not for whether anyone replies. In PeshaMitra we started from a different question: what would a board look like if the thing it optimised was whether employers actually respond?

## The idea: measure behaviour, not claims

A listing can claim to be active forever. Behaviour is harder to fake. If an employer opens applications, moves candidates through stages and replies within a reasonable time, that is evidence the role is live. If applications sit unopened for weeks, that is evidence it is not.

So PeshaMitra tracks how employers respond and shows the result to applicants, as a seal on the listing. Rather than boosting listings that pay for visibility, it labels the ones whose behaviour earns trust, and flags the ones that go quiet.

## How a seal model works

The model is a small state machine, driven by events and elapsed time.

- Verified active: the employer has responded to applicants within the window they promised

- Going quiet: applications are arriving but replies have slipped beyond that window

- No seal yet: the listing is new and there is not enough behaviour to judge

The important design choices are what counts as a reply, what the window is, and how a listing moves between states. A reply that is only an automatic acknowledgement should not count, or employers could keep a seal without engaging. Conversely, the window should be set by the employer when they post, so the promise is theirs and visible, and the seal reflects whether they kept it.

## Make the employer promise something

A reply-time promise changes the posting itself. When an employer states how quickly they will respond, the applicant has an expectation, and the board has a standard to measure against. It also helps honest employers: those who reply quickly now have a visible advantage over those who do not, which rewards good behaviour instead of volume.

## A status trail instead of silence

The seal is about the employer. For the applicant, the matching feature is a status trail: each application shows where it stands, such as submitted, viewed, in review or closed. Even when the answer is no, a clear no is better than silence, and the trail makes the absence of movement visible too.

## Engineering notes

### Time-based states need scheduled work

A listing moves to "going quiet" because time passed, not because someone clicked. That needs a scheduled process that evaluates listings and updates seals, designed to be safe to run repeatedly and to recover if a run is missed. Computing the state from stored events and timestamps, rather than only updating a flag, makes it easy to explain why a seal is what it is.

### Be fair about what you display

A seal affects an employer's reputation, so the rules must be consistent and visible. Show what counts as a reply, let employers see their own response data, and give them a way to correct a mistaken state. A system that cannot explain itself will be distrusted by both sides.

### Use AI to help, not to replace

PeshaMitra also helps applicants draft applications from their own profile, with the text grounded in what is on the profile and highlighted so they can see where it came from. The person reviews and sends it themselves; nothing is applied to on their behalf. That keeps the applicant accountable for what is sent in their name, and it matters for the same reason as the seals: trust.

## What we took from it

- Measure what you want to encourage. If you want replies, count replies.

- Ask for a promise, then report on whether it was kept.

- Replace silence with visible state.

- Keep rules simple enough to explain in one sentence.

The same thinking applies to any marketplace where one side can ignore the other. The HR and recruitment page describes more of what we have built in that space, and our web application development service covers two-sided platforms like this. To talk about your own, use the contact page.

## Related reading and services

- PeshaMitra case study

- HR and recruitment

- Web application development

## Have a project in mind?

Tell us what you are building. A senior engineer replies within one business day.
