The Infosys Global Education Centre in Mysore is unlike any corporate training facility most freshers have encountered. Spread across a campus the size of a small township, it houses tens of thousands of trainees at any given time, runs parallel training cohorts across dozens of classrooms and labs, and operates with a level of logistical precision that reflects decades of refining the art of onboarding large engineering batches. For the majority of Infosys freshers, the months spent here represent the last structured learning environment they will inhabit before the demands of client delivery take over - and they are months that many Infosys employees describe, years later, as among the most formative of their professional lives.
This guide is written as the inside account that most new joiners wish they had before they arrived. Not the sanitised version in the official orientation slides, but the ground-level reality: what actually happens in the first week, how the training schedule is structured and experienced, what the assessment pressure genuinely feels like, how stream allocation works and what it means for your career, what the campus life involves beyond the classroom, what the rules are and what the consequences of breaking them look like, and what the transition from training to project deployment actually entails. If you are about to go to Mysore, or if you are trying to understand what someone you know is experiencing there, this is the guide that covers all of it.
Table of Contents
- The Mysore GEC: Understanding the Scale and Purpose
- Before You Arrive: Pre-Joining Checklist and What to Bring
- Day One: Reporting, Induction, and First Impressions
- Accommodation: Hostels, Rooms, and Living Arrangements
- The Daily Schedule: A Week in the Life of a Mysore Trainee
- The Training Curriculum: Generic Training Phase
- Stream-Specific Training Phase
- Soft Skills and Communication Training
- The Assessment and Evaluation System
- Stream Allocation: How It Works and What It Means
- The Project Phase: From Classroom to Real Delivery
- Food, Facilities, and Daily Life on Campus
- Cultural Life, Extracurriculars, and Social Dynamics
- Rules, Restrictions, and the Disciplinary Framework
- Tips for Thriving During Mysore Training
- The Transition: From Training Completion to Project Allocation
- Frequently Asked Questions
The Mysore GEC: Understanding the Scale and Purpose
The Infosys Global Education Centre in Mysore, commonly referred to simply as the GEC or “Mysore campus,” is one of the largest corporate training facilities in the world. The campus spans hundreds of acres and includes residential blocks, multiple academic buildings with hundreds of classrooms and computer labs, sports facilities, food courts, retail outlets, healthcare facilities, and recreational spaces. It functions less like a training centre and more like a self-contained residential university.
The scale is not incidental. Infosys absorbs thousands of engineering freshers per hiring cycle, and the Mysore GEC is the infrastructure through which all of them pass. The training programme is designed to transform engineering graduates from diverse academic backgrounds, with widely varying levels of programming exposure, into professionals who can contribute to Infosys’s client delivery operations within a defined period.
The philosophy behind the GEC is what Infosys calls the “learning by doing” model. The training is not primarily lecture-based information transfer. It combines instruction, hands-on programming exercises, project simulations, and continuous assessment into a structured progression that is meant to replicate - in compressed form - the kind of learning that a junior engineer might experience over the first two years of a job. Whether this compression is fully successful depends significantly on what each trainee brings to the experience and how seriously they engage with the curriculum.
The GEC’s role in Infosys’s talent pipeline extends beyond technical training. It is also the site where Infosys’s culture, values, and ways of working are actively transmitted to new joiners. The campus environment, the rules, the team-based project work, and the formal and informal interactions between trainees and faculty are all vectors through which the organisation communicates what it means to be an Infosys employee. New joiners who understand this dual function of the training - technical onboarding and cultural immersion - approach the experience with a more complete picture of what it is designed to accomplish.
The batches and cohorts. The GEC runs multiple training batches simultaneously. A single training batch is typically several hundred to a few thousand trainees, depending on the hiring cycle. Each batch has a cohort structure: trainees are grouped into smaller units (often called sections or classes) of 30 to 50 people for the classroom portions of training. This smaller grouping is the primary social and academic unit within which most of the training experience unfolds. The relationships formed within a section often persist long after Mysore, becoming the foundation of early professional networks within Infosys.
The GEC and its role in Infosys history. The Mysore campus has been the site of Infosys’s fresher training since the early years of the company’s rapid growth phase. The campus itself has expanded multiple times as hiring volumes grew. Understanding that the campus was purpose-built around the specific demands of large-scale technology training - with computer labs designed for simultaneous programming exercises, assessment centres capable of proctoring hundreds of examinations simultaneously, and residential infrastructure designed to house thousands comfortably - helps new joiners understand why the campus operates the way it does and why certain logistical rules exist.
Before You Arrive: Pre-Joining Checklist and What to Bring
Preparation for Mysore begins well before the joining date, and the candidates who arrive prepared for both the administrative and personal logistics of the experience have a significantly smoother first week.
Documents to carry. The offer letter from Infosys specifies the documents required for joining. These typically include: all original academic certificates and marksheets (from Class 10 through the most recent qualification), the original degree certificate, all copies of identity documents (Aadhaar card, PAN card, Passport if applicable), a specified number of passport-size photographs with a white background, the medical fitness certificate signed by a doctor (the format is usually specified by Infosys HR), the relieving letter or experience certificate if previously employed, and all signed bond documents as specified in the pre-joining portal.
Document handling at Mysore is a formal, HR-processed activity. Original documents are submitted and verified; they are not retained permanently but are checked against copies. Missing documents create administrative complications that persist through the joining process and can delay system access, ID card issuance, and in serious cases, the formal confirmation of employment. Carry every document on the list, in the specified quantity, with appropriate protective packaging to prevent damage during travel.
What to bring for personal living. The hostel rooms at Mysore are furnished and provide the basics, but personal comfort items are the trainee’s responsibility. Bring: adequate clothing for the training period (the dress code requires business casual or formal attire during training hours, while personal clothes are worn in the hostel and recreational areas), formal shoes and casual footwear, a laptop (Infosys provides access to training systems, but a personal laptop is valuable for self-study and accessing training materials in the hostel), necessary toiletries and personal care items (the campus has a supermarket, but bringing a personal supply reduces early friction), bedding if the offer letter specifies that it is not provided (many trainees bring at least a personal pillowcase), any prescription medications with copies of prescriptions, and a reasonable amount of cash (digital payment is widely accepted on campus, but some transactions require cash).
Financial preparation. The salary during the Mysore training period is paid, but the first salary credit has a processing delay that catches many freshers unprepared. In the first two to three weeks, before the first salary is credited, trainees need to manage their own expenses. Arriving with at least 10,000 to 15,000 rupees in accessible funds prevents hardship during this initial gap. The campus has an ATM, but managing the transition period without financial stress requires some advance planning.
Mental and physical preparation. This point is rarely mentioned in official pre-joining communications but is practically important: the Mysore training schedule is demanding. The academic hours are long, the assessments are frequent, and the adjustment to hostel living - particularly for trainees who have lived at home throughout college - can be tiring in the early weeks. Arriving with reasonable physical fitness (sufficient sleep in the days before joining, not exhausted from a long, disruptive travel experience) and a mental posture of engagement rather than passive attendance sets the tone for the entire training period.
Travel to Mysore. Mysore city is accessible by road, rail, and air (the nearest major airport is Bengaluru’s Kempegowda International Airport, with road connectivity from there). The Infosys campus is located on the outskirts of Mysore city, and the exact address is provided in the joining communication. First-time visitors to Mysore unfamiliar with the city should use the pick-up arrangements Infosys provides (where available for the batch) or confirm transportation logistics in advance. Arriving the evening before the official joining date, rather than the morning of, reduces the risk of travel delays affecting the first day.
Day One: Reporting, Induction, and First Impressions
The first day at the GEC is a carefully orchestrated logistics exercise that processes hundreds or thousands of new joiners simultaneously through a sequence of administrative, HR, and orientation activities.
Reporting time and the initial assembly. Trainees report at a designated assembly point - typically an auditorium or a large outdoor gathering space - at the specified time. The reporting desk is managed by HR and facilities teams who verify joining documents, confirm accommodation assignment, and issue the trainee’s initial identification and access credentials. This process takes longer than most trainees anticipate. Queues are long in large batch reporting events, and the physical process of verification, badging, and room assignment can take several hours.
First-day patience is a practical virtue. The queue culture of the first day sets expectations: the campus handles scale through process, not individual attention, and the administrative queues will be a recurring feature of the first week. Trainees who arrive expecting to be immediately absorbed into a welcoming orientation and find instead a two-hour queue for badge collection are less prepared than those who know in advance that administrative processing is the functional reality of day one at scale.
ID card and system access. The Infosys ID card is the central access credential for the campus. It unlocks entry to the academic buildings, the cafeteria billing system, the library, and the hostel. It is also the identity document required for all campus transactions. Losing the ID card triggers a replacement process that incurs a formal administrative request and a nominal fee. Guarding the ID card from day one is practical habit-formation.
System access - the login credentials for Infosys’s internal learning management system, email, and training resources - is typically issued on the first day or within the first two days. These credentials provide access to the training materials, the assessment calendar, the course progression tracking system, and internal communication channels. Setting up these credentials correctly and verifying access before the academic programme begins the next day prevents the first morning’s training sessions from being disrupted by login issues.
The orientation programme. After administrative processing, the first day typically includes a formal orientation session - sometimes called the induction programme. This session covers Infosys’s history, values (the six core values that underpin the Infosys culture: client value, leadership by example, integrity and transparency, fairness, excellence, and pursuit of excellence), the structure of the training programme, the rules and expectations of the GEC, the assessment framework, and the support resources available to trainees. Senior training faculty and occasionally senior Infosys employees address the batch.
The orientation content is genuinely useful, even where it feels formal or ceremonial. The values discussion, in particular, is more practically relevant than it appears in an auditorium setting: these are the values that the HR interview evaluated the candidate against, that the performance appraisal system uses as one of its dimensions, and that the daily workplace culture is built around. New joiners who pay attention to the values session with this continuity in mind extract more value from it than those who are mentally skipping ahead to when the “real” training starts.
First evening. After the day’s activities conclude, trainees have the first evening to settle into their hostel room, meet their roommates, explore the immediate campus area, have their first meal in the campus cafeteria, and begin the social process of connecting with their batch. The first evening’s informal social dynamics - who gravitates toward whom, how different personality types navigate a new social environment of strangers, how the competitive programming enthusiasts find each other and the extroverts manage the cafeteria table selection - are the opening of a social experience that will shape the training months in ways that are not yet visible on day one.
Accommodation: Hostels, Rooms, and Living Arrangements
The hostel accommodation at the Mysore GEC is the primary living environment for trainees throughout the training period. Understanding the accommodation setup, its quality, its rules, and its practical realities is essential for managing the transition from college or home life to the training campus.
Hostel blocks and room assignment. The GEC has multiple hostel blocks, designated separately for male and female trainees. Room assignment is done by Infosys’s facilities team and is not subject to individual preferences at the time of joining. Trainees are assigned to a room before or on joining day and are not typically permitted to request specific roommates or block locations. The hostel blocks are named (different blocks have different names or letter designations), and knowing which block you are assigned to becomes your logistical baseline - it determines walking distances to the academic buildings, the cafeteria allocation, and the hostel-specific facilities.
Room type and configuration. Most hostel rooms at the GEC accommodate two trainees, though triple rooms exist in some blocks. The rooms are furnished with single beds, study desks, chairs, storage cupboards, and a shared or individual bathroom depending on the block. Air conditioning availability varies by block, which is a practically significant detail in the Mysore heat. The room is functional rather than spacious: two adults with their full luggage occupy most of the available floor space. The adjustment to shared close-quarters living is one of the more personal transitions of the Mysore experience.
Bathroom and hygiene facilities. Bathroom access is either attached to the room (in better-grade blocks) or shared at the floor level (in older blocks). Hot water availability and timing vary by block, and the specifics of morning hot water schedules become important when a hundred trainees on a floor are all trying to prepare for the 8 AM training session start. The early-riser advantage is not just about study time; it is also about hot water access.
Housekeeping and room maintenance. Housekeeping services maintain common areas and provide basic room cleaning on a schedule. Trainees are responsible for keeping their own rooms in acceptable condition beyond the housekeeping schedule. A room inspection culture exists, particularly during the initial weeks, and maintaining a reasonably orderly room is both a personal comfort decision and a practical compliance with hostel norms.
Laundry. The campus has a laundry facility, but it operates on a submission and collection model rather than self-service. Trainees submit clothes and collect them at specified times. The laundry turnaround time means maintaining an adequate personal clothing supply is important - running low on clean formal attire for training sessions because of laundry timing is a practical inconvenience that catches trainees who brought too little clothing. Some trainees supplement the campus laundry with self-washing for items needed quickly.
Security and hostel access. Hostel entry and exit is managed through the ID card access system. There are defined curfew times for the hostel, particularly for female trainees, which are taken seriously by the facilities management team. The hostel curfew is not merely a theoretical policy - it is monitored, and violations carry formal consequences. Understanding and respecting the curfew schedule from the first week is important both for avoiding disciplinary issues and for establishing the habit of time-managed movement that the training schedule generally requires.
The roommate experience. The roommate assigned on joining day may remain the roommate for the entire training period or may change due to batch reshuffling, health considerations, or administrative adjustments. The roommate relationship is the closest daily relationship during the training months. Trainees who end up with compatible roommates - compatible in sleep schedules, noise tolerance, study habits, and basic living standards - have a materially more comfortable training experience than those with incompatible pairings. Where incompatibility is severe, the hostel management has a process for requesting a room change, though these requests are not always accommodated quickly or at all. Managing roommate differences with the communication and compromise skills that will be needed throughout a professional career is the training-within-the-training that the accommodation experience provides.
The Daily Schedule: A Week in the Life of a Mysore Trainee
The Infosys Mysore training schedule is dense and structured, designed to make efficient use of every weekday. Understanding the schedule architecture helps trainees plan their days, manage their energy, and make deliberate use of the available time outside formal sessions.
Morning routine and reporting. Training sessions begin at 8 AM at most schedule configurations, which means trainees need to have completed personal morning routines, breakfast, and commute within the campus from their hostel block by this time. The campus is large enough that walking from certain hostel blocks to the academic buildings takes 10 to 15 minutes. For trainees in the farther blocks, the 8 AM session effectively requires leaving the hostel no later than 7:30 AM, which means the morning routine must begin by 6:30 to 7:00 AM.
The cafeteria operates specific breakfast hours, and the combination of several thousand trainees all attempting breakfast before 8 AM creates queuing dynamics. Trainees who learn the peak and off-peak cafeteria timing within the first week manage their morning time more efficiently than those who try to eat at peak time every day and arrive at sessions slightly late because of the queue.
The training session structure. The academic day is divided into sessions, typically of 1.5 to 2 hour duration, with short breaks between them. A standard training day has three to four sessions covering the curriculum topics for that day. Sessions are conducted in designated classrooms or computer labs depending on whether the content is theoretical or practical. Attendance is marked - formally, through the ID card swipe system at the classroom entrance or manually by the faculty. Attendance thresholds are enforced, and consistently missing sessions without approved reasons creates administrative issues.
The session format varies by content type. Programming sessions in computer labs are highly interactive - the faculty presents a concept, demonstrates it on a projector, and then trainees implement it themselves on their lab computers, with the faculty circulating to assist. Conceptual sessions (covering software engineering principles, SDLC, or communication topics) are more lecture-and-discussion-based. Soft skills sessions involve group activities, role plays, and presentations. The variety of session formats prevents the training week from feeling uniformly static, though the density of the schedule means mental fatigue is a real factor by Thursday of each week.
Lunch and the midday break. A lunch break of approximately one hour is built into the midday schedule. The cafeteria handles several thousand simultaneous lunches, which means lunchtime is a logistical event at the cafeteria level. The cafeteria experience during lunch hour is one of the more memorable aspects of campus life - the sheer scale of the dining hall, the variety of cuisines, and the constant background noise of thousands of trainees in simultaneous conversation create an atmosphere that is neither quiet nor solitary.
Many trainees use the lunchtime not just for food but for conversations with section-mates, quick naps in the hostel, or a brief break from the campus’s intensity. Managing the lunch hour as personal recharge time - not just caloric intake time - is a sustainable practice over a training period of several months.
Afternoon sessions. The afternoon typically carries two more sessions before the formal training day concludes. Afternoon sessions are harder to sustain concentration through than morning sessions, particularly after lunch in warm weather. Trainees who have developed the discipline of focused attention despite physical fatigue find the afternoon sessions more productive than those who drift into passive attendance.
Evening: Study, social, or both. The formal training day typically concludes between 5:30 and 6:30 PM, after which trainees have free time until the hostel curfew. This evening period is the most individually managed part of the day. Some trainees immediately return to their rooms for self-study, reinforcing the day’s content and preparing for the next day’s sessions. Others head to the food court, the recreational facilities, the gym, or the various social spaces on campus. The most effective approach is a balance: adequate study time to keep up with the assessment schedule, and adequate social and recreational time to prevent the kind of accumulated exhaustion that impairs learning.
Weekends. Saturday and Sunday are generally free from formal training sessions, providing genuine recovery time. Weekends at Mysore campus have a noticeably different energy from weekdays - the academic buildings empty, the recreational spaces fill, and the social life of the training community becomes more visible. Some trainees use weekends for excursions to Mysore city or the surrounding attractions (the Mysore Palace, Chamundi Hills, Brindavan Gardens). Others focus on weekly study review, preparation for upcoming assessments, or personal projects. The weekend is a resource that trainees who use it wisely (balancing rest with preparation) manage their training period sustainability better than those who either work through it or spend it entirely passively.
The Training Curriculum: Generic Training Phase
The Infosys Mysore training programme begins with the Generic Training (GT) phase, which all incoming trainees attend regardless of their prior academic background or the specific technology stream they will eventually be allocated to. The Generic Training is designed to establish a common technical baseline across the entire batch.
Java Programming and Software Development Fundamentals
Java is the primary programming language of the Infosys training curriculum. This is a deliberate choice: Java is the most widely used language in Infosys’s delivery operations, and establishing fluency in it during the training phase minimises the ramp-up required when trainees are placed on client projects.
The Java curriculum progression. The Java training begins from basics: setting up the development environment, understanding the Java Virtual Machine, writing and compiling the first Java programme. It then progresses through the core object-oriented programming concepts with Java as the implementation language: classes and objects, encapsulation (access modifiers, getters and setters), inheritance (single, multilevel, and why Java does not support multiple class inheritance), polymorphism (method overloading and overriding), and abstraction (abstract classes and interfaces).
After the OOP fundamentals, the curriculum covers Java’s standard library: the Collections framework (ArrayList, LinkedList, HashMap, HashSet, and their usage patterns), exception handling (try-catch-finally, checked versus unchecked exceptions, creating custom exceptions), file I/O (reading and writing files with Java’s I/O streams), and multithreading basics (the Thread class, the Runnable interface, and the concept of synchronisation).
The final sections of the Java curriculum cover enterprise-relevant topics: JDBC (Java Database Connectivity, allowing Java programmes to interact with relational databases), and an introduction to web technologies and servlets (the foundation of Java-based web application development that underpins many Infosys client projects).
The lab sessions. Every conceptual Java module is accompanied by lab sessions where trainees implement the concepts in working code. The lab exercises range from straightforward (write a class with specific attributes and methods demonstrating encapsulation) to non-trivial (implement a multi-level inheritance hierarchy for a library management scenario, including appropriate use of interfaces and exception handling). The quality of engagement in these lab sessions is the strongest predictor of training assessment performance because the assessments test implementation knowledge, not just concept recall.
Trainees who have prior Java experience (typically CS graduates who covered Java in their curriculum) advance through the early modules quickly and can use the lab time to consolidate their knowledge or explore extensions of the exercises. Trainees from non-CS backgrounds or those whose college Java exposure was superficial need to invest more heavily in these lab sessions and in self-study to build the same fluency. The training faculty is available during lab sessions for questions, and using this availability actively rather than struggling silently is the most effective use of the resource.
Database Management and SQL
The DBMS component of the generic training covers relational database theory and SQL at a practical level aligned with what Infosys developers need to know to work on client database layers.
The DBMS curriculum. The training begins with the relational model: what a database is, what a table (relation) represents, how primary and foreign keys establish relationships between tables, and what referential integrity means. It then covers normalisation - moving through 1NF, 2NF, 3NF, and BCNF with worked examples that trainees are expected to follow and apply in exercises.
The SQL portion of the curriculum is the most practically important part of the DBMS module. It covers: SELECT statements from single tables with filtering using WHERE, sorting with ORDER BY, and limiting results. Multi-table operations using INNER JOIN, LEFT JOIN, RIGHT JOIN, and FULL OUTER JOIN. Aggregate functions (COUNT, SUM, AVG, MIN, MAX) and their interaction with GROUP BY and HAVING. Subqueries (both correlated and non-correlated). Data manipulation language: INSERT, UPDATE, DELETE. Data definition language: CREATE TABLE, ALTER TABLE, DROP TABLE. And transaction control: COMMIT, ROLLBACK, and the concept of ACID properties.
The lab environment for DBMS typically uses Oracle or MySQL, with trainees writing and executing queries against pre-populated sample databases that simulate business scenarios (customer orders, employee records, inventory management). The realistic database scenarios are more useful for learning than abstract exercises because they connect SQL syntax to the kind of business data that client projects actually involve.
Software Engineering and Development Lifecycle
The software engineering module covers the professional practices and methodologies that govern how software is built in an enterprise context. This module is often underestimated by trainees eager to get back to coding, but it is directly relevant to how Infosys delivers for its clients.
SDLC models covered. The curriculum covers the major software development lifecycle models: Waterfall (sequential phases from requirements through design, implementation, testing, deployment, and maintenance), Agile (iterative development with sprint cycles, daily stand-ups, sprint retrospectives, and a focus on working software over comprehensive documentation), and Scrum as the most common Agile implementation framework. The differences between these models - not just theoretical but in terms of how teams organise work, communicate, and deliver - are explained with industry examples.
The Agile and Scrum content is particularly relevant because Infosys’s delivery operations are largely Agile-based. New joiners who arrive at their first project having genuinely understood what a sprint is, what a user story looks like, and what happens in a sprint retrospective adapt to the project rhythm faster than those who treat this module as peripheral theory.
Version control and collaborative development. The curriculum includes an introduction to version control using Git. Trainees learn: initialising a repository, staging and committing changes, branching (creating feature branches, switching branches), merging (including handling merge conflicts), and working with remote repositories. These are the practical Git operations that every Infosys developer uses daily, and the training module’s goal is to make these operations second nature before trainees arrive at their first project.
Testing fundamentals. The software engineering module also covers testing concepts: the difference between unit testing, integration testing, and system testing; the test case design concepts of equivalence partitioning and boundary value analysis; and an introduction to test-driven development (TDD) as a development approach. These concepts matter because many Infosys projects have a testing component, and trainees who understand testing methodology can contribute to quality assurance work alongside their development responsibilities.
Operating Systems, Computer Networks, and Systems Concepts
The systems concepts module provides the foundational knowledge of how computers and networks actually operate, which is relevant to troubleshooting, system design, and understanding the infrastructure on which the software that Infosys deploys runs.
Operating systems coverage. The OS module covers process management (what a process is, how the operating system schedules processes, what context switching involves), memory management (virtual memory, paging, segmentation), file systems (how files are organised and accessed on disk), and concurrency concepts (threads, synchronisation, deadlock and its conditions, prevention, and avoidance). The coverage is conceptual rather than implementation-level - trainees are not expected to write OS kernel code but to understand the mechanisms well enough to reason about system behaviour.
Computer networks. The networking module covers the OSI model and its layers (Physical, Data Link, Network, Transport, Session, Presentation, Application), the TCP/IP protocol suite, how IP addressing and subnetting work, the roles of key protocols (HTTP, HTTPS, DNS, DHCP, FTP, SMTP), and the basics of how web requests travel from a browser to a server and back. For software developers, the most practically relevant networking knowledge is at the Application layer - understanding HTTP request methods, status codes, and headers is a daily requirement for web and API development.
Stream-Specific Training Phase
After the Generic Training phase concludes and trainees have received their stream allocation (the process of which is described in detail in the dedicated section below), the training shifts to stream-specific content. This phase covers the technologies and practices associated with the specific technology practice that each trainee has been allocated to.
What streams exist. Infosys allocates trainees to technology practice streams that reflect its major delivery capability areas. The specific streams available in a given batch depend on Infosys’s current project portfolio and talent demand. Common streams include: Java Full Stack (covering advanced Java, Spring framework, microservices architecture, REST API development, and frontend integration), .NET Full Stack (covering C#, ASP.NET, and Microsoft technology stack), Python and Data (covering Python for data processing, Pandas, data engineering tools, and analytics platforms), Testing (covering manual and automated testing methodologies, testing tools like Selenium and JIRA), Cloud (covering cloud platform services and deployment), Database and SQL (covering advanced database engineering and administration), SAP (covering the SAP enterprise resource planning ecosystem), and others depending on specific cohort demand.
The stream-specific training phase is significantly more specialised than the generic phase. The pace increases, the technical depth grows, and the relevance of the content to the actual work trainees will do on client projects becomes immediate. Trainees who are allocated to a stream that aligns with their academic background or personal interests typically engage more deeply with this phase. Those allocated to less familiar streams face a steeper learning curve that requires more deliberate self-study to supplement the classroom sessions.
The stream-specific curriculum structure. Each stream’s curriculum is structured around a progression from foundational stream concepts through to an integrated project simulation. For the Java Full Stack stream, for example, the progression might cover: Spring Boot for building REST APIs, Spring Data JPA for database integration, Hibernate for object-relational mapping, building a microservices architecture with multiple communicating services, deploying a Spring Boot application to a containerised environment, and finally, an integrated project that combines all these components into a working application.
The stream-specific phase’s integrated project is a particularly important element. It is where trainees must synthesise everything learned in the stream into a functional deliverable, working in small teams with defined roles. This simulates the project delivery environment of the actual client work ahead and provides early exposure to the team dynamics, task allocation, and communication patterns of software development teams.
The stream trainer relationship. Stream-specific training involves a closer relationship with the stream’s faculty than the generic phase because the cohort size is smaller (only trainees in the same stream share sessions) and the technical depth invites more specific questions. Building a productive relationship with stream trainers - engaging actively in discussions, asking clarifying questions, and demonstrating initiative in the lab exercises - has practical career benefits beyond the training period. Some stream trainers have informal influence in the project allocation process, and trainees who have demonstrated genuine technical engagement are noted positively.
Soft Skills and Communication Training
The soft skills and communication component of the Mysore training is a parallel track that runs alongside the technical curriculum throughout the training period. It covers the professional competencies that technical training alone does not build: spoken and written English communication, presentation skills, email etiquette, interpersonal skills, teamwork, and client-facing communication.
Why Infosys invests in this training. Infosys’s delivery model is fundamentally client-facing. Even developers who never travel onsite communicate with client team members through email, video calls, and documentation. The quality of this communication directly affects client satisfaction, which affects project success and account growth. Infosys’s experience over decades of delivery is that technical capability without communication quality is a persistent bottleneck for engineer effectiveness. The soft skills training is designed to address this bottleneck systematically.
The English communication module. For trainees whose primary education was not in English, the English communication module is a practical and sometimes uncomfortable adjustment. The module covers spoken English fluency (pronunciation, pacing, articulating technical concepts in plain English), business writing (professional email structure, clarity, and tone), and comprehension of business English in client communications and documentation. The discomfort of practising English communication in a group setting is real but temporary - trainees who engage honestly with this module and practice consistently are in a visibly better position by the end of training than those who resist the sessions.
Presentation skills. Trainees practise presenting technical content to an audience, delivering project updates in a structured format, and handling questions from an audience under mild pressure. These skills are practised through in-session exercises and, in many batches, through formal presentation assessments where each trainee presents to their section and is evaluated by faculty and peers. The first formal presentation is an anxiety-inducing experience for most trainees; the subsequent ones are progressively more comfortable as the skill is genuinely developed through repetition.
Team and interpersonal skills. Group activities, team-based problem-solving exercises, and structured discussions are used to develop awareness of how to work effectively in diverse teams. The cultural and educational diversity of a Mysore training batch - trainees from across India with different languages, backgrounds, and work styles - is itself the classroom for interpersonal skills development. Navigating this diversity with respect, curiosity, and professional communication is both a training outcome and a direct preparation for the diverse project teams that Infosys employees work in.
Mock client interactions. Some training batches include simulated client interaction exercises, where trainees role-play as developers in a client meeting or requirements discussion. These role plays are an advanced soft skills exercise that combines communication skill with technical content delivery - the trainee must explain a technical decision to a non-technical client representative in terms the client can understand while maintaining professional composure under gentle challenge. The simulation is imperfect, but it provides a first exposure to a communication dynamic that is central to Infosys’s delivery environment.
Business communication writing in depth. The written communication component of the soft skills module deserves particular attention because it is one of the most practically exercised skills after training. Professional email writing at Infosys involves several conventions that are not taught in engineering curricula: the appropriate use of the Subject line (specific and descriptive, not vague), the structure of a status update email (brief executive summary followed by details), how to communicate a problem to a client without causing alarm (presenting the issue alongside the proposed resolution path), and how to write a meeting summary (action items clearly attributed, timelines specific). These conventions are covered in the soft skills training and then applied in the assessment exercises. Trainees who genuinely internalize them - not just as assessment material but as professional habits - are meaningfully more effective communicators in their first project.
The Infosys values and ethics module. Woven through the soft skills training is a module on Infosys’s code of conduct, ethics in the workplace, and the practical application of the company’s core values to everyday decisions. This module covers: what constitutes a conflict of interest and how to disclose one, the whistleblower policy and how to report ethical concerns, intellectual property protection and the obligations of an Infosys employee regarding client and Infosys confidential information, and harassment and discrimination policy. These topics are presented through scenario-based discussions where trainees reason through realistic situations and apply the values and policy framework to determine the appropriate action.
This is among the most practically important modules for new joiners who have not previously worked in a corporate environment where professional ethics have specific legal and contractual dimensions. The intellectual property protection content, in particular, is critical: Infosys employees working on client projects have access to client systems, data, and intellectual property, and the obligations regarding how this information may be used, stored, and shared are serious. Understanding these obligations from the start of the career, rather than learning them through an uncomfortable incident, is the module’s core purpose.
Mental Health and Wellbeing During the Training Period
Mental health during the Mysore training period is a topic that training administrations are increasingly attentive to, and that trainees themselves benefit from understanding before they arrive. The combination of factors present at Mysore - physical relocation from family, new social environment, sustained assessment pressure, limited privacy in shared accommodation, and career anxiety about project allocation - creates conditions in which a significant proportion of trainees experience some level of psychological difficulty.
The adjustment period. The first two to three weeks at Mysore are typically the most psychologically challenging. Everything is new simultaneously: the city, the campus, the roommate, the section, the training intensity, the food, the accommodation, and the professional context. The brain is processing an extraordinary volume of new information and social stimuli while simultaneously trying to engage with a demanding academic programme. The combination produces a period of what psychologists call acculturation stress - the stress of adapting to a new cultural and social environment.
This stress is normal, temporary, and does not indicate a problem with the trainee’s suitability for the role. The majority of trainees who experience it intensely in the first two weeks find that it substantially diminishes by the end of the first month as routines establish themselves, familiar faces become known individuals, and the novelty of the environment transitions to familiarity. Knowing in advance that this adjustment period is normal and time-limited helps trainees not catastrophize the discomfort of the first weeks.
Homesickness. For many freshers, the Mysore training is the first extended period away from family. Homesickness - the emotional experience of missing familiar people, places, and routines - is a genuine psychological state that has both emotional and sometimes physical manifestations (disrupted sleep, reduced appetite, difficulty concentrating). Managing homesickness effectively involves: maintaining regular contact with family and friends through calls and messages (the campus connectivity makes this practical), building new relationships on campus that provide social belonging, and investing in activities that are absorbing and meaningful (which is another reason the extracurricular and recreational opportunities on campus are worth engaging with).
What makes homesickness worse is social isolation - staying in the room during free time, declining social invitations, and interacting only minimally with section-mates. What makes it better is social engagement, even when it requires overcoming inertia. The first invitation to the food court or the cricket ground from a section-mate is worth accepting even if the motivation to go is low. Social connection is the most effective management for homesickness, and it is available in abundance on the campus.
Assessment anxiety and performance pressure. Assessment anxiety during the Mysore period is partly rational (the assessments genuinely matter for the training outcome and career trajectory) and partly cognitive distortion (the catastrophising of assessment stakes to levels that are disproportionate to the actual consequences). Managing the rational component involves good preparation. Managing the cognitive distortion component involves perspective: the vast majority of trainees who engage genuinely with the training, even if not at the top of the performance distribution, complete training successfully and are deployed to projects. The tail risk of training-related employment consequences is real but applies to a small fraction of trainees with very specific underperformance patterns.
Practical assessment anxiety management strategies that are effective in the Mysore context: regular physical activity (documented to reduce anxiety through neurobiological mechanisms), consistent and specific study routines (reducing the open-ended uncertainty about whether preparation is adequate), mutual support in study groups (social connection reduces isolation-amplified anxiety), and maintaining daily activities that are not assessment-related (music, sport, social conversation) as a psychological counterbalance to the assessment focus.
When to seek formal support. The GEC’s counselling service is staffed by trained professionals and is available to trainees experiencing significant psychological difficulty. The threshold for seeking counselling is not a psychiatric crisis - it is any experience of distress that is interfering with the trainee’s ability to function effectively in training, sleep, eat, or maintain basic social connection. Seeking counselling is a professional act of self-management, not a sign of weakness, and it is entirely confidential within the support service. Trainees who seek support early, before a manageable difficulty becomes an entrenched crisis, have better outcomes than those who delay until the difficulty has compounded over weeks.
The hostel warden and the assigned section mentor are also accessible points of contact for trainees who are not ready for a formal counselling session but need to talk to someone in a supportive role. These contacts can often provide informal support, practical advice, and, where necessary, referral to the formal counselling service.
Supporting peers. The social community of a training section means that trainees are often the first to notice when a peer is struggling before the faculty or administration does. The appropriate response to noticing that a roommate, section-mate, or friend is significantly withdrawn, sleeping excessively, not eating, or expressing hopelessness is compassionate engagement - checking in personally and, if the concern is serious, encouraging them to use the campus support services. Being a supportive peer in the Mysore community is both the humane thing to do and the professional thing to do - teams take care of their members, and the training period is the first laboratory for that professional virtue.
The Post-Mysore Infosys Employee: What Has Actually Changed
The conclusion of the Mysore training is the formal beginning of the Infosys employment in its deployed phase, and reflecting on what the training has actually changed in the new employee helps calibrate the transition from training to project work.
Technical foundations established. The Mysore training establishes a common technical vocabulary and a working Java and SQL foundation that all trainees share at training completion. This common foundation is Infosys’s internal technical language - the capability baseline that project managers assume when receiving a freshly trained employee onto their team. Trainees who have built this foundation genuinely can step into a Java-based development project, understand the codebase’s organisation, contribute to SQL-based data layer work, and communicate using the same technical terminology as senior team members. Those who have gone through the motions of training without genuine knowledge acquisition will find the assumption of this foundation uncomfortable in the first project weeks.
Professional conduct and culture absorbed. Beyond technical skills, the Mysore training has transmitted Infosys’s professional culture through four to five months of daily immersion. The punctuality habits, the attendance discipline, the collaborative team ethic, the communication norms, the code of conduct awareness, and the values-based decision-making framework are all aspects of Infosys professional culture that have been absorbed during the training period - some consciously, some implicitly through the environmental norms of the campus.
A professional network initiated. The section-mates, the project teammates, the roommates, and the various connections made through campus activities are the beginning of a professional network that will serve the new employee throughout their Infosys career. Keeping this network alive - staying in touch with batch connections after deployment, especially after the geographic dispersion of the first project allocation scatters the batch across multiple cities - is a career investment that takes almost no effort in the immediate post-training period but pays dividends over years.
Personal growth alongside professional development. For many trainees, the Mysore experience is also the first extended period of genuinely independent adult living - managing finances, living with strangers, navigating a new city, and making daily decisions without family guidance. This personal growth dimension of the Mysore experience is real and consequential: trainees who have managed the Mysore experience successfully are more capable of navigating the relocations, the unfamiliar project environments, and the professional challenges of the early career than they would have been without it. The personal confidence that comes from having successfully navigated four months of an intense new experience is a career resource that is difficult to quantify but impossible to miss.
The assessment system at Mysore is the mechanism through which Infosys determines each trainee’s readiness for project deployment and, in some dimensions, their stream allocation and designation within the organisation. It is formal, frequent, and taken seriously by the training administration.
Types of Assessments
Module assessments. After each major curriculum module concludes, there is a module-level assessment that tests the content covered. These assessments are typically computer-based, multiple-choice or code-submission format, and are conducted in the assessment centre (a dedicated proctored examination facility on campus). The module assessment results are recorded in the trainee’s training profile and contribute to the overall training performance score.
The module assessments for programming topics (Java, SQL) include both theoretical questions (output tracing, error identification, concept application) and coding exercises where the trainee writes working code that is evaluated against test cases. The coding exercises in module assessments mirror the structure of the selection process coding assessments - candidates who have maintained their technical sharpness from the hiring process are at an advantage in the early module assessments.
Daily quizzes and in-session assessments. Many training sections incorporate short, in-session quizzes or exercises that are informally tracked but still contribute to the trainee’s engagement record. These are less formal than the proctored module assessments but serve the purpose of keeping trainees continuously engaged with the material rather than allowing knowledge to accumulate only immediately before major assessments.
Soft skills assessments. The soft skills and communication components are assessed through a combination of: presentation evaluations (where faculty and sometimes peers rate the trainee’s presentation on a structured rubric), written communication assessments (email writing and report writing exercises evaluated for structure, clarity, and appropriateness), and group discussion assessments (where the trainee’s participation in a structured group discussion is evaluated for content quality, communication clarity, and interpersonal contribution).
Project phase assessment. The integrated project simulation in the stream-specific phase is assessed as a team deliverable. The project assessment typically covers: technical completeness (does the project do what it was specified to do?), code quality (is the code structured appropriately, with good naming and readable organisation?), documentation (are the design decisions documented clearly?), and presentation (can the team explain what they built and why they made specific technical choices?). Individual contributions within the team are also noted, and free-riders on team projects are identifiable to faculty who observe the project process, not just the final deliverable.
The comprehensive final assessment. Near the end of the training period, a comprehensive assessment tests content from across the entire training curriculum. This assessment is the highest-stakes single evaluation of the training period and carries significant weight in the overall training profile. Trainees who have maintained consistent performance through the module assessments are well-positioned for the final assessment; those who have been inconsistent may find the comprehensive nature of the final assessment challenging because there is no single module to remediate - the gaps from multiple modules converge.
The Grading System Explained
Infosys’s training assessment results are expressed in a grading system that categorises trainee performance into bands. The specific labels and thresholds for these bands have been described by trainees over many batches with the following structure:
Grade A (Outstanding or Excellent): Performance that indicates above-average mastery of the curriculum across both technical and soft skills components. Trainees in this band have typically achieved high scores across module assessments, demonstrated strong project contributions, and shown consistent engagement across the training period.
Grade B (Meets Expectations or Good): Performance that indicates satisfactory mastery of the curriculum. The majority of the training batch typically falls in this category. Grade B performance is sufficient for successful training completion and project deployment.
Grade C (Partially Meets Expectations): Performance that indicates below-average mastery in some components. Trainees in this band have typically struggled with specific assessment areas, though not at the level that requires formal remediation.
Grade D and below (Does Not Meet Expectations): Performance that indicates a failure to achieve the minimum competency standard required for training completion in one or more critical components. This grade triggers a formal remediation pathway.
The training grade has implications beyond training completion. Project allocation and, in some cases, designation classification within the organisation can be influenced by training performance. Trainees who achieve consistently high grades are more likely to be placed on high-complexity, high-visibility projects and may be considered for faster-track designation movement. The grade is a signal that persists in the trainee’s Infosys record and is visible to project managers during the allocation process.
What Happens If You Fail an Assessment
The word “failure” in the Mysore assessment context covers a range of situations, and the consequences vary by the severity and the specific assessment involved.
Failed module assessment: First attempt. If a trainee fails a module assessment on the first attempt, they are typically given a remediation window - a defined period (often a few days to a week) to review the failed module’s content and retake the assessment. The retake assessment may be the same format as the original or a variant. Retake results are typically noted in the training record, though the consequence of a single failed module’s retake, when passed on the second attempt, is primarily the note in the record rather than a formal grade penalty.
Failed module assessment: Second attempt. If the retake is also not passed, the situation becomes more serious. A second failure in a module assessment triggers a formal review with the training coordinator and the trainee’s assigned mentor or faculty advisor. The outcome of this review depends on the nature of the failure (was it a specific conceptual gap, or is there a broader foundational issue?) and may result in extended remediation, module repetition, or in persistent cases, a formal performance management discussion.
Track assignment consequences. Trainees who consistently underperform across multiple modules and who do not improve through remediation may face reassignment to the BPM (Business Process Management) track. The BPM track is a different employment category within Infosys with different project types and career paths compared to the technology delivery track. This reassignment is not a termination, but it is a meaningful change in the career trajectory that most technology track freshers would prefer to avoid. The BPM track typically involves less technically demanding work in business operations support rather than software development.
Termination for persistent non-performance. In cases where multiple remediation attempts across multiple modules fail and the trainee demonstrates no viable path to minimum competency, Infosys may exercise the employment termination clause under the training performance framework. This outcome is rare but documented. It is most commonly associated with trainees who have either significantly misrepresented their technical background during hiring or who have chosen not to engage with the training at a basic level. The training administration actively tries to prevent this outcome through early intervention, but the mechanism exists and is applied when necessary.
The psychological reality of assessment pressure. The assessment frequency and consequences at Mysore create a stress environment that some trainees find difficult to manage. Assessment anxiety is real, and the combination of unfamiliar living conditions, distance from family, and the perceived stakes of every evaluation can compound into significant psychological pressure for vulnerable trainees. Infosys’s GEC has counselling services available, and the hostel and training administration have pastoral support mechanisms. Trainees who are experiencing disproportionate anxiety should use these resources proactively - not doing so is one of the most common ways that otherwise capable trainees make avoidable mistakes during the assessment period.
Stream Allocation: How It Works and What It Means
Stream allocation is one of the most consequential moments of the Mysore training experience. It determines the specific technology domain each trainee will train in, the type of projects they are likely to be allocated to after training, and in a meaningful sense, the shape of the first phase of their Infosys career.
When stream allocation happens. Stream allocation typically occurs after the Generic Training phase is completed but before the stream-specific training begins. This timing means that trainee performance in the GT phase is one of the primary inputs into the allocation decision. The allocation is not announced all at once for the entire batch at a single moment; it is communicated to individual trainees or small groups over a day or two, which creates a period of considerable batch-wide anticipation and anxiety.
The factors that determine allocation. Infosys’s stream allocation process considers several inputs simultaneously:
Training performance in the GT phase: Trainees who performed strongly in Java programming and SQL assessments are more likely to be allocated to technically demanding streams. Trainees with strong soft skills assessment performance may be favoured for streams with higher client-communication requirements.
Declared preferences: In some training batches, trainees are asked to submit a stream preference form before allocation. This preference is considered but is not determinative. Infosys’s project and client demand is the primary driver, and individual preferences are accommodated where they align with that demand.
Business demand: The allocation reflects the current project pipeline. If Infosys has a large wave of SAP implementations beginning, more trainees may be allocated to the SAP stream than in previous batches, regardless of individual preference distributions. The allocation is, fundamentally, a supply-demand matching exercise.
Academic background: A Computer Science background does not guarantee a Java Full Stack allocation, nor does an Electronics background prevent it. However, where demand is roughly balanced across streams, academic background and declared interest can tip the allocation toward a better fit.
Streams trainees want vs what they get. The gap between preferred and assigned stream is one of the most common sources of Mysore-related frustration. Trainees who have invested their preparation time in specific technologies and hoped for an aligned stream allocation sometimes find themselves in streams they did not anticipate. This gap is real and its emotional impact should not be dismissed, but the practical significance is often less severe than the initial reaction suggests. The stream-specific training provides all trainees, regardless of prior exposure, with sufficient foundation in the allocated stream to begin productive work. The first project assignment, with its own learning curve, is the greater equaliser.
Trainees who are allocated to a stream they do not prefer have two productive responses: engage fully with the stream’s training to become genuinely capable in the allocated technology (capability compounds regardless of starting preference), and actively explore internal mobility mechanisms after the training period to shift toward their preferred practice area. Both strategies are more effective than spending the stream-specific training in resentment of the allocation.
What stream allocation does not determine. Stream allocation determines the technology focus of the stream-specific training. It does not determine the specific client or project, the location of the first project, or the long-term technology trajectory of the career. Infosys has internal mobility mechanisms that allow employees to move between practices after initial project tenure. A trainee allocated to .NET Full Stack who has a strong personal interest in data engineering can, over the first two years of employment, build data engineering skills through self-study and certification, and transition to a data-facing project through internal movement. The allocation is a starting point, not a permanent assignment.
The designation within each stream. Stream allocation is related to but not identical with the designation outcome (whether a trainee completes as Systems Engineer or Digital Specialist Engineer, for those allocated via tracks where this distinction applies). The stream training outcome and the training performance grade together inform the post-training designation classification for trainees where this decision point exists.
The Project Phase: From Classroom to Real Delivery
The project phase of the Mysore training is the bridge between the classroom environment and the actual client delivery work that comes after training. It is structured as a simulation of a real project, with defined requirements, team roles, development sprints, and a final deliverable, but it operates within the training environment’s support structure.
Project formation and team assignment. Training project teams are typically formed by the faculty rather than by trainee self-selection. This is intentional: the training administration knows from experience that self-selected teams create homogeneous comfort groups that do not provide the interpersonal challenge of working with diverse personality and skill profiles. Assigned teams are more likely to replicate the conditions of an actual Infosys project team, where the composition is driven by availability rather than social preference.
Team sizes for training projects typically range from four to eight trainees. Within the team, roles are defined: some members focus on backend development, some on frontend, some on database design, and some on testing - mirroring the role division of actual software development teams.
The project scenario and requirements. The training project scenario is presented as a business problem requiring a software solution. The requirements are given in a structured format similar to what a business analyst would deliver in a real project. The team must interpret these requirements, design a solution architecture, divide the development work among team members, implement the solution, and integrate the components into a working application.
Common project scenario types include: an inventory management system, a hospital patient management application, a library management system, a small e-commerce platform, or an HR management tool. The scenarios are simple enough that a reasonably skilled team can complete them within the project phase timeline, but complex enough that the team must make real architectural decisions and handle real integration challenges.
The sprint structure within the project phase. The project is typically managed in mini-sprints (each lasting three to five days) with daily stand-up discussions, sprint planning, and sprint review sessions. The faculty takes on a dual role during this phase: they act as both technical mentors (available for technical questions and guidance) and process observers (watching how the team organises its work, handles disagreements, manages time, and communicates progress). The process observation dimension of the faculty role is why the team dynamics during the project phase are consequential: the soft skills assessment that runs through the project phase captures not just the final deliverable but the team’s collaborative process.
Version control discipline during the project. The project phase is where Git usage moves from the theory of the software engineering module to the daily practice of managing a shared codebase. Merge conflicts, branch management, and commit message discipline become lived experiences rather than classroom concepts. Trainees who struggle with Git concepts in the module now have the context of a real codebase to understand why these practices exist. The first time a careless merge overwrites a teammate’s two-day effort is an experience that no textbook explanation of version control’s importance replicates - and it happens in a project phase context where recovery is possible and learning is the outcome, rather than in a client project where the consequences are more severe.
Project presentation and the final demo. The project phase concludes with a formal presentation and demonstration to faculty and sometimes to a panel that includes senior training staff. The presentation must convey: the original requirements, the architectural approach taken, a live demonstration of the working application, a description of technical challenges encountered and how they were resolved, and what the team would do differently given another opportunity. This presentation is the highest-stakes team communication exercise of the training period and directly prepares trainees for the sprint reviews and project status demonstrations they will give in their first client project.
Food, Facilities, and Daily Life on Campus
The daily life infrastructure of the Mysore GEC is comprehensive enough that trainees can meet essentially all their daily needs without leaving the campus. Understanding what is available, how it works, and where the friction points are helps trainees manage the practical dimensions of campus living efficiently.
The cafeteria system. The GEC has multiple cafeterias, typically designated by hostel block or academic building zone. Each cafeteria serves breakfast, lunch, and dinner at defined times. The food is subsidised, making the campus cafeteria significantly cheaper than equivalent food outside the campus. The menu rotates across a range of North Indian, South Indian, and occasionally other regional cuisines, with vegetarian options always available and non-vegetarian options at specified meals.
The quality of the cafeteria food is a topic of ongoing opinion among trainees. The scale of production (cooking for thousands simultaneously) means that the food is consistent and adequate rather than restaurant-quality. Most trainees adjust to the cafeteria food within a week or two, occasionally supplementing with the food court options (described below). The occasional “special meal” events, festive food during national holidays, and themed dinner nights are highlights that trainees look forward to.
The food court and retail outlets. Beyond the main cafeteria, the GEC has a food court with outlets from various food brands, offering a wider variety of food options including fast food, snacks, beverages, and regional specialities. The food court is a social hub in the evenings, with trainees meeting for chai, snacks, and conversation after the training day. The pricing at the food court is market-rate rather than subsidised, making it a supplement to rather than a replacement for the cafeteria.
The campus also has retail outlets including a supermarket, a stationery shop, and a bank branch with ATM access. The supermarket stocks personal care products, snacks, beverages, and basic household items, reducing the need for trainees to venture into Mysore city for ordinary daily needs.
Healthcare. The campus has a medical facility staffed with doctors and nurses available during defined hours. Basic medical care, consultation, and common medications are available on campus. For more serious medical needs, the campus management arranges access to external hospitals with appropriate support. Trainees with ongoing medical conditions should register these with the campus health team and ensure their medication supply is adequate for the training period duration.
Sports and recreation. The GEC’s sports facilities include cricket grounds, tennis courts, basketball courts, a swimming pool, a gym, and indoor game facilities (table tennis, carrom, chess). The facilities are available during designated times outside training hours. Sports and recreation are actively encouraged by the training administration because physical activity is one of the most effective stress management strategies available, and trainees who use the facilities consistently report better energy levels and emotional balance during the training period.
The library and self-study spaces. The GEC has a library stocked with technical books, professional development resources, and recreational reading. Quiet study spaces within the library and in designated areas of the academic buildings are available for self-directed learning outside training hours. The library’s technical collection is particularly useful for trainees who want deeper reference material than the training handouts provide.
Internet access. Campus Wi-Fi is available across the academic buildings and in the hostel blocks. The bandwidth is shared across a very large number of simultaneous users, which means streaming performance during peak hours (particularly evenings) is inconsistent. For intensive video streaming, downloading large files, or video calls, off-peak hours produce a significantly better experience. Bringing a mobile data SIM as a backup for when campus Wi-Fi is slow is practical preparation.
Cultural Life, Extracurriculars, and Social Dynamics
The Mysore training experience is not purely academic. The campus’s extracurricular and cultural dimension is a meaningful part of the overall experience and one that former trainees consistently describe as an important aspect of what made Mysore memorable.
Cultural events and festivals. The GEC celebrates national festivals and cultural events throughout the training period. Diwali, Dussehra, Holi, Navratri, Independence Day, and other occasions are marked with campus-wide events including performances, decorations, special meals, and organised activities. These events create moments of collective experience that cut across the batch divisions and remind trainees that the campus is a community, not just a training facility.
Inter-section competitions and hackathons. The training administration organises inter-section competitions across technical and non-technical domains. Technical competitions include coding contests (which provide excellent practice for the assessment environment), database design challenges, and debugging competitions. Non-technical competitions include quiz events, public speaking contests, cultural performances, and sports tournaments. Participation in these events builds skills, relationships, and a sense of belonging to the Mysore community beyond the immediate section cohort.
Hackathons are a particularly valued format, especially for technically enthusiastic trainees. Infosys occasionally organises internal hackathons during the training period where small teams build working applications around a defined problem statement over 24 to 48 hours. These events are high-energy, collaborative, and often produce the best technical work of the training period - there is something about the time-bounded, team-based format of a hackathon that brings out creative problem-solving that classroom exercises cannot replicate.
The social landscape. The social dynamics of a Mysore training batch are a miniature sociological case study. A few thousand young professionals, most of whom know no one when they arrive, forming a complex social web over a period of months creates patterns that are both predictable and fascinating. Social clusters form quickly - the competitive programmers, the cricket enthusiasts, the cooks who find the campus kitchen, the people from the same state or city who cluster by shared language and cultural reference, the philosophical debaters who occupy specific cafeteria corners.
Within sections, the relationship dynamics are shaped by the assessment pressure. Collaborative study groups form, and the willingness to share knowledge rather than hoard it as competitive advantage is a cultural norm that either emerges early in a section and becomes self-reinforcing, or does not emerge and leaves the section more isolated individuals than a community. Sections that develop a culture of mutual help consistently outperform in the team-based project assessments and, often, in individual assessments too - the social cognitive benefit of teaching and explaining to peers is a genuine learning multiplier.
Romantic relationships and social conduct. The GEC’s social environment, like any environment where large numbers of young adults live in close proximity, includes romantic relationships. These relationships are not prohibited by campus rules, but the rules do govern the conduct and the spaces within which personal relationships are conducted. The campus rules apply equally to all trainees, and the social judgment norms of a professional environment apply - conduct that would be inappropriate in a professional workplace is inappropriate on the GEC campus. Most trainees navigate this dimension of campus life without incident, but awareness of the applicable social and conduct norms prevents the kind of misunderstandings that can create formal complaints.
The city of Mysore. Mysore city itself, beyond the campus gates, is a culturally rich destination. The Mysore Palace, one of India’s most famous royal residences, is a short distance from the campus. Chamundi Hills offers a scenic viewpoint and a major temple complex. Brindavan Gardens provides a spectacular evening illuminated fountain experience. The city’s silk textile markets, food culture (including the famous Mysore pak sweet), and the broader Kodagu region’s coffee estates and natural beauty are all accessible during weekends. Trainees who explore Mysore city and its surroundings return to the campus with fresh energy and with memories that become part of the overall Mysore narrative.
Rules, Restrictions, and the Disciplinary Framework
The GEC operates under a formal set of rules and a corresponding disciplinary framework that is enforced consistently. Understanding these rules before arriving prevents inadvertent violations and helps trainees distinguish between the rules that reflect genuine safety or conduct concerns and those that reflect the logistical management needs of a very large residential campus.
Attendance rules. Attendance in training sessions is mandatory. The campus systems track attendance electronically through the ID card swipe at session entry, supplemented by manual checks by faculty. The minimum attendance threshold for each module is defined (typically above 85 percent), and falling below this threshold has formal consequences ranging from a written warning to exclusion from the module assessment. A legitimate absence (illness, family emergency) must be communicated to the training coordinator in advance or on the same day through the defined notification process. Self-certifying absence requires the trainee’s own documentation; medical absence requires a medical certificate from the campus health facility or an external doctor.
The attendance rule is strictly enforced because Infosys views the training period as the trainee’s primary professional obligation. Just as arriving at a client project site on time is a professional commitment, so is arriving at training sessions on time. The discipline of consistent, punctual attendance during training is preparation for the professional conduct expected on client projects.
Dress code. Business casual to formal attire is required during training hours. For most trainees, this means formal trousers (or salwar suits or similar professional attire), collared shirts, and formal shoes. Jeans, shorts, t-shirts, and casual footwear are not permitted in the academic buildings during training hours. After hours, in the hostel and recreational areas, personal dress choices are informal. The dress code is enforced by faculty and occasionally by facilities staff, and consistent violations can result in being turned away from sessions until appropriately dressed.
Hostel curfew. The hostel has defined curfew times, with different timings for different hostel blocks and sometimes different timings for weekdays and weekends. The female hostel blocks have stricter and earlier curfew timings, which are enforced by the hostel management staff at the entry points. Male trainees also have curfew times, though these are sometimes slightly later. Violations of curfew are recorded and, if persistent, result in escalating disciplinary responses up to and including a formal conduct record.
Electronic devices and equipment. Personal laptops are allowed and useful. Mobile phones are permitted in the hostel but must be kept on silent mode during training sessions. Campus IT resources (computers, software, network access) are for training purposes and are subject to Infosys’s acceptable use policy - accessing prohibited content, attempting to circumvent network security, or using campus resources for personal business ventures are policy violations.
Alcohol and substance policy. Alcohol and other controlled substances are prohibited on the campus. This rule is absolute and is enforced through a combination of trust and periodic checks in the hostel blocks. Violations involving alcohol are treated as serious conduct matters with consequences that can include immediate suspension from training and, depending on severity, formal employment action. The campus is effectively a dry campus, and trainees who wish to consume alcohol must do so entirely off-campus in Mysore city during weekend leave.
Leave of absence during training. Casual leave during the training period is available but limited. Trainees must apply for leave in advance through the formal leave request mechanism and receive approval from the training coordinator. Approved leave is recorded but does not exempt the trainee from the assessment consequences of missed sessions - the material missed during approved leave is the trainee’s responsibility to catch up independently.
Financial conduct and campus commerce. Conducting unofficial commerce on campus - selling goods to fellow trainees, running informal financial transactions, or any other unauthorised economic activity - is prohibited. The campus has designated commercial facilities for all legitimate purchasing needs, and anything outside these channels is a conduct violation.
The tone of enforcement. The disciplinary framework at Mysore is enforced consistently but with a generally supportive rather than punitive intent. The training administration’s goal is to prepare trainees for professional conduct in client-facing roles, and the rules are explained in that context. Trainees who approach the rules as professional conduct standards - the same standards that would apply in any professional workplace - adapt to them naturally. Those who approach them as arbitrary restrictions to be gamed tend to have more friction with the enforcement mechanisms and accumulate more conduct records.
Tips for Thriving During Mysore Training
The trainees who look back on Mysore as one of the best professional experiences of their careers are not necessarily the ones who were the most naturally talented at the start. They are the ones who made deliberate choices about how to engage with the training, the assessment pressure, the campus life, and the people around them. These are the patterns that distinguish thriving from merely surviving.
Start strong in the Java module. The first weeks of the generic training phase set the academic pace for the entire training period. Trainees who invest heavily in the Java module from week one build a knowledge foundation that makes every subsequent module easier and every assessment more manageable. Those who allow the first week to pass in adjustment mode and fall behind on Java basics spend the rest of the generic phase catching up rather than building forward. The Java module is the single highest-leverage investment of the early training period.
Build genuine relationships, not just strategic ones. The most valuable professional network you will have within Infosys is built in Mysore. The section-mates who struggled through Java exercises with you, the project teammates who stayed up debugging until midnight with you, and the hostel neighbours who talked through assessment anxiety with you - these are the people who will refer you to internal opportunities, support your retention conversations, and advocate for your projects years later. These relationships are built through genuine mutual investment, not through calculated networking. Show up for people without keeping score, and the professional network builds itself.
Use the self-study time deliberately. The evening study time after training sessions is not automatically productive - it requires intention. Before leaving the training session each day, write down the three things from the day’s content that you are least confident about and commit to addressing those three things specifically during the evening study session. This specificity prevents the common trap of spending two hours “studying” while actually doing comfortable review of already-understood material.
Talk to faculty outside sessions. The training faculty at Mysore are practitioners who have moved into a training role. They have industry experience, project knowledge, and perspective that is available to trainees who seek it out. Using the post-session time to ask faculty about how the day’s content relates to actual project scenarios, what technology skills are most valued in the current market, or what the most effective preparation approach for an upcoming assessment looks like, extracts value that passive session attendance cannot.
Maintain physical activity. The sedentary pressure of hours of classroom and lab work, combined with the stress of frequent assessments, creates physical and mental fatigue that accumulates over weeks. Trainees who build a physical activity habit - using the gym three times a week, playing a sport at least twice a week, walking the campus perimeter in the evening - consistently report better focus, better sleep quality, and lower assessment anxiety than those who remain sedentary. The evidence for exercise as a cognitive and emotional performance enhancer is robust, and the campus facilities make it accessible.
Manage the assessment anxiety cycle. Assessment anxiety is the experience of being more worried about the outcome of an assessment than focused on the learning that makes the outcome good. The most practical antidote is preparation that is honest rather than aspirational: know what you know solidly, know what you are uncertain about specifically, address the uncertain areas directly, and arrive at the assessment having done the realistic work. Anxiety about a gap you have actually addressed is lower than anxiety about a gap you have not looked at. Converting the anxiety into targeted preparation action is the most effective psychological management of the assessment pressure.
Keep a training journal. Writing briefly each day - what you learned, what was confusing, what you want to revisit, what interactions were meaningful - creates a running account of the training that serves multiple purposes. It reinforces learning through the act of writing. It provides a reference when revision is needed before assessments. And it creates a memory bank that, years later when Mysore is a distant recollection, provides a vivid record of an important formative period.
Engage with the stream allocation process actively. When the stream preference form is circulated (if it is in your batch), complete it thoughtfully based on genuine interest and honest self-assessment rather than peer pressure or salary myths about specific streams. The stream you are most interested in is typically the stream you will engage with most deeply and perform best in. Where the allocation differs from the preference, engage with the allocated stream genuinely rather than as a second choice - the difference in career outcomes between trainees in the same stream who engage fully versus those who do not is larger than the difference between streams themselves.
Leave Mysore with your reputation intact. The training administration’s memory of each trainee extends beyond the formal grade. The faculty, the hostel management, the training coordinators, and the HR personnel who manage the batch all form impressions based on how each trainee conducted themselves. The trainee who was consistently late, frequently argued about rules, and contributed friction to team projects leaves a different informal record than the one who was punctual, collaborative, and professionally engaged. This informal record does not disappear with the batch; it lives in the organisation’s memory and can surface in ways that are difficult to predict.
The Transition: From Training Completion to Project Allocation
The conclusion of the training period at Mysore is not a single moment but a process that unfolds over several weeks. Understanding this transition process helps trainees manage the uncertainty and waiting that characterises it.
The training period conclusion. The formal training programme ends with the completion of the stream-specific phase, the comprehensive final assessment, and any remaining soft skills assessments or project phase evaluations. The batch is formally released from the training calendar, which triggers the project allocation process.
The training result and grade communication. After all assessments are completed and graded, trainees receive their training result through the Infosys HR system. The result specifies the overall training grade, the performance in each component, and the stream in which training was completed. This result is the primary input document for the project allocation team.
The waiting period. Between the conclusion of training at Mysore and the receipt of the first project allocation, there is typically a waiting period of one to several weeks. During this period, trainees may remain on the Mysore campus, be asked to relocate to their home cities while awaiting allocation, or be given a reporting date for a different Infosys office location. The specific handling of this waiting period varies by batch and by Infosys’s project pipeline at that time.
The waiting period is a psychologically mixed experience. After the intensity of the training schedule, the sudden absence of a structured programme feels like relief initially. But as the days accumulate without a project allocation, the uncertainty about when and where the first posting will be creates a different kind of stress - one of open-ended waiting rather than performance pressure. Managing this waiting period with deliberate activity (self-directed learning in the allocated stream, exploring the technology certification ecosystem, staying physically active) is better than passive waiting.
Project allocation communication. The first project allocation is communicated through the Infosys HR system and through the trainee’s Infosys email. The communication specifies: the project name and client account (often coded for client confidentiality), the technology stack relevant to the project, the project location, the reporting date, and the manager or team lead to report to. This communication is the formal end of the training period and the beginning of the working career at Infosys.
The relocation reality. The project allocation location may be different from any location the trainee expected. Infosys assigns project location based on project demand, not trainee preference. A trainee from Mumbai who hoped to be posted in Mumbai may receive a Hyderabad or Chennai posting. The service agreement signed during the joining process acknowledges this geographic flexibility. Trainees who have had genuine conversations with their families about this possibility - rather than making assumptions about home-city posting - handle the relocation communication with less disruption.
The first project experience vs the training experience. The gap between the Mysore training environment and the first real project is one of the most significant adjustments of the early career. In training, the environment is structured, the feedback is frequent, the support from faculty is readily available, and failure is a learning event rather than a business consequence. In the first project, the structure is the project timeline, the feedback comes from code reviews and sprint retrospectives, the support comes from team members who have their own delivery responsibilities, and quality failures have real business impact for the client. The adjustment to this shift in stakes is part of the first project experience, and knowing in advance that it will feel different from training - not worse, just different - helps new engineers approach it with appropriate expectations.
Using the Mysore foundation on the first project. The technical foundation built during Mysore - Java fluency, SQL competence, Git version control habits, SDLC and Agile methodology understanding, code review culture, and team communication practices - is directly applicable from the first sprint of the first project. Trainees who engaged genuinely with the training will recognise the connection between what was taught and what is being done on the project. This recognition is one of the more satisfying early career experiences and validates the investment in the training period.
Frequently Asked Questions
1. How long is the Infosys Mysore training programme?
The Infosys Mysore training programme is typically 16 to 20 weeks for freshers joining the standard Systems Engineer track, though the exact duration can vary based on the batch, the stream, and Infosys’s internal training planning for that cohort. Digital Specialist Engineer and Power Programmer track trainees may have a modified training duration based on the specific curriculum calibrated to their track. The generic training phase typically occupies the first half of the programme, with the stream-specific phase and project simulation in the second half.
2. Is the Mysore training stipend different from the full salary?
Yes. During the Mysore training period, trainees receive a stipend rather than the full deployed salary. The stipend is lower than the salary that takes effect after training completion and project deployment. The exact stipend amount is specified in the offer letter. Trainees should plan their personal finances for the training period with the stipend amount in mind, accounting for the first salary credit delay in the initial weeks.
3. Can I choose my stream allocation in Mysore?
Trainees can express preferences through a preference form if it is provided in their batch. However, stream allocation is primarily driven by Infosys’s project demand and business requirements, not individual preferences. The preference is considered as one input but is not determinative. Trainees who are given a stream different from their preference should engage genuinely with the allocated stream - the training provides the foundation regardless of prior exposure, and career trajectory is more influenced by post-training performance than by initial stream assignment.
4. What happens if I fail an assessment in Mysore?
Failing a single module assessment on the first attempt triggers a remediation period and a retake opportunity. Failing the retake triggers a formal review process. Persistent failure across multiple modules and retakes can lead to reassignment to the BPM (Business Process Management) track or, in extreme cases of non-engagement, formal employment action. The training administration actively supports trainees through remediation and makes early intervention available for those who are struggling. The outcome of assessment failure is not predetermined and depends on the trainee’s engagement with the remediation process.
5. Is mobile phone use allowed during training sessions?
Mobile phones must be kept on silent mode and not actively used during training sessions. The social norm and the explicit rule both require that phones not be used during classroom time. Checking messages, texting, or using social media during sessions is a professional conduct issue, not just a distraction concern. Outside training sessions, in the hostel and recreational areas, phone use is unrestricted.
6. Can I leave the Mysore campus during weekends?
Trainees can leave the campus on weekends during designated leave windows, subject to hostel curfew requirements. Mysore city and the surrounding region are accessible and worth exploring. For travel outside Mysore to home cities or other destinations, formal leave must be applied for and approved in advance. Not all leave requests for out-of-city travel are automatically approved, particularly during periods when weekend assessment or training activities are scheduled.
7. What should I bring to Mysore that the official packing list might not mention?
Beyond the official document list, practical items that make the training period more comfortable include: a personal power strip or multi-plug adapter (hostel rooms have limited outlets), earplugs if you are a light sleeper (hostel rooms involve shared accommodation), a small personal first aid kit for minor ailments, a physical notebook for handwritten notes (screen fatigue is real after hours of computer lab time), comfortable indoor shoes or slippers for hostel use (you cannot wear formal shoes all day comfortably), and a small personal fan or any temperature regulation aids if your allocated block has limited air conditioning.
8. How is the project posted after Mysore training decided?
The first project posting after Mysore is determined by the project allocation team based on: open project requirements in Infosys’s current client portfolio, the trainee’s stream allocation and training performance, geographic availability, and internal supply-demand matching. Individual preferences for project type, technology stack, or city can be expressed through the HR system, but these are considered against available openings rather than guaranteed. The first project is almost never exactly what the trainee imagined, and the ability to adapt quickly to the actual project context is one of the most important early career skills.
9. Is the Mysore campus safe?
The GEC campus is a monitored and secure environment with 24-hour security, controlled access to hostel blocks (particularly female hostels), CCTV coverage of common areas, and a responsive campus management team. Trainees - particularly female trainees - report feeling safe within the campus environment, and the campus’s security infrastructure is genuinely effective at maintaining a safe residential and academic space. Outside the campus, Mysore city is generally considered a safe city in the Indian context, though the standard personal safety practices of any urban environment apply when venturing off-campus.
10. What can I do if I am having trouble adjusting to Mysore life?
The GEC has formal support resources including: counselling services (confidential sessions with a counsellor for personal or psychological difficulties), a training coordinator who is the formal point of contact for training-related concerns, a hostel warden who manages hostel-related issues, and a mentor assigned to each section who acts as a personal academic and professional advisor. Trainees who are struggling - whether with the academic content, the living conditions, the social adjustment, or personal circumstances affecting their performance - should proactively reach out to these support mechanisms rather than trying to manage silently. The training administration’s interest is in each trainee’s success, and the support structures exist because the challenges are real and recognized.
11. How important is the training grade for long-term career at Infosys?
The training grade is visible to project managers during the project allocation process and influences early career perception within the organisation. A strong training grade is a positive signal that the trainee is capable, engaged, and ready for challenging project work. A weak training grade, while not disqualifying from project deployment (assuming minimum standards are met), creates a perception that requires additional effort to overcome in the early project phase. Over the long term (three to five years), actual project performance, skill development, and performance ratings become the dominant career determinants, gradually reducing the relative weight of the training grade. The training grade matters most in the first six to twelve months post-training.
12. What technology should I study independently before arriving at Mysore?
Strengthening Java fundamentals before arriving is the single highest-return pre-joining investment. The Java module is the most demanding and most consequential of the generic training phase, and trainees who arrive with a solid Java foundation (OOP concepts, Collections, exception handling, basic file I/O) advance through it more confidently and have more energy for the deeper content. Beyond Java, reviewing SQL joins and aggregate queries and practising Git command-line operations are the next most useful investments. Soft skills preparation - practising spoken English in professional contexts, reviewing professional email writing conventions - is useful for non-English-medium graduates who want to reduce the adjustment curve in the communication training sessions.
The Infosys Mysore training is a formative experience that compresses years of professional acculturation into a few months. Its value is not limited to the technical skills it builds - it is also in the professional identity it shapes, the relationships it establishes, and the cultural understanding of what it means to be an Infosys professional that it transmits. Trainees who arrive with genuine engagement, manage the intensity without being overwhelmed by it, and invest in both the technical curriculum and the human dimensions of the campus life emerge from Mysore meaningfully better prepared for the demands of their career than they were when they arrived. That transformation, repeated thousands of times per year, is what the GEC is built to produce.