Egnyte’s bet on junior engineers in an era of AI-assisted coding

While much of the industry debate in 2025 and 2026 has focused on whether AI will replace software developers, Egnyte is quietly taking a different path. The $1.5 billion cloud content governance company has rolled out AI coding tools to more than 350 engineers worldwide—but instead of using them to cut staff, it is doubling down on hiring junior talent.

For engineering leaders and technical decision-makers, Egnyte’s approach offers a concrete alternative to “AI will kill dev jobs” narratives: treat AI as infrastructure to accelerate capability and talent development, not as a replacement for it.

Why Egnyte is investing in juniors instead of shrinking its dev bench

Egnyte’s core bet is straightforward: long-term engineering capacity depends on a healthy pipeline of junior developers who can grow into future senior leaders. AI tools are being deployed to speed that progression, not to make it unnecessary.

“To have engineers disappear or us not hiring junior engineers doesn’t look like the likely outcome,” said Amrit Jassal, Egnyte CTO and co-founder. “You’ve got to have people you’re training and doing all types of succession planning. The junior engineer of today is the senior engineer of tomorrow.”

This stance runs counter to the more aggressive automation rhetoric in the market. Rather than assuming AI will eventually handle the bulk of coding work, Egnyte is planning for continuity: experienced engineers will still be needed to understand complex systems, shape architectures, and provide judgment on trade-offs. That, in turn, requires a steady flow of juniors gaining system knowledge and operational experience.

The company does expect productivity gains from AI—enough that net hiring may slow over time—but it is explicit that hiring will continue, both to scale the business and to cultivate the next generation of senior engineers.

How Egnyte’s teams actually use AI coding tools

Egnyte has standardized on a set of AI-assisted coding tools that are embedded into daily developer workflows. Across its more than 22,000 users, which include customers like NASDAQ, Red Bull and BuzzFeed, Egnyte’s own engineering organization is using these tools to support both its core platform and newer AI-powered features such as customer-facing copilots and customizable AI agents.

The toolset spans multiple vendors and interfaces, including Claude Code, Cursor, Augment and a Gemini command-line interface (CLI). Developers use them for a range of well-bounded, assistive tasks rather than for fully automated change generation.

Common use cases include:

• Code comprehension and discovery: Egnyte’s codebase—heavy on Java and varied libraries and versions—is large and complex. AI tools help developers, especially those unfamiliar with a particular domain, understand how components fit together and where relevant logic lives.
• Smart search and lookup: Instead of manual, multi-step greps or browsing through repositories, developers can query the AI layer to surface examples, patterns, or specific implementations.
• Peer-like guidance: Jassal describes these tools as strong for “peer-to-peer programming,” helping new developers get the lay of the land and enabling experienced ones to navigate unfamiliar parts of the stack more quickly.

“We have a pretty big code base, right?” Jassal said. “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 teams have also started using AI to generate automatic pull request (PR) summaries that capture the “what,” “how,” and “why” behind proposed changes. That accelerates code reviews by making intent and scope easier to grasp at a glance.

Crucially, Egnyte draws a hard line around responsibility and control. “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 emphasized. “I would not trust AI to commit to the production code base.”

All commits continue to pass through human review and security validation. Items that raise concerns are escalated to senior engineers. Developers are explicitly warned about the risks of “autopilot mode”—accepting AI output without scrutiny—especially because models may not have seen enough examples of Egnyte-specific infrastructure or patterns during training.

Another expanding but carefully monitored area is unit testing. AI can help generate tests and run components in isolation to verify basic behavior. Jassal characterizes this as incremental, not transformative: “At the end of the day, it is a productivity improvement tool. It is really a continuation, it’s like any other tool, it’s not some magic.”

Compressing the learning curve from junior to senior

Egnyte is using AI tools most aggressively where they can reshape the speed and shape of developer growth. The company expects a “much faster learning curve” from junior to mid-level engineers, enabled by AI’s ability to clear traditional early-career roadblocks.

For a new hire dropped into a large, mature codebase, the hardest parts have historically been:

• Finding the right entry points in sprawling repositories
• Understanding legacy design decisions and implicit assumptions
• Decoding scattered documentation and tribal knowledge

Egnyte’s AI stack helps on all three fronts. New developers can use AI-driven search and explanation to rapidly understand modules, trace call flows, and identify relevant patterns without waiting for synchronous guidance from a busy senior engineer. Tools assist in dissecting requirements, generating initial tests and scaffolding, and surfacing examples of similar prior work.

“Many of the traditional roadblocks are navigated faster these days with AI; for example, understanding the codebase, dissecting requirements, auto-testing,” Jassal said. “This faster track allows our talented junior hires to progress more quickly and provide higher value to the company sooner.”

At the same time, Egnyte is careful to frame AI as an accelerator, not a substitute for experience. Senior engineers still own cross-cutting responsibilities—such as writing architecture notes that span the platform and require a holistic, system-level view. Those artifacts depend on deep product context, trade-off awareness, and organizational history that AI cannot infer on its own.

The net effect is not to flatten career progression, but to raise expectations: juniors are expected to reach mid-level impact faster, given the support that AI offers. That, in turn, shifts the bar for what it means to be a senior engineer—placing even more emphasis on architecture, judgment, and mentoring.

Redefining the junior engineer role beyond “just writing code”

Egnyte’s junior engineers are not confined to narrow implementation tasks. Their day-to-day responsibilities are intentionally distributed across the full software development lifecycle, with AI acting as an enabler rather than a gatekeeper.

According to Jassal, early-career developers are involved in:

• Requirement analysis: Participating in the early phases of software engineering, understanding business and technical needs, and helping shape implementation plans.
• Deployment and productization: Working on how features move from development into production environments, and what is required to make them robust and operable.
• Post-deployment maintenance: Engaging in debugging, support, and ongoing improvements once features are live.

These activities require what Jassal calls “Egnyte-specific tacit knowledge and experience,” which is transmitted primarily by senior engineers. AI can surface patterns and past examples, but it cannot replace lived experience with the company’s platform, customers and operational realities.

This distribution of responsibility shapes how AI is introduced. Tools help with code comprehension, testing, and exploration, making it easier for juniors to contribute meaningfully in more phases of the lifecycle earlier in their tenure. Meanwhile, senior engineers focus on areas that AI is not well suited for: system-wide design, architectural decision-making, and the creation of cross-cutting documentation that ties components together.

As a result, AI becomes part of the apprenticeship model. Juniors learn not just “how to get code to work,” but how to operate within a full product lifecycle—while also learning when and how to trust, verify, or override AI suggestions.

Managing culture, expectations and adoption across experience levels

Egnyte’s strategy also acknowledges the human side of AI adoption in engineering organizations. Different cohorts of developers come with different expectations and levels of enthusiasm.

New entrants to the workforce, Jassal noted, are typically eager to experiment with the latest tools. “It’s always the case that people coming straight into the workforce are much more excited about trying new things,” he said. AI aligns with that mindset—but expectations still need to be “colored with reality” so juniors understand both the limitations of the tools and the enduring importance of foundational engineering skills.

Senior engineers often present the opposite challenge. Many have tried earlier generations of tools and been disappointed, which can lead to skepticism or slower uptake. Egnyte responds with incremental introduction rather than mandates, allowing senior developers to experience concrete benefits in their own workflows.

Jassal sees value in this tension. “The senior people, having been burnt multiple times, bring that perspective,” he said. “So both [types of engineers] play an important role.” Juniors help pull the organization toward new capabilities, while seniors provide guardrails, risk awareness, and critical evaluation of AI output.

On the cultural front, Egnyte pushes back against narratives that oversell AI’s autonomy or inevitability. Jassal describes claims that human coders will become obsolete as “really hyped by folks who want to sell you tokens.”

He is similarly cautious about buzzwords like “vibe coding,” preferring more grounded terminology like “AI assisted coding,” in which programmers remain in a self-driven loop: generating code, analyzing exceptions, correcting, and scaling. That framing reinforces that engineers, not models, own the outcome.

What Egnyte’s model implies for engineering leaders

Egnyte’s experience offers several concrete lessons for technical decision-makers evaluating how to fold AI into their own engineering organizations.

First, AI-assisted coding does not have to be a headcount reduction strategy. At Egnyte, AI is explicitly framed as infrastructure: a layer that increases the throughput and impact of human engineers while preserving human accountability for production changes.

Second, the company treats its junior pipeline as a strategic asset, not an expendable layer. AI is used to compress learning curves, enabling junior hires to become productive faster and reach mid-level capabilities sooner. That, in turn, strengthens the future pool of senior talent rather than undermining it.

Third, governance and culture matter as much as tooling. Egnyte keeps humans in the loop for all production commits, routes red-flagged issues to experienced engineers, and explicitly warns against blind trust in AI output. It balances enthusiasm from junior engineers with prudence from senior ones, and it introduces tools in ways that respect prior experience and skepticism.

Finally, Egnyte’s stance is that AI will reshape how engineering talent is developed, not whether it is needed. “We are not just hiring for scale, but to develop the next generation of senior developers and inject fresh perspectives into our development practices,” Jassal said.

For organizations that view AI primarily as a way to cut engineering roles, the long-term risk is a hollowed-out talent pipeline with fewer developers gaining the breadth of experience required to lead complex systems. By contrast, companies that adopt AI as an assistive layer—much like Egnyte—can move faster today while investing in the expertise they will rely on tomorrow.

In Egnyte’s model, AI-assisted coding raises the bar for what teams can deliver, accelerates the growth of junior engineers, and clarifies the enduring value of human judgment, creativity and accountability in software development.