Skip to main content
Egnyte office scene with junior engineers collaborating at desks, laptops displaying AI coding tool dashboards.

AI news illustration: Egnyte Doubles Down on Junior Engineers Amid AI Coding Tool Surge

Egnyte Bets Big on Junior Engineers Despite AI Coding Wave

Egnyte Doubles Down on Junior Engineers Amid AI Coding Tool Surge

Updated: 3 min read

The AI coding tool surge is rewriting the rules of development, or so the hype suggests. At Egnyte, the reality is more measured. Vineet Jassal, the company’s VP of engineering, puts it bluntly: “I would not trust AI to commit to the production code base.” That skepticism isn’t a rejection of the technology; it’s a recalibration.

While some developers lean on large language models to summarize pull requests or navigate unfamiliar iOS codebases, every change still demands a human stamp. Commits pass through human review and security validation; anything red-flagged escalates to senior engineers. In this environment, where AI assists but never decides, Egnyte is making a counterintuitive bet.

It is doubling down on junior engineers.

"Let's say you're looking at an iOS application, but you're not well versed; you will fire up Google CLI or an Augment, and ask it to discover the code base." Some Egnyte devs are moving into automatic pull request summaries, which provide simple overviews of code changes that essentially explain the "what," "how," and "why" of proposed modifications. "But obviously, any change that's made, we don't want to hear that AI made the change; it has to be that developer made the change," Jassal pointed out. "I would not trust AI to commit to the production code base." Commits still pass through human review and security validation, and anything red-flagged is escalated to senior engineers.

AI coding tools are powerful, but they lack the judgment to know what *not* to build. Egnyte’s bet on junior engineers isn’t nostalgia, it’s discipline. By insisting that every commit be owned by a human, the company preserves the one thing no model can replicate: accountability.

Junior engineers learn to question the output, to understand the "why" behind the code, and to carry the weight of a production change. That muscle atrophies when AI becomes a crutch. The pull request summaries are helpful.

The code discovery tools save time. But the final gate remains human judgment, and that gate is best manned by engineers who earned their intuition, not by those who outsourced it to a prompt. In the rush to automate, Egnyte is making a quieter, harder bet: that the best way to prepare for an AI-infused future is to double down on the messy, slow, irreplaceable work of building good developers.

Common Questions Answered

How is Egnyte using AI coding tools to support junior engineers?

Egnyte is embedding AI tools across its development team to help junior engineers learn and become more productive. Instead of replacing human talent, the company views AI as an accelerator that helps new developers quickly understand complex codebases and reduce the traditional learning curve.

What specific AI-powered techniques are Egnyte developers using?

Egnyte developers are leveraging tools like Google CLI and Augment to explore and understand unfamiliar code bases, particularly in areas like iOS development. Some team members are also implementing automatic pull request summaries, which use AI to provide concise explanations of code changes, detailing the 'what,' 'how,' and 'why' of proposed modifications.

Why is Egnyte's approach to AI coding tools different from other tech companies?

Unlike many companies that are scaling back human talent in response to AI coding tools, Egnyte is doubling down on junior engineers. The company sees AI as a collaborative tool that enhances developer capabilities rather than a replacement for human talent, focusing on using AI to accelerate learning and productivity.

LIVE03:21OpenAI's Miles Wang in Talks for USD 2B AI Drug Discovery Startup