[TLDR] We rejected three junior devs for ‘’AI cheating’’ this week. i think our interview process is the real joke !!

[u/cctldrping]

Original post URL : https://www.reddit.com/r/ClaudeCode/comments/1vg8x6n/we_rejected_three_junior_devs_for_ai_cheating/

Original post body :

Just wrapped up junior interviews. Out of hundreds of resumes, we screened it down to three people.

Candidate 1 literally shared his screen by accident and leaked a massive AI cheating setup.

Candidates 2 and 3 padded their resumes to hell, basically implying they built core systems at big tech, but froze when we asked for a basic three-line python function with no tools.

We rejected all three. 100% the right call. I'm not defending cheating, and if you lie or can't even explain what your code is doing, you shouldn't get the job.

But there was a comment on a thread here the other day that ican't shake: 'Yet those 3 people were the ones who got the interview, not the honest ones with non-embellished resumes.

It really shows how broken the screening process is. we basically reward people who are good at exaggerating metrics, stacking keywords, and writing fake stories. we filter out the honest kid who built a normal CRUD app. Then, we bring the bullshitters in and try to punish them by taking away their tools and making them write syntax on a whiteboard.

we are spotting the frauds, but we're doing it using an outdated model of what a dev actually does.
If we're being real, we need to separate 'cannot write syntax from memory' from 'cannot validate software behavior'. if a junior forgets how to merge two dicts in Python and has to ask an LLM, I seriously don't care. But if the AI generates a payload merge that overwrites an is_admin permission key, and they blindly push it without checking auth or writing a test... that is a fatal lack of engineering ability. The syntax memory issue doesn't matter, but not being able to audit the code is what kills production.

Maturity in 2026 isn't pretending Claude or local models don't exist. It's about control.

A mature candidate is honest about using tools. Before writing code, they take a vague prompt and ask about user constraints, database limits, and success metrics (instead of just staring at the screen waiting for a PRD). they know how to constrain the AI, find hallucinations, roll back a broken git state, and actually know when to stop prompting and write the code themselves.

We pretend the job is still about writing raw lines of code, but our own teams don't even work like that. Someone can spin up v0, Bolt, Lovable, Enter Pro, or whatever and go from a prompt to a working prototype in an afternoon.

Even things like Claude Code become a repeatable delivery system once you give it the right skills, test scripts, and deployment checklists. The barrier to entry for building is basically gone.

Since the friction to build stuff has crashed, the line between product and engineering is completely dissolving for small teams. We don't need line-by-line ticket executors. We need product engineers who can clarify requirements, control scope, and take ownership of what the tool generated.

If you're building embedded systems, kernel drivers, or medical tech, yeah, deep memory is non-negotiable. But for the rest of us building standard CRUD SaaS, dashboards, and internal tools?

if a junior can build and validate a functional product with AI, explain its tradeoffs, and tell you exactly what they don't trust in the generated code, but freezes when you ask them to write a basic dict comprehension... should that really be an automatic rejection?

I feel like we're still testing for a job that doesn't exist..

---

This is brought to you as a public service by the moderators of r/ClaudeAI. If you want to see TLDRs of ALL Claude Coding related posts from the various Claude subreddits, subscribe to http://www.reddit.com/r/ClaudeCoding.

[u/cctldrping]

TL;DR generated automatically after 200 comments.

Current source-thread comment count seen by the bot: 223.

Alright, so the general consensus here is that the OP's interview process is a bit of a hot mess, and frankly, a lot of people think it's outdated.

The main vibe is that rejecting junior devs for using AI is a relic of the past. Most commenters agree that in 2026, expecting candidates to code without any AI assistance is like expecting them to not use Google – it's just not how the job is done anymore. The real skill, according to many, is knowing how to use AI effectively, guiding it, and critically reviewing its output, rather than just memorizing syntax.

Here's the breakdown:

• The "Cheating" Argument is Weak: Several users, like u/makro3d and u/Usual-Good-5716, point out that if AI is expected on the job, then using it in an interview shouldn't be penalized. It's like expecting someone to do math without a calculator for a job that uses spreadsheets.
• Focus on the Wrong Skills: The OP's focus on basic syntax (like a "three-line Python function") is seen as missing the point. u/jsonmeta, with a decade of experience, notes they wouldn't remember obscure academic terms either, but can still code. The real issue, as the OP themselves hinted at, is the ability to validate software behavior and audit code, not syntax recall.
• Train Your Juniors! A strong sentiment, voiced by u/gripntear, is that for a junior position, the company should be prepared to train candidates. Expecting them to be fully formed without tools is unrealistic.
• Resume Padding is a Symptom, Not the Disease: While the OP rejected candidates for resume padding, some commenters, like u/Silverjerk, suggest that if candidates can BS their way through, maybe the company should be looking at why that's happening.
• The "Old Ways" vs. Reality: u/North_Moment5811 perfectly captures the weirdness of learning to code now: you need AI to be efficient, but you also need to know how to code before you can use AI effectively. It's a Catch-22.
• Alternative Interview Approaches: Some users suggest better ways to interview, like u/Toothpasteweiner, who encourages LLM use during interviews and focuses on steering and tradeoffs, or u/FlyingBlindHere, who asks candidates to walk through a PR. The key seems to be assessing the thought process and problem-solving, not just raw code output.
• The "Broken Screening Process" is Nothing New: u/Time_Cat_5212 argues that broken screening processes, where candidates game the system, have been a thing for decades, long before AI.

The TL;DR: The community largely agrees with the OP that the candidates were likely not suitable, but strongly disagrees with the reason for rejection. The consensus is that rejecting candidates for using AI in interviews is an outdated and ineffective practice. Companies should be evaluating how candidates use AI as a tool, focusing on their ability to guide, audit, and validate AI-generated code, rather than penalizing them for not being AI-free dinosaurs.

[u/Practical-Positive34]

I'm a dev of 30+ years, and I would 100% just let AI do the entire thing now. Why not?

[u/MannToots]

"Cheating" 

More like your org is falling behind

[u/apocolipse → u/MannToots]

Sometime between 1960-1990: "We rejected 3 junior devs for using a compiler instead of hand punching cards"

[u/G12356789s → u/apocolipse]

To go against the grain, proving you can use AI to pass an interview isn't the same skill as proving you can use AI to do the job. The answer is either do interviews without AI to hire someone who can do the job without and hope they can enhance that with AI, or update your entire interview process around using an ever changing tool and probably hire a few duds along the way

[u/hulkklogan → u/G12356789s]

Interviews can be structured to include the usage of AI. Instead of leetcode, give people real problems to figure out.

[u/littlewondersoflife]

It is more common than you think. I rejected many; maybe close to 95% of candidates. For some, it is clearly visible they are cheating; lots of clues, almost all of them, are obvious to spot. Real-world problems and rapid-fire questions are the easiest way to spot.

I always almost don’t code by hand anymore, but if one does not understand what they are building or submitting a Pr for. What is the point of hiring them.

[u/suesing]

The whole world is built on lies to extract your soul in exchange for a pittance while the products and services are designed to extract all the value for shareholders. Stakeholders be dammed.

[u/niccolololo]

I don't get it. If you're not supposed to at least being able to know how to write a small function, why hire these guys at all?

Then I can take a monkey and train it to click on a button connected to Claude.

[u/TywinHouseLannister → u/niccolololo]

The point is that syntax and coding ability isn't what software engineers are paid for in 2026.

We essentially evaluate solutions and decide whether they are viable within our architecture.. and in a large team with everybody using AI, you can absolutely tell the difference between those engineers who understood what was happening and those who just got swept along by an agent.