1 in 5 remote software jobs now asks you to code with AI. A year ago it was 1 in 20.
August 2026
More job descriptions now say the engineer is expected to use tools like Claude Code or Cursor. We have 17 months of remote software engineering posts, so we measured how common this has become and how fast it is changing.
The number
In August 2025, 5.1% of remote software engineering posts from startups and scaleups on Matcha said the engineer would be expected to work with AI coding tools. In August 2026 it is 20.7%. Four times more in twelve months, and the line is still going up.
| Quarter | Posts | Expect AI-assisted coding | Name a specific tool |
|---|---|---|---|
| Apr to Jun 2025 | 5,991 | 4.3% | 3.5% |
| Jul to Sep 2025 | 4,942 | 5.3% | 4.4% |
| Oct to Dec 2025 | 3,382 | 8.4% | 6.7% |
| Jan to Mar 2026 | 13,562 | 13.3% | 9.7% |
| Apr to Jun 2026 | 5,243 | 17.2% | 11.9% |
| Jul to Aug 2026 | 5,977 | 18.1% | 12.6% |
"Expect AI-assisted coding" means the post says so in plain words: it names a tool, or it uses phrases like "AI-assisted development", "AI coding tools", "coding assistants", or "we expect you to use AI tools to build". It does not count posts where the company merely sells an AI product. Those would roughly double every number above.
In the summer of 2026, 494 of the 2,350 companies with a remote engineering opening named at least one tool in the post. That is one company in five.
Which tools
Share of remote software engineering posts naming each tool, August 2025 versus August 2026:
- Cursor: 2.3% to 10.1%
- Claude Code: 0.9% to 7.8%
- GitHub Copilot: 2.0% to 4.4%
- OpenAI Codex: 0.2% to 3.0%
Copilot was the default name a year ago and has barely moved. Cursor and Claude Code went from almost nothing to being written into one post in ten. Claude Code passed Copilot in April 2026, less than a year after its general release, and has been level with Cursor since.
What the posts actually say
The wording has shifted from "nice to have" to "this is how we work here." A few from August 2026:
- Mattermost, Senior Full Stack Engineer: "We expect engineers to work fluently with AI coding agents such as Claude Code day-to-day."
- CarOnSale, Senior Backend Engineer: "Coding agents, LLMs and AI-assisted development are part of the daily workflow here, not a pilot project."
- Alt Platform, Data Engineer: "Use Claude Code or Cursor as the default way you work through a migration or a backfill, not as autocomplete."
- Brightfield, Senior Go Engineer: "Experience using AI coding tools such as Claude Code in daily development, with the ability to discuss specific work you've shipped using these tools."
- TRM Labs, Staff Data Platform Engineer: "comfort using AI tools (Claude, Cursor, or similar) to accelerate debugging, code review, and documentation."
- Patrianna, Junior QA Engineer: "Preference for AI-free workflows or resistance to AI-assisted development is NOT aligned with how we operate."
The Brightfield post is worth noting: it asks candidates to discuss specific work shipped with these tools, which suggests this will come up in interviews, not just in the job description.
What it does not change
You might expect posts that want AI fluency to relax the experience bar, on the theory that a fast engineer with good tools replaces a senior one. In our data they do not. Among the live posts from the last six months, the ones that name an AI coding tool ask for a median of 5 years of experience, and 60% of them ask for 5 or more. The posts that do not mention AI tools ask for a median of 5 years, with 57% asking for 5 or more. Same bar.
Pay is not higher either. Posts naming a tool show a median salary of $175,500 against $187,500 for the rest, which is the mix of company sizes talking, not a discount for AI skills. The tools are being added to the list of things a senior engineer is expected to know, not swapped in for the years.
What to do with this
If you are a software engineer looking for a remote role, one in five posts now expects you to work with AI coding tools, and some will ask you to describe what you built with them. It helps to have one concrete example ready: a migration you ran with Claude Code, a feature you built in Cursor, and what you had to fix afterwards.
If you are hiring, "we use AI tools" no longer distinguishes a post. The posts in our sample that were specific said which tools, for what tasks, and what the engineer was still expected to own.
How we counted
39,097 remote software engineering posts from fully remote startups and scaleups, posted on Matcha between April 2025 and August 2026, including posts that have since expired. We searched the original posting text for a named coding tool (Cursor, Claude Code, Copilot, Codex, Windsurf, Devin) or explicit phrases about AI-assisted development, and read a random sample of matches by hand to check that they describe how the engineer works rather than what the company sells. About 1 match in 10 is a product mention rather than a requirement, so the true share is slightly lower than the numbers above. Monthly figures bounce with which companies happen to be hiring, which is why the table shows quarters. The experience and salary comparison uses the 4,304 posts that were still live at the end of August 2026, USD yearly salaries only.