How the project lives after applying: statuses, invitations, conversations and a manual dashboard

A good bot can’t end at the submit button.

After applying, the second half of the system begins: statuses, employer messages, invitations, manual cases, questionnaires, pending approvals.

So the project watches not only the sending but also the consequences. It tracks statuses and conversations, and the Telegram bot raises not the whole flow but only significant signals: messages from employers, invitations and cases where my participation is really needed. It doesn’t drag rejections to the centre of attention.

This was a matter of principle for me.

Where a person is still needed, the project has a separate working surface. I made a dashboard that gathers vacancies and scenarios requiring manual participation: questionnaires, handoff cases and pending approvals.

So manual work doesn’t disappear here, but it stops being chaotic. It no longer lives in random tabs, messages and forgotten links. It’s gathered in one place and becomes manageable.

That’s why the project long ago stopped being just an auto-apply machine.

It became a system that can live after applying: filter out noise, raise what matters, and separately gather everything that still needs a person.