NexGen Software, a prominent product-based SaaS company specializing in enterprise HR tech solutions with a workforce of 800 employees, finds itself at a critical juncture following the discovery of one of its top backend engineers, Arjun Nair, engaging in extensive freelance work, including for a direct competitor. The incident has sparked a heated internal debate within the company’s leadership, pitting the imperative of protecting intellectual property and maintaining employee loyalty against the realities of a rapidly evolving employment landscape characterized by the rise of the gig economy and a more transactional view of work. The core issue revolves around a vague company policy on outside employment, leaving HR with a profound decision that could set a significant precedent for the organization and the broader tech industry.
The Unveiling of a Conflict: A CTO’s Discovery
Arjun Nair, a highly valued backend engineer, has been a cornerstone of NexGen Software’s technical team for over three years. His contributions have been instrumental in building core features of the company’s flagship HR tech product. Known for consistently delivering ahead of deadlines and actively mentoring junior developers, Nair was widely regarded as being on a fast track to a lead architect role, a testament to his exceptional skill and dedication. His role required deep understanding of NexGen’s proprietary architecture, strategic product roadmap, and problem-solving methodologies.
The situation came to light during a routine LinkedIn scroll by NexGen’s Chief Technology Officer (CTO). The CTO discovered Arjun Nair’s profile listed him not only as a NexGen employee but also as a "Freelance Software Consultant." Further investigation revealed a separate website advertising Nair’s services, which included high-demand specializations such as API development, cloud architecture, and database optimization, with listed rates ranging from Rs 5,000 to Rs 8,000 per hour.
A more comprehensive internal review unearthed concerning details: Arjun had reportedly been undertaking freelance projects for at least a year, primarily during nights and weekends. While some clients operated in adjacent industries, a particularly alarming discovery was that one of his clients was a direct competitor building a similar HR tech product. This revelation immediately escalated the matter from a potential policy breach to a severe conflict of interest in the eyes of many within NexGen’s leadership.
When confronted with these findings, Arjun Nair remained unapologetic, articulating his defense: "I work 9 to 6 for NexGen. After that, my time is mine. I am not using company resources. I am not sharing IP. I am simply using my skills to earn additional income. What is the problem?" His response, while asserting personal autonomy, underscored the fundamental clash between traditional employment expectations and contemporary employee perspectives.
Internal Discord and Policy Ambiguity
The fallout from Arjun’s revelation created a significant rift within NexGen’s senior leadership. The CTO, representing the technological and competitive interests of the company, advocated strongly for immediate termination. "This is a conflict of interest. He is working for a competitor. Even if he is not sharing code, he is sharing knowledge – patterns, architecture thinking. It is a breach of trust," the CTO asserted, emphasizing the subtle yet profound ways intellectual capital can be transferred, even without explicit data sharing. The CTO’s stance highlighted the critical importance of protecting NexGen’s proprietary knowledge and competitive edge in the fast-paced HR tech market.
Conversely, the Head of Engineering expressed a more pragmatic, talent-centric view, arguing against such a severe punitive measure. "Arjun is one of our best. Developers moonlight everywhere, and that is the reality today. If we fire him over this, we lose talent and look draconian. We should update the policy and move on," the Head of Engineering contended. This perspective reflects the intense competition for skilled tech talent and the potential negative employer branding that could result from perceived harshness. The argument also acknowledges the growing prevalence of side gigs in the tech sector, suggesting that strict adherence to traditional exclusivity might be counterproductive for talent retention.
Adding another layer of complexity, NexGen’s Human Resources department reviewed Arjun Nair’s employment contract. The clause pertaining to outside employment was found to be notably vague, stating merely: "Employees should not engage in activities that conflict with the company’s interests." Critically, it did not explicitly prohibit freelancing or specify conditions for external work. This lack of explicit guidance placed HR in an unenviable position, caught between conflicting leadership directives and an ambiguous legal framework within the company.
The Broader Context: The Rise of the "Side Hustle" Economy
Arjun Nair’s case is not an isolated incident but rather a microcosm of a larger societal and economic shift towards the "side hustle" or "gig economy." Over the past decade, driven by factors such as technological advancements, the accessibility of remote work, economic pressures like inflation, and a growing desire for financial independence and skill diversification, moonlighting has become increasingly common, particularly in the knowledge-based industries like software development.
Recent analyses suggest that a significant percentage of tech professionals, sometimes estimated to be as high as 30-40% in some regions, engage in external projects or entrepreneurial ventures outside their primary full-time roles. This trend has been further accelerated by the COVID-19 pandemic, which normalized remote work and blurred the lines between professional and personal time, offering more opportunities for individuals to pursue additional income streams or passion projects.
For many employees, moonlighting is seen as a way to supplement income, develop new skills, explore entrepreneurial ambitions, or simply to feel more in control of their professional lives. The traditional idea of a single, lifelong employer demanding exclusive loyalty has been gradually eroding, replaced by a more transactional view of employment where individuals seek multiple income streams and diverse professional experiences. Companies, particularly in competitive sectors like HR tech, are grappling with how to adapt to this evolving mindset without compromising their core business interests, intellectual property, and organizational culture. The challenge for NexGen, therefore, extends beyond Arjun Nair to how it will define and manage employee engagement in this new paradigm.
Expert Perspectives: Navigating the Ethical and Practical Minefield
To shed light on this complex dilemma, NexGen sought insights from seasoned HR leaders, whose varying perspectives underscore the multifaceted nature of the challenge.
Pradyumna Pandey, a Senior HR leader, emphasized the principle of primary commitment and the unique nature of creative work in software development. "From my perspective, the first principle is respect for the employee’s primary commitment. When someone joins an organisation full-time, their first responsibility is towards that role and the value they are expected to create there," Pandey stated. He drew a parallel with manufacturing, where outside work is often prohibited due to safety risks, arguing that in IT, the risk pertains to "intellectual capital and creative energy." Pandey elaborated, "Software development is a creative discipline. Ideas don’t always emerge between 9 a.m. and 6 p.m.; they come during leisure time, reflection, and even late at night. If an employee is using that creative bandwidth to build solutions for someone else – especially in adjacent industries – it inevitably dilutes the attention available for the primary employer."
However, Pandey critically pointed to NexGen’s policy clarity, or lack thereof. "That said, the key issue in NexGen’s case is policy clarity. If the employment contract explicitly prohibited outside engagements, Arjun’s actions would clearly be a breach of trust. But if the clause is vague, the organisation must also take responsibility for not communicating its expectations clearly." He cited academia as an example where clear policies on outside assignments, coupled with disclosure requirements, allow for external engagements without conflict. Concluding his stance, Pandey affirmed, "So, in this case, I would not support moonlighting in principle because it distracts from the primary role. However, if the company has not explicitly prohibited it, termination would send the wrong signal. When policies are unclear, punishment is unfair. Organisations must first define clear rules on outside work before enforcing consequences."
Anil Mohanty, Group CHRO at Falcon Marine, presented a more unequivocal stance, asserting that moonlighting becomes unacceptable the moment it involves a conflict of interest, particularly with a competitor. "For me, the situation is very straightforward. Moonlighting becomes unacceptable the moment it creates a conflict of interest – especially when the employee works for a competitor," Mohanty declared. He dismissed the argument that a star performer should be treated differently, stating, "Whether someone is a star performer or an average contributor does not change that principle. If I am working for my organisation and at the same time helping a competing company build similar solutions, that is a direct conflict."
Mohanty also addressed the common defense of not sharing code or documents. "Many people argue that what they do after office hours is their personal matter. But employment is built on a relationship of trust and confidentiality. You may say you are not sharing code or documents, but how can anyone guarantee that knowledge, patterns, or best practices gained from your employer are not influencing your work elsewhere? Even if it happens unintentionally, it still compromises the organisation’s intellectual advantage." While acknowledging that some external engagements like advisory sessions might be acceptable, he drew a firm line at competitor involvement. "However, when the engagement is with a competitor, that is a clear breach. Talent is important, but no individual is indispensable. Organisations cannot compromise ethics simply because someone is a high performer… Moonlighting may be negotiable in some contexts, but conflict with a competitor is non-negotiable."
Chandrasekhar Mukherjee, another Senior HR leader, emphasized the legal, cultural, and ethical dimensions of the problem, arguing that exclusivity is inherent in full-time employment. "The first lens I apply to this situation is legality. A full-time employee is engaged by the organisation as a full-time resource. That is what ‘FTE’ means. When someone accepts full-time employment, they cannot simultaneously work elsewhere in a similar capacity without permission," Mukherjee explained, underscoring the legal expectation of full commitment. He noted that even in cases of legitimate external roles like guest lectures, professionals typically seek prior approval, stressing the importance of transparency.
Beyond legality, Mukherjee highlighted the profound impact on organizational culture. "But the bigger concern here is not just legality – it is culture and precedent. Organisations are built not only on performance metrics but also on behavioural standards. If a high-performing employee is allowed to break those standards because he is valuable, the message to the rest of the organisation is simple: rules apply selectively. That is the fastest way to weaken organisational culture." He reinforced the danger of working for a competitor, stating, "Whether or not Arjun shares code is irrelevant. He carries with him knowledge about architecture, product strategy, and problem-solving approaches. Even informal conversations can transfer competitive insights." Mukherjee concluded with a strong assertion about the long-term health of the company. "Some may argue that losing a star performer would hurt NexGen. But organisations must think long-term. Culture is defined by the actions taken in difficult moments. If leadership tolerates such behaviour, others will inevitably follow. Soon, employees may start prioritising their side work over the organisation’s goals. In my view, this is not just a policy issue – it is an ethical one. Organisations must stand firm on such matters. Allowing a top performer to break rules creates a dangerous precedent. Culture must outweigh individual brilliance."
Implications for NexGen and the Broader Workforce
The dilemma facing NexGen is fraught with significant implications, both immediate and long-term. Terminating Arjun Nair, despite his high performance, would send a strong signal about the company’s commitment to loyalty and the protection of its competitive advantage. This could deter other employees from engaging in similar activities and reinforce a traditional view of employment. However, such a decision carries substantial risks: the loss of a critical talent, potential damage to employer brand if the termination is perceived as overly harsh given the vague policy, and even potential legal challenges if Arjun were to argue unfair dismissal based on the lack of explicit prohibition. Furthermore, in the current competitive tech talent market, replacing an engineer of Arjun’s caliber could be costly and time-consuming.
Conversely, choosing to retain Arjun while clarifying the policy moving forward also presents its own set of challenges. It might be seen as a lenient approach that prioritizes talent retention over strict adherence to ethical boundaries, potentially encouraging other employees to engage in similar side ventures. This could make it harder for NexGen to enforce stricter policies in the future and could lead to a perceived erosion of trust and exclusivity. The risk of subtle knowledge transfer or competitive intelligence leakage would persist, even with updated policies, as it is inherently difficult to monitor and prove. The psychological impact on other employees, particularly those who strictly adhere to their full-time commitments, could also be negative, fostering a sense of unfairness.
Beyond NexGen, Arjun’s case highlights a fundamental tension in the modern workforce: can organizations still expect exclusive loyalty in an era where talent increasingly views employment as transactional and actively seeks multiple income streams? The traditional employment contract, often implicitly built on an assumption of exclusivity and undivided attention, appears to be struggling to keep pace with the realities of the gig economy and changing employee expectations. Companies are increasingly pressured to either explicitly prohibit moonlighting, develop nuanced policies requiring disclosure and approval, or embrace a more flexible model that redefines "full-time employment" to accommodate side hustles under strict conditions.
The decision NexGen makes will not only define its internal culture and talent management strategy but will also contribute to the ongoing industry-wide conversation about the future of work. It forces a re-evaluation of how organizations balance their need for competitive advantage and intellectual property protection with the evolving aspirations and economic realities of their highly skilled workforce. The core question remains: in a world where talent seeks autonomy and diversification, how can companies foster loyalty and commitment while adapting to a new employment paradigm? The answer, for NexGen and countless other companies, lies in navigating this complex landscape with clear communication, fair policies, and a forward-looking vision for employee engagement.
