Startup company forces techie to use AI for coding, then fires him for using AI at work. 'They were delusional'

In today’s tech world, artificial intelligence is becoming a big part of software development. Many companies are experimenting with AI tools to speed up coding and automate tasks. But a recent story from a small AI-focused startup shows that the push for AI can backfire, especially when leadership expectations clash with practical coding realities.

A troubling story from the tech world is making the rounds online after a frontend engineer described how a colleague was pushed to rely on artificial intelligence tools at work and then lost his job over the same reason.

In a Reddit post shared on a public forum by a self-identified software engineer, a junior developer at a small AI-focused startup was reportedly fired after two bugs made it into production. The original poster said that management in the company was “bullish on AI” and “forced” engineers to use AI tools extensively in everyday coding tasks.


“I personally think they were delusional,” the poster wrote about the leadership’s insistence on heavy AI usage. He said although deadlines were met, the emphasis was always on using AI rather than traditional coding.

Pressure to Use AI, Then Blame When Things Break

According to the post, the junior developer was a fresh graduate with solid college credentials, including knowledge of Python and data structures. Despite that, the poster said, the colleague struggled to estimate timelines and the team gradually tightened deadlines. Eventually, the junior started using AI to generate code just to keep up.

The Reddit user explained that the junior began to rely on AI output without fully understanding how it worked under the hood, leading to a style where he could explain what a function did but not how. The poster wrote, “AI does not care if the file is fifteen thousand lines wrong,” a situation that ultimately made debugging difficult.

One night, the team was notified via Slack that something had broken in production. The engineer described the next day spent tracking the issue, only to find the root cause in the junior developer’s code. The team discovered that earlier AI-generated changes had been merged after a review done with AI. That second production bug led management to fire the junior engineer.

Social Media Reacts: Leadership, QA, and Coding Culture Under Fire

Responses to the post were swift and often critical of the company’s leadership. One commenter said the title should have been “AI helps man avoid terrible company,” arguing that bugs and production issues happen at all levels of software development. Others criticized firing someone over two bugs, saying it creates a toxic culture.

A number of people pointed out flaws in the company’s process, particularly the lack of a proper quality assurance system. One commenter said, “There is a reason why reviews, pipelines, regressions exist … Firing creates a culture of fear and kills innovation especially in such cases.” Another said the responsibility for bugs should be shared among developers, reviewers, and QA, not placed on a single programmer.

Many replies also took aim at leadership and its handling of deadlines and code review. One voice in the thread wrote, “When reviewing the code, he didn’t bother checking the code quality and simply used AI tool to review and merge it,” arguing that this showed a deeper problem than just a mistake by the junior engineer.

Others took a broader view, cautioning that companies rushing to adopt AI coding tools without proper training and oversight were setting employees up to fail. One commenter warned about the dangers of leaning too much on AI for core logic instead of guiding it with solid technical understanding.