Infosys Work From Home and Remote Policy: Complete Guide

The Infosys work from home policy is one of the most searched and least accurately documented topics about the company. Employees who joined during the pandemic era work alongside colleagues who joined post-pandemic, and the two groups often have fundamentally different assumptions about what the work arrangement is and should be. Freshers joining from campus expect the office-centric experience their placement team described. Experienced lateral hires who negotiated remote work in their offer letter find the practical implementation differs from what was agreed. Managers navigate client requirements that override whatever the official HR policy says.

Infosys WFH and Remote Policy Complete Guide

This guide cuts through the confusion with an honest, specific account of how work arrangements actually function at Infosys. It covers the official policy framework, the client override reality that shapes most employees’ actual experience, how attendance is tracked and what the consequences of non-compliance are, how WFH arrangements differ by designation level and business unit, how to negotiate remote work in offer letters and during employment, what the tools and infrastructure for remote work look like, and the genuine career implications of different work arrangements. This is not a polished corporate narrative; it is a practical guide for employees who need to make real decisions about their work arrangement.

The Official Infosys WFH Policy Framework
The Client Override Reality
How Work Arrangements Differ by Business Unit and Role
Attendance Tracking: How Infosys Monitors Presence
The Hybrid Work Model in Practice
Fully Remote Roles: When They Exist and Who Gets Them
Negotiating WFH in the Offer Letter and During Employment
The Tools and Infrastructure for Remote Work at Infosys
Career Implications of WFH vs Office Work
WFH for Freshers: The Reality
WFH During Special Circumstances
Comparison: Infosys WFH vs Peer IT Services Companies
Managing WFH Effectively as an Infosys Employee
The Future of WFH at Infosys
Frequently Asked Questions

The Official Infosys WFH Policy Framework

The Post-Pandemic Policy Evolution:

Infosys’s work arrangement policy has gone through three distinct phases. Pre-pandemic (before 2020): the overwhelming majority of Infosys employees worked from Infosys development centers or client sites. Remote work was an exception requiring specific approval.

During the pandemic (2020-2022): Infosys, like every large IT company, shifted almost entirely to remote work. The company invested in remote work infrastructure, collaboration tools, and security frameworks. Employees who joined during this period built their entire Infosys experience in a remote context.

Post-pandemic (2022 onward): Infosys has implemented a hybrid work model that requires a defined proportion of in-office presence while preserving flexibility for the remainder. This is the current policy framework, though its implementation varies significantly across business units, projects, and locations.

The Official Hybrid Requirement:

Infosys’s official hybrid policy, as communicated through internal channels, requires employees to be physically present in the office for a defined minimum number of days per week or per month. The specific requirement has been communicated as approximately three days per week for most roles, though this varies by business unit policy, client requirements, and manager discretion.

The three-days-per-week requirement is a guideline at the organizational level. At the project level, the actual requirement is determined by the combination of the Infosys unit policy and the client’s requirements for the specific engagement. In practice, many employees work more than three days from the office due to client requirements, and some work fewer than three when project and client conditions permit.

What the Policy Does and Does Not Specify:

The official policy specifies: minimum in-office days, the requirement to be reachable during core business hours regardless of location, and the requirement to use Infosys-approved tools for remote work. It does not specify: which specific days must be in-office (Monday vs Friday flexibility), the exact timing of the in-office days, or whether the in-office days must include any specific meetings.

The policy also specifies that client requirements override the standard hybrid policy where client requirements demand greater presence. This override clause is the most practically significant element of the policy for most employees.

The Policy Communication Challenge:

One of the persistent frustrations for Infosys employees is that the WFH policy is not communicated with a single, clear, comprehensive document. Instead, it is communicated through a combination of: internal InfyMe announcements, manager communications, project-specific instructions from the client, and business unit-specific guidelines from the delivery manager or unit head.

The result is that two employees in the same city but in different projects have materially different work arrangements, both of which are compliant with Infosys’s official policy. Understanding that the policy has multiple layers (organizational, business unit, project, client) is the first step to understanding your own specific arrangement.

The Client Override Reality

The most important thing to understand about Infosys’s WFH policy is the client override provision. For employees on client-facing delivery projects, which is the majority of Infosys’s workforce, the client’s requirements take precedence over the standard hybrid policy.

Why Client Requirements Override:

Infosys’s business model is client delivery. Infosys’s contracts with clients specify how the delivery team will work: where they will work, what security requirements apply to the working environment, when they will be available for client interactions, and in some cases whether on-site presence at the client location is required.

A US banking client that requires its technology partners to maintain SOC 2 Type II compliance may specify that work involving their systems must be done from Infosys’s certified delivery center, not from employees’ homes. A retail client that requires daily scrum calls at 7 AM India time to align with UK time may effectively require that employees work in the office early morning for reliable connectivity and focus. A client with proprietary data restrictions may prohibit any work on their systems from non-secure home environments.

These requirements are contractual obligations, not preferences. Infosys cannot grant employees WFH flexibility for a client project if the client’s contract prohibits it.

The Spectrum of Client Requirements:

Client requirements fall into a spectrum:

Fully on-site client requirements: the client requires Infosys team members to work from the Infosys delivery center for all working hours. This is most common for: highly regulated industry clients (banking, healthcare, defense), clients with sensitive data that cannot leave the secure environment, and clients with specific security certifications that require on-site work.

Hybrid client requirements: the client requires certain activities (client calls, sprint reviews, production deployments) to be done from the office but permits other work (development, testing) from home. This is the most common arrangement.

Flexible client requirements: the client has no specific presence requirements and defers to Infosys’s standard policy. This is most common for: newer digital clients, startup clients, and clients in less regulated industries.

How to Find Out What Your Client’s Requirement Is:

The client requirement for your specific project is known to the project manager and delivery manager. When joining a new project, ask explicitly: “What is the client’s requirement for in-office presence for our team?” This question gets the specific answer rather than the general organizational policy, which may not reflect what your project actually requires.

When Client Requirements Change:

Client requirements for in-office presence can change when: the client changes their security policy, the project phase changes (going live often requires more presence than development phases), the client’s own hybrid policy evolves, or there is a change in the client-side project leadership.

When client requirements change, the change typically flows through the delivery manager who communicates it to the team. The adjustment to the work arrangement must be immediate; the client requirement override means individual preferences cannot delay compliance.

How Work Arrangements Differ by Business Unit and Role

The Infosys employee experience of WFH varies significantly depending on which business unit the employee belongs to, what type of role they hold, and at what designation level they work.

By Business Unit:

Infosys’s delivery units serve different client types with different requirements. Units serving banking and financial services clients (a large portion of Infosys’s portfolio) tend to have stricter in-office requirements due to regulatory and security considerations. Units serving retail, consumer goods, and digital-native clients tend to have more flexibility.

The Infosys BPM (Business Process Management) arm typically has stricter in-office requirements than the IT services arm, because process delivery work often requires access to client systems in the secure delivery center environment.

The Infosys digital units (Cobalt, Topaz) tend to have somewhat more flexibility than traditional application maintenance units, because digital work cultures typically embrace flexible arrangements and many digital clients are themselves more flexible employers.

By Role Type:

Development and engineering roles: typically the most flexibility, as coding work can be done effectively from any location with adequate connectivity and tooling. The constraint is client data access requirements.

Testing and QA roles: similar flexibility to development for test design and automation, but more constrained when testing requires access to client environments that are restricted to the secure delivery center.

Business analysis and consulting roles: variable, often requiring client presence for discovery workshops and requirement sessions but allowing flexibility for analysis and documentation work.

Project and delivery management roles: often require greater office presence because client escalation management and team coordination are more effective in person. Senior delivery managers are frequently required to be available in the office or on-site.

Infrastructure and cloud operations roles: often significant flexibility for monitoring and maintenance work, but strict presence requirements during planned maintenance windows, production incidents, and major deployments.

By Designation Level:

Freshers and SE-level employees: the least WFH flexibility in most units. The rationale is that in-person learning and mentoring are more effective for employees in their first one to two years. Many units specifically require SE-level employees to be in the office full-time or nearly full-time.

SSE and TA level: more flexibility, reflecting established capability and the trust built through demonstrated delivery. Two to three days in office per week is common for this level in hybrid arrangements.

TL and DM level: the expectation is higher in-office presence than for delivery engineers, because client management, team leadership, and escalation handling are activities where physical presence matters. TL and DM employees are often expected to be in the office four to five days per week.

Senior leadership (SDM and above): significant travel and on-site client time, with India office presence balanced against client location requirements.

Attendance Tracking: How Infosys Monitors Presence

Understanding how Infosys monitors attendance prevents the confusion that arises when employees are uncertain about the consequences of different work patterns.

The Physical Attendance Systems:

Infosys development centers use biometric or card-based access systems that record entry and exit times. Every swipe of the access card or biometric scan is logged. The attendance record is available to the employee through InfyMe and to the manager and HR through the HR management system.

The attendance data shows: days present in the office, arrival and departure times, and the total hours logged per day. This is the primary mechanism through which compliance with the in-office requirement is tracked.

The Remote Work Monitoring Tools:

For days when employees work from home, Infosys relies on a combination of: VPN connectivity logs (when the employee connected to the Infosys network and for how long), collaboration platform activity (Microsoft Teams or equivalent), and project-tracking tool activity (JIRA ticket updates, code commits, etc.).

These logs are not typically reviewed on a daily basis by managers as a surveillance mechanism. They are available for review if there is a specific concern about whether an employee was working during their declared WFH hours.

The Manager’s Role in Attendance Monitoring:

In practice, the primary monitoring of attendance compliance is through the manager’s direct observation and the team’s communication patterns. A manager who notices that a team member is not responding to messages during core hours, is consistently unavailable for meetings, or is not producing expected output during WFH days investigates through a conversation rather than through log review.

The formal attendance tracking system becomes relevant primarily in two contexts: when an employee’s attendance record is used in the appraisal (consistent poor attendance can be documented as a performance concern), and when there is a formal HR matter involving attendance.

The Consequences of Non-Compliance:

Non-compliance with the in-office requirement, without prior approval for exceptions, is treated as a policy compliance matter. The progression:

First instance: informal conversation with the manager about the expectation. Repeated instances: formal discussion documented in HR records, possible reflection in the appraisal assessment. Persistent non-compliance: formal corrective action, which may include a written warning in the HR record and potential impact on the next appraisal rating.

The consequences are rarely severe for occasional non-compliance. They become significant when non-compliance is systematic and documented over multiple months.

What “Work From Home Day” Means in the Attendance Record:

Days where the employee does not swipe in at any Infosys office are recorded as work from home if the employee was on approved WFH, or as leave if no WFH arrangement was in place. Employees need to ensure that WFH days are appropriately recorded in the system to avoid them being counted as unauthorized absences.

The process for recording WFH days varies by unit: some units use the leave management system for formal WFH recording, others rely on team-level tracking through email or Teams, and others use a dedicated attendance portal. Confirm the specific process used in your unit.

The Hybrid Work Model in Practice

The gap between the official hybrid policy and the day-to-day experience of hybrid work at Infosys is significant. Understanding what the practice actually looks like is more useful than understanding the policy statement.

The Three-Day-Per-Week Reality:

For employees in units with a standard hybrid arrangement (approximately three days in office), the practical experience:

Monday: typically a home day in many teams, as it is heavy with planning calls that work well remotely. Tuesday and Wednesday: typically the preferred in-office days because the middle of the week has the highest density of team and cross-team interactions. Thursday: often in-office. Friday: often a home day; client-facing sprint reviews or delivery milestones may require office presence.

This pattern is common but not universal. Some units require Tuesdays, Wednesdays, and Thursdays specifically (the “Anchor Days” concept). Others are completely flexible about which three days are in-office. The team lead or delivery manager communicates the specific expectation.

The Anchor Day Concept:

Some Infosys business units have implemented “anchor days” - specific days of the week when the entire team is expected to be in the office simultaneously, ensuring face-to-face collaboration at least once or twice per week. The purpose is to ensure that the in-office days are productive collaborative days rather than individual work days that happen to occur at the office.

When anchor days are implemented, individual flexibility about which days to come in is reduced: the anchor days are mandatory for everyone on the team, and the remaining required in-office days can be chosen flexibly.

The Effective Hybrid Meeting:

A consistent frustration in hybrid teams is the ineffective meeting format where some participants are in the office and others are on video. The office attendees are in a conference room where remote participants cannot read the whiteboard, hear side conversations, or fully participate. The remote participants feel excluded while the office participants feel their in-person presence is underutilized.

Well-managed Infosys teams address this by: using individual laptops even in conference rooms so everyone is on camera equally, using shared digital whiteboards (Miro, Microsoft Whiteboard) instead of physical ones, and designating specific meeting types as “all in person” versus “all remote” rather than mixing.

The quality of the hybrid meeting experience varies significantly by team and manager. Teams that have explicitly addressed the hybrid meeting challenge run better meetings than those that have not.

The Home Office Infrastructure:

Infosys does not typically provide home office infrastructure (desks, chairs, monitors, internet connectivity) for standard employees. The responsibility for creating an adequate home working environment falls on the employee. This contrasts with some product companies and GCCs that provide home office stipends.

The minimum adequate home office setup for productive WFH at Infosys: reliable internet (minimum 50 Mbps, 100 Mbps+ preferred), a dedicated workspace free from household interruptions, a computer with adequate processing power for VPN and video conferencing, a headset for audio quality in calls, and sufficient battery backup or UPS for areas with power fluctuations.

Infosys provides the laptop (standard issue) and the VPN client software. The connectivity and physical workspace are the employee’s responsibility.

Fully Remote Roles: When They Exist and Who Gets Them

Fully remote roles at Infosys exist but are genuinely rare. Understanding when they occur and who is eligible for them prevents unrealistic expectations.

When Fully Remote Arrangements Exist:

Fully remote arrangements at Infosys exist in specific circumstances:

Employees with specific high-demand skills who are located outside the primary cities where Infosys has offices, where relocation is not feasible and the skill is sufficiently scarce that Infosys hires remotely.

Employees who relocated during the pandemic to non-Infosys cities and whose remote work was grandfathered when the standard hybrid policy was reinstated.

Specific roles that are inherently remote by nature: some niche advisory, practice, or presales roles where the work is primarily writing, research, or client calls that do not require physical presence.

Project-specific arrangements for specific client engagements where the client is remote and the project structure permits fully distributed work.

Who Gets Fully Remote Arrangements:

The honest answer is that fully remote arrangements at Infosys are primarily available to: senior professionals at TL level and above who have established a track record, professionals with specific high-demand skills (cloud security specialists, specific AI/ML profiles, SAP specialists in niche modules) where the supply of qualified professionals in Infosys office cities is insufficient, and employees who negotiated remote work explicitly in their offer letter for a role that Infosys deemed remote-eligible.

SE and SSE level employees in standard delivery roles very rarely receive fully remote arrangements. The expectation for these levels is in-person mentoring, team presence, and the learning environment that office presence provides.

Maintaining a Fully Remote Arrangement:

For employees who have a fully remote arrangement, maintaining it requires: consistent strong performance that gives the manager no reason to question the arrangement, availability during core hours that is indistinguishable from office-based availability, proactive communication that compensates for the reduced informal visibility, and a professional home environment that is appropriate for client calls.

Fully remote arrangements are not always permanent. A change in the project (new client with on-site requirement), a change in the manager (new manager who is less flexible), or a business unit policy change can all affect a grandfathered remote arrangement. Employees in fully remote roles should periodically reconfirm the arrangement’s status rather than assuming it is permanent.

The Quiet Erosion of Remote Arrangements:

A pattern that repeats across large IT companies: a fully remote arrangement, when not reinforced, gradually erodes. The manager starts asking for more office presence “just this week” for a specific reason. Then a client requirement creates a week of office presence. Then the team’s anchor days policy is implemented and the employee is expected to be in for anchor days. The nominal fully remote arrangement becomes de facto hybrid without any formal policy change.

Employees with fully remote arrangements should document the arrangement formally (offer letter or written agreement), reference it specifically when any in-office expectation arises, and address erosion attempts early through a direct, professional conversation rather than gradually accommodating expectations that contradict the agreement.

Negotiating WFH in the Offer Letter and During Employment

The most effective point to secure a WFH or remote arrangement is at the offer stage, before the employment relationship is established. Negotiating after joining is harder.

What to Negotiate at the Offer Stage:

In the offer letter negotiation, the WFH arrangement should be specified explicitly. The offer letter specifies the joining location (city and office); anything beyond this requires a separate written agreement.

Effective negotiation language: “I want to confirm that the role includes a primarily remote / hybrid work arrangement. Specifically, I would like to confirm [fully remote / three days per week WFH / two days per week WFH]. Could you include this in the offer letter or provide a written confirmation of this arrangement before I sign?”

If the recruiter agrees verbally but the offer letter does not specify the arrangement, get it in writing before signing. “I appreciate the confirmation. Could you send a follow-up email with this confirmed so I have the written reference?” An unwritten verbal agreement about WFH is not enforceable and will not be honored when organizational policy changes.

What Is Negotiable:

The number of in-office days required per week is negotiable at the offer stage for roles where the client has no specific presence requirement. For roles with client-specified presence requirements, the client’s requirement is not negotiable.

Geographic location (which city to be based in) is negotiable if the role does not require proximity to a specific client site. For many Infosys digital and back-office roles, working from a non-primary city is negotiable if the candidate has strong skills.

What Is Not Negotiable:

Client-mandated presence requirements cannot be negotiated away at the offer stage. If the role involves a banking client that requires full in-office presence, no individual negotiation can override that requirement.

Mysore training attendance for freshers: freshers must attend Mysore training in person. This is not negotiable.

Security-related physical presence requirements: roles involving classified or highly sensitive client data that must be accessed only from secure environments cannot be conducted remotely.

Negotiating WFH During Employment:

If you are already employed at Infosys and want to adjust your work arrangement, the negotiation approach is:

Establish a track record first. Requesting additional WFH flexibility before demonstrating that remote work does not impact your output gives the manager no basis for agreement. At least three to six months of demonstrably strong remote performance (measurable through delivery metrics, client satisfaction, and peer feedback) is the foundation for the negotiation.

Make the business case, not the personal case. “I have found that I produce higher-quality code with fewer interruptions when working from home on focused development days. I would like to propose adjusting to two in-office days for team meetings and client calls, and three home days for focused development work” is a business case. “I prefer working from home because my commute is long” is a personal preference. The business case is more persuasive.

Get the agreement in writing. A manager’s verbal approval for an adjusted arrangement is not durable when the manager changes. A written confirmation through email is the minimum; an updated policy record in HR is better.

The Manager’s Discretion:

For standard employees in hybrid arrangements, the manager has significant discretion in interpreting and applying the hybrid policy. A manager who is flexible and trusts the team can make the practical experience much more WFH-friendly than the policy technically requires. A manager who prioritizes in-office presence can make the practical experience much more office-centric than the policy minimum requires.

The manager relationship is therefore the most practically important factor in the actual WFH experience. A manager who has seen consistent strong remote performance is a natural advocate for flexible arrangements; a manager who has seen poor remote performance is understandably skeptical.

The Tools and Infrastructure for Remote Work at Infosys

Infosys has invested significantly in remote work infrastructure since 2020. Understanding the specific tools available and their limitations helps employees use them effectively.

The Primary Collaboration Tools:

Microsoft Teams: Infosys’s primary real-time communication and video conferencing platform. Teams is used for: daily standups, client calls, team meetings, one-on-ones with managers, and persistent team chat. Teams is accessible on both the Infosys-issued laptop and, in a more limited form, on personal devices.

Microsoft SharePoint and OneDrive: document management and sharing. Project documentation, technical specifications, and shared team files are maintained in SharePoint libraries accessible from any location through the VPN.

Lex (Learning Platform): Infosys’s internal learning platform, accessible through the VPN for training content and certifications.

InfyMe: the HR self-service portal, accessible from any location for payslips, leave management, investment declarations, and HR forms.

The VPN:

Infosys employees working remotely connect to Infosys’s corporate network through a VPN client that is installed on the company laptop. The VPN is required for: accessing client systems, accessing internal Infosys systems (InfyMe, Lex, internal project tools), and conducting any work that involves proprietary or client-confidential data.

The VPN connection affects: internet speed (routing through the corporate network adds latency), access to non-approved websites (Infosys’s web proxy blocks categories of sites), and battery life (VPN clients consume additional resources).

Connectivity quality for VPN work depends on both the employee’s home internet connection and the VPN gateway load. During peak hours (9 AM to 12 PM IST, when large portions of the workforce are simultaneously VPN-connected), latency increases and disconnections are more frequent.

Project Management Tools:

JIRA (or equivalent): task tracking and project management. Accessible via VPN for most Infosys projects.

Confluence: documentation and wiki tool often used alongside JIRA. Accessible via VPN.

Git repositories: source code version control, hosted on Infosys’s internal servers or on client-approved cloud repositories. Accessible via VPN.

The Security Framework for Remote Work:

Infosys’s remote work security framework includes: full disk encryption on company laptops, endpoint security software (antivirus, DLP), VPN with split tunneling policies, multi-factor authentication for corporate systems, and screen sharing restrictions on non-approved applications.

The DLP (Data Loss Prevention) software monitors for attempts to copy client data to unauthorized locations: personal email, personal cloud storage, external USB drives. This monitoring is active both in the office and during remote work. Employees should never attempt to move client data to personal accounts or devices; this is a serious policy violation that can result in termination.

Tool Limitations in Practice:

The primary practical limitation of Infosys’s remote work tooling is the dependency on VPN for most work. VPN connectivity issues directly impact productivity: a dropped VPN connection in the middle of a production deployment, a video call, or a code review creates immediate work disruption.

The recommendation: maintain two internet connectivity options at home. The primary (broadband or fiber) for normal work, and a backup (mobile hotspot or secondary broadband provider) for when the primary has issues. Given that production incidents and critical client calls do not reschedule around personal internet outages, having backup connectivity is a professional necessity for anyone in a hybrid or remote role.

Career Implications of WFH vs Office Work

The WFH vs office work decision has genuine career implications that most employees do not explicitly consider. Being aware of them allows for deliberate choices.

The Visibility Factor:

In-office presence creates passive visibility: managers and senior stakeholders observe your work habits, your demeanor in informal settings, and your engagement with colleagues without any deliberate action on your part. This passive visibility contributes to the “familiarity advantage” that in-person employees have in promotion considerations and informal opportunity allocation.

Remote workers must substitute deliberate communication for this passive visibility. Regular status updates, proactive communication about contributions, active participation in virtual meetings, and visible engagement in internal platforms all substitute for the passive visibility that office presence provides.

Research on large organizations consistently shows that remote workers receive slightly lower performance ratings and slower promotion timelines than equivalent in-office workers, even when controlling for objective output measures. This is the visibility factor in action, not a judgment about remote work’s inherent productivity.

The Networking Deficit:

Office environments create casual networking opportunities: conversations at the coffee machine, hallway encounters with senior leaders, lunch with cross-team colleagues. These informal connections build the professional network within Infosys that creates opportunities: being thought of for a specific project, being recommended for an internal posting, being introduced to a client stakeholder.

Remote workers miss these informal connections systematically. The deliberate substitute: scheduling regular virtual coffee chats with colleagues across teams, attending internal events (which may be in-person), participating in internal communities and knowledge-sharing forums, and being deliberate about maintaining relationships with managers and cross-functional contacts.

The Learning Environment:

For early-career employees in particular, office presence provides a learning-rich environment: overhearing a senior engineer’s troubleshooting approach, watching how a team lead conducts a client call, absorbing professional norms through observation. Remote learning from these informal sources is significantly reduced.

This is the genuine basis for Infosys’s preference for in-office presence for SE-level employees. The learning environment at the office is genuinely richer for early-career professionals than the home environment, and the pace of skill and professional development in the first two years is meaningfully higher in office-present environments.

The Project Assignment Impact:

For certain high-profile projects (client onsite visits, major strategic accounts, innovation labs), in-office or on-site presence is a de facto requirement for participation. Remote employees may be systematically excluded from opportunities that require physical presence, not through any discriminatory intent but through practical logistics.

An employee who is remote during the client visit when the engagement team is presenting may not be considered for the follow-on project that results from that visit. An employee present at the visit, even in a junior capacity, may be included in the follow-on team due to having been present and visible.

The Balance Point:

The career-optimal work arrangement for most Infosys employees is hybrid, with more in-office days than the minimum required. The career costs of full remote work (visibility deficit, networking deficit, opportunity exclusion) outweigh the personal benefits for most career stages. The career costs of full in-office work (commute time, fixed schedule constraints) are real but manageable for most city-based employees.

The specific calibration depends on: the career stage (early-career benefits more from office presence than senior-career), the role type (leadership roles benefit more from presence than individual contributor technical roles), and the personal circumstances (significant commute, family caregiving responsibilities, health considerations).

WFH for Freshers: The Reality

Freshers who join Infosys with the expectation of significant WFH flexibility based on what they saw during the pandemic or heard from older batchmates typically encounter a different reality.

The Standard Expectation for Freshers:

Most Infosys business units expect SE-level freshers to be in the office four to five days per week, particularly during the first year of employment. The rationale is consistent across business units: the learning curve is steepest in the first year, the mentoring relationship is most effective in person, and the professional norm formation that happens in an office environment is genuinely valuable for someone entering professional work for the first time.

This expectation is communicated (with varying clarity) during the offer process and more explicitly during Mysore training. Freshers who join with the expectation of two to three days WFH per week are often surprised to find that their project team or business unit expects near-full-time office presence in the first year.

How to Navigate WFH Expectations as a Fresher:

The most effective approach for freshers who want flexibility is to establish a track record of strong delivery and reliable professional behavior before requesting any adjustment to the standard expectation.

A fresher who has been on the project for six months, delivered consistently well, built a positive reputation with the team lead, and demonstrated that their remote work (during the occasional approved WFH day) is as productive as their office work has a far stronger case for a hybrid arrangement than one who has just joined.

Do not request WFH flexibility in the first three months. The request signals that the employee is not fully committed to the learning investment that early-career in-office presence provides, and it is almost always refused.

By month six to eight, if the delivery record is strong, a request for one additional WFH day per week (from none or one to two) is a reasonable conversation with the team lead. Frame it around productivity: “I have found that my focused development work is more efficient when done from home. I would like to propose taking one WFH day per week for focused coding, while continuing to be in the office for all team meetings and client calls.”

The Mysore Training WFH Question:

Mysore training is entirely on-campus at the Infosys training facility. There is no WFH component to Mysore training. All trainees are physically present for the duration of the training. This is non-negotiable.

The First Project WFH Question:

In the first project after Mysore, the WFH arrangement is determined by the project’s requirements and the business unit’s standard policy. The fresher does not bring WFH expectations to the first project; they adapt to the project’s requirements.

WFH During Special Circumstances

Beyond the standard policy, specific circumstances create temporary or permanent adjustments to work arrangements.

Medical Reasons:

Employees with documented medical conditions that make commuting or office presence difficult can request temporary or longer-term WFH arrangements through HR. The request requires: a medical certificate from a registered physician documenting the condition, an HR review, and manager agreement.

Medical-reason WFH is processed through the formal accommodation request process. The HR team is required to engage with medical accommodation requests seriously and cannot simply deny them without considering the specific circumstances. The accommodation must be reasonable and consistent with the employee’s ability to perform their essential job functions.

Maternity and Paternity Leave and Return:

Post-maternity leave return often comes with a transitional period of WFH or part-time arrangements. Infosys’s maternity policy includes statutory maternity leave (26 weeks for the first two children) and the return process can include a structured reintegration that accommodates nursing or caregiving needs through flexible hours and hybrid arrangements.

The maternity return WFH accommodation is not automatic; it requires discussion with the manager and HR. The manager and HR are expected to facilitate a reasonable return arrangement given the statutory protection of maternity-related accommodations.

Natural Disasters and Extreme Weather:

During natural disasters, extreme weather events (cyclones, flooding, severe heat waves), or public health emergencies, Infosys activates its business continuity protocols which may include temporary full WFH. These are organizational decisions communicated through InfyMe and the manager.

Personal Emergencies:

For personal emergencies that require temporary WFH (a family health crisis, a situation requiring the employee to travel to their hometown while remaining available to work), WFH can be approved as a temporary exception with manager and HR approval. These are handled case-by-case.

The key: communicate proactively, get written approval, and ensure that the work commitments are met during the temporary arrangement. An undisclosed absence from the office that turns out to involve working from a different city is not the same as an approved temporary remote arrangement.

COVID-19 and Future Health Events:

COVID-19 established that Infosys can effectively operate with the entire workforce remote. The infrastructure and policies built during the pandemic mean that future public health events requiring WFH can be activated quickly. The company’s pandemic response demonstrated both the capability and the willingness to implement universal WFH when circumstances require it.

Comparison: Infosys WFH vs Peer IT Services Companies

Placing Infosys’s WFH policy in context against TCS, Wipro, HCLTech, and Cognizant helps employees evaluate whether the arrangement is competitive within the IT services sector.

TCS:

TCS has been one of the most vocal advocates for return-to-office in the IT services sector. The company’s leadership has explicitly stated that WFH creates cultural and productivity challenges, and TCS has implemented policies requiring near-full office presence (four to five days per week) for most employees. TCS’s approach is more office-centric than Infosys’s.

The TCS comparison: Infosys’s hybrid policy is more flexible than TCS’s standard approach, though both vary by business unit and client requirements.

Wipro:

Wipro has implemented a hybrid model similar to Infosys’s, with approximately three days per week in office for most employees. The specific implementation varies by business unit and client requirements, similar to Infosys. The two companies have comparable approaches.

HCLTech:

HCLTech has maintained a hybrid approach broadly similar to Infosys and Wipro, with the specific day count varying by business unit and client requirement.

Cognizant:

Cognizant has implemented similar hybrid policies. The specific implementation varies more by business unit than by a single organizational policy.

The Common Pattern:

All major IT services companies have landed in broadly similar places: hybrid work with varying in-office day requirements (three to five days per week) depending on the project and client, with client requirements taking precedence over standard policy. The differentiation between companies on WFH flexibility is smaller than the differentiation between projects within the same company.

The practical reality: if WFH flexibility is the primary factor in choosing between IT services companies, the differences are marginal. The more significant differentiators are compensation, project quality, and career development opportunity.

IT Services vs Product Companies and GCCs:

The real WFH differentiation is between IT services companies as a group and product companies and GCCs. Many product companies (particularly those influenced by tech culture) offer greater WFH flexibility than IT services companies. Many premium GCCs offer remote-first or flexible hybrid arrangements that are more generous than the IT services standard.

For employees who prioritize remote work flexibility as a career requirement, the product company and GCC segment is more accommodating than the IT services segment, but this comes with the trade-offs described in the Lateral Hiring and Career Growth guides.

Managing WFH Effectively as an Infosys Employee

For employees who have WFH as part of their arrangement, making it effective requires deliberate management of the specific challenges that remote work creates in an IT services context.

The Availability Signal:

In an office, availability is communicated by physical presence. At home, availability must be communicated explicitly. The most effective availability signals for remote Infosys employees:

Microsoft Teams status: actively managed to reflect current status (Available, In a Meeting, Do Not Disturb). A perpetually green “Available” status when the employee is actually on a call is misleading; a consistent absent status when the employee is actually available creates unnecessary communication friction.

Response time: responding to messages within 15 to 30 minutes during core hours demonstrates availability. Longer response times create the impression of disengagement. If you will be unavailable for an extended period (a focused coding session, a call), communicate it proactively: “I am in heads-down mode until 3 PM, will check messages then.”

Proactive status communication: sending a brief morning message to the team lead (“Good morning, I am online and working on [current task]”) removes the need for the manager to wonder whether the remote employee is actually working.

The Productivity Environment:

Remote work productivity requires a dedicated workspace. Sharing a dining table with household members, being interrupted by family, or working in an environment with video-call-unfriendly backgrounds creates professional friction. The minimum requirements:

A dedicated desk or workspace that is consistently used for work, creating a psychological boundary between work and personal time. A neutral or professional video background (or a virtual background that is not distracting). A headset for audio quality in calls: the built-in microphone on a laptop picks up ambient noise that a headset eliminates. Reliable internet with backup connectivity.

The Distraction Management Challenge:

Home environments have categorically different distraction profiles from offices. The office has: other people’s conversations, open plan noise, physical interruptions. The home has: household chores, personal devices, family interruptions, streaming services. Different people have different optimal distraction management strategies; the common element is intentionality.

The Pomodoro technique (25 minutes of focused work, 5-minute break), deep work scheduling (designating specific hours as uninterruptible focused work time), and physical environment structuring (phone in another room, streaming services logged out on the work laptop) are all viable approaches.

Maintaining Professional Boundaries in WFH:

Remote work at IT services companies can create work-life boundary challenges. Because the work laptop is in the home, the temptation to “just quickly check” messages at 10 PM or “finish this one thing” on a Saturday is higher than in an office context where leaving the building creates a natural boundary.

Setting deliberate work hours and adhering to them is important for sustainable WFH. An employee who is always available creates an implicit expectation of always-on availability that is not sustainable and not required by Infosys’s policy.

The Social Isolation Risk:

Remote work, particularly for employees who live alone or in a new city, can create professional and personal isolation. The office environment provides incidental social interaction that remote work eliminates. Infosys employees on hybrid arrangements who use their in-office days purely for solo desk work miss the social and collegial benefit that office presence is designed to provide.

Use in-office days for: team interactions, informal conversations, visible participation in team culture, and the collegial connection that remote work does not provide. If the in-office days are simply “work at a desk in the office rather than at home,” the social and collegial benefit of office presence is lost.

The Future of WFH at Infosys

The WFH policy will continue to evolve. Understanding the forces that drive that evolution helps employees anticipate direction rather than being surprised by changes.

The Talent Competition Pressure:

IT services companies compete for talent against product companies and GCCs that often offer greater WFH flexibility. This talent competition creates pressure to maintain some level of WFH flexibility rather than reverting to full in-office requirements. Employees who would leave for more flexible employers represent a retention risk that influences policy decisions.

The Client Requirement Evolution:

As enterprise clients themselves adopt hybrid models, the requirement for fully on-site Infosys delivery teams is gradually relaxing in some segments. Clients who are hybrid employers are less likely to require their technology partners to be fully on-site. This trend slowly expands the space for Infosys’s hybrid arrangements.

The AI and Automation Effect:

The increasing use of AI tools for development, testing, and analysis may gradually reduce the benefit of in-person mentoring and informal learning, because AI-assisted development produces faster learning loops than observation-based learning. If AI tools raise the productivity of solo remote work relative to office-based collaboration, the organizational calculus around WFH requirements may shift.

The Real Estate and Cost Pressure:

Large office campuses represent significant fixed costs. As workforce headcount fluctuates with business cycles, the desire to optimize real estate costs creates pressure toward hybrid arrangements that allow offices to accommodate more employees per physical desk (hot-desking). This economic pressure is a structural driver of hybrid rather than full in-office policies.

What to Expect:

The current hybrid model (approximately three days in office, two days WFH as the organizational baseline, with client requirements creating variations) is likely stable for the near-to-medium term. A full return to pre-pandemic full in-office requirements is unlikely given the talent competition and real estate dynamics. A shift to greater WFH flexibility (two days in office, three at home) is possible as the talent competition intensifies, particularly for high-demand digital skills.

For employees planning their career decisions around WFH flexibility, the safe assumption is: Infosys’s hybrid model will remain broadly similar to its current form, with client requirements continuing to dominate the practical experience for most employees.

Frequently Asked Questions

1. What is the current Infosys WFH policy for 2024?

The standard Infosys hybrid policy requires approximately three days per week in the office for most employees, with the remaining days as WFH. The specific implementation varies significantly by business unit, project, and client requirements. Client requirements override the standard policy where they demand greater presence. The most accurate way to know your specific arrangement is to ask your manager and delivery manager what the project and client requirement is.

2. Do Infosys freshers get WFH?

Most Infosys business units expect freshers to be in the office four to five days per week for the first year, particularly during the first six months. The rationale is effective learning and mentoring in an in-person environment. WFH for freshers is typically an exception rather than a standard arrangement in the first year.

3. Does Infosys track if employees work from home?

Infosys tracks in-office attendance through the biometric/card access system. Remote work is tracked through VPN connectivity logs and collaboration tool activity. Systematic review of these logs as daily surveillance is not standard practice; they are used when specific performance or policy compliance concerns arise.

4. Can I work from a different city than my joining location?

Working from a different city without approval is a policy violation. Infosys assigns employees to specific locations, and working from an unapproved location (including another Indian city) without HR and manager approval is not permitted. If you need to temporarily work from a different city (travel, family circumstances), get explicit approval before doing so.

5. What happens if the client requires full in-office presence but I prefer to work from home?

Client requirements take precedence over individual preferences. If your project’s client requires full in-office presence, you must comply regardless of your personal WFH preference. If this is a deal-breaker, the appropriate resolution is requesting a project change to one with more flexible client requirements, which may or may not be feasible depending on your skills and available project openings.

6. How does WFH work during the Mysore training period?

There is no WFH component to Mysore training. All trainees are on-campus in Mysore for the duration of the foundation training program.

7. Can I work from home if I have a medical condition that makes commuting difficult?

Yes. Medical accommodation requests for WFH are processed through the formal HR accommodation request process. A medical certificate from a registered physician, an HR review, and manager agreement are required. Medical accommodations cannot be arbitrarily denied.

8. Does WFH affect performance ratings?

Indirectly. Remote workers face a visibility deficit that can affect performance assessments if they do not compensate with deliberate communication. Research consistently shows that remote workers receive slightly lower ratings than equivalent in-office workers on average, due to the visibility factor. Proactive communication, documented contributions, and strong delivery metrics compensate for this.

9. Is there a difference in WFH flexibility between Infosys Limited and Infosys BPM?

Yes. Infosys BPM typically has stricter in-office requirements than Infosys Limited’s IT services arm, because process delivery work often requires access to client systems in the secure delivery center. Infosys Limited’s hybrid policy is more flexible than Infosys BPM’s standard arrangement.

10. Can I negotiate a fully remote arrangement at the offer stage?

For specific roles that are remote-eligible (typically senior specialists or roles in geographies without Infosys offices), fully remote can be negotiated at the offer stage with a written confirmation in the offer letter or a supplementary agreement. For standard delivery roles, fully remote is not the standard offer and negotiation to this arrangement is difficult.

11. What tools does Infosys provide for remote work?

Infosys provides: the company laptop, VPN client software, Microsoft Teams, SharePoint, and access to project-specific tools through the VPN. Infosys does not typically provide home office hardware (monitors, chairs, desks) or internet connectivity stipends for standard employees.

12. How does WFH affect PF and gratuity?

WFH does not affect PF or gratuity calculations. These statutory benefits are calculated on the salary structure, which is not affected by whether the employee works from the office or from home. PF contributions, gratuity accrual, and all statutory benefits remain identical regardless of work location.

13. If I work from home regularly, does that count toward my experience for future job applications?

Yes. Experience is counted based on employment period, not work location. Remote work experience at Infosys counts the same as office-based experience for future employers’ background verification and experience claims.

14. What are the consequences of working from an unnapproved location (e.g., working from abroad while on personal travel)?

Working from abroad without approval is a policy violation with potentially significant consequences: tax implications (the country where work is performed may have tax jurisdiction), visa and work permit implications (working on a tourist visa in another country may be illegal), and Infosys policy violations. Always get explicit HR and manager approval before working from abroad, even temporarily.

15. Is Infosys’s WFH policy better or worse than TCS?

Infosys’s standard hybrid policy (approximately three days in office) is generally considered more flexible than TCS’s policy, which has been more office-centric in its post-pandemic implementation. However, both companies’ policies vary significantly by project and client, so the practical experience depends more on the specific project than on the company-level comparison.

The WFH Experience Across Different Infosys Cities

The WFH experience is not uniform across Infosys’s India locations. The city of posting significantly affects how the hybrid policy is experienced in practice.

Bengaluru:

Bengaluru hosts the largest concentration of Infosys employees and the largest Infosys development campus (Electronic City). The commute in Bengaluru is one of India’s most challenging, with average commute times exceeding 60 to 90 minutes each way for many employees.

The long commute creates genuine productivity pressure around in-office days: an 8-hour office day that involves 3 hours of commuting consumes 11 hours of the employee’s day. This is one reason why Bengaluru employees often advocate most strongly for WFH flexibility.

The Infosys management is aware of Bengaluru’s commute challenges and this awareness is reflected in the hybrid policy’s design. Three days per week in-office in Bengaluru is materially different from three days in a city with 20-minute commutes.

Hyderabad:

Infosys’s Hyderabad campus (Madhapur area) also involves significant commute times for employees from many parts of the city, though the city’s road infrastructure is generally better than Bengaluru’s.

Pune:

Pune’s Hinjawadi and Kharadi technology hubs have significant traffic but shorter absolute distances for most employees compared to Bengaluru.

Chennai, Kolkata, and Other Cities:

Infosys’s smaller India locations generally have more manageable commute times, which affects the WFH pressure less acutely. Employees in these locations typically experience less WFH advocacy culture compared to Bengaluru and Hyderabad.

The Geographic Dimension of WFH Negotiation:

When negotiating WFH arrangements, the commute burden in the specific city is a legitimate business case element. “My commute from my current residence to the Electronic City campus is 90 minutes each way, representing 15 hours per week in commuting time. I can redirect a meaningful portion of that time into productive work during WFH days” is a quantified business case that is specific to the Bengaluru context.

The WFH Infrastructure Checklist for Infosys Employees

Before settling into a regular WFH arrangement, verify that the home office setup meets the minimum professional standard for Infosys remote work.

Connectivity:

Broadband or fiber internet with minimum 50 Mbps download / 20 Mbps upload
Backup mobile hotspot or secondary broadband for connectivity failures
Router positioned to provide strong signal at the workspace (not across the house from the router)
Ethernet cable connection to router preferred over Wi-Fi for VPN stability

Hardware:

Infosys-issued laptop in working order (any hardware issues reported to IT helpdesk before WFH starts)
Headset with microphone for call quality (built-in laptop microphone is insufficient for prolonged use)
External monitor if available (significantly improves productivity for development work)
Webcam functional (most Infosys laptops have built-in webcams; verify it works before the first client call)

Workspace:

Dedicated desk or workspace separate from personal/leisure areas
Adequate lighting for video calls (front-lit, not backlit against a window)
Neutral or professional video background visible in the camera frame
Minimal interruption environment during core work hours
Adequate power and UPS for areas with voltage fluctuations

Software and Access:

VPN client installed and tested before first WFH day
Microsoft Teams installed and tested with audio and video
Access to all project tools confirmed through VPN before WFH day
InfyMe portal accessible for HR and administrative tasks

Security:

No sensitive client data on personal devices or personal cloud storage
Laptop screen locked when stepping away, even at home
VPN connected before accessing any client or Infosys systems
No sharing of company laptop with family members

This checklist ensures that the first WFH day is professionally effective rather than a series of connectivity troubleshooting sessions that undermine the case for WFH flexibility.

Understanding WFH in the Context of Your Offer Letter

For candidates who are evaluating Infosys offer letters, understanding how WFH terms are or are not reflected in the offer documentation is important.

What the Standard Offer Letter Specifies:

The standard Infosys offer letter specifies the joining location (city and office address) and the standard hybrid work policy reference. It does not typically specify the exact number of WFH days, because this varies by project and client. The offer letter may state something like: “Your primary work location will be [City]. You will be expected to adhere to the company’s hybrid work policy as communicated by your manager and HR from time to time.”

This language is deliberately flexible: “as communicated from time to time” means the company retains the right to change the expectation based on organizational and client needs.

What to Add if WFH Was Verbally Discussed:

If a specific WFH arrangement was discussed and agreed during the offer negotiation (for example, a primarily remote role for a specialist being hired from outside a Infosys office city), request that the specific arrangement be added to the offer letter or confirmed in a supplementary written agreement.

The language to request: “Working arrangement: primarily remote, with in-office presence at the [City] campus required for [specified events/frequency/conditions] as agreed.”

Without this written confirmation, the verbal agreement is not enforceable. Infosys HR can truthfully state that the offer letter reflects the standard hybrid policy if the specific arrangement was not documented.

When the Offer Letter Specifies a Different City From Your Desired WFH Location:

If your offer letter specifies Bengaluru as the joining city but you live in another city and hope to work remotely from there, this arrangement requires explicit written approval from HR beyond the offer letter. The offer letter city is the authorized work location. Working from a different city without authorization is a policy violation even if it is technically remote work.

Real Scenarios: WFH at Infosys in Practice

The following scenarios are composites of common WFH situations at Infosys. They illustrate how the policy plays out in practice.

Scenario 1: The Fresher With WFH Expectations

Rahul joined Infosys as an SE in Bengaluru after placement. During the campus process, the recruiter mentioned “hybrid work with flexibility.” Rahul expected two days per week WFH from day one.

Reality: Rahul’s project team expected five days per week in office for the first six months. The team lead explained that freshers are expected to be in office to maximize learning and mentoring effectiveness. Rahul adjusted, built a strong delivery record in six months, and then raised the WFH conversation. His team lead approved one WFH day per week from month seven onward.

Scenario 2: The Grandfathered Remote Worker

Priya was working fully remote from her hometown (a city without an Infosys office) since the pandemic period, when Infosys allowed full WFH. When Infosys reinstated the hybrid policy in 2022, her manager asked her to relocate to Bengaluru or transition to a different arrangement.

Priya raised this with HR, documenting that she had been working remotely for two years with no decline in delivery quality or client satisfaction. The delivery manager supported retaining her in a primarily remote arrangement given her strong performance record and the difficulty of replacing her specific cloud expertise. Her arrangement was formally documented as a remote exception.

Scenario 3: The Client Override Surprise

Arjun joined an Infosys data engineering team with the understanding that the arrangement was hybrid (three days office). Six months in, the team was assigned to a banking client engagement that required all team members to work from the secure Infosys delivery center five days per week due to the client’s data security requirements.

Arjun’s WFH days were eliminated for the duration of the banking engagement. He was told the change was required by the client and non-negotiable. He accepted it, and when the engagement ended twelve months later, the standard hybrid arrangement resumed.

Scenario 4: The Remote Work Abuse

Meera had a hybrid arrangement (three days office) but had been consistently working from home five days per week for four months, reporting office attendance on non-office days without actually being in the office. Her manager noticed the discrepancy between reported attendance and the access system records and raised it with HR.

The investigation confirmed the discrepancy. Meera received a formal written warning that was documented in her HR record and reflected in her appraisal. The WFH arrangement was also terminated and a fully in-office requirement was imposed for six months.

This scenario illustrates that misrepresenting attendance is treated as a serious policy violation, not a minor HR infraction.

Scenario 5: The Successful WFH Negotiation

Vikram was offered a role at a competitor that was fully remote at a 20 percent higher salary. He brought this competing offer to his delivery manager and HR, asking whether Infosys could match either the compensation or the remote arrangement.

HR reviewed the situation: Vikram was a Band 2 performer with three years of experience, held AWS SAA and Databricks certifications, and was the lead engineer on a high-profile client account. The delivery manager supported retaining him. The resolution: Infosys offered a retention bonus, a two-day-per-week additional WFH flexibility (moving from three to five in-office, the standard, to two days, more flexible), and a faster-tracked promotion timeline. Vikram stayed.

This scenario illustrates that WFH flexibility can be part of a retention negotiation for high-value employees.

The Ten Things Every Infosys Employee Should Know About WFH

The client requirement overrides everything. If your client requires full in-office presence, no individual preference or organizational policy changes that.
The official policy is a floor, not a ceiling. The hybrid minimum is three days in office; client requirements can push it to five days.
WFH flexibility is earned, not given. A strong delivery track record is the basis for WFH flexibility requests. Requests without track record are rarely approved.
Freshers are expected to be in office more, not less. The learning environment benefit of office presence is highest in the first year. Most units expect near-full in-office for the first six months.
Get WFH agreements in writing. Verbal agreements about WFH arrangements are not durable through manager changes or policy revisions. Written confirmation is necessary.
Remote work has career implications. Visibility deficit, networking deficit, and potential opportunity exclusion are real career costs of remote work that must be managed deliberately.
Misrepresenting attendance is a serious violation. Claiming office presence when not in office is documented in HR records and treated as an integrity matter.
The manager’s discretion is the most important practical variable. The actual WFH experience depends more on the manager’s approach than on the official policy.
WFH days require professional standards. Availability during core hours, prompt response to messages, professional video backgrounds, and reliable connectivity are not optional for WFH days.
The policy will continue to evolve. The current hybrid model is the equilibrium state, not a permanent one. Be prepared for both more and less flexibility based on business, client, and talent market conditions.

Infosys WFH Quick Reference

Factor	Standard Position	Exceptions
Official WFH policy	Hybrid ~3 days/week in office	Client requirements override
Fresher WFH	Near-full in-office first year	Only with strong 6-month track record
Fully remote roles	Rare, specific cases only	Senior specialists, remote-eligible roles
Client-mandated in-office	Must comply	No individual exception possible
Medical WFH	Available via HR process	Requires medical certificate
WFH tracking	Biometric + VPN logs	Not daily surveillance; used for HR issues
Tools provided	Laptop, VPN, Teams	Home connectivity not provided
WFH during Mysore	Not available	Mysore is entirely on-campus
WFH negotiation point	Offer stage (best)	During employment requires track record
Working from abroad	Not permitted without approval	Tax/visa implications apply

Article 27 of the InsightCrunch Infosys Series. Read all 30 articles at insightcrunch.com for the complete guide to every stage of the Infosys career journey.

Optimizing the Hybrid Week: A Practical Day-by-Day Framework

For employees in the standard three-days-in-office hybrid arrangement, intentionally designing which activities happen on which days significantly improves both productivity and career visibility.

The Principle of Day Design:

The office and home environments have different strengths. Office days are better for: collaborative work requiring real-time interaction, relationship-building with colleagues and managers, complex discussions with clients, whiteboarding sessions, and activities requiring access to hardware or secure facilities. Home days are better for: deep-focus individual work (coding, writing, data analysis), extended uninterrupted problem-solving, studying for certifications, and administrative work that does not require collaboration.

Aligning activities to environments multiplies the value of both.

Recommended Day Structure for Engineers (3 Office Days):

Monday (Home): review the previous week’s open items, plan the current week’s sprint tasks, respond to any weekend messages, set up the week’s work.

Tuesday (Office): Sprint ceremonies if they fall on Tuesday (planning, retrospectives, standups in person). One-on-ones with team lead or manager. Pair programming or collaborative technical sessions. Cross-team conversations.

Wednesday (Home): deep-focus development work. The midweek, mid-day WFH is productive for extended coding sessions without meeting interruptions.

Thursday (Office): client sprint reviews if they fall on Thursday (visible in client-facing formats). Knowledge-sharing sessions. Peer code reviews that benefit from in-person discussion.

Friday (Home): documentation, certification study, administrative items (expense reports, timesheet, performance goal updates).

For Senior Engineers and TLs (4-5 Office Days Typical):

The framework shifts: most days in office, with WFH reserved for: focused writing (technical proposals, architecture documents), client-preparation work that requires uninterrupted thinking, and any day where no client interaction is scheduled.

The Anchor Day Principle:

If the team uses anchor days, align WFH design with the anchor structure rather than against it. Being in office on anchor days for team collaboration, and using the non-anchor in-office days for the high-visibility activities (client reviews, manager meetings) maximizes the value of every in-office day.

The WFH Communication Protocol: What Strong Remote Workers Do Differently

The difference between a remote worker who is professionally effective and one who struggles is almost entirely in communication behavior.

The Morning Check-In:

Send a brief morning message to the team channel or to the manager: “Good morning, I am online. Working on [current sprint task] today. Available for any questions.” This takes 30 seconds and removes the ambiguity about whether you are actually working.

The Blocker Communication:

When working remotely and encountering a technical blocker or dependency, communicate it earlier than you would in an office. In an office, you might spend 30 more minutes trying before asking because you can see whether the senior engineer is available. Remotely, you cannot see availability, so the standard should be: attempt for 30 minutes, then send a specific message: “I am stuck on [specific technical issue]. I have tried [approaches]. Could you help me with this when you have 15 minutes today?”

The Status Update Cadence:

Update JIRA tickets as work progresses, not just at end-of-day. When working remotely, the JIRA ticket is often the primary visibility tool the manager has for current work. A JIRA ticket that has been “In Progress” for three days without a comment update creates uncertainty about whether the work is progressing.

The Proactive End-of-Day Summary:

Once per day (typically at the end of the working day), send a brief summary to the team lead: “Today I completed [specific tasks], submitted [PRs or deliverables], and attended [meetings]. Tomorrow I plan to [next tasks]. No blockers currently.” This takes two minutes and replaces the passive end-of-day visibility that office presence provides.

The Video-On Default:

For client-facing calls and one-on-ones with managers, camera on is the professional default in remote settings. The no-camera default creates an impersonal, low-engagement impression that erodes the relationship over time. Reserve camera-off for large group calls where individual camera visibility adds no interaction value.

WFH and Mental Health: The Honest Conversation

Remote work has well-documented mental health dimensions that Infosys employees should be aware of. Acknowledging these is important rather than pretending they do not exist.

The Isolation Risk:

Working from home full-time or near-full-time eliminates the incidental social interaction that office environments provide. For employees who live alone, who have moved to a new city without an established social network, or who are naturally extroverted, full-time remote work can produce genuine professional and personal isolation.

The symptoms: feeling disconnected from the team, reduced motivation, difficulty maintaining work-life boundaries (work bleeding into all waking hours because there is no natural separation), and reduced professional enthusiasm. These are not personal weaknesses; they are predictable responses to the removal of social and professional structure.

The Boundary Collapse Risk:

Home environments without deliberate structure blur the boundary between work and personal life. The laptop is always accessible; the next task is always just a click away. Employees who work hybrid or remote without explicit work-hour boundaries often find themselves working longer hours than they would in an office, not because of productivity but because the stopping signal that leaving the office provides is absent.

The Infosys Support Resources:

Infosys’s employee assistance program (EAP) provides confidential counseling and mental health support that is accessible to all employees. The specific resources vary by region; the InfyMe portal lists the available support services. These services are available regardless of work location.

If the remote work arrangement is creating genuine mental health challenges, this is a legitimate reason to discuss adjusting the arrangement (to more in-office days or a different structure), not a reason to endure the situation silently.

The Deliberate Reconnection:

Employees who recognize the isolation risk of WFH and actively counter it tend to have better experiences. Specific practices: joining Infosys’s in-person employee communities (sports, cultural, professional development), using in-office days for social reconnection not just task completion, maintaining a social life outside Infosys that provides non-work interaction, and scheduling regular video calls with colleagues that are relationship-building rather than task-focused.

Complete Policy Summary: What We Know and What Remains Variable

Because the Infosys WFH policy has multiple layers and frequent evolution, it is useful to separate what is stable and consistently true from what varies and cannot be stated universally.

Consistently True (Stable Elements):

Client requirements override the standard hybrid policy. This has been consistent across all Infosys policy versions.

Mysore training is fully on-campus. No WFH during foundation training.

Medical accommodation for WFH is legally required to be considered. This is driven by statutory requirements, not internal policy.

Misrepresenting attendance is a serious policy violation. This is treated as an integrity matter regardless of the specific WFH arrangement.

Working from an unauthorized location (different city or abroad) without explicit approval is a policy violation. Tax and visa considerations make this a compliance matter, not just a preference issue.

Variable (Depends on Business Unit, Manager, Client, Project Phase):

The specific number of required in-office days per week: ranges from zero (for specific approved remote roles) to five (for fully on-site client requirements) with most employees in the two-to-four range.

Whether anchor days are required: depends on the business unit’s policy, which is set by the unit head.

The tracking strictness of attendance compliance: varies by manager and business unit.

The availability of WFH for freshers: varies by business unit and team lead approach.

The WFH tools available and their quality: varies by project and the specific client environment.

The Bottom Line:

Know your specific arrangement by asking your manager and delivery manager, not by relying on the general organizational policy. The general policy tells you the boundaries; the project and client requirements tell you what the arrangement actually is.

This guide provides the framework for understanding both. The specific details for your specific situation require the direct conversation with your project team.

Infosys WFH in Numbers: What the Data Tells Us

Specific numbers help frame the WFH conversation at Infosys rather than relying on vague impressions.

Infosys Headcount and Location Distribution:

Infosys employs approximately 300,000 to 340,000 employees globally (the figure varies with hiring and attrition cycles). Approximately 60 to 65 percent of this headcount is India-based. The India workforce is concentrated in Bengaluru (the largest campus), Hyderabad, Pune, Chennai, Mysore (training campus), and Chandigarh, with smaller centers in Kolkata, Bhubaneswar, Nagpur, and other cities.

The Post-Pandemic Return:

When Infosys moved toward hybrid return in 2022, the target was bringing approximately 75 to 80 percent of the India workforce to some level of in-office presence, with the remaining 20 to 25 percent in roles or situations that warranted continued remote work (medical, remote-eligible specialist roles, or geographic exceptions).

The Commute Dimension:

In Bengaluru, the Infosys Electronic City campus is one of India’s largest IT campuses. The campus employs tens of thousands of people. Average commute time from residential areas in Bengaluru to Electronic City ranges from 45 minutes (nearby areas) to 120 minutes or more (from north Bengaluru) in peak hours. The total daily commute cost for a three-days-per-week in-office employee working at Electronic City from a 60-minute-each-way location is 360 minutes per week (6 hours) in transit.

The Productivity Research Context:

Academic and industry research on hybrid work consistently shows: knowledge workers, including software developers, report higher individual productivity in remote settings due to fewer interruptions. Teams report better collaboration and cohesion from some in-person interaction. The optimal arrangement for most knowledge workers in terms of combined individual and team productivity is two to three days per week in office with the remainder remote. This research context informed Infosys’s post-pandemic hybrid policy design.

The Attrition Connection:

Infosys’s attrition rate peaked at approximately 28 percent in some quarters following the aggressive return-to-office push post-pandemic, before settling to lower levels as the hybrid model was refined. The correlation between return-to-office pressure and attrition spikes is observable across IT services companies and is one of the organizational pressures that makes maintaining some WFH flexibility a business necessity rather than just an employee preference.

Using Leave for WFH vs Taking WFH Days

A clarification that confuses many employees: the difference between using leave and using WFH days.

WFH Days Are Working Days:

WFH days are not leave. An employee on an approved WFH day is expected to be fully available during core hours, responsive to messages, attending scheduled meetings, and delivering on their work commitments. WFH is a work location flexibility, not a reduction in work obligations.

When to Take Leave vs WFH:

Take leave when you will not be working: vacation, personal emergencies where you cannot work, medical illness, or any situation where you will not be available for work during normal hours.

Use WFH when you are fully working but from home. The output expected from a WFH day is identical to the output expected from an office day.

The Misuse Risk:

Using WFH days as de facto partial leave (being available for two to three hours but not truly working for the full day) is a policy violation. If the workday will be genuinely reduced due to personal circumstances, the correct approach is to take half-day leave for the portion that will not be worked, not to claim a full WFH day.

The Documentation:

WFH days should be recorded in the attendance system through whatever mechanism your unit uses (leave portal WFH category, email confirmation, or attendance portal). Unrecorded WFH days that appear in the access system as absent days without leave record create compliance discrepancies that require explanation.

The Last Word on WFH at Infosys

Infosys’s work from home policy, in its current hybrid form, represents a genuine accommodation of the post-pandemic shift in employee expectations while balancing the client delivery obligations and organizational learning culture that the business requires. It is neither the unlimited flexibility that some employees want nor the full return to pre-pandemic in-office requirements that some organizations have mandated.

The practical experience of any individual employee within this framework depends almost entirely on: the client their project serves (the single biggest determinant), the business unit’s culture, and the manager’s approach to hybrid work. These three variables produce a range of actual experiences that spans from near-fully-remote to near-fully-in-office, all within the boundaries of Infosys’s organizational policy.

Navigating this framework effectively requires understanding all three layers, knowing which layer controls your specific situation, engaging with the policy through proper channels (offer letter negotiation, documented agreements, medical accommodation requests) rather than informal assumptions, and building the track record of strong remote performance that is the prerequisite for any flexibility discussion.

The guide has covered every dimension of this navigation. The decisions about where to work, how to make the case for flexibility, and how to maintain productivity and career momentum in whichever arrangement results from those decisions are, ultimately, the employee’s to make.

Make them deliberately, with accurate information, and they will produce better outcomes than most employees achieve by navigating this by feel.

This WFH guide connects to several other articles in the series. The Infosys Work Culture and Exit guide (Article 8) covers the broader workplace culture including office environment, team dynamics, and the resignation process. The Infosys Fresher First 90 Days guide (Article 21) covers the first project experience including the office presence expectations for new joiners. The Infosys Lateral Hiring guide (Article 23) covers how to negotiate WFH arrangements at the offer stage for experienced hires. The Infosys Performance Appraisal guide (Article 26) covers the career implications of WFH on visibility and rating outcomes.

Article 27 of the InsightCrunch Infosys Series. Read all 30 articles at insightcrunch.com.

WFH Policy Comparison: Before, During, and After the Pandemic

Understanding how Infosys’s WFH policy has evolved provides context for where the current policy sits and where it may move.

Pre-2020 (Pre-Pandemic Standard):

Standard: 5 days per week in office for essentially all employees
WFH: exceptional, required specific manager and HR approval
Remote roles: virtually non-existent for standard delivery positions
Technology: limited remote work infrastructure; VPN existed but not at scale
Culture: in-office presence assumed and expected

2020-2022 (Pandemic Period):

Standard: fully remote for all employees during lockdown periods
WFH: universal, no approval needed
Infrastructure: rapid investment in VPN capacity, Microsoft Teams rollout, security frameworks for home work
Culture: remote work became normalized across the organization
Hiring: candidates were hired and onboarded entirely remotely

2022-Present (Hybrid Return):

Standard: approximately 3 days in office / 2 days WFH for most employees
WFH: built into the standard policy but with client override provisions
Infrastructure: maintained post-pandemic investment in remote work tools
Culture: hybrid culture in active development, with ongoing calibration
New hires: expected to be more in-office than pandemic-era employees

The Policy Stability Assessment: The current hybrid model has been stable for approximately two to three years, suggesting it has reached a working equilibrium. Major disruptions (another pandemic, significant business model change, major client requirement shifts) could change it. Absent such disruptions, the current three-day in-office framework is the foreseeable standard.

This evolution context explains why Infosys employees have such varied expectations: the generation that joined pre-2020 experienced full in-office as normal; the pandemic generation experienced full remote as normal; the post-2022 joiners are calibrated to hybrid from day one. Managing a team with all three groups requires deliberate communication about expectations rather than assuming everyone shares the same baseline assumption.

The WFH Policy FAQ for Specific Situations

Beyond the fifteen main FAQs, the following addresses the specific edge-case situations that employees encounter.

Q: I have been working from home for a year without my manager explicitly approving it. Is this a problem? A: If the work arrangement was informally allowed by practice but never formally documented, you are in a vulnerable position. If the manager or HR raises the issue, you have no written confirmation to reference. Document the arrangement proactively by sending an email to your manager: “I want to confirm our current working arrangement is [X days WFH / primarily remote]. Please let me know if this is different from your understanding.” The manager’s reply (or lack of objection) creates a partial paper trail.

Q: My new manager is more strict about in-office than my previous one. Can I appeal to the previous arrangement? A: The previous manager’s informal approval is not binding on the new manager. The new manager can set the in-office expectation consistent with the organizational policy. If you had a formally documented arrangement, that carries more weight. If it was informal, the new manager’s standard applies. The path forward is establishing a track record with the new manager before negotiating any flexibility.

Q: I want to work from home on Fridays specifically because of Shabbat / religious observance. Is this accommodatable? A: Religious accommodation requests are handled through HR and may allow specific day flexibility. Submit the request formally through HR with the specific days and the religious observance basis. Religious accommodations are required to be considered under Indian labor law, though the specific implementation depends on operational feasibility.

Q: My team is distributed across multiple cities. Do in-office requirements still apply if there is no team in my city? A: If you are the only team member in your city, in-office requirements still technically apply (you work from the Infosys office in your city, not from home). If there is no Infosys office in your city, this is likely already a formally approved remote arrangement. Clarify the specific expectation with HR.

Q: Can I work from a coworking space instead of the Infosys office? A: Working from a coworking space is not the same as working from the Infosys office for compliance purposes. The in-office requirement means the Infosys development center (or a client site). A coworking space counts as working from home for attendance purposes. There is no security objection to working from a coworking space on WFH days (provided the security protocols for VPN and screen privacy are maintained), but it does not satisfy the in-office requirement.

Q: I have a health condition that makes the office environment difficult (noise sensitivity, temperature regulation issue). Can I request accommodation? A: Health-related accommodation requests can cover workspace adjustments, not just WFH. If the specific condition affects your ability to work in an open office environment, the accommodation request might focus on a specific workspace arrangement (quieter area, specific seating, temperature adjustment) rather than full WFH. Discuss with HR through the accommodation request process.

These edge cases represent the situations where standard policy guidance is insufficient and specific HR consultation is necessary. Always go to HR directly for circumstances not covered by the general framework. The information in this guide provides the context; the specific resolution requires the conversation with HR.

Infosys WFH Policy, Hybrid Work Arrangements, Remote Work Rules, and What Employees Actually Experience in 2024

Table of Contents

The Official Infosys WFH Policy Framework

The Client Override Reality

How Work Arrangements Differ by Business Unit and Role

Attendance Tracking: How Infosys Monitors Presence

The Hybrid Work Model in Practice

Fully Remote Roles: When They Exist and Who Gets Them

Negotiating WFH in the Offer Letter and During Employment

The Tools and Infrastructure for Remote Work at Infosys

Career Implications of WFH vs Office Work

WFH for Freshers: The Reality

WFH During Special Circumstances

Comparison: Infosys WFH vs Peer IT Services Companies

Managing WFH Effectively as an Infosys Employee

The Future of WFH at Infosys

Frequently Asked Questions

The WFH Experience Across Different Infosys Cities

The WFH Infrastructure Checklist for Infosys Employees

Understanding WFH in the Context of Your Offer Letter

Real Scenarios: WFH at Infosys in Practice

The Ten Things Every Infosys Employee Should Know About WFH

Infosys WFH Quick Reference

Optimizing the Hybrid Week: A Practical Day-by-Day Framework

The WFH Communication Protocol: What Strong Remote Workers Do Differently

WFH and Mental Health: The Honest Conversation

Complete Policy Summary: What We Know and What Remains Variable

Infosys WFH in Numbers: What the Data Tells Us

Using Leave for WFH vs Taking WFH Days

The Last Word on WFH at Infosys

WFH Policy Comparison: Before, During, and After the Pandemic

The WFH Policy FAQ for Specific Situations

Table of Contents

The Official Infosys WFH Policy Framework

The Client Override Reality

How Work Arrangements Differ by Business Unit and Role

Attendance Tracking: How Infosys Monitors Presence

The Hybrid Work Model in Practice

Fully Remote Roles: When They Exist and Who Gets Them

Negotiating WFH in the Offer Letter and During Employment

The Tools and Infrastructure for Remote Work at Infosys

Career Implications of WFH vs Office Work

WFH for Freshers: The Reality

WFH During Special Circumstances

Comparison: Infosys WFH vs Peer IT Services Companies

Managing WFH Effectively as an Infosys Employee

The Future of WFH at Infosys

Frequently Asked Questions

The WFH Experience Across Different Infosys Cities

The WFH Infrastructure Checklist for Infosys Employees

Understanding WFH in the Context of Your Offer Letter

Real Scenarios: WFH at Infosys in Practice

The Ten Things Every Infosys Employee Should Know About WFH

Infosys WFH Quick Reference

Optimizing the Hybrid Week: A Practical Day-by-Day Framework

The WFH Communication Protocol: What Strong Remote Workers Do Differently

WFH and Mental Health: The Honest Conversation

Complete Policy Summary: What We Know and What Remains Variable

Infosys WFH in Numbers: What the Data Tells Us

Using Leave for WFH vs Taking WFH Days

The Last Word on WFH at Infosys

Related Articles in the InsightCrunch Infosys Series

WFH Policy Comparison: Before, During, and After the Pandemic

The WFH Policy FAQ for Specific Situations

Related Reading