Until recently, the tools a developer used to write code were a private choice. In the sample, 44 positions name an AI coding assistant as a requirement: Claude Code (29), Cursor (19) and GitHub Copilot (18). Claude Code alone appears in more positions than PHP.
What employers are signaling
A named assistant tells you the team has adopted AI-assisted development as a working practice. Expect conversations about how you use these tools, how you verify their output and how you keep secrets and proprietary code safe. These requirements sit alongside a conventional stack: of the 44 positions that name an assistant, 42 also name other technical skills.
Using them well
- Give context deliberately. Repository conventions, tests and acceptance criteria produce better results than one-line requests.
- Review everything. Treat generated code like a teammate's pull request: read it, test it, and own it.
- Use them where they are strongest. Tests, refactors, documentation and unfamiliar APIs are common high-value uses.
- Follow team policy. Know which tools are approved and what data may be shared with them.
Showing it in an application
Describe a real piece of work where an assistant changed how you delivered it: what you delegated, what you rejected, and how you verified the result. That is more convincing than listing the tool.