find your role first.

Guide

How do I find remote jobs with an AI agent?

How do I find remote jobs with an AI agent? Connect Claude Code or Codex to Find your role first, search the location field for the ways companies actually write "remote", then have the agent open each posting to confirm who can really apply. The search finds candidates. The posting decides whether you're eligible.

That second step is the part people skip, and it's why remote searches feel unreliable.

How does remote location search work?

The feed reads 8,519 company career boards on Greenhouse, Lever and Ashby. Each role has a location field, and that field holds exactly what the company typed. search_jobs matches your words against title, company and location.

So "remote" in a search finds roles whose location text contains the word remote. That sounds simple. It mostly is. The catch is how differently companies write it.

How do companies write remote in job locations?

A small sample of shapes you'll see:

The last two are the tricky ones. "Anywhere" means remote but doesn't say it. "United States" can mean remote within the US, or it can mean the company didn't bother with a city. You can't tell from the location alone.

It goes the other way too. A role listed as "Remote" can say three paragraphs down that it only hires in certain states, or needs overlap with a particular time zone, or wants you in an office once a quarter. The location text comes from the company, and the feed passes it along as written. Honestly, that's the right call, since a feed guessing at remote rules would get it wrong in ways you couldn't see.

What prompts find remote jobs with an AI agent?

These work once the feed is connected.

Search for product designer roles where the location mentions remote, discovered since yesterday. Then open each posting and tell me the country or region it hires in, and any time zone requirement.
Find backend engineer roles with "Remote, US", "US Remote" or "Remote (United States)" in the location, published in the last week. Open each and keep only the ones that hire in Colorado.
Search for data analyst roles with remote, anywhere, EMEA or Europe in the location, discovered in the last 3 days. Open each posting and keep only the ones open to candidates in Portugal.
Find customer success roles in the US discovered this week, including ones whose location just says "United States". Open each posting and label it fully remote, hybrid, or on site.
Search remote marketing roles discovered since Monday. For each, open the posting and pull the exact sentence about where you need to live. Quote it, don't paraphrase.

The last instruction is worth reusing. Getting the exact sentence back makes it easy to check the agent's reading yourself.

Why should my agent open every remote posting?

Because the feed deliberately returns short records. For each role you get the title, company, location, the date the company published it, the date the feed first discovered it, the original posting link, the apply link and whether it's closed. There's no description text. Your agent reads that with its own web tool.

For remote roles that's where the answer lives. Things the agent should pull from each posting:

Turns out a lot of remote searching is really eligibility checking. Letting the agent do that reading is where it saves you the most time.

Can I get new remote roles every day?

Yes. Ask for roles discovered since your last check. The feed records when each role was first discovered, separately from the date the company shows, and every board is checked every two hours with the checks spread out through the day.

For a scripted routine, get_changes returns new, updated, reopened and closed roles since a saved cursor. get_job refreshes a single role, useful for confirming a remote role is still open before you apply. get_usage shows your allowance and doesn't count against it.

Sign in with Google at findyourrolefirst.click/account, subscribe, create an agent key, then paste one line.

Claude Code:

claude mcp add --transport http --scope user jobfeed https://findyourrolefirst.click/mcp --header 'Authorization: Bearer YOUR_API_KEY'

Codex CLI:

export JOBFEED_API_KEY=YOUR_API_KEY
codex mcp add jobfeed --url https://findyourrolefirst.click/mcp --bearer-token-env-var JOBFEED_API_KEY

It's $9 a month for 3,000 new roles, up to 1,000 a day. Running several location variants is fine: a role you've already seen that month is free to read again, and empty searches are free. Cancel anytime, refund within 3 days. The feed only covers companies on Greenhouse, Lever and Ashby, and it won't apply for you.

Questions

Can an AI agent find remote jobs?

Yes. Connected to Find your role first, Claude Code or Codex can search roles whose location mentions remote across 8,519 company career boards, then open each posting to check where you're allowed to work from.

Does "Remote" in the location mean I can work from anywhere?

Not necessarily. The location text is whatever the company wrote, and many remote roles limit hiring to certain countries, states or time zones in the description. Have your agent read the posting.

How do I search for remote jobs in the US only?

Ask your agent to search several forms, like "Remote, US", "US Remote", "Remote (United States)" and "United States", then open each posting to confirm it's remote and open to your state.

Does the feed tag roles as remote, hybrid or on site?

No. It returns the location text as the company wrote it. Your agent can label each role after reading the posting.

How often do new remote roles appear?

Every board is checked every two hours, spread out so new roles arrive continuously. Ask for roles discovered since your last check to see only what's new.

Try it in your agent

$9 a month. Sign in with Google, subscribe, then paste one line into Claude Code or Codex. Cancel anytime, refund within 3 days.

Get started

More guides