The experience of working at Infosys is shaped by forces that no offer letter mentions. The daily culture of a project team, the dynamics of being on bench between assignments, the process and politics of getting selected for an onsite posting, the mechanics and emotional weight of resigning, and the rules around moonlighting and internal movement all determine what it actually feels like to build a career at this company. These are the things people learn after joining, sometimes the hard way.
This guide covers all of it with the honesty and specificity that someone about to join, currently working at, or planning to leave Infosys actually needs. It maps the day-to-day work culture across different project types and locations, explains how project teams and manager relationships are typically structured, details how onsite deputation decisions are made and what the experience involves, describes exactly what happens when you are on bench and how to navigate that period well, walks through the complete resignation process step by step including notice period negotiation, exit interviews, experience letters, PF settlement, and gratuity, explains the service agreement and bond clause in plain terms, covers what happens if the bond is broken, describes the moonlighting policy and its enforcement, and explains how internal transfers work through the IJP system.
Table of Contents
- The Day-to-Day Work Culture at Infosys
- How Teams and Projects Are Structured
- The Manager-Employee Relationship
- Work Culture Across Different Project Types
- Work Culture Across Locations
- Onsite Deputation: How It Works
- Selection Criteria for Onsite Roles
- Visa Process and Pre-Departure Preparation
- Client Expectations and Compensation During Onsite
- The Bench Experience: What Actually Happens
- How to Get Off Bench Faster
- The Complete Resignation Process
- Notice Period Negotiation
- Exit Interview, Experience Letter, and Relieving Letter
- PF Settlement and Gratuity
- The Service Agreement and Bond Clause
- What Happens If You Break the Bond
- Moonlighting Policy at Infosys
- Internal Transfer Mechanisms
- Frequently Asked Questions
The Day-to-Day Work Culture at Infosys
The culture at Infosys is not one thing. It is a mosaic of micro-cultures shaped by project type, client industry, business unit, location, and team composition, all operating within a shared framework of company values, processes, and governance standards. Understanding this mosaic is more useful than accepting any single description of what Infosys culture is like.
At the foundation, Infosys has a well-documented set of values captured in the acronym C-LIFE: Client Value, Leadership by Example, Integrity and Transparency, Fairness, and Excellence. These values are not merely marketing language. They were embedded into the company’s culture during its founding years and have persisted as genuine organizational touchstones. Employees who violate these values, particularly around integrity and transparency, face consequences that are more serious than at companies where values are treated as aspirational rather than operational.
In practice, this values orientation manifests in a few consistent cultural features across virtually all parts of Infosys. Governance standards are high: financial reporting, project status communications, and client commitments are expected to be accurate. Covering up a project problem or misleading a client or a senior manager is treated as a serious integrity violation. The culture of straight-talking upward, of not hiding bad news, is more pronounced at Infosys than at some peers and is one of its most distinctive cultural features.
The emphasis on client value creates a service orientation that pervades the culture. Infosys employees are expected to think of themselves as representing the company’s capabilities and values in every client interaction. This is not abstract; it shapes how meetings are run, how emails are written, and how project escalations are handled. Employees who adopt this client-service mindset early in their career tend to advance faster than those who treat client work as a contractual obligation to be fulfilled minimally.
The Culture of Learning:
Infosys has historically differentiated itself from peers through investment in employee learning and development. The Lex learning platform, the Mysore training campus, the certification support programs, and the internal knowledge-sharing communities are all expressions of this investment. The culture expects employees to engage with continuous learning throughout their careers, not just during the initial training period.
Employees who actively use Lex, pursue certifications relevant to their project domain, and contribute to internal knowledge sharing communities signal a professional seriousness that is noticed and valued in performance evaluations. Conversely, employees who disengage from learning after the initial training period find themselves falling behind both in skill development and in the profile signals that matter for appraisals and promotions.
The Culture of Accountability:
Project delivery accountability is genuinely high at Infosys compared to IT services norms. Deadlines are treated as real commitments, not aspirational targets. Status reporting is expected to be accurate even when the status is bad. Project managers and Delivery Managers who manage to hide problems until they become crises are not rewarded; those who surface issues early and propose solutions are.
For individual contributors, this accountability culture means being expected to own the quality of their work output, not just the volume of tasks completed. An SE who marks a task complete when it has unresolved defects is not in compliance with the delivery standards; discovering this through a client test failure rather than through internal quality checks is a significant failure. Building the habit of personal quality accountability early in the Infosys career is one of the most valuable professional investments a new joiner can make.
Work-Life Balance Reality:
The work-life balance experience at Infosys varies significantly by project type and phase. On stable, mature projects in a steady-state delivery mode, working hours are typically predictable: nine to ten hours a day with reasonable boundaries on evenings and weekends. On projects in active development phases, approaching critical deadlines, or managing a client escalation, hours can extend significantly, with evening and weekend work becoming the norm during crunch periods.
The Infosys culture does not explicitly glorify overwork the way some technology company cultures do, but the client-service model creates implicit pressure to meet client commitments even when that requires extended hours. Employees who want to maintain work-life balance should be explicit with their manager about sustainable working norms and should raise concerns about unsustainable work patterns through the appropriate channels rather than silently absorbing them.
The Diversity of the Infosys Workforce:
Infosys employs people from virtually every state in India and, through its global operations, from many countries. The Mysore training experience is specifically designed to bring this diverse workforce to a common foundation, but the diversity itself enriches the day-to-day work experience in ways that are often underappreciated.
Working alongside colleagues who bring different regional perspectives, different educational backgrounds, and different problem-solving approaches develops interpersonal adaptability that is genuinely valuable in a global client-service career. Infosys employees who engage with this diversity rather than clustering exclusively within their own regional or linguistic group build broader professional networks and more flexible working styles.
How Teams and Projects Are Structured
The organizational unit at Infosys that most directly shapes day-to-day work experience is the project team. Understanding how projects are structured, how roles within teams are defined, and how work flows through the team provides the context for making the most of project assignments.
The Standard Project Structure:
A typical Infosys project team is organized hierarchically, with the Delivery Manager (DM) at the top of the delivery team, followed by one or more Technology Leads (TLs) who own specific technical workstreams, Technology Analysts (TAs) who lead modules within workstreams, and Senior Systems Engineers (SSEs) and Systems Engineers (SEs) who perform the execution work.
In smaller engagements, the DM may also function as the TL for some workstreams. In larger programs, there may be multiple layers of management above the DM on the Infosys side (a Program Manager, an Account Manager, or both), and the client itself may have a complex governance structure with multiple stakeholders.
The Client Interface:
The interaction between the Infosys team and the client team is one of the defining features of the project work experience. In most Infosys engagements, the Infosys team operates in a hybrid structure where the client provides the business requirements, the acceptance criteria, and the production environment, while Infosys provides the development, testing, and sometimes the operations team.
How directly individual contributors interact with the client depends on the project model and on the individual’s designation. SEs and SSEs at the early career stage typically have limited direct client interaction; their work is reviewed by TAs and TLs before it reaches the client. TLs and above typically interact with client technical counterparts regularly. Senior DMs and Program Managers interact with client senior leadership.
Employees who want more client exposure than their current role offers should discuss this explicitly with their TL or DM. Most project managers are willing to provide junior team members with some client-facing opportunities when the team’s relationships are stable and the individual has demonstrated readiness.
Agile vs Waterfall Delivery:
The delivery methodology used by any given project significantly shapes the daily work experience. Infosys has moved strongly toward Agile delivery in recent cycles, reflecting client preferences and industry best practices. On Agile projects, the work is organized in sprints (typically two-week periods) with daily standups, sprint reviews, and retrospectives. This rhythm creates more frequent checkpoints, more visibility into progress, and more structured opportunities for course-correction than waterfall delivery.
On waterfall projects, which still exist in some client contexts, the work is organized into longer phases (requirements, design, build, test, deploy) with less frequent formal checkpoints. Waterfall projects often feel less dynamic and can involve longer periods of steady execution without the sprint rhythm’s built-in variety.
Understanding the delivery methodology of any project you are considering joining helps set appropriate expectations for what daily work will feel like.
The Offshore-Onsite Split:
Many Infosys client engagements use a split model where part of the team is based in India (offshore) and part is based at or near the client location (onsite). The offshore-onsite split creates specific coordination challenges: time zone differences, communication delays, and the different context between team members who have direct client access and those who do not.
For India-based employees on these hybrid teams, the experience is shaped by the quality of the communication and handoff processes between onsite and offshore. Good projects invest in clear requirements documentation, structured daily handoffs, and regular video calls that keep the offshore team aligned with client priorities. Poor projects leave the offshore team guessing about context, creating rework and frustration.
The Manager-Employee Relationship
The single most significant variable in the day-to-day Infosys work experience is the relationship with the immediate manager. This is true across all levels and all project types. A supportive, engaged manager who provides clear direction, advocates for the team, and creates development opportunities produces a dramatically better work experience than a disengaged or adversarial manager, regardless of how interesting or dull the underlying project work is.
What Managers Are Accountable For:
At the TL level and above, managers at Infosys are accountable for team delivery quality, team performance, team development, client relationship health, and project financial performance. These are competing priorities: a manager under pressure to improve project margins may reduce the investment in team development that a less pressured quarter would allow. A manager managing a difficult client relationship may have less bandwidth for regular one-on-ones with individual team members.
Understanding the pressures your manager is navigating helps interpret their behavior. A manager who has been short on one-on-ones during a project crisis week is not necessarily disengaged; they may be managing an escalation that required all their bandwidth. A manager who consistently fails to have developmental conversations across normal project periods is a different situation.
Building a Productive Manager Relationship:
The responsibility for building a productive manager relationship does not rest entirely with the manager. Employees who make themselves easy to manage, who communicate proactively about their work status and any blockers, who deliver on commitments without needing to be chased, and who bring their manager useful information (about project risks, about client feedback, about team dynamics) are consistently better-supported than employees who operate as black boxes.
Specific habits that build the manager relationship: scheduled regular one-on-ones (not waiting for the manager to initiate), bringing a written agenda to these one-on-ones so the conversation is productive, sharing the self-assessment draft with the manager before it is formally submitted to get alignment, and communicating career aspirations clearly so the manager can create relevant opportunities rather than guessing about what the employee wants.
When the Manager Relationship Is Difficult:
Not every manager relationship works. Managers who are actively unhelpful, who take credit for team members’ work, who provide inconsistent feedback, or who create hostile team environments represent a genuine problem rather than a temporary inconvenience. The appropriate response to a genuinely difficult manager situation is not to silently suffer or to resign: it is to document the specific issues, use Infosys’s HR escalation channels, and pursue an IJP move to a different project and manager as the most effective resolution.
Resigning from Infosys because of one bad manager, without first attempting an internal move, is typically a suboptimal outcome. The size of Infosys’s project portfolio means there are almost always better manager-project fits available internally. Using the IJP system to escape a difficult manager situation is not disloyalty; it is a legitimate use of the tools the company provides for exactly this scenario.
Work Culture Across Different Project Types
The culture varies significantly by the type of project work being done. Understanding these differences helps employees anticipate what joining a specific stream or project type will actually feel like.
New Development Projects:
Projects that involve building new software systems or significant new features tend to have the most energetic and engaging cultures. There is a clear visible output to the work, technical decisions have real consequences, and the team is often working toward a defined and visible milestone. New development projects also tend to involve more creative problem-solving and more variety in the technical challenges encountered.
The pressure on new development projects, particularly those with fixed-price contracts or hard launch deadlines, can be intense. Crunch periods, where the team works extended hours to meet a deadline, are more common on new development projects than on maintenance work. The post-launch satisfaction of seeing a new system go live, however, is a rewarding experience that maintenance work does not typically offer.
Application Maintenance and Support:
Application maintenance and support (AMS) projects, which involve keeping existing systems running, fixing defects, and making incremental changes, are the bread and butter of Infosys’s delivery portfolio. The culture on these projects is typically steadier and less intense than new development: the work follows predictable rhythms of ticket resolution, release management, and periodic minor enhancement delivery.
AMS work is often described by employees as less intellectually stimulating than new development, which is sometimes accurate. However, AMS projects on complex, business-critical systems at large enterprises involve significant technical depth: understanding a system that has been built over many years, diagnosing issues in a codebase of millions of lines, and making changes that must not break existing functionality while delivering new value requires a level of technical maturity that new development work does not always develop.
AMS project culture also tends to have more predictable working hours than new development, which suits employees who value work-life balance above work variety.
Digital Transformation Projects:
Digital transformation projects, which involve migrating clients from legacy systems to modern cloud-based or digital platforms, represent one of Infosys’s fastest-growing project categories. The culture on these projects is typically energetic and technology-forward: teams work with modern cloud platforms, microservices architectures, DevOps tooling, and data analytics platforms.
The challenge of digital transformation projects is managing the complexity of changing large, business-critical systems while keeping them operational. The technical and organizational complexity is high, and the pace of change can be demanding. Employees who enjoy working in complex, fast-evolving environments and who are comfortable with ambiguity tend to thrive on these projects.
Testing and Quality Assurance Projects:
Testing-focused projects have a distinct culture shaped by the nature of QA work: systematic, process-oriented, and focused on defect prevention rather than feature delivery. Testing culture at Infosys has evolved significantly with the growth of automation testing; modern QA projects are less about manual test case execution and more about building and maintaining automated test suites that run in CI/CD pipelines.
Testing teams at Infosys are sometimes undervalued relative to development teams in the informal project culture, which is an industry-wide bias rather than an Infosys-specific one. QA professionals who develop strong automation skills (particularly in tools like Selenium, Cypress, or Appium) and who can contribute to the DevOps pipeline as well as the testing function build more compelling profiles than those who remain focused on manual testing only.
Infrastructure and Cloud Operations Projects:
Infrastructure and cloud operations projects involve managing the technology platforms on which client applications run. This includes cloud infrastructure management, database administration, network management, and increasingly Kubernetes cluster management, cloud cost optimization, and security operations.
The culture on infrastructure projects tends to be more operational and reactive than on development projects: the team is always on standby for production issues, monitoring systems continuously, and responding to incidents when they occur. The on-call rotation and the unpredictability of production incidents can affect work-life balance more significantly on infrastructure projects than on pure development work.
For employees who find operational challenges engaging, who enjoy the combination of technical depth and real-time problem-solving, and who want to develop cloud and DevOps skills, infrastructure projects at Infosys can be genuinely rewarding. The market demand for cloud and infrastructure expertise is high, making the skills developed on these projects highly marketable both internally and externally.
Work Culture Across Locations
Infosys operates delivery centers across multiple cities in India, and the work culture varies by location in ways that go beyond just the cost of living differences.
Bangalore:
The Bangalore delivery centers, particularly in areas like Electronic City, Whitefield, and Manyata Tech Park, house the largest concentration of Infosys employees in India. The culture in Bangalore is heavily influenced by the broader Bangalore technology ecosystem: the density of technology companies, the large population of experienced technology professionals, and the vibrant startup and product company community all create a culture of ambition and technical energy that permeates even the traditional IT services work.
Infosys’s headquarters are in Bangalore, which also means the company’s leadership and central functions are proximate to the Bangalore delivery centers. This creates more opportunities for involvement in company-wide initiatives, internal events, and leadership visibility than at other locations.
The cost of living in Bangalore, particularly housing, commute times, and general urban costs, is the highest of all Infosys delivery locations in India. Employees in Bangalore need to budget carefully on the standard SE salary; the financial calculus improves significantly at SSE and above levels.
Hyderabad and Pune:
Hyderabad and Pune are the second and third largest Infosys delivery locations and offer a work culture that is slightly less intense than Bangalore while still being technologically sophisticated. Both cities have strong technology ecosystems, good engineering talent pools, and growing digital and cloud project portfolios at Infosys. The cost of living is lower than Bangalore, making the same salary go further in practical terms.
Hyderabad’s Infosys campus in the HITEC City area is large and well-equipped. Pune’s Hinjewadi and Kharadi offices host significant Infosys operations. Both locations offer good quality of life for technology professionals relative to the metro cost of living tradeoff.
Chennai:
Chennai’s Infosys operations are substantial and have a specific character shaped by the city’s cultural and professional norms. Chennai delivery centers are known for strong technical depth, particularly in software engineering and banking technology work. The work culture in Chennai tends to be slightly more formal and process-oriented than in Bangalore. The city’s lower cost of living relative to Bangalore is a positive for employees, and the Infosys campus infrastructure in Chennai is well-developed.
Tier-2 and Smaller Centers:
Infosys also operates offices in smaller cities including Bhubaneswar, Chandigarh, Mangalore, and others. These centers typically house specific project teams or centers of excellence rather than broad delivery operations. The work culture at smaller centers is often more tightly knit and community-oriented, with fewer anonymous large-campus dynamics. The technology exposure at smaller centers tends to be more limited than at the major metros, which is a career consideration for employees who want to work on the most technically demanding projects.
Onsite Deputation: How It Works
The onsite deputation system at Infosys is the mechanism through which India-based employees are sent to client locations overseas for defined periods. Understanding how this system works from the inside is essential for any employee who wants to maximize their chances of receiving an onsite opportunity.
The Business Model of Onsite Staffing:
From Infosys’s commercial perspective, onsite staffing involves billing the client at rates that are significantly higher than the rates for offshore delivery. Onsite positions are therefore in high demand from the commercial side: they generate more revenue per person than offshore delivery does. However, the costs associated with onsite staffing (the overseas allowance paid to the employee, visa processing costs, travel, and accommodation support) are also higher, so the margin on onsite work is not uniformly better than offshore.
From the client’s perspective, onsite resources are available for direct interaction, can attend meetings in person, and can work within the client’s time zone. The value of onsite presence is highest for roles that require daily collaboration with client team members, for work that involves access to systems not available remotely, and for relationship management activities that benefit from face-to-face contact.
How Onsite Needs Are Identified:
Onsite staffing needs arise at the project level when the DM or Program Manager assesses that specific roles require in-person presence. This assessment is based on client preferences, project phase requirements, and the commercial terms of the engagement. Not every project has onsite positions; some engagements are entirely offshore delivery. Projects with significant client-side collaboration, transformation work, or relationship management components are most likely to have onsite positions.
Once a need is identified, the DM works with the Resource Management Group (RMG) and the onsite Project Manager (if there is already a team onsite) to identify suitable candidates from the India-based team.
The Duration of Onsite Postings:
Onsite stints range from short assignments of two to six weeks (typically for specific project phases, review meetings, or knowledge transfer) to long-term postings of one to three years (for continuous client relationship management or large program management). The nature of the onsite work shapes the duration: short-term stints are task-specific, while long-term postings involve sustained client relationship ownership.
The most career-significant onsite experiences are typically those that last six months or more, because the depth of client relationship and project ownership developed over a longer period creates the career evidence that promotion decisions rely on. Short onsite trips, while valuable for exposure, do not build the same depth of client management credibility as sustained long-term postings.
Selection Criteria for Onsite Roles
The selection process for onsite deputation is one of the more consequential and least transparent processes in the Infosys employee experience. Understanding the actual criteria, rather than the informal assumptions most employees operate from, significantly improves the ability to position for onsite opportunities.
Technical Capability:
The foundation requirement for onsite selection is technical capability at a level appropriate for the role. The client environment is demanding: onsite resources work directly with client technical counterparts, participate in design reviews, and must resolve issues in real time without the support network available in the India office. Employees who are not yet technically ready for independent, client-facing technical work are not appropriate candidates for onsite placement, regardless of other factors.
The specific technical capability required depends on the role. A development lead onsite needs to be able to make architectural decisions and explain them to a client technical team. A testing lead onsite needs to be able to walk a client QA manager through the testing strategy and handle challenges to it. A business analyst onsite needs to be able to facilitate requirement discussions with business stakeholders who may not be technically sophisticated.
English Communication Readiness:
Onsite roles require professional English communication across multiple formats: verbal communication in meetings and informal discussions, written communication in emails and status reports, and presentation communication in formal review settings. Employees whose English communication is unclear, heavily accented in ways that impede comprehension, or inconsistent in professional register are not considered for onsite roles, regardless of technical capability.
This criterion is sometimes a sensitive topic. The intent is not cultural bias; it is a practical client service requirement. An Infosys resource working onsite at a client location who cannot communicate effectively in the client’s working language (almost always English for international clients) creates problems for the client relationship that reflect on Infosys’s delivery quality. The assessment is about communication effectiveness, not about English accent per se.
Employees who want to improve their communication readiness for onsite consideration should take advantage of the communication development resources in Lex, seek feedback on written communication from managers, and practice verbal communication in diverse settings within the workplace.
Professional Maturity and Client-Readiness:
Beyond technical and communication capabilities, onsite selection also evaluates what is sometimes described as “client-readiness” or professional maturity. This includes: the ability to represent Infosys professionally in all interactions, the judgment to handle ambiguous or sensitive situations without escalating unnecessarily, the self-management to work independently without the support infrastructure of the India office, and the interpersonal adaptability to build effective working relationships with client team members from different cultural backgrounds.
These qualities are evaluated informally through the manager’s and DM’s observations of the employee in the project context. Employees who handle difficult situations well, who communicate professionally at all times, and who demonstrate good judgment in their current role build the reputation that leads to onsite nomination.
Visa Eligibility:
A practical constraint on onsite selection is visa eligibility. For the US market (the largest destination for Infosys onsite deputation), the primary visa types used are H-1B (for specialty occupation workers) and B-1 (for business visitors on shorter stints). H-1B visas are subject to an annual lottery and the application process is lengthy; employees who have not yet gone through H-1B processing or who have had previous visa complications may face delays in onsite deployment even when otherwise ready.
Employees who want to maximize their onsite options should ensure their passport is valid well in advance, understand the visa categories applicable to their role, and be ready to initiate visa documentation as soon as an opportunity is identified.
Timing and Business Need:
Even a fully qualified candidate cannot be sent onsite if there is no open position that matches their profile. Onsite opportunities are driven by client need, not by employee readiness. Employees who have done everything right in terms of preparation may still wait for the right project alignment. Communicating clearly to the DM and RMG that an employee is ready and interested in onsite opportunities ensures they are in the consideration set when needs arise.
Visa Process and Pre-Departure Preparation
The visa and pre-departure process for Infosys onsite deputation is handled through Infosys’s immigration team, which coordinates with the relevant embassy or consulate and provides the documentation required for visa applications.
The H-1B Visa Process:
For long-term US onsite postings, the H-1B visa is the primary category. The H-1B application requires employer sponsorship, a prevailing wage determination, a Labor Condition Application (LCA) filed with the US Department of Labor, and the actual visa petition filed with USCIS. The process is lengthy: initiation to approval can take several months, and the annual cap system means that not all petitions are approved in any given year.
Infosys files H-1B petitions as part of its ongoing US staffing requirements. Employees who are nominated for long-term US postings are enrolled in the H-1B process by the immigration team. Employees should provide accurate and complete information to the immigration team, as errors in visa applications can have lasting consequences on future US visa eligibility.
The B-1 Visa for Short Business Trips:
For shorter onsite stints of a few weeks to a few months (typically for project kickoffs, training, or review visits), the B-1 business visitor visa is used. B-1 visa applications typically take a few weeks for processing after the consulate appointment. The immigration team handles the documentation, but the employee needs to attend the consulate appointment in person and should be prepared to answer standard visa interview questions about the purpose and duration of the visit.
Pre-Departure Preparation:
Before departing for an onsite posting, Infosys provides briefings on the destination country’s business culture, the specific client and project context, and the administrative arrangements for the posting. These briefings cover: compensation arrangements during the onsite period, expense reimbursement procedures, accommodation support, and the reporting structure while onsite.
Practical pre-departure preparation includes: currency arrangements (informing the bank of international travel, ensuring a card with international usage is available), communication setup (SIM card or roaming plan for the destination country), health insurance verification (confirming that coverage is valid in the destination country), and ensuring any prescription medications are in adequate supply.
Client Expectations and Compensation During Onsite
What Clients Expect From Onsite Resources:
The expectations placed on onsite Infosys resources by clients are higher than what is typical for offshore delivery. Onsite resources are expected to be available during client business hours, which may differ from India working hours. They are expected to participate actively in meetings, to provide real-time answers to technical questions, and to function as integrated members of the client team rather than as external vendors keeping their distance.
The cultural adjustment for India-based employees working onsite for the first time is significant. US clients, for example, typically have a more direct communication style than is common in the Indian professional context: disagreements are expressed openly rather than through indirect signals, questions are asked without the deference hierarchy that is common in Indian corporate settings, and the pace of decision-making is often faster. Adapting to this communication style is one of the most important adjustments onsite employees make.
Building genuine working relationships with client team members during an onsite posting creates the interpersonal credit that makes the Infosys team more trusted and more effective. Onsite resources who remain exclusively in the Infosys group even when at the client site, eating lunch only with other Infosys colleagues and not engaging informally with client team members, build fewer relationships and deliver less strategic value than those who integrate into the broader team.
Onsite Compensation Structure:
During an onsite deputation, the employee’s compensation changes significantly from the India-based structure. The typical arrangement includes:
India-based salary components: a portion of the India salary (usually the basic salary and some allowances) continues to be credited to the Indian bank account during the onsite period. This amount varies by the specific compensation policy and the duration of the posting.
Overseas allowance: an overseas daily allowance or per diem is paid in the currency of the destination country. This allowance is calibrated to cover local living costs: accommodation, local transportation, food, and incidentals. For US postings, the per diem or allowance is often sufficient to cover a modest lifestyle and generate savings, particularly if the employee shares accommodation with other Infosys colleagues.
The combination of the maintained India salary components and the overseas allowance typically results in total compensation significantly higher than the India-only salary. For employees on extended US postings, the accumulation of savings during the onsite period often represents the most significant wealth-building event of the early career.
Tax Implications of Onsite Compensation:
The tax treatment of onsite compensation is complex and depends on the duration of the posting, the tax treaty between India and the destination country, and the individual’s residential status. Employees who are onsite for extended periods may become tax residents of the destination country, which changes the tax treatment of their income. Infosys typically provides tax advisory support for employees on long-term postings to help navigate these complexities.
Employees planning extended onsite postings should proactively engage with Infosys’s tax advisory resources and, if needed, an independent tax consultant familiar with the relevant bilateral tax treaty provisions.
The Bench Experience: What Actually Happens
Being on bench at Infosys, the period between project assignments when an employee is employed but not actively billing to a client project, is one of the most discussed and least accurately understood aspects of the Infosys work experience. The bench reality varies considerably depending on how long the bench period lasts, what the employee does during it, and what the overall business environment is like.
The First Few Days on Bench:
The transition from an active project to bench is often abrupt. A project ends, a deployment happens, a client contract winds down, or a restructuring occurs, and suddenly there is no daily standup to attend, no sprint tasks to work on, and no project Jira board to update. For employees who have been on active, engaging projects for a long time, the sudden absence of structure can feel disorienting.
The immediate practical reality of being on bench includes: still receiving full salary (bench does not affect monthly salary), having access to all Infosys systems and the office premises, and being expected to continue showing up (or being available online for remote employees) during normal working hours. The bench is not a paid holiday; it is a period of employed availability.
The Learning Expectation:
Infosys’s official expectation for bench employees is that they engage actively with learning through the Lex platform. Bench employees are typically given specific learning goals or certification targets to work toward during the bench period. This expectation is genuine, not bureaucratic: the RMG and HR teams track whether bench employees are using their bench time productively, and an employee who is completing certifications and developing new skills is viewed more favorably than one who is idle.
Proactively pursuing Lex learning paths, targeting certifications that are relevant to the types of projects available in the business unit, and demonstrating continued technical development during the bench period produces tangible benefits: stronger positioning for upcoming project opportunities, a better performance review for the bench period, and improved skill marketability for both internal and external opportunities.
The Social and Psychological Dimension:
Extended bench periods can be psychologically challenging. The absence of project purpose, the uncertainty about when the next assignment will come, and the potential for anxiety about job security combine to create a state of professional limbo that is difficult to manage without deliberate effort.
The most effective approach is to treat the bench period as a defined career development phase rather than as empty time. Setting daily goals for Lex progress, scheduling regular check-ins with the RMG and the manager, connecting with colleagues in the business unit for informal conversations and networking, and maintaining normal working hours and professional routines all help preserve the sense of professional purpose during the bench period.
Employees who share their concerns about bench duration with their manager and HR contact, rather than suffering silently, typically receive more active support in finding the next project assignment.
What Bench Looks Like in Practice:
A typical bench day for an Infosys employee might involve: logging in during normal working hours, completing a Lex learning module or certification practice test, attending any internal knowledge-sharing sessions or BU meetings scheduled for the day, sending a status update to the RMG if a conversation was pending, applying for one or two IJP positions if new relevant postings are visible, and potentially having an informal call with a former project colleague or manager to stay connected within the BU network.
This is not glamorous, but it is productive. Employees who approach the bench period with this kind of structured intention consistently report both a better psychological experience and a faster return to project assignment than those who either sit idle or who treat the bench period as a period of low expectations.
Bench During Business Downturns:
The bench experience during periods of Infosys business downturn is qualitatively different from the experience during normal operating periods. When revenue growth slows or project pipelines thin, the bench pool grows and the RMG has fewer active requirements to match resources to. In these periods, bench tolerance shortens, the communication from HR becomes more pointed about the need to pursue any available project opportunity, and the implicit pressure to accept sub-optimal project matches increases.
Employees who have developed broad skills rather than narrow specializations are more resilient during bench periods in downturns, because they are eligible for a wider range of project opportunities. Employees with relevant certifications in high-demand areas (cloud, data engineering, DevOps) are prioritized in the matching process during these periods. Preparing broadly during normal bench periods is therefore an investment that pays off during the more stressful bench experiences that downturns create.
The RMG’s Role:
The Resource Management Group is the primary mechanism through which bench employees are matched to open project positions. The RMG maintains a database of available resources and open project requirements and works to match them. Employees on bench are visible in the RMG system, but the effectiveness of the match depends on how clearly the employee’s skills and preferences are communicated in the system.
A common mistake bench employees make is passivity: assuming that the RMG will identify the right match without the employee doing anything to facilitate it. In practice, the RMG handles very large numbers of transactions and may not have detailed visibility into every nuance of an employee’s skill profile. Proactive communication with the RMG, specifically articulating what types of projects and technologies are of interest, what availability exists, and what certifications have been recently completed, significantly accelerates the matching process.
How to Get Off Bench Faster
The practical actions that reduce bench duration are well-known among Infosys employees who have navigated multiple bench periods successfully.
Update the Infosys Profile Immediately:
As soon as a project ends and bench begins, update the Infosys employee profile in the relevant internal system to reflect the most current skill set, including any certifications completed during the project, new technologies used, and the specific types of work done in the recent project. The RMG uses profile data in its matching algorithm; an outdated profile with missing skills creates mismatches that delay placement.
Contact the RMG Directly:
Do not wait for the RMG to find the profile in the system. Send a direct email or use the internal ticketing system to introduce yourself as a bench resource, describe your skill set concisely, indicate your location and mobility preferences, and ask what open requirements might be a good match. A direct, professional communication from a bench employee to the RMG consistently produces faster engagement than passive waiting.
Leverage the Business Unit Network:
Managers, TLs, and DMs in the business unit often know about upcoming project needs before they are formally opened through the RMG. An employee who has built relationships within the BU can sometimes learn about an upcoming project through informal channels and express interest directly to the relevant manager before the formal process is initiated. This is not circumventing the process; it is how a significant proportion of bench placements actually happen.
Attending internal knowledge-sharing sessions, participating in BU-wide town halls, and maintaining contact with former project team members all keep the employee visible within the BU during the bench period.
Pursue Internal Job Postings:
The IJP system is available to bench employees, and bench employees in particular should use it actively. An IJP application during a bench period is the fastest and most direct mechanism for securing a new project assignment. Target IJP postings in areas where the skill profile matches, where certifications can be demonstrated, and where the role represents a genuine development opportunity rather than just a bench escape.
Be Open About Location and Project Type:
Employees who are highly specific about location and project type during bench periods extend their time on bench. While it is reasonable to have preferences, being open to locations beyond the primary city, open to project types adjacent to the primary expertise, and open to technology streams that are adjacent to (but not identical to) the preferred stack significantly expands the pool of matching positions.
The Complete Resignation Process
Resigning from Infosys is a multi-step process that requires careful execution to ensure all obligations are met and all entitlements are received. Understanding the full process in advance prevents the common administrative complications that make an already emotionally complex transition more difficult.
Step 1: Making the Decision
The decision to resign should be made deliberately, not in a moment of frustration. Before resigning, confirm that the new offer is firm (not conditional on a reference or background check), that the notice period can realistically be served (the new employer’s joining date is compatible with the Infosys notice period), and that the financial implications are understood (PF portability, gratuity eligibility, bond implications if within the service agreement period).
Step 2: Informing the Manager
The professional standard in the Infosys culture is to inform the direct manager before submitting the formal resignation in the HRMS. This is not a bureaucratic requirement; it is a professional courtesy that affects the quality of the exit experience. A manager who is blindsided by a resignation in the HRMS system before any conversation is typically less cooperative on notice period flexibility, knowledge transfer, and experience letter timing than a manager who was told first in a private conversation.
The conversation with the manager should be direct and professional. Explain that a decision to resign has been made, give a brief professional reason (career opportunity, personal growth, not a litany of complaints), and express appreciation for the work experience. Even if the manager relationship has been difficult, this conversation sets the tone for the entire exit period that follows.
Step 3: Formal Resignation Submission
After informing the manager, the formal resignation is submitted through the Infosys HRMS (InfyMe portal). The submission records the resignation date and triggers the HR processes for notice period calculation, clearance, and documentation.
The resignation should be submitted in writing even if the HRMS allows online submission. Keeping a record of the resignation submission date is important for tracking notice period timelines accurately.
Step 4: HR Processing and Notice Period Confirmation
After the resignation is submitted, HR processes it and confirms the notice period calculation. The standard notice period at Infosys is 90 days (3 months) for most employees. The HR communication confirms the last working day based on the notice period start date.
Employees who need a shorter notice period (because the new employer’s joining date requires it) should initiate the notice period shortening request at this stage.
Step 5: Knowledge Transfer
Infosys expects resigning employees to complete a thorough knowledge transfer to the team members who will take over their responsibilities. The KT (Knowledge Transfer) process involves documenting the work currently in progress, the relevant system architecture, any issues or open items that will need follow-up, and the relationships with client contacts that the employee manages.
A well-executed knowledge transfer benefits the employee: it creates a record of professionalism, reduces the likelihood of a counter-claim about handover quality, and maintains relationships with colleagues who may be professional references or contacts throughout the career. A poorly executed KT creates tension with the manager and team, can delay the relieving letter, and leaves a negative impression that persists after departure.
Step 6: Asset Return and IT Clearance
Before the last working day, all company assets must be returned: laptop, access cards, any hardware assigned to the employee. IT clearance involves deprovisioning access to Infosys systems, email, and the client systems the employee had access to. The HR and IT clearance certificates are prerequisites for the relieving letter.
Delays in asset return or incomplete IT clearance extend the timeline for receiving the experience letter and relieving letter. Initiating these processes proactively, well before the last working day, avoids last-minute complications.
Step 7: Exit Interview
The formal exit interview is conducted by HR and covers the reason for leaving, the experience at Infosys, feedback on management and team, and any suggestions for improvement. Exit interviews at Infosys are officially confidential, though in practice many employees are cautious about how specific their feedback is.
The most constructive approach to the exit interview is to be honest but professional: specific feedback about genuinely problematic practices or managers is useful to the organization, and Infosys’s HR function genuinely uses exit interview data to identify patterns. However, personal attacks or extended complaints about individuals are not productive and create an unnecessarily negative parting impression.
The Emotional Dimension of Resigning:
For many employees, particularly those who joined Infosys directly from college and spent their formative professional years there, resigning involves a genuine emotional dimension beyond the administrative steps. The relationships built with colleagues over years, the identity built around being an Infosys employee, and the uncertainty about what comes next all combine to make the resignation more emotionally complex than a simple administrative transaction.
Acknowledging this emotional reality rather than suppressing it helps navigate the exit more healthily. It is entirely normal to feel a mix of excitement about the new opportunity and sadness about leaving familiar colleagues and environment. Employees who allow themselves to process these feelings, say genuine goodbyes to colleagues they valued, and leave with appreciation expressed for what the Infosys experience provided tend to maintain better professional relationships post-exit than those who exit with bitterness or abruptness.
Counter-Offer Dynamics:
When a valued employee resigns, managers or senior leaders at Infosys sometimes make a counter-offer: a salary revision, a promotion, a better project assignment, or some combination of these. Counter-offers are worth evaluating carefully but should not be accepted without critical thinking.
The fundamental analysis is straightforward: if the reasons for leaving were primarily about the specific things being offered in the counter-offer (salary, role, project), and the new employer’s offer is being declined solely because the counter-offer addresses those issues, then the counter-offer may be worth accepting. If the reasons for leaving were about the overall career trajectory, the culture, the technology exposure, or longer-term positioning, then a counter-offer that does not address these deeper issues merely delays the departure.
Employees facing a counter-offer should ask themselves honestly: “If this offer had been made six months ago, would I still have started looking for a new job?” If the honest answer is yes, the counter-offer is likely not a genuine resolution.
Step 8: Experience Letter and Relieving Letter
After all clearances are complete, Infosys issues the experience letter (which documents tenure, designation, and the fact of employment) and the relieving letter (which confirms the end of employment relationship). These documents are required by the new employer for background verification and employment record.
In routine cases where there are no bond disputes, pending dues, or clearance issues, the experience and relieving letters are issued within a few business days of the last working day. In cases with complications, the timeline extends until the issues are resolved.
Notice Period Negotiation
The 90-day standard notice period at Infosys is a formal commitment, but in practice many employees successfully negotiate shorter periods depending on their project situation and the new employer’s flexibility.
Factors That Favor Shorter Notice:
Employees on bench have the most flexibility for early release since there is no active project continuity to protect. A bench employee who has completed knowledge transfer has no practical reason for a full 90-day notice from the company’s perspective, and many bench employees are released within 30 to 45 days.
Employees on projects that are in a quiet phase (post-go-live support, transition periods, or low-activity maintenance) are also more negotiable than those in active development or near a major deadline. Timing the resignation for a period of low project intensity improves the probability of a shorter notice negotiation.
The Role of the Manager in Notice Negotiations:
The decision to release an employee before the full 90-day notice is made by the manager and DM, not unilaterally by HR. Employees who have a good relationship with their manager and who have executed the KT thoroughly are more likely to receive early release than those who have a difficult manager relationship or who have been slow to document their work.
Asking for a shorter notice period should be done directly, honestly, and early in the process. Saying “My new employer needs me to join in 45 days and I am wondering if there is any flexibility to release me before the full 90 days” is a clear, professional request. Providing the joining date as a concrete constraint gives the manager something specific to work with.
Notice Period Buyout:
If the new employer offers to buy out the notice period (pay the remaining notice period salary to Infosys as compensation for early release), this can be proposed to the HR team. Infosys does accept notice period buyouts in some cases, particularly when the employee is on bench or in a low-activity project phase. The buyout amount is typically the gross salary for the remaining notice days.
What Cannot Be Negotiated:
The formal notice period cannot be unilaterally shortened by the employee. If the notice period cannot be negotiated with the manager and HR, the employee must either serve the full period or face consequences for abandonment that include withholding of the experience letter and potential legal action in some cases. Employees who walk off the job without completing the notice period or properly negotiating an exit find themselves unable to obtain their relieving letter, which creates difficulties in the new employment’s background verification.
Exit Interview, Experience Letter, and Relieving Letter
The Exit Interview:
Beyond the formal HR exit interview, many managers conduct informal exit conversations with departing team members. These conversations serve multiple purposes: they give the manager feedback, they allow for genuine expression of appreciation for the work done together, and they are an opportunity to part on terms that preserve the professional relationship.
The informal exit conversation with the manager is worth having even when the manager relationship has been difficult. A professional farewell that acknowledges the positive aspects of the experience, regardless of the challenges, leaves a better professional residue than an exit marked by grievances. The Indian IT industry is a connected ecosystem, and the colleague who is leaving today may be the hiring manager or professional reference five years from now.
The Experience Letter:
The Infosys experience letter documents the employee’s name, employee ID, date of joining, date of leaving, designation at the time of departure, and a statement of satisfactory service. This document is one of the most important in the professional file: it is required for all future background verifications and is a permanent record of the Infosys employment.
Employees should verify that the experience letter accurately reflects all the information (especially the correct designation, as some employees receive promotions close to their exit date that may or may not be reflected). Any errors should be raised with HR for correction before the letter is used for background verification.
The Relieving Letter:
The relieving letter is the formal document that confirms the termination of the employment relationship. It states that the employee has been relieved from services effective the last working day and that all formalities have been completed. This document is required by the new employer to confirm that the previous employment relationship has been formally concluded.
The relieving letter is issued only after all HR clearances, IT clearances, and asset returns are completed, and after any bond-related issues are resolved. Ensuring these processes are completed promptly is entirely within the employee’s control and directly determines when the relieving letter arrives.
PF Settlement and Gratuity
PF Settlement:
The Provident Fund accumulated during Infosys employment does not disappear when an employee leaves. It can be handled in one of two ways: transferred to the new employer’s PF account or withdrawn.
Transfer is the preferred option under most circumstances: it continues the compounding accumulation of the PF balance, avoids tax liability (PF withdrawals before five years of service attract tax under certain conditions), and contributes to the retirement corpus. The transfer is initiated through the EPFO online portal using the Universal Account Number (UAN) linked to both the old and new PF accounts.
Withdrawal is available for employees who need the funds or who are not joining a new employer. PF withdrawals before completing five years of service attract income tax on the employer’s contribution and the accumulated interest. Employees considering early withdrawal should verify the tax implications before initiating the claim.
Gratuity:
Gratuity is a statutory payment to employees who have completed five or more years of continuous service with the same employer. The calculation is based on the last drawn basic salary multiplied by the number of completed years of service multiplied by 15/26 (as per the Payment of Gratuity Act formula).
Employees who have served less than five years at Infosys are not entitled to gratuity under the standard statutory interpretation. The gratuity that has been accrued and included in the CTC during their tenure is forfeited.
Employees completing exactly or just over five years should be aware that the gratuity amount can be significant. A Technology Lead with five years of service and a basic salary of 50,000 rupees per month receives approximately 1,44,231 rupees in gratuity (50,000 x 5 x 15/26). This amount is tax-exempt for Infosys employees under the provisions applicable to government-compliant employers.
Infosys must pay gratuity within 30 days of the last working day for eligible employees. If payment is delayed, the employee can raise the matter with the regional Labour Commissioner.
The Service Agreement and Bond Clause
What the Service Agreement Is:
The Infosys service agreement is a legal contract signed by the new joiner at the time of joining (typically on the first day at Mysore). It obligates the employee to remain with Infosys for a defined minimum period in exchange for the company’s investment in the initial training program.
The specific terms of the service agreement have been revised multiple times across Infosys’s hiring history. The key parameters are:
The minimum service period: typically one to two years from the date of joining. This is the period during which leaving attracts the financial penalty.
The penalty amount: specified in the agreement as a fixed amount (in recent cycles, ranging from approximately 50,000 to 1,00,000 rupees or more depending on the hiring track and training investment). This is not negotiable at the time of signing but is the contractually specified liquidated damages amount.
The Legal Nature of the Agreement:
The Infosys service agreement is a binding contract under Indian contract law. Courts have generally upheld reasonable service agreements that specify a defined period and a reasonable penalty amount as being enforceable, particularly where the employer has made a genuine training investment. However, courts have also found some service agreements to be unenforceable in specific circumstances (such as where the penalty amount is unreasonably high relative to the training investment, or where the employer failed to provide the training promised).
The legal landscape around IT services bonds in India is not uniformly settled, and outcomes have varied in cases where employees have challenged bond enforcement. This variability is sometimes cited as a reason why some employees assume that bonds are routinely unenforceable, which is not a safe assumption.
What the Agreement Does Not Cover:
The service agreement covers the minimum service period for the role that the employee was hired for. It does not prevent the employee from discussing their experience on professional networks, from pursuing education outside working hours, or from networking with other companies in a professional capacity.
Reading the Agreement Before Signing:
The service agreement is presented on day one at Mysore, a busy and emotionally charged day when new joiners are processing many things simultaneously. The temptation is to sign quickly and move on. This temptation should be resisted. The service agreement is a legally binding contract with significant financial implications, and the 10 to 15 minutes required to read it carefully is time well spent.
The specific clauses to read carefully include: the exact minimum service period (some agreements specify it as months from the date of joining, others from the date of completing training), the exact penalty amount (which should match what was communicated during the hiring process), any conditions under which the penalty is waived (medical incapacity, company-initiated separation, etc.), and any provisions around what constitutes a valid resignation versus an abandonment of employment.
If anything in the agreement is unclear or differs from what was communicated during hiring, the right time to raise it is before signing, not after. HR representatives present on day one are the appropriate point of contact for clarification.
The Practical Impact of the Bond on Early Career Decisions:
For most new joiners, the bond is a non-issue because they plan to stay with Infosys for the minimum service period regardless. For candidates who are treating Infosys as a backup offer while actively pursuing other options, or who have significant uncertainty about their commitment to staying, the bond is a real financial consideration.
The financial analysis is straightforward: the bond amount (typically 50,000 to 1,00,000 rupees) divided by the monthly savings potential during the bond period determines how many months of savings are at risk. For a fresher with modest savings, 75,000 rupees represents approximately two to three months of net income. This is a meaningful but not catastrophic amount for most candidates, and it should be weighed against the financial benefit of accepting the Infosys offer versus the alternative.
What Happens If You Break the Bond
Leaving Infosys before completing the minimum service period specified in the service agreement is commonly described as “breaking the bond.” The practical consequences are specific and worth understanding clearly.
Withholding of Documents:
The primary mechanism through which Infosys enforces the service agreement is document withholding. Infosys typically will not issue the experience letter and the relieving letter until the bond amount has been paid. Without the relieving letter, the employee cannot complete background verification at the new employer, which can create significant complications in the new employment.
Many employees in this situation negotiate a payment arrangement: they pay the bond amount (often through a demand draft drawn on their own account or paid by the new employer as a joining allowance recovery), receive the documents, and proceed to the new joining. The payment of the bond amount in exchange for the documents is the most common resolution.
Legal Action:
In some cases, particularly where the employee refuses to pay the bond amount or where the amount is large, Infosys may initiate legal proceedings. Legal action involves sending a legal notice demanding payment and, if no resolution is reached, filing a recovery suit. This path is more resource-intensive for Infosys and is typically reserved for situations where the bond amount is significant or where the company wants to make an example for attrition deterrence purposes.
Most bond breakage situations in practice are resolved through document-for-payment negotiation rather than litigation. However, employees should not assume that Infosys will not pursue legal action; the documented cases of Infosys pursuing bond recovery do exist.
Joining the New Employer Without Documents:
Some employees attempt to join a new employer before receiving the relieving letter, relying on the new employer’s flexibility in the background verification process. This is risky: a growing number of employers in India, particularly product companies and GCCs, have strict background verification requirements that include the relieving letter. Joining without a relieving letter and hoping the new employer overlooks this creates legal exposure for both the employee and the new employer if the full employment history later cannot be verified.
The cleanest resolution is always to pay the bond amount (or negotiate its payment through the new employer as a joining benefit), receive the documents, and join the new employer fully documented.
Moonlighting Policy at Infosys
The Official Position:
Infosys prohibits employees from working for other employers, particularly for competitors, simultaneously with their Infosys employment. This prohibition is stated in the employment agreement and is enforced. The specific prohibition covers:
Working for a competitor (another IT services company, a technology product company, or any entity that competes with Infosys for clients or talent).
Working in any capacity that creates a conflict of interest with Infosys business.
Using Infosys resources (systems, time, proprietary knowledge, or client information) for any outside commercial activity.
What Infosys Does Not Prohibit:
The employment agreement is not designed to prevent all personal activity outside of working hours. Non-conflicting freelance work (writing, teaching, content creation, or personal project development in areas completely unrelated to Infosys’s business) is generally not prohibited, though the specific language of the employment agreement should be reviewed to confirm.
Teaching at a college or coaching institute, writing technical content on personal blogs or platforms, contributing to open-source projects in personal time, and developing personal mobile applications or websites are all activities that typically fall outside the moonlighting prohibition. However, employees should be cautious about: using Infosys-proprietary knowledge in their personal work, working on projects for clients who are also Infosys clients in the same domain, and any activity that could be perceived as a conflict of interest.
The Enforcement Approach:
Infosys has communicated publicly that it takes moonlighting violations seriously and that detection will lead to disciplinary action up to termination. The detection mechanisms include background verification processes for employees being considered for onsite roles, information from team members or managers, and in some cases formal audits of employee outside activities.
Employees who are considering any outside commercial activity should review their employment agreement carefully, consult with HR if the nature of the activity is unclear, and err strongly on the side of disclosure and clearance rather than proceeding without verification.
The Moonlighting Debate in the Indian IT Industry:
The moonlighting issue became a high-profile conversation in the Indian IT industry after several companies took public positions and made high-profile terminations of employees found to be working for competitors simultaneously. The debate reflects a genuine tension: employees argue that their personal time and skills are their own to use as they choose; employers argue that the employment relationship includes an implicit exclusivity that protects the employer’s legitimate business interests.
Infosys’s position is clearly stated and is legally defensible: the employment contract prohibits conflicting secondary employment, and the company enforces this provision. Employees who disagree with this policy as a matter of principle have the option of building careers in employment models (such as freelance contracts or specific companies with explicit moonlighting-friendly policies) that align with their preferences. Within the Infosys employment context, the policy is what it is, and employees bear full responsibility for the consequences of violating it.
Protecting Intellectual Property:
Beyond the direct moonlighting prohibition, employees must be vigilant about intellectual property boundaries. Using code written at Infosys in a personal project, sharing client architecture details in a public technical blog post (even without naming the client), or building a personal commercial product using insights gained from confidential client work all constitute IP violations that can have serious consequences beyond the moonlighting policy.
The intellectual property generated during Infosys employment belongs to Infosys, not to the employee who created it. This is a standard provision in IT employment contracts and means that personal projects should use independently developed approaches rather than adaptations of work done for Infosys or its clients.
Internal Transfer Mechanisms
The Internal Job Posting system, described in detail in the career growth guide in this series, is the primary formal mechanism for internal transfers. This section covers the practical aspects of using internal transfers effectively in the Infosys context.
Types of Internal Transfers:
Project transfer: moving from one project to another within the same business unit or across business units. This is the most common type of internal transfer and is processed through the IJP system or through direct manager and RMG coordination.
Location transfer: moving from one Infosys delivery city to another while remaining on the same or a different project. Location transfers are processed through a separate HR workflow and may require business justification (such as a project requirement for the new location) or personal justification (such as a family relocation).
Business unit transfer: moving from one Infosys business unit to another. This is a more significant transition that may involve changes in the types of clients, project methodologies, and cultural norms. BU transfers are typically facilitated through the IJP system when the target BU has an open requirement.
The Timing of IJP Applications:
Employees become eligible for IJP applications after a defined tenure in their current role, typically six months to one year from joining or from the last IJP move. The cooldown period between IJP moves is also typically six months to one year after completing a transfer.
Applying for a transfer before the minimum tenure is complete is possible in exceptional circumstances with manager approval, but the standard eligibility window should be respected to maintain the integrity of the process and the employee’s relationship with the current manager.
Getting Manager Support for a Transfer:
While IJP applications are technically independent of the current manager’s approval in the first-application phase, in practice manager support significantly improves the probability of a smooth transfer. Managers who are informed of the employee’s transfer interest in advance, who understand the reasons for it, and who are supportive of the employee’s career development tend to release employees to IJP moves more smoothly than those who feel blindsided.
Framing the transfer request to the manager as a career development initiative (“I am interested in developing cloud skills and there is an opportunity in the cloud practice area through IJP”) rather than as a rejection of the current project (“I want to leave this project because of X”) produces a much better manager response.
The Lifecycle of an Infosys Career and Internal Mobility:
Internal mobility at Infosys is not a single event but a pattern that recurs across the career. Most employees who build long careers at Infosys move through multiple projects, multiple managers, multiple business units, and sometimes multiple locations over the years. Each internal move is an opportunity to refresh skills, escape stagnant environments, and build new relationships.
Employees who approach internal mobility proactively, planning their next move rather than waiting for circumstances to force a change, consistently build more varied, more interesting, and more marketable careers than those who remain in the same project context for extended periods without reassessment.
The IJP system, combined with the bench periods that occur between project assignments, creates natural inflection points for career reassessment. Using these moments deliberately, applying the question “is this next opportunity moving me toward where I want to be in three years?” before accepting any new assignment, is the most reliable navigational tool for building the Infosys career with intention.
Final Thoughts: Understanding What You Are Signing Up For
The Infosys employment experience is specific and knowable. The work culture has identifiable characteristics that suit some people and challenge others. The onsite process has criteria that can be understood and prepared for. The bench experience has a predictable structure with clear strategies for navigating it well. The resignation process has defined steps that, when followed correctly, produce a clean exit without complications.
Employees who understand these dynamics before they encounter them are consistently better positioned than those who learn them reactively. The new joiner who understands the importance of the self-assessment arrives at the first appraisal ready to make the most of it. The experienced employee who understands how onsite selection works can position systematically rather than waiting to be tapped. The employee who is considering resigning but understands the notice period dynamics can plan the transition timeline accurately.
The underlying principle across all of these dimensions is that Infosys is a large, process-driven organization that provides genuine opportunities to those who engage with it actively, and delivers a passive and sometimes frustrating experience to those who wait for the organization to do things for them. The engagement model is a choice, and it is one that employees can make consciously from day one rather than discovering through years of experience what they wish they had known at the beginning.
Use this guide as a reference throughout the Infosys career journey: revisit the onsite section when an opportunity appears on the horizon, revisit the bench section if a project ends without a clear next assignment, and revisit the resignation section when the time comes to think about what the next chapter should look like. The information is here to be used, not just to be read once.
Frequently Asked Questions
1. What is the Infosys notice period and can it be reduced?
The standard Infosys notice period is 90 days (3 months). It can be reduced through negotiation with the manager and HR, particularly if the employee is on bench, in a low-activity project phase, or if the new employer offers a notice period buyout. The decision to grant early release is made by the manager and DM, not unilaterally by HR.
2. How long can I stay on bench at Infosys before facing consequences?
There is no fixed published threshold, but bench periods beyond two to three months typically trigger more active intervention from HR and the RMG. In business downturns or restructuring periods, bench tolerance may shorten significantly. Employees who use the bench period productively (completing certifications, engaging with the RMG actively, participating in BU activities) are treated more favorably than those who are visibly disengaged.
3. Can I travel to the US for onsite work on a B-1 visa?
Yes, short-term business visits for project-related work are typically handled on a B-1 business visitor visa. The B-1 visa is appropriate for attending meetings, conducting training, consulting, or performing specific limited activities. Long-term work (more than a few weeks or involving direct work on US-based systems) requires an H-1B or other appropriate work authorization visa.
4. How does Infosys select employees for onsite opportunities?
Selection is based on technical capability appropriate for the role, English communication readiness, professional maturity, visa eligibility, and the match between the employee’s skill profile and the specific onsite requirement. Employees who want onsite opportunities should communicate their interest clearly to their DM and maintain a strong performance record and communication skills.
5. What happens to my PF if I leave Infosys before completing five years?
The PF balance (both employee and employer contributions) is yours and can be transferred to the new employer’s PF account or withdrawn subject to tax rules. The gratuity, however, is forfeit if you leave before completing five years of continuous service.
6. Can I do freelance work while employed at Infosys?
Freelance work that is completely unrelated to Infosys’s business, does not involve Infosys clients, does not use Infosys resources, and does not create any conflict of interest is generally not prohibited. The safest approach is to review the employment agreement carefully and consult HR if the nature of the planned freelance activity is in any way adjacent to Infosys’s business.
7. What is the Infosys bond amount and can it be negotiated?
The bond amount is specified in the service agreement signed at joining and is not negotiable after signing. In recent hiring cycles, the bond amount has been in the range of 50,000 to 1,00,000 rupees or higher depending on the designation track. Candidates who have concerns about the bond amount should raise them before signing the agreement, as they cannot be renegotiated afterward.
8. What if I want to resign during an active project near a critical deadline?
The professional approach is to still serve the full notice period or negotiate it with the manager. Leaving in the middle of a critical project phase without adequate notice creates genuine harm to the client and to your colleagues, damages the manager relationship, and leaves a negative professional impression that can persist. If the timeline is genuinely inflexible, work with the manager and HR to find the minimum feasible exit timeline that does not catastrophically impact the project.
9. How does the onsite compensation work?
During onsite deputation, a portion of the India salary is maintained in Indian accounts, and an overseas allowance (per diem or monthly) is paid in the local currency of the destination country. The overseas allowance is calibrated to cover local living costs. The total effective compensation during a US onsite posting is typically significantly higher than the India-only salary, and extended onsite postings are often the most significant wealth-building events of the early career.
10. Can I resign if I am on bench?
Yes. Being on bench does not restrict the employee’s ability to resign. Notice period calculation starts from the resignation date regardless of whether the employee is on a project or bench. Bench employees often have more flexibility for early release than project-assigned employees because there is no active project continuity to protect.
11. What is the difference between an experience letter and a relieving letter?
The experience letter documents the period of employment, the designation, and the fact of satisfactory service. The relieving letter formally confirms that the employment relationship has ended and the employee has been relieved from all duties. Both documents are required by new employers. The experience letter is a permanent record; the relieving letter is an end-of-relationship confirmation.
12. How do I transfer my PF after leaving Infosys?
PF transfer is initiated through the EPFO Unified Portal using the Universal Account Number (UAN). The employee submits a transfer claim specifying the previous employer’s PF account details and the new employer’s PF account details. Infosys’s HR helpdesk can provide the PF account number required for the transfer. The transfer typically completes within 20 to 30 working days.
13. What is moonlighting and why does Infosys prohibit it?
Moonlighting refers to working for another employer simultaneously with the primary employment. Infosys prohibits conflicting secondary employment because it creates risks of data security breaches, conflicts of interest, and reduced attention to the primary role. The prohibition on competing employment also protects Infosys’s commercial interests by preventing employees from simultaneously working for competitors. Non-conflicting personal activities are generally not prohibited.
14. Can Infosys management see the exit interview responses?
The exit interview is officially confidential and responses are not shared with the specific manager being referenced. HR uses exit interview data in aggregate to identify patterns. In practice, particularly in small teams or BUs, very specific feedback about individuals may be recognizable even without names. Employees should be honest but thoughtful about the specificity of individual references in exit interview feedback.
15. What should I do if Infosys refuses to issue my relieving letter after I paid the bond?
If the bond amount has been paid and the clearances are complete but the relieving letter is still not issued, escalate the matter through the InfyMe HR helpdesk with documented evidence of the payment and the clearances. If the internal escalation does not resolve the issue within a reasonable period, consulting an employment lawyer familiar with Indian labour law is the appropriate next step. Infosys is legally obligated to issue the relieving letter once all legitimate exit formalities are completed.
The Returning Infosys Employee:
A pattern worth noting is the number of employees who leave Infosys, build experience at other organizations, and return to Infosys later at a higher designation or in a different capacity. Infosys’s rehire policy allows former employees to rejoin subject to the standard hiring process, and the company’s familiarity with the professional’s background can accelerate the evaluation.
The returning employee typically joins at a designation that reflects both the experience gained since leaving and the current market rate for that experience, which often represents a significantly higher designation and salary than the employee left at. This alumni-return pattern is a testament to the quality of the professional foundation Infosys provides: the skills developed, the professional habits formed, and the delivery experience accumulated during the Infosys years remain valuable across the career, even after moving elsewhere.
Building the Infosys Career Intentionally:
The theme across this entire guide is intentionality. The work culture rewards those who engage actively with it. The onsite selection rewards those who position for it deliberately. The bench period rewards those who use it productively. The resignation process rewards those who execute it professionally. The bond is navigable for those who understand its terms.
Every one of these dimensions is more manageable with advance knowledge than without it. The purpose of this guide is to provide that knowledge so that the Infosys career experience, in all its phases from joining to eventual exit, can be navigated with the clarity and confidence that deliberate preparation provides. -e The Importance of Peer Relationships in Daily Work:
Beyond the manager relationship, the quality of peer relationships within the project team significantly shapes the daily work experience. Colleagues who share knowledge freely, who help each other debug difficult problems, and who cover for each other during personal emergencies create a team environment that makes even challenging projects manageable. Employees who invest in being genuinely helpful colleagues, who share useful resources without being asked, and who celebrate team successes collectively rather than attributing them entirely to individual effort build the kind of team reputation that opens doors to the best project assignments and the strongest professional references.
The Infosys culture broadly supports collaborative team behavior over hyper-competitive individual behavior, which is a feature worth preserving in day-to-day interactions. Employees who undermine colleagues to appear more impressive to management are creating short-term career tactics that damage the team culture in ways that eventually become visible and counter-productive.