Job Search Agent / August 2026 9.
Job searching stays chaotic while the email inbox is the database
A major step for the agent was giving the application process its own CRM ledger, connected to Gmail and Calendar watchers, Telegram notifications and explicit next actions.
Situation
With several applications moving in parallel, mental bookkeeping falls apart quickly: which role received a CV, where a reply arrived, which email belongs to an interview, and who needs a follow-up. When the inbox itself is the source of truth, a person repeatedly has to reconstruct the same state from subjects, threads and calendar events.
Approach
I organized the workflow around a CRM ledger. The Gmail watcher could read but did not receive unrestricted write access; the Calendar watcher could confirm interview appointments; and the Telegram-based Rikkancs surfaced only changes that genuinely mattered. Applications, email threads, statuses and actions became separate entities, so external events could no longer overwrite one another blindly.
Outcome
The system no longer only found jobs; it could follow the lifecycle of an application as well. A Calendar event could close an earlier scheduling action, while the CRM could identify the next meaningful step without requiring a manual scan of the inbox.