DEV Community: Ava Bagherzadeh

Connect Gmail, Outlook and Indeed to your job search: what our integrations beta does

Ava Bagherzadeh — Thu, 15 Oct 2026 12:37:55 +0000

By Ava Bagherzadeh, founder of AI Applyd

You can now connect Gmail, Outlook and Indeed to AI Applyd. With your inbox connected, AI Applyd applies from your own email address, reads the codes and replies employers send there, and answers from that address. All three connections are a beta on the Hired Yesterday plan. We approve each account by hand, and Indeed is the least finished of the three.

Gmail and Outlook: the inbox you already check

Every AI Applyd account has a private relay address. Applications go out with it, and the job mail that comes back lands in your AI Applyd inbox. That still works and needs no setup.

With Gmail or Outlook connected, AI Applyd reads your job mail in that inbox the same way it reads the relay:

It picks up the sign-in codes that hiring systems send, so an application does not stall at a verification step.
It files each job email under the application it belongs to.
It sends your replies from your own address.
It can apply from your own address, so employers write back to the inbox you already use. You pick the address under "Apply with".

Gmail covers personal Gmail and Google Workspace. Outlook covers Outlook.com, Hotmail, Live and Microsoft 365. You connect each one with the provider's own sign-in screen, so AI Applyd never sees your password.

What it reads, and what it leaves alone

AI Applyd stores job mail only. It decides from the sender and the subject. A sign-in code counts only when it comes from a hiring sender, unless one of your applications is waiting for a code at that moment. If a message with a job-sounding subject turns out to be a promotion, spam or unrelated, AI Applyd deletes the copy it stored.

New job mail comes in on a regular check, and you can press Sync to check right away.

Indeed: the earliest part of the beta

Some employers put a "Sign in with Indeed" button on their application, and some jobs only take Indeed's own form. The Indeed connection is our first step toward both.

You connect Gmail or Outlook first, because Indeed signs you in by email. Then you pick the Indeed site your account lives on, such as indeed.com for the US. AI Applyd signs in with your connected email and reads Indeed's code from your inbox, so there is no password to share. Indeed may also ask you to verify a phone number.

Indeed's terms limit automated applying. The version dated 29 September 2026 says: "Use of any automation, scripting, or bots to automate the Indeed Apply process outside of Indeed's official vendors and tooling is prohibited." The Indeed card in the app says so before you connect. Indeed also runs a security check at sign-in that sometimes stops us, so we open Indeed slowly.

What "beta" means here

Integrations come with the Hired Yesterday plan. During the beta you press "Request beta access" on the Integrations page, and we approve each account by hand.
Google has not finished verifying our Gmail access. Until it does, Google shows a warning that the app is unverified when you connect, and an unverified app can serve at most 100 users. Google has asked for a security assessment before it approves access to read Gmail.
Microsoft also shows the app as unverified for now.
iCloud and Yahoo Mail are marked "Coming soon" on the page, and so are more job sites.

How to get access

Get on the Hired Yesterday plan.
Open Integrations in your dashboard and press "Request beta access".
Once we approve you, connect Gmail or Outlook and pick it under "Apply with".
If you want Indeed, connect it last.

On another plan you can still open the Integrations page, and it shows you the plan options.

In ChatGPT and Claude too

If you run your job search in the AI Applyd plugin for ChatGPT or Claude, version 1.9.0 knows about these connections. Ask "which accounts are connected?" and it tells you whether Gmail, Outlook and Indeed are linked. Follow-ups on applications that went quiet go out from your connected Gmail or Outlook after you approve the text. Setup is at aiapplyd.com/mcps.

How this was made: I wrote this from our product notes and the Integrations page, with an AI assistant helping on drafts. The Indeed quote is from Indeed's own terms.

AI Applyd 1.9.0: your job search assistant can now read recruiter replies, follow up and save searches inside ChatGPT and Claude

Ava Bagherzadeh — Thu, 15 Oct 2026 12:37:48 +0000

By Ava Bagherzadeh, founder of AI Applyd

AI Applyd is a plugin that runs your job search inside ChatGPT and Claude. It finds jobs that fit your resume and applies on the employer's own hiring system. With version 1.9.0 it also reads the replies recruiters send you and drafts your answers. It follows up on applications that went quiet and saves your searches, all from the chat you already have open.

What is new in 1.9.0

Version 1.9.0 went live on 14 October 2026. The plugin now has 23 tools, up from 17. You never call a tool by name. You ask in plain words and the assistant picks one.

Recruiter replies, inside the chat

Ask "did any recruiter reply?" and the assistant reads the emails employers sent about your applications. Ask it to draft an answer and it shows you the exact text. The reply goes out only after you approve that text.

Follow-ups on applications that went quiet

Ask "which applications went quiet?" and it finds them. It drafts a follow-up for each one and sends it from your connected Gmail or Outlook once you approve it.

Saved searches with email alerts

Tell it what you want, for example "remote product design roles in Europe", and save that as a named search. You get an email when new matches come in.

Auto Apply from the chat

You can turn Auto Apply on or off from the chat. You also choose whether each application goes out on its own or waits for your review.

The answers employer forms ask for

Save the answers that application forms keep asking for, once. The EEO questions are optional, and each one accepts "prefer not to say".

Your resume, pasted or attached

Paste your resume into the chat, or attach the file in ChatGPT, and the resume and cover letter tools work from it. If you share nothing, they use the resume already on your account.

Smaller changes

Application details now show the tailored resume, cover letter and screening answers that the application used.
The account tool shows whether Gmail, Outlook and Indeed are connected.
Every result ends with one suggested next step.

Why replies and follow-ups came next

Sending the application starts the next part of a job search, and that part runs on email. Hiring systems send receipts, sign-in codes and interview invites. Recruiters write back with questions. Until 1.9.0 you had to leave the chat to read any of it.

Now the whole loop stays in one conversation. You find a job, apply, see whether the employer confirmed it, read the reply and answer it. AI Applyd still counts an application as sent only when the employer's own hiring system confirms it.

Anything that writes to an employer waits for you. Each tool is labeled as read-only or as an action, so the assistant can tell a lookup from a send. A reply or a follow-up shows you its exact text first.

How to add the plugin

You add it once with one address: https://mcp.aiapplyd.com/mcp. There is no API key. The first time it acts for you, a browser window opens and you sign in to AI Applyd with Google or an email link.

In ChatGPT you need a paid plan (Plus, Pro, Business, Enterprise or Edu):

Open Settings, then Apps and Connectors.
Turn on Developer mode, then choose Create.
Name it AI Applyd, paste the address and choose OAuth.
In a chat, pick AI Applyd from the tools menu.

In Claude it works on any plan, on the web or in the desktop app:

Open Settings, then Connectors.
Choose Add custom connector.
Name it AI Applyd, paste the address and choose Add.
Choose Connect and sign in.

The same address works in Cursor, Codex and Claude Code. Steps for every app are at aiapplyd.com/mcps. If your app can only launch a command, run npx aiapplyd-mcp.

What to know before you start

A free account covers matching, resume and cover letter work and interview prep. Sending applications needs an application allowance, which comes with a paid plan.
Follow-ups go out from a connected Gmail or Outlook. Those connections are a beta on the Hired Yesterday plan, and we open them one account at a time.
The plugin is still in review for the ChatGPT app directory and the Claude connector directory. Until then, you add it by address as shown above.
Applications go out on the 34 hiring systems AI Applyd supports, including Greenhouse, Lever, Ashby, Workable, Workday and iCIMS.

The full changelog

Every version, newest first, is at aiapplyd.com/mcps/changelog. The release notes for 1.9.0 are on GitHub, and version 1.9.0 is also on npm and in the official MCP Registry.

How this was made: I wrote this from our public changelog and setup page, with an AI assistant helping on drafts. Every feature named here is in the 1.9.0 release notes.

You can now apply to jobs from inside ChatGPT and Claude: here is how it works

Ava Bagherzadeh — Thu, 15 Oct 2026 11:56:14 +0000

By Ava Bagherzadeh, founder of AI Applyd

ChatGPT and Claude can find jobs that fit you and apply to them once you add a plugin for it. I built one, AI Applyd, so this walkthrough uses it. You add it with one address, sign in once, and then ask in the chat. It applies on the employer's own hiring system, and it counts an application as sent only when the employer's system confirms it.

What ChatGPT and Claude can't do on their own

On its own, a chat assistant has no list of open jobs matched to your resume. In a 2 October r/jobhunting thread asking whether Claude or ChatGPT is better for automating applications, the top reply said "Neither Claude nor ChatGPT will search for jobs matching your profile on their own".

Browser agents can type into a form, but logins and verification codes get in the way. On r/ClaudeCode on 5 October, someone driving a browser from Claude Code wrote that the browser opened without any of their logins, and that Claude said it "cannot copy and paste one time code into the application" and "cannot create username and password".

Sources: r/jobhunting, r/ClaudeCode

What a plugin changes

A plugin hands the assistant tools that run on another service. The assistant decides when to call them, and the service does the work. ChatGPT lists them under Apps and Connectors and Claude calls them connectors. Both use the same open standard underneath, MCP (Model Context Protocol).

Adding AI Applyd to ChatGPT

You need a paid ChatGPT plan: Plus, Pro, Business, Enterprise or Edu.

Open Settings, then Apps and Connectors.
Turn on Developer mode, then choose Create.
Name it AI Applyd and paste the address https://mcp.aiapplyd.com/mcp
Choose OAuth, then save.
In any chat, pick AI Applyd from the tools menu and ask for your next job.

Adding it to Claude

This works on any Claude plan, on the web or in the desktop app.

Open Settings, then Connectors.
Choose Add custom connector.
Name it AI Applyd, paste https://mcp.aiapplyd.com/mcp and choose Add.
Choose Connect and sign in.

There is no API key to paste. The first time the plugin acts for you, a browser window opens, you sign in to AI Applyd with Google or an email link, and you approve a consent screen that names the app asking. The same address works in Cursor, Codex and Claude Code; steps for those are at aiapplyd.com/mcps.

What you can ask

The plugin has 23 tools. You never call them by name; you ask in plain words and the assistant picks the tool. Some requests that work:

"Show me jobs that fit my resume, best fit first."
"Here is my resume" (pasted, or attached as a file in ChatGPT), "score it against this posting and tell me what is missing."
"Apply to the second one, but let me review it first."
"Which of my applications did the employer confirm?"
"Did any recruiter reply? Draft an answer." It shows you the exact text and sends only after you say yes.
"Follow up on the ones that went quiet." The follow-up goes from your connected Gmail or Outlook once you approve it.
"Prep me for the interview at this company."

When it applies, it fills the form on the employer's own hiring system, with a resume and cover letter written for that job. It covers 34 hiring systems, including Greenhouse, Lever, Ashby, Workable, Workday and iCIMS.

Limits worth knowing

A free AI Applyd account covers matching, resume rewrites, cover letters and interview prep. Sending applications needs an application allowance, which comes with a paid plan.
The plugin is still in review for the ChatGPT app directory and the Claude connector directory. Until they approve it, you add it by address as shown above.
In ChatGPT it needs Developer mode and a paid ChatGPT plan.
Applications go out only on the 34 hiring systems it supports.

Privacy and control

Every tool runs on your own AI Applyd account. The sign-in uses OAuth, so the assistant never sees your password, and the consent screen names the app you are connecting.

Each tool is labeled as read-only or as an action, so the assistant can tell a lookup from a send. Replies and follow-ups to employers show you the exact text and go out only after you approve. Applications can go out on their own or wait for your review, and you pick which in the Auto Apply setting.

To disconnect, remove AI Applyd from the same Apps or Connectors screen where you added it.

How this was made: I wrote this from our setup page, our product rules and the public threads linked above, with an AI assistant helping on drafts and research.

How to tell if an auto-applied job application actually reached the employer

Ava Bagherzadeh — Thu, 15 Oct 2026 11:55:14 +0000

By Ava Bagherzadeh, founder of AI Applyd

If an auto-apply tool says it applied for you, the proof has to come from the employer. That means the confirmation page the hiring system shows after a successful submit, a receipt email from that system, or the application listed in the employer's candidate portal. A "submitted" label inside the tool only tells you the tool clicked a button.

Why "submitted" in a tool is not a receipt

An auto-apply tool keeps a record of its own actions. When it marks a job "applied", it means it pressed submit. What happened next on the employer's side is a separate event. The hiring system can still refuse the form, say because a required field is empty or the session timed out, and the tool may log the click as a success anyway.

A corporate recruiter wrote about this on r/recruitinghell on 14 October 2026, in a post called "DO NOT use auto apply services/sites". According to the post, bulk tools "fail to actually complete the application", send a stock resume in place of the one the candidate supplied, and apply with "throw away email domains that are often either invalid, or don't actually make their way to you". If the employer writes to an inbox you never open, you never find out whether it sent a rejection or an interview invite.

What a real confirmation looks like

You need one of these three, and each one comes from the employer's system.

The confirmation page

Most hiring systems show one right after a submit goes through. You see it when you apply by hand. A tool sees it as well, and it can save a copy.

A receipt email

The University of Washington hires through Workday. Its applicant page says you "should receive an email from" its Workday sender "confirming we received your application", and it asks you to add uw@myworkday.com to your safe senders so the email stays out of spam.

The employer's candidate portal

On a Workday site you sign in, open Candidate Home and look under My Applications. The City of Tucson lists every application there with a status, where "In Progress" means "Application received from the job posting and is under review". Greenhouse has a candidate account too, called MyGreenhouse, though its FAQ notes: "You'll only see application updates and tasks if the hiring company chooses to share them."

What to check, in order

Find out which email address the tool applied with. Every receipt and every reply goes there, and on Greenhouse you cannot change it later. The MyGreenhouse FAQ says: "Greenhouse can't change the email on an application after it's submitted." If the tool used an address of its own, ask where that mail goes and how you read it.
Search that inbox for the company name and for the hiring system, for example "Workday" or "Greenhouse". Look in spam and promotions as well.
For a Workday job, sign in to that employer's Workday site and open Candidate Home. Each employer has its own site, so you need the login for that one. If the tool made the account, ask the tool for the login.
Ask the tool for its evidence: a screenshot of the confirmation page, an application ID from the employer's system, or the receipt email. A green "applied" badge with nothing behind it is not evidence.
Still nothing? Ask the company. The MyGreenhouse FAQ says the same for status questions: "contact the company you applied to directly."

How AI Applyd handles this

I founded AI Applyd, so weigh this section with that in mind.

AI Applyd applies on the employer's own hiring system. It works on 34 of them, Greenhouse, Lever, Ashby, Workable, Workday and iCIMS among them, and it tailors the resume and cover letter to each job. An application counts as sent only after the employer's system confirms it. The app states the rule on the Applications screen: a verified landing is "the confirmation their server returned, the application ID their ATS minted, or their system reporting it already on file. Our submit click alone never earns the word."

We also apply with an AI Applyd email address, which is the setup the recruiter complained about. You can read that inbox, though. Employer emails about your applications show up in the app, and you can reply from there.

If you already spend your day in ChatGPT or Claude, you can run these checks from the chat. Add the AI Applyd plugin and ask "which of my applications did the employer confirm?" or "did any employer reply this week?". Setup steps for both are at aiapplyd.com/mcps.

How this was made: I wrote this from our own product rules and the public sources linked above, with an AI assistant helping on drafts and research. Every outside quote links to its source.

How we built a ChatGPT and Claude plugin that applies to jobs

Ava Bagherzadeh — Thu, 15 Oct 2026 09:36:18 +0000

AI Applyd launched on Product Hunt today, our third launch there: https://www.producthunt.com/products/ai-applyd/launches/ai-applyd-4

The newest part is a plugin for ChatGPT and Claude. You ask the assistant for jobs that fit you, and it applies on the employer's own hiring system with a resume and cover letter tailored to each one. It covers 34 hiring systems, Greenhouse, Lever, Ashby, Workable, Workday and iCIMS among them, and an application counts as sent only when the employer's system confirms receipt.

Under the hood the plugin is an MCP server. MCP (Model Context Protocol) is the open standard that lets an assistant call tools on another service. Version 1.9.0 went live yesterday with 23 tools, and the same server works in Cursor, Codex and Claude Code.

One hosted server, many clients

The server runs at https://mcp.aiapplyd.com/mcp over Streamable HTTP, with no API key. In ChatGPT you add it under Settings, Apps and Connectors, with Developer mode on. In Claude it goes in Settings, Connectors, Add custom connector. People who live in a terminal can use the npm bridge, npx aiapplyd-mcp.

Sign-in is OAuth, and the first call fails on purpose

Sign-in uses OAuth 2.1 with PKCE and dynamic client registration. The first tool call returns 401 with protected-resource metadata in the WWW-Authenticate header. The client reads it and opens a browser on our sign-in page. The user signs in with Google or a magic link and approves a consent screen that names the client asking.

The bug that cost us the most time lived here. During the OpenAI tool scan, ChatGPT reported "OAuth flow canceled". Our analytics showed that our server had issued the code, but the browser tab never left the consent page.

Our own Content Security Policy caused it. The consent form POST answered with a 302 to ChatGPT's callback, which was on our form-action allowlist. That callback redirects again, to platform.openai.com. Chrome checks form-action against every hop of a form's redirect chain, so it blocked the second hop and showed no error. Codex worked the whole time, because its callback on 127.0.0.1 is the final hop.

The fix was to stop redirecting from the form. The Connect button now returns a 200 page that moves on with a meta refresh, and the browser treats that as a fresh navigation. If you build an OAuth consent page for MCP clients, test it with a client whose callback redirects again.

Resumes attached in ChatGPT

In 1.9.0 the resume tools take two new inputs. resume_text is a resume pasted into the chat. resume_file is a file the user attached in ChatGPT, which ChatGPT hands to the tool when the parameter is declared in the tool's _meta under openai/fileParams. With neither, the tools use the resume saved on the account.

Scoring, rewriting and translating a resume all accept both. Before 1.9.0 these tools read only the saved resume, and translation also needed a document from our resume builder.

Recruiter replies in the chat

1.9.0 also added the inbox. aiapplyd_get_inbox reads the emails employers sent to the user's AI Applyd address, and aiapplyd_reply_to_email sends the user's reply. The skill shows the exact text first and sends only after the user says yes. Follow-ups work the same way and go out from a connected Gmail or Outlook. Sign-up codes and other account mail are marked, so they never count as an employer reply.

What the OpenAI review taught us

The plugin is still in review for the ChatGPT directory, and the Claude connector directory has it in review too. Until they approve it, people add it by address.

Give the reviewer an account that works with no setup. On our first review run, users who had never opened our website hit a data-consent error on every AI tool, which is a dead end inside ChatGPT. We removed that gate, and signing up now accepts the terms.

Annotate every tool. Each of ours declares readOnlyHint and destructiveHint, so a client can tell a read from an action that sends an application to an employer.

Try it

Setup steps for ChatGPT, Claude, Cursor, Codex and Claude Code are at https://aiapplyd.com/mcps. The bridge and the skills are MIT licensed at https://github.com/aiapplyd/aiapplyd-mcp.

I made our product demo in HTML with HyperFrames, no video editor

Ava Bagherzadeh — Mon, 28 Sep 2026 11:29:47 +0000

I build AI Applyd, a tool that applies to jobs for you on the company's own hiring system. Before our Product Hunt launch on 6 October I needed a demo video, and I made it without a video editor. The whole thing is HTML, rendered to video with HyperFrames.

Why HTML instead of a screen recording

Recording a real web app is messier than it looks. Pages load in stages, spinners show up, the test data is never quite right, and every small UI change means recording again. I wanted the demo to look exactly like the product without fighting any of that.

HyperFrames takes an HTML page per scene and renders it to frames. That meant the demo could use the same fonts, colors and layout tokens as our site, because they were literally the site's files.

How the project was set up

One HTML file per scene. 12 scenes, about 90 seconds in total.
Real screens, seeded data. I captured the screens from our app running locally on a test account, so every card and label is something the product actually renders.
Brand tokens copied by hand. The generator guessed our colors from the light theme, but the live site is dark, so I repainted the palette myself: a near-black ground, off-white text and one orange accent.
Captions typed as HTML. Geist for the main line and Geist Pixel for the accent word, which is why the captions look like the site and not like a video template.

What was easy

Timing. A scene's length is a number in the file, so tightening the pacing is a one-line change and a re-render. Reordering scenes is moving a block. Nothing needs a timeline scrubber.

What was slow

The audio. Cutting scene changes to the beat of a music track means lining up timestamps by ear, and it took several rounds before the cuts stopped feeling mechanical. The voiceover was the other hard part. The first voices I tried read the script like an audiobook narrator, which flattened a product demo that needed some energy.

Would I do it again

Yes, for anything where the product UI is the star. If a scene is mostly your own interface, building it in the same HTML and CSS as the product is faster than recording it and cleaning it up. For live action or anything with people in it, a normal editor is still the right tool.

If you want to see what the product does, it's at aiapplyd.com. And if you have made a launch video in code, I'd like to know how you handled the music.

Four things that cost us money while automating job applications

Ava Bagherzadeh — Tue, 22 Sep 2026 14:52:46 +0000

Filling a job application is a browser-automation problem that looks solved and is not.

We run an MCP server that applies to jobs end to end on the employer's own hiring system. Fifteen applicant tracking systems: Greenhouse, Lever, Ashby, Workday, iCIMS, Personio, Teamtailor, SmartRecruiters, Recruitee, Breezy, Workable, Rippling, BambooHR, JazzHR and softgarden. Here are four things that cost us real money to learn.

1. Scoring on your own input is not evidence

The first version reported success when the upload call returned staged: true and the field read back files: 1. Both were true. Zero bytes reached the server.

The automation library took a different code path on a remote browser and sent nothing, while every counter we owned said it had worked. We were reading our own writes back and calling it proof.

The rule we run on now: never score on a read-back of your own input. Only score on something the other side produced. A request on the wire. A confirmation page. An email from the employer. submitted: true is a variable you set. It is not a receipt.

This generalises well past job forms. If your integration test asserts on state your own code wrote, it asserts nothing.

2. An empty result is not a zero until you prove you were watching

We spent 23 debugging sessions reading logs that showed nothing wrong. Nothing was wrong in the logs. The instrument started 18 seconds after the event it was supposed to measure, so a working fix and a total failure produced identical output: silence.

Before you believe any empty list, prove three things:

The instrument was armed at all, at the right scope.
It was armed before the event and still armed after.
The mechanism works when a human does it. Then diff the human run against yours. The divergence is the bug.

If you cannot prove all three, the correct word is not "absent". It is unobserved. Write that down instead, and go fix the instrument before you touch the subject.

We found the upload bug in minutes once we stopped reading logs and opened the page in a real browser.

3. HTTP 200 is not success, and a 200 from an SPA is not even a page

Two separate versions of this one bit us.

A provider returning an overloaded-service message inside the body of a 200 made our SDK classify it as a schema validation failure. We spent a day looking for drift in a parser that was fine. Match the error text, not the status code.

Separately, while surveying sites this week, several returned 200 for /submit, /add-tool, /new and four other paths that do not exist. They are single-page apps with a catch-all route. A 200 there proves the server answered. It says nothing about whether the page exists. Read the body.

4. A list that is still rendering is not a list

Dropdowns were harvesting exactly one option. The code waited for a loading placeholder to disappear, which it did, correctly, while the list kept painting rows behind it.

Waiting for the absence of a spinner is not the same as waiting for the presence of the data. We now settle on count stability: read the option count, wait, read it again, and only proceed when it stops changing. One field went from 1 option to 7.

The part that has no clever fix

The distinction we built the product around is that an application is not "sent" because we clicked submit. It is sent when the employer's system says it received it. Those are different events and only one of them is checkable.

Most of the engineering above exists to keep that honest, because the tempting version, where your own click counts as the outcome, is much easier to build and quietly useless to the person waiting for an interview.

The MCP server is public and works in Claude, ChatGPT and Cursor over streamable HTTP at https://mcp.aiapplyd.com/mcp. Source mirror: github.com/aiapplyd/aiapplyd-mcp. The product is AI Applyd.

Happy to answer anything about the ATS-specific parts. Workday alone is worth its own post.

An HTTP 200 is not a delivered job application

Ava Bagherzadeh — Mon, 14 Sep 2026 07:40:23 +0000

We are launching on Peerlist this week. If this is your kind of problem, come and tell us where it still falls short: AI Applyd on Peerlist Launchpad

Every auto-apply tool I have taken apart marks an application "sent" at the same moment: the instant it dispatches the click. That is a read-back of our own input, and it is the weakest signal in the whole pipeline.

The four signals that look like proof and are not

I shipped all four of these at some point and had to take them back out.

1. Our own click. The submit button was pressed. Nothing about that tells you a request left the browser, or that the server accepted it, or that a row was written on the other side.

2. HTTP 200. A 200 means a server answered. Applicant tracking systems return 200 for validation errors, for a re-rendered form with a red field, and for a page that says "we could not process your application". A status code is not a receipt.

3. Our own database row. We wrote status = submitted. We wrote it. Scoring on a value you set yourself is circular, and it is the single easiest way to build a dashboard that is confidently wrong.

4. A page that looks like a thank-you. Heuristics on the confirmation screen are the most seductive of the four, because they are usually right. Usually is the problem. A cached page, a redirect to a generic careers landing page, or an ATS that renders the same shell for success and failure all pass a text match.

What we count instead

One thing: the employer's own system says the application arrived, and we can link to that evidence. A confirmation email from their ATS tied to that application. A post-submit screen we retained and verified as an employer confirmation. Nothing else moves a row to sent.

When we cannot get that, the application does not silently become a success. It says so, in plain words, and it names what it is waiting on.

What that bought

Refusing the weak signals forced the agent to get further on its own, because every shortcut we removed was a shortcut around a real wall.

It opens the employer's real hiring form on Greenhouse, Lever, Ashby, Workday, iCIMS, Personio, Teamtailor, SmartRecruiters, Recruitee, Breezy, Workable and Rippling.
It rewrites the resume for that specific posting and writes the cover letter in the candidate's voice.
It gets through account walls by itself: it signs up, verifies the email and resets a password using a private inbox we create for the user. The user is never asked for a code or a login.
It solves the captcha inside the vendor's own frame rather than giving up when the challenge sits in an iframe.
It stops pressing once the employer says yes.

If you want to poke at it

There is a remote MCP server, so the same tools run inside Claude, Cursor or ChatGPT. Streamable HTTP on Cloudflare Workers with OAuth 2.1 and dynamic client registration, so there is nothing to install and no API key to paste.

https://mcp.aiapplyd.com/mcp

The product itself is at aiapplyd.com.

I build AI Applyd - https://aiapplyd.com?ref=devto - auto-apply that proves your application arrived.

The question I keep asking, and the one that keeps changing this codebase: what would make you trust that an application actually landed?

Come and kick the tyres on the launch page, it is live all week and every comment there reaches me: peerlist.io/firstexhotic/project/ai-applyd-mcp

Both sides of the job interview are running models now, and neither one says so

Ava Bagherzadeh — Sat, 12 Sep 2026 12:39:48 +0000

A recruiter sends you a link. You record four answers into a webcam with nobody on the other end. A model scores the transcript. A human skims the top of the pile.

Meanwhile, on your side of the screen, there is a second window open with the job description pasted into it.

Neither party mentions any of this. Both parties suspect the other.

The part that gets called cheating depends entirely on who went first

The usual framing is that candidates started it. It is worth checking the order.

Automated screening was in the pipeline long before consumer language models were. Keyword filters, then scoring, then recorded-interview scoring. By the time a candidate could open a chat window and ask for help with a cover letter, the other end of the process had already been machine-read for years.

That does not make anything permissible. It does mean the moral panic is pointed in a strange direction.

And it is not a wash, because one side had to consent

Here is the asymmetry that actually matters, and it is structural rather than a matter of opinion.

If a candidate uses a model to prepare, that is their own time and their own business. If an employer uses one to score, it is deciding an outcome about a person, often without telling them, and the person cannot see the rubric, cannot appeal it, and frequently cannot even confirm it happened.

Same technology. Very different position in the power arrangement.

The measured cost is not accuracy, it is who stays in the room

This is where it stops being a vibes argument.

In CESifo Working Paper 12573, researchers randomised over 3,000 real job applicants into asynchronous audio interviews, asynchronous video interviews, live online interviews, or a control group.

Asynchronous interviews caused an over 50% decrease in application continuation. The paper reports the decline happened "including among the most qualified applicants", and that it was largest for women.

Read that as a systems person rather than as a candidate. A stage that removes more than half your input, non-uniformly, and correlated with something other than the quality you are selecting for, is not a filter. It is a sampling bug. Anywhere else in engineering you would treat that as a defect in the pipeline rather than a property of the population.

So what does a candidate actually do about a system they cannot see

Not much, honestly. But not nothing.

Ask what is recorded and what is analysed by software. In the EU the AI Act treats candidate-evaluation systems as high risk. Illinois requires notice and consent before AI analyses a video interview. New York City requires a published bias audit for automated hiring tools. Elsewhere there is usually no rule, and you should ask anyway, because the shape of the answer is information about the company.

Then write for the reader you actually have. A transcript scorer reads structure, not charm. Name your structure out loud. "There were three constraints. The first was cost." That sounds faintly robotic to a person and it is exactly what survives being turned into text and graded.

And answer the follow-up nobody is there to ask. On a recorder, the second attempt does not exist. Whatever you said is the artefact.

The uncomfortable ending

Everyone reaches for the same closing line here, which is that we should go back to talking to each other. Nobody is going to do that. Interviewing a thousand people by hand is genuinely expensive, and that was a real problem, and the recorder was a real answer to it.

But if the cheapest way to interview a thousand people also removes the best of them before anyone is assessed, the saving is being booked on the wrong side of the ledger.

I build AI Applyd, which fills in and sends job applications on the employer's own careers page across fifteen of the hiring systems companies actually use, so the hours before any of this go somewhere better.

One question I do not have a good answer to, and I would take yours: if you were designing the first screening stage from scratch, knowing it has to scale to a thousand applicants and knowing the recorder costs you your strongest candidates, what would you build instead?

Laid off this week? Four clocks started the day you found out

Ava Bagherzadeh — Fri, 11 Sep 2026 07:40:57 +0000

The August jobs report came out on September 4. It said the US added 162,000 jobs. It also said the information sector lost 23,000, and that the median time someone stays unemployed is now 11.4 weeks, up from 9.9 a year ago.

Then the first week of September happened. Uber told staff it was cutting about 10% of its workforce on September 2. Volkswagen's supervisory board approved another 50,000 job cuts on September 3. Jaguar Land Rover announced 4,000 on September 7.

If you are one of those people, here is the thing nobody says in the meeting. Several clocks started the moment you found out. Most people hear about them after the shortest one has already run out.

The shortest clock is three days, and it is not the one you are thinking about

If you work in Germany, you have to register as job-seeking with the Agentur für Arbeit within three days of learning your job is ending. If you learn more than three months ahead, the rule is three months before the end date instead (§ 38 SGB III).

Register late and you can lose a week of unemployment benefit, a Sperrzeit (§ 159 SGB III). You can register online. It takes less time than writing the message to your team.

The second German clock is three weeks. That is how long you have to file a claim against the dismissal itself, counted from the day you receive the written notice (§ 4 KSchG). Miss it and the dismissal is treated as valid, whatever was wrong with it.

And one right with no clock at all: you are always entitled to a written reference, the Arbeitszeugnis (§ 109 GewO). Ask for it now, while the people who know your work are still there to write it.

So if the German clocks are the short ones, why do Americans get more time on the most expensive decision?

The paper they hand you in the meeting can wait 21 days

In the US, if you are 40 or older, a severance agreement that asks you to waive age-discrimination claims has to give you at least 21 days to consider it. In a group layoff, that becomes 45 days. After you sign, you still get 7 days to change your mind (29 U.S.C. § 626(f)).

The pressure in the room is real. The deadline in the law is longer. Take the paper home and read it with someone who does not work for the company.

Your health cover has a window, not a cliff

COBRA gives you at least 60 days to elect continued health coverage. The window is counted from the later of two dates: the day your coverage ends, or the day the notice is sent (29 U.S.C. § 1165).

That window exists so you can decide calmly. Find the date on the notice tonight and put the last day in your calendar, because the most expensive mistake is a date that passes while you are busy with everything else.

Which brings us to the clock that only starts when you start it.

Unemployment only starts counting when you do

The Department of Labor's own advice is to contact your state's unemployment agency as soon as possible after you lose your job. Some states have an unpaid waiting week. The first payment usually arrives two to three weeks after you file. Most states pay for up to 26 weeks.

Every one of those numbers is measured from the day you file, not the day you were let go. Filing on day one costs you an afternoon. Filing in week three costs you three weeks.

The clock nobody gives you a date for

Then there is the search itself. The Bureau of Labor Statistics puts the median time unemployed at 11.4 weeks in August 2026, up from 10.5 in July (Employment Situation, table A-12). Nobody hands you that one on paper, and it is the one that decides how the other clocks feel.

So spend week one on the dated clocks: register, read, elect, file. Start the applications in week two, with your calendar clear and your head in it.

When you do, that part does not have to eat your evenings. I build AI Applyd. You pick the job, it fills in the whole application on the company's own careers page, sends it, and brings back the company's own confirmation. Only the employer can call an application sent, so that is what we count.

This is general information, not legal advice. Check the rules for your state or your situation.

Which of these clocks did nobody tell you about?

The hiring window that opens in September, and the two dates it shuts

Ava Bagherzadeh — Wed, 09 Sep 2026 08:13:35 +0000

Job hunting feels like weather. It is closer to tides.

There is a shape to the hiring year, and right now you are standing in the best part of it. Not because of luck, and not because of anything mystical about autumn. Because of how companies actually spend money and book calendars.

Here is the whole thing, and you can check every piece of it yourself in about ten minutes. No signup, no tool, nothing to buy.

First, the ten minute check

Open the careers page of three companies you actually want to work at. Not a job board. Their own page.

Sort by newest. Look at the date on the top role.

A page that added something this week has a person behind it this week.
A page whose newest role is six weeks old is a page nobody is working.

That one number tells you more than the job description does. A description tells you what they wish they needed. A date tells you whether anyone is currently allowed to hire.

Why September is different from August

Two things change at once, and they are not the ones people talk about.

The money became real. A role does not appear because a manager wants help. It appears after someone in finance approves the headcount. Those approvals cluster around planning cycles, and a role approved for this quarter has a spend-it-or-lose-it clock attached to it.

You are allowed to ask about this. "Which quarter was this headcount approved for?" is a normal question and recruiters answer it. If the answer is this one, the deadline is on their side of the table, not yours.

The people came back. Hiring is a scheduling problem wearing a trench coat. A single loop usually needs a hiring manager, someone from the team, a skip level, and whoever signs the offer. In September you can get those four calendars to line up inside a week.

Why December is different from September

The window does not shut once. It shuts twice.

Gate one, late November. The panel starts to break up. Interviews still happen, they just take three times as long. Most of what people describe as being ghosted in December is not rejection. It is four calendars that no longer overlap.

Gate two, mid December. Nothing decides until January. A role posted after that is usually being parked so the req stays alive, not filled.

Neither gate is a reason to stop applying. Both are a reason to stop waiting on a specific role and to keep the next one moving.

The five moves for this month

Sort by newest. Not by relevance, not by best match. Newest.
Go for it the same week it appears. Not the same hour. Rushing is not the point, being inside the window is.
Ask which quarter the headcount came from. One sentence, in your first reply to the recruiter.
Send the CV that is good enough today rather than the perfect one on Friday. Friday is four days of this window gone.
Write every application down somewhere you can see it. So that in November you are looking at a list instead of a feeling.

That last one sounds like admin. It is the one that changes how the next two months feel. The worst part of a job search is not rejection, it is not knowing what is still alive.

Where I am coming from

I build AI Applyd. It keeps that list for you and it fills in the applications, across fifteen of the systems companies actually use. One thing we are stubborn about: a job only moves to sent when the company's own system confirms it arrived. Our own screenshot is not proof of anything.

But the five moves above cost nothing and work without any of that. Use them either way.

What is the oldest job you are still waiting to hear back on? I would genuinely like to know how long people are holding on before they call it.

The counter-intuitive thing job seekers started doing in 2026

Ava Bagherzadeh — Tue, 08 Sep 2026 08:48:15 +0000

There is a number in this year's job-search data that reads like a mistake.

Nearly a quarter of job seekers say they have significantly reduced the number of jobs they apply to. Not because they gave up. Because applying more stopped working, and they noticed before the advice did.

If you have been hunting this year, you already feel why. The median time from starting a search to a first offer is now past 100 days. Somewhere in there, most people cross a line where the search stops being a project and starts being a second job that pays nothing.

The maths that broke

The old advice was volume. Apply to everything, something lands, it is a numbers game.

That advice assumed each application costs you five minutes. It does not any more. Here is the honest cost of one real application in 2026:

Read the posting properly. Four minutes.
Adjust the CV so the first third matches what the role actually screens for. Ten minutes if you are fast.
Upload it. Watch the parser eat it and hand back a form with your dates wrong. Fix it by hand. Twelve minutes, and this is the part nobody counts.
Answer the extra questions. Notice period, salary expectation, work authorisation, the essay box. Six minutes.
Press submit. Find out nothing.

That is over half an hour. Twenty applications is a working week. And a chunk of those postings are not real, which is its own tax on top.

So people did the sensible thing. They cut the number down and put the saved hours somewhere with a better return.

What the people cutting back are doing instead

Three things, and none of them are clever:

They apply to fewer, better-matched roles. Not "roles I could do" but "roles where the first screen will not reject me on the four things it checks": the title, the years, the location, and whether you can legally work there. Everything else is decided later by a human. If one of those four reads wrong, nothing you wrote below matters.

They spend the saved time on one warm route per week. One message to a person who actually works there beats six cold applications, and it takes less time than one of them. Not "networking". One message.

They keep a record of what they sent. Sounds like admin. It is the only way to tell a rejection from an application that quietly never arrived, and those two things look identical from where you are sitting: silence.

The part I find genuinely interesting

The volume advice never died because it was right. It died because volume got expensive. When an application cost five minutes, spraying was rational. At thirty-five minutes, it is the most expensive possible way to be ignored.

And the tooling response to that has mostly been to make spraying cheaper rather than to make it unnecessary, which is how you end up with a market where everyone applies more and nobody hears back sooner.

I build in this space, so treat that as an interest declared. The thing I would defend is narrower than a product pitch: the expensive part of an application is not the writing, it is the retyping and the silence afterwards. Fix those two and the volume question mostly answers itself.

If you are in it right now

Cut your list. Check the four screening facts before you spend thirty minutes on anything. Keep the record. Send one warm message a week.

And do not read your own silence as a verdict on you. Most of it is a req that got frozen, an offer waiting on a signature, or a form that failed.

What actually moved the needle in your search this year? I am collecting honest answers rather than advice, and the honest ones have been more useful.

I build AI Applyd - it fills in and submits job applications across the twelve systems companies actually use to receive them.