Track your job applications with OpenClaw

You apply to a dozen roles in a good week, then mean to follow up on the ones that went quiet, lose track of which recruiter you already spoke to, and a month later you cannot remember whether that promising lead ever replied or just slipped through. Most of the work is follow up, the second email and the check in after an interview, and it is the first thing to drop when you are juggling several applications at once.

Your Operator.io agent can hold the whole pipeline together. You send it one prompt and it keeps a record of every application and where it stands, then comes to you with who is due a nudge and what is coming up, so the search keeps moving even on the weeks you are busy or discouraged.

How it works

You send the tracker prompt, and the agent sets up the pipeline and the reminders around it:

• It keeps a CSV in its workspace with one row per application: the company, the role, the link, the date you applied, the stage, the last time you heard anything, when you should follow up, and notes like the contact and what they said.
• When you tell it you applied somewhere, it adds a row, so logging is just mentioning it.
• When something moves, a recruiter reply, a screen scheduled, a rejection, it updates the stage and the dates on that row rather than starting a new one.
• A few times a week it messages you which applications have gone quiet long enough to follow up on and which interviews are coming up.

The follow up timing is yours to set, so it nudges you to check back on a silent application after the number of days you chose rather than guessing. You can change the cadence on the Automations page in your dashboard.

The prompt

This is the instruction the agent acts on:

Be my job application tracker. Create a spreadsheet in your workspace, a CSV
with columns for the company, the role, the link, the date I applied, the
stage, the date I last heard anything, when I should follow up, and notes
like the contact and what they said. When I tell you I applied somewhere, add
a row, and when something moves, like a recruiter reply or an interview
getting scheduled, update the stage and the dates rather than adding a new
row. Set up an automation that messages me a few times a week with which
applications are due a follow up because they have gone quiet, and which
interviews are coming up. Before you start, ask me which roles I am going
for, how long to wait before nudging on a silent application, and what day to
send the rundown.

The same prompt is saved in the prompts library, so you can send it to your agent without retyping a word.

Using it day to day

You log an application by telling the agent you applied, and you keep the row current the same way: forward it the gist of a recruiter email, tell it an interview got set for Thursday, note that a role got filled. A few times a week it comes back with the short list that matters, the applications that have gone cold and are due a check in, and the interviews on the horizon so you can prepare rather than be surprised. When a follow up is due, you can ask it to help draft the note right there, since it already has the context of who you spoke to and what was said.

Because the pipeline is a CSV the agent keeps, you can ask it the questions a spreadsheet makes you build a view for. How many applications are still open, which stage most of them are stuck at, what your response rate looks like, which roles you applied to but never heard back on. It answers from the file, and you can ask it to send you the whole thing whenever you want to see it laid out.

Follow up timing that works

The hardest part of a job search is knowing when silence means "still reviewing" and when it means "move on." Career coaches and recruiters converge on a few practical windows. Leon Consulting's guide to following up ties the first nudge to company size.

ApplyWave's 2026 follow up timeline suggests a first follow up between days 7 and 10, a second around day 14, and then mentally moving on after day 21 if you still hear nothing.

Set your agent's default follow up window to match the kind of roles you are targeting. If you are applying to early stage startups, 7 days is reasonable. If you are applying to Fortune 500 companies or government roles, 14 days before the first nudge avoids looking impatient. Tell the agent which category each application falls into when you add it, and it can use different timers for different rows.

Two follow ups is the usual ceiling. A first email a week or two after applying, a second a week after that if you hear nothing, and then you redirect your energy to new applications. Each message should add something, a relevant project, a certification, a brief note on why the role fits, rather than just asking if they received your application. When a posting names a review deadline, wait until a few days after that date before reaching out.

What happens on the employer's side

Most applications land in an applicant tracking system, software like Workday, Greenhouse, Lever, or iCIMS that companies use to collect, sort, and filter candidates before a human reads the pile. ATS tools keyword match resumes against the job description, track which stage each candidate is in, and generate the automated rejection emails you get at 2 AM. Understanding this helps set expectations: a week of silence after applying to a large company often means your application is still in a queue, not that it was rejected.

The tracker does not replace tailoring your resume or writing a strong cover letter. It handles the part that breaks down after the application goes in: remembering where each one stands, knowing when to follow up, and preparing for interviews that sneak up on you. When a recruiter does reply, having the notes column populated with who you spoke to and what they said saves you from reintroducing yourself in the next email.

Stages worth tracking explicitly: applied, acknowledged, phone screen, take home, onsite, final round, offer, rejected, withdrawn. You can use your own labels, but consistent stage names make the weekly rundown readable. When you get a rejection, mark it and move on. Keeping rejected rows in the file helps you calculate response rates later.

Why this beats a tracker app

The job search trackers keep their best features for paid tiers.

Simplify is mostly an autofill extension you run alongside a tracker rather than a tracker itself. They are each one more dashboard you have to open, and the reminders only help if you go looking for them.

This brings the pipeline to you instead. The reminders to follow up and the heads up on interviews arrive in the channel you already use, so a nudge is a reply rather than a login. The record is a plain CSV you own, which matters in a search you might run for months and want to keep afterward, and it runs on the OpenClaw you already pay for with no subscription that ends when you land the job.

Most applications vanish into an applicant tracking system on the employer's side and you never hear back, which is exactly why staying on top of follow ups is the part worth automating.

To set it up, open the prompts library and send the job application tracker to your agent. It asks which roles you are after and how long to wait before nudging, then it keeps the pipeline current and reminds you who to chase.