Remote AI automation jobs

Where to look

Weekly search routine

  1. Set alerts for 4–5 title variants on LinkedIn and one niche board.
  2. Track 20 target companies; check careers pages every Monday.
  3. Post one public build note or mini case study every two weeks.

Application package

Lead with a one-page project sheet: problem, stack, metrics, link to repo or video. Mention timezone overlap and async communication habits—remote hiring managers worry about handoff friction.

Interview prep

Expect live whiteboarding of a multi-step workflow, questions about failure modes, and a discussion of when not to automate. Review core skills and bring questions about their monitoring and change-management process.

Reading listings in this niche specifically

Titles are unreliable: the same job ships as "automation engineer," "business systems analyst," "RevOps engineer," "integration specialist," or "AI operations." Search by the systems instead — a listing that names HubSpot, webhooks, and error handling is this job whatever the title says. Watch for two red flags: roles that list every platform under the sun usually mean an ops team that has not decided what it needs, and "AI automation" roles with no mention of monitoring or review processes usually mean you will be the one discovering why those matter. A concrete pay anchor for the contract end of this market: a July 2026 A.Team listing on Remotive advertised $120–170/hour for senior independent AI engineers — marketplaces like that screen on entry but set the ceiling for what production automation experience bills at.

Remote jobs FAQ

Where do remote AI automation jobs get posted?

Company career pages, Wellfound, LinkedIn, and niche communities around n8n and Make. Also watch RevOps and internal tooling roles—they often include automation under a different title.

What job titles should I search?

Try “automation engineer,” “workflow engineer,” “RevOps automation,” “AI operations,” and “integration engineer.” Smaller companies combine the work under “operations” or “growth engineering.”

What belongs in a portfolio?

Two or three documented workflows with architecture sketches, sample error handling, and a paragraph on business outcome. Live demos or Loom walkthroughs beat buzzword lists.