Does listing AI skills on your résumé win more interviews, and does it matter whether you're a designer or a developer?

This explores why recruiters might value AI skills differently depending on the job, with graphic design and software engineering as the test case. One thing up front: the corpus has no study that puts these two occupations side by side, so it can't tell you exactly how big the gap is. What it does have is enough on how recruiters read AI skills and how AI demand spreads across the labor market to explain why a gap would appear.

The main evidence is a large experiment with 1,725 recruiters. They were shown fictional candidate profiles, some listing AI skills and some not. Listing AI skills raised interview invitations by 8 to 15 percentage points, and the size of the boost varied by occupation Do AI skills help candidates get more job interviews?. The surprising part is what made little difference. A certificate added only a modest bump over simply saying 'I have AI skills.' So recruiters seem to reward the claim without checking whether the candidate can actually do it. That suggests occupation matters less because of what AI does in each job and more because of what recruiters already believe 'AI skill' means in that field.

Those beliefs follow a real split in the job market. Job-ad data from ten countries shows AI skill demand clustering in technical work around Python, SQL, machine learning and data analysis. Non-technical jobs are moving away from that cluster, not toward it Is AI creating common skills across jobs or deepening divisions?. For a software engineer, 'AI skills' fits a skill set recruiters already know how to picture. For a graphic designer, the same phrase could mean prompting an image generator, automating production work, or something else entirely, and there's no shared template to judge it against. A signal that's easy to interpret gets priced one way. A vague one gets priced differently, either as a bonus for seeming up to date or with doubt about what it replaces.

The less obvious point is that AI is also weakening the other signals recruiters use, which makes self-reported AI skill carry more weight than it deserves. On Freelancer.com, removing written signals like cover letters made hiring 19% less merit-based: top workers got hired less often and weaker ones more often Does cheap writing weaken hiring based on worker ability?. Within the same platform, workers who spent more time editing their AI-drafted applications were hired more often Does editing time on AI drafts predict hiring success?. Effort still shows through, just less visibly. Meanwhile recruiters are overwhelmed by AI-generated applications and prompt-injection tricks Are job applicants and employers locked in an escalating AI arms race?, and only 21% are very confident their own screening tools don't reject qualified people Do hiring managers and job seekers agree on AI fairness?. When signals are noisy everywhere, recruiters lean on shortcuts, and what 'AI skill' is assumed to mean differs by field.

There's a twist on the software side. Interviews with engineers suggest AI is taking over the entry-level tasks juniors used to learn on and moving them into senior engineers' AI-assisted workflows Does generative AI prevent juniors from getting entry-level work?. So a premium for AI skills in software engineering may reward people who can direct AI, while the routes for building the judgment that makes such direction good are disappearing. If you want to see how occupation shapes the premium, start with the recruiter experiment. Then read the labor-market split note to see why the meaning of 'AI skill' itself differs by field.