AI Skills Are in One in Three Intern Postings. Almost Nobody Can Prove It.

In partnership with

Tackle your credit card debt by paying 0% interest until nearly 2028

If you have outstanding credit card debt, getting a new 0% intro APR credit card could help ease the pressure while you pay down your balances. Our credit card experts identified top credit cards that are perfect for anyone looking to pay down debt and not add to it! Click through to see what all the hype is about.

Learn How To Apply Now

Welcome to today's SCALIS EarlyCareers newsletter! 🚀

Here is the number that should reframe your fall applications. According to NACE's Job Outlook 2026 Spring Update, more than one-third of entry-level jobs now require AI skills. That is nearly triple the figure from fall 2025. Six months. Tripled.

Dig one layer down and it gets more specific. Twenty-eight percent of employers say they are actively seeking early-career talent with AI capability. Nearly 60 percent say they are assigning interns projects that involve AI tools. And separately, NACE is tracking that 16.5 percent of entry-level job descriptions now contain AI skills in the actual posting text, which means a lot of this screening is happening in conversation and in interviews rather than in the req itself.

The debate about whether AI belongs in entry-level work is over. Employers decided. Over half of them say AI is not reducing the amount of work they hand to entry-level people, and only about 11 percent are even discussing eliminating positions. They are not replacing you with it. They are expecting you to arrive holding it.

So here is the real gap, and it is not the one students think it is. Almost every student applying this cycle has used AI. Almost none of them can prove it in a way a recruiter can verify in eight seconds. "Familiar with ChatGPT, Claude, and Gemini" on a skills line is not proof. It is a claim, and recruiters have stopped reading claims. Today is about the difference between the two.

(One note on the source: the NACE survey was sponsored by Jobscan, an AI resume tool. The numbers are credible and widely cited, but you should know who funded them.)

Why 1.1M+ readers open this AI newsletter every day

From ML engineers to founders, 1.1M+ readers use TLDR AI to spot new tools and research before they go mainstream. One free email, every morning.

Subscribe for free

4,052 BRAND NEW internship positions freshly posted today. View the full list below and start applying!

A claim lives in the skills section. Proof lives in the experience section.

Open your resume right now. If every mention of AI is sitting in a comma-separated skills line at the bottom, you have made a claim and nothing else. That line is where recruiters' eyes skip, and it is where every other applicant put the identical words.

Proof means AI appears inside a bullet describing something you actually produced. Not as a listed tool, but as part of a sentence that has an output in it. The test: could a recruiter read that bullet and describe to a hiring manager what you built? If the answer is no, it is still a claim.

Move it. Take the AI tools out of the skills dump and work them into the two or three bullets where you genuinely used them to finish something. You will end up listing fewer tools and sounding significantly more capable.

Know which AI skills they are actually screening for

The NACE language is specific and worth paying attention to: employers want AI skills that complement human work rather than replace it. In practice, that means a short list. Drafting and revision. Data analysis and summarization of messy inputs. Research synthesis. Workflow automation of repetitive steps. Quality-checking output before it goes anywhere.

What they are not screening for is "I used ChatGPT." Everyone used ChatGPT. The signal they are looking for is whether you know when the output is wrong. An intern who can run a prompt is worth less than nothing if they cannot tell when the model confidently hands them something false, because now a manager has to check it twice.

Pick the two things you are genuinely good at from that list and build your examples around them. Depth beats breadth here, badly.

Write the bullet as output plus tool plus judgment

Most students write the bullet backwards. They lead with the tool, because the tool is the thing they think is impressive. The tool is the least impressive part.

The structure that works is: what you produced, how AI was involved, and what you did that the AI could not. That last piece is the whole ballgame. It is the part that proves you were operating the thing instead of being operated by it.

Same project. The second version tells a hiring manager you can be trusted with output that leaves the building.

The question behind "how do you use AI in your work?"

When an interviewer asks this, they are not collecting tool preferences. They are testing for one of three things, usually all three: do you know the limits, do you verify, and will you quietly ship something hallucinated into a client deck.

The answer that fails is enthusiasm. "I use it for everything, it saves me so much time" tells them you have never been burned, which tells them you are about to burn them.

The answer that works has a failure in it:

Specific. Shows a scar. Shows a rule you developed from it. That is what a verified AI skill sounds like out loud.

Ask what the AI stack actually is before you accept

Nearly 60 percent of employers are assigning interns AI-involved projects. That means during your interview process, you have a completely legitimate, impressive-sounding question available that most candidates will not think to ask.

This question does three jobs at once. It signals you expect to use AI productively, it signals you care about the governance side (which is exactly what makes managers nervous about interns and AI), and it gets you a real answer about whether this company is thoughtful or chaotic about the whole thing.

And practically: if they tell you they run on Copilot and an internal RAG tool, you now have two weeks before you start to get competent in both.

The AI newsletter curated by engineers who build it

TLDR AI is a free daily email curated by Anthropic and ex-Google engineers: the new tools worth trying and the research worth understanding, summarized for 1.1M+ readers.

Subscribe for free

The portfolio move almost nobody is making

Here is where the gap is widest, and it is the easiest thing on this list to fix this weekend.

A claim on a resume cannot be verified. A link can. If you have built anything with AI involved, put it somewhere a recruiter can click: a GitHub repo with a readme explaining your prompting approach, a Notion page walking through a project, a one-page write-up of an automation you built for a student org.

The write-up matters more than the artifact. Three short sections: what the problem was, where you used AI and where you deliberately did not, and what broke along the way. That third section is the one that makes a recruiter stop. Nobody writes about what broke. It is also the only part that proves the project was real.

Then put the link in your resume header next to your email, not buried at the bottom. You are now one of the very few applicants in the stack who did not just claim AI competency, but handed over evidence of it before anyone asked.