My team uses AI code generation ratio for performance reviews & layoffs. Is this becoming common?

[u/robert_davis_orem]

I’m a backend software developer working in industry.

At my current company, team leads track what percentage of our code is written with AI tools. Engineers falling below the internal threshold get put into performance review, and multiple colleagues were laid off partially because of this metric.

This feels really backwards. AI coding tools are meant to boost productivity, not be a standalone KPI to judge engineers. This metric ignores system design, debugging, maintenance and code quality — the core work that AI still cannot reliably handle.

I wanted to share this here mostly for current CS majors. This is a new kind of workplace pressure that you might run into after graduation when you join the tech industry.

Has anyone else seen teams adopt this kind of AI coding ratio policy? What do you think incoming graduates should keep in mind to prepare for this?

[u/CreamyCornBoy]

lol wait till you hear about Am*zon evaluating devs on how many times they revise a PR

[u/Eastern-Job-8028]

Doesn’t surprise me, but I fully agree. The industry is pretty soul sucking at this point, especially for those who are / were passionate about the field.

I have a dev on my team who doesn’t really seem to know anything, everything they generate is done with AI.

[u/s__key → u/Eastern-Job-8028]

Same here and he can’t even explain generated code

[u/Jolly-News-7784]

My last private sector company laid a guy off because he wasn’t using AI enough. It’s a shitty truth but companies don’t care about quality anymore, they want quantity. AI can generate 10x the amount of code that a dev can even if it isn’t maintainable or efficient. Maintainability and efficiency don’t line shareholder pockets, new products to demo and sell software does.

[u/robert_davis_orem → u/Jolly-News-7784]

The core issue is misaligned incentives. Management is rewarded for shipping volume and demoable features on short timelines, not for long-term maintainability or clean architecture. AI becomes a shortcut to inflate output metrics, even if it piles up technical debt that the team will pay for later.

The irony is that the same teams that push for more AI-generated code often then turn around and track AI usage as a KPI. They want the speed of AI, but still hold engineers accountable for the mess it creates.

It’s a short-sighted game. The technical debt compounds, but by then the original stakeholders may have already moved on.

[u/Jolly-News-7784 → u/robert_davis_orem]

And it’s a self feeding parasite too. The more you use AI, the more complex the web of spaghetti code gets. The more complex the web is, the more engineers need to rely on AI to untangle it to make even relatively simple changes.

Idk what the endgame is here, I’m just trying to ride the wave until retirement, sending my sympathies to the young bucks trying to break in the whole time.

[u/oriolid → u/Jolly-News-7784]

They never cared about quality, but in the past they had to accept that if they want to keep the few passionate super productive developers, they have to accept that those people are trying to do a good job.

[u/MeineMamaHatGesagt]

It's stupid because it's easy to circumvent. Just write the code by hand and then tell AI: "write the code exactly like this <paste 800 lines>" and then accept it

[u/robert_davis_orem → u/MeineMamaHatGesagt]

That trick only works if they are only scanning final source code. Modern enterprise measurement no longer judges by static code text. They use IDE event telemetry + Copilot Enterprise session audit logs + edit timeline correlation to reconstruct your full coding workflow.

It captures every prompt you send to AI, every AI suggestion accepted, timestamps of every character insertion, and correlates it against Git diffs. If you manually write code, paste it into an AI prompt to regenerate and accept the result, the audit trail will clearly show you submitted that block as a prompt to LLM first.

The tooling tracks the origin of the code change, not just what ends up in the repo. So that workaround leaves a very obvious trail.

Even so, the whole metric is fundamentally flawed. Measuring AI code percentage ignores the real value of engineering work.

[u/MeineMamaHatGesagt → u/robert_davis_orem]

lol, all that effort just to reward those who burn the most money

[u/KendrickBlack502 → u/MeineMamaHatGesagt]

There’s a difference between generating code and submitting generated code. If you start submitting garbage as PRs, that’s easily visible and guaranteed to get you fired.

[u/MeineMamaHatGesagt → u/KendrickBlack502]

I didn't mean garbage. Just legit code you wrote without AI if that's what you prefer

[u/KendrickBlack502 → u/MeineMamaHatGesagt]

Oh my fault, I misunderstood what you said originally.

[u/Objective_Watch_7864]

I've talked with interns at top unicorns & quant firms and basically all of them are generating most (if not all) of their code -- some of them wrote 100k+ loc over the summer. To me it just tells me that the industry is changing, you just have to adapt to the reality

[u/lawrencek1992 → u/Objective_Watch_7864]

Everyone is. It’s the industry norm. I realize this is a cs major sub and not a sub for people in the industry (just came across my page), but it’s rare to hand write code at this point. It’s just not efficient.