A career at Infosys follows a well-defined ladder. The designations are clearly named, the competency expectations at each level are documented, and the appraisal mechanism that drives movement from one level to the next is structured and predictable. Yet despite this clarity of structure, many Infosys employees feel unclear about where they stand, how fast they should be progressing, what specifically they need to demonstrate to move up, and whether the pace of their career reflects the quality of their work.
This guide resolves that ambiguity. It maps the entire Infosys designation hierarchy from Systems Engineer at the entry level through Senior Systems Engineer, Technology Analyst, Technology Lead, Delivery Manager, Senior Delivery Manager, Associate Vice President, and Vice President. For each level it covers: the typical time spent before the next promotion, the skills and competencies evaluated, how the appraisal process works, what a performance rating means and how it drives outcomes, the salary jump at each promotion, whether certifications help, how Internal Job Postings work, the difference between technical and managerial career tracks, how onsite experience factors into advancement, and realistic timelines for top performers versus average performers.
This is the guide that turns the Infosys career ladder from a vague aspiration into a navigable plan.
Table of Contents
- The Infosys Designation Hierarchy: An Overview
- Systems Engineer (SE): The Starting Point
- Senior Systems Engineer (SSE): The First Promotion
- Technology Analyst (TA): The Mid-Career Inflection
- Technology Lead (TL): The Senior Individual Contributor
- Delivery Manager (DM): The Management Threshold
- Senior Delivery Manager and Associate Vice President
- Vice President and Above
- The Appraisal Process: How It Actually Works
- Performance Ratings and What They Mean
- How Increments Are Determined
- The Role of Certifications in Career Growth
- Internal Job Postings: The IJP System
- Technical Track vs Managerial Track
- Onsite Opportunities and Career Acceleration
- Realistic Timelines: Top Performer vs Average Performer
- Common Career Growth Mistakes at Infosys
- Frequently Asked Questions
The Infosys Designation Hierarchy: An Overview
The Infosys designation hierarchy is structured in a way that mirrors the progression from individual execution to team ownership to business accountability. At the bottom of the ladder, the focus is entirely on doing: writing code, completing test cases, building modules, and delivering assigned work to specification. As the ladder progresses, the focus shifts from doing to enabling, from enabling to directing, and ultimately from directing to strategizing.
The standard designation ladder, from entry level to senior leadership, looks like this:
- Systems Engineer (SE) - Entry level
- Senior Systems Engineer (SSE) - First promotion
- Technology Analyst (TA) - Mid-level individual contributor
- Technology Lead (TL) - Senior individual contributor or first-line technical lead
- Delivery Manager (DM) - First management designation
- Senior Delivery Manager (SDM) - Senior manager
- Associate Vice President (AVP) - Senior leader
- Vice President (VP) - Executive
- Senior Vice President (SVP) / Executive Vice President (EVP) - Senior executive
There are also specialist tracks within this hierarchy that do not follow the standard progression: Principal Architect, Chief Architect, and Distinguished Member of Technical Staff are designations that recognize deep technical expertise rather than managerial progression. These tracks are less commonly discussed but represent meaningful career options for employees who want to build deep technical careers without moving into management.
The Hierarchy in Practice:
The designations above represent the formal titles. In practice, each designation band contains sub-levels or seniority differentiations that are not reflected in the title but are reflected in compensation, project accountability, and the expectations placed on the employee. A newly promoted TL and a TL with four years at that designation have the same title but very different profiles. Understanding this internal differentiation within bands is important for calibrating career position accurately.
How the Hierarchy Differs From Other IT Companies:
The Infosys designation structure is broadly similar to those used by peer IT services companies, with designations mapped to comparable roles across the industry. However, there are nuances: the specific competency expectations at each Infosys level, the time-to-promotion norms, and the salary bands attached to each designation differ from those at TCS, Wipro, HCLTech, and Cognizant. Employees who have worked at multiple IT services companies often note that the Infosys career framework is more explicitly documented and communicated than at some peer firms, which makes it more navigable once understood.
Lateral Hires and the Designation Mapping:
Lateral hires who join Infosys from other companies are mapped to a designation based on their years of experience, skill profile, and the role they are being hired for. An experienced professional with five years at a competitor may join as a Technology Analyst even if their previous title was something different. The designation mapping is negotiated during the hiring process and can sometimes be a point of discussion for candidates who believe their experience warrants a higher starting designation than the initial offer reflects.
Business Units and Career Growth:
Infosys is organized into multiple business units (BUs) that serve different industry verticals (Financial Services, Retail, Manufacturing, Healthcare, Communications, and others) and different service lines (Digital, Application Services, Infrastructure, Testing, and others). Career growth dynamics are not uniform across all BUs. Some BUs have larger project portfolios and more frequent promotion opportunities; others are more stable with slower movement. The BU an employee lands in after Mysore training is a significant variable in the career trajectory, and employees who find themselves in BUs with limited growth opportunities should use the IJP system proactively to move to higher-growth environments.
Understanding Band Overlap:
One feature of the Infosys hierarchy that surprises many employees is the degree of salary band overlap between adjacent designations. An SSE at the high end of the SSE salary band may earn more than a newly promoted TA at the entry point of the TA band. This overlap exists because salary progression within a band is continuous through annual increments, while promotions happen at discrete points. The practical implication is that a promotion to a new designation does not automatically mean earning more than all employees at the prior designation; it means entering a band with a higher ceiling and a trajectory toward higher compensation over time.
Systems Engineer (SE): The Starting Point
The Systems Engineer is the entry-level designation at Infosys. Every fresher joins at this level (unless they enter through the PP or DSE premium tracks, which map to different starting points in the hierarchy). The SE designation represents the first professional role in most employees’ careers, and the habits, work ethic, and technical approach developed at this level establish the foundation for everything that follows.
What the SE Role Involves:
At the SE level, the primary expectation is execution. The SE is expected to understand assigned tasks, ask clarifying questions when needed, implement the task correctly and on time, and escalate blockers to the senior team member or project lead before they cause timeline slippages. The SE is not yet expected to design solutions, manage timelines, or engage directly with clients in most project environments.
The specific work of an SE depends entirely on the project stream: in a Java Full Stack project, the SE writes code for specific modules under the guidance of an SSE or TA; in a testing project, the SE executes test cases and logs defects; in a cloud project, the SE follows the architecture established by a senior team member and implements specific configurations or deployments. The common thread is that the SE works within a framework established by others.
First Project Reality:
The first project after Mysore training is a significant adjustment for most new joiners. The structured schedule of training gives way to the self-directed demands of project work. There is no trainer to guide each day’s learning; instead, there is a codebase to understand, a project context to absorb, and a team of colleagues whose working styles and expectations must be navigated.
Most SEs spend the first two to four weeks of their first project primarily in learning mode: reading documentation, reviewing existing code, attending meetings without fully understanding the context, and completing small tasks that orient them to the system. This initial period can feel uncomfortable if the SE expects to be immediately productive at a high level. The most constructive mindset is patient curiosity: absorb as much as possible, ask specific and well-formed questions, and gradually expand the scope of contribution as familiarity builds.
What Distinguishes an SE Who Advances Quickly:
The SEs who advance to SSE faster than average share several characteristics. They deliver assigned work reliably and on time, consistently, without needing to be chased. They ask good questions when stuck rather than either guessing incorrectly or sitting paralyzed. They invest time in self-learning beyond the assigned work: studying the parts of the system they have not yet been assigned to, practicing skills not yet tested in the current project, and maintaining the learning habit developed at Mysore.
Perhaps most importantly, fast-advancing SEs look for ways to contribute beyond the minimum. This does not mean working excessive hours; it means bringing initiative to the role. Identifying a test that was missed, suggesting a more efficient implementation approach, or documenting a tricky piece of the system that has no existing documentation are all examples of initiative that becomes visible to senior team members and project managers and creates the foundation for a strong performance rating.
Typical Tenure at SE:
The standard tenure at the SE designation before promotion to SSE ranges from two to three years for average performers. High performers with consistent top ratings can be promoted in as little as one and a half to two years. SEs whose performance is consistently average or below may remain at the SE designation for three or more years. The exact promotion timeline is influenced by performance ratings accumulated over multiple appraisal cycles and by the availability of SSE positions in the business unit.
Building the Promotion Case at SE Level:
The promotion from SE to SSE does not happen by default based on time served. It requires the employee to actively build a case through consistent, visible performance. The most effective approach is to treat each project phase as a promotion-building opportunity: deliver assigned work at a quality that exceeds the minimum expectation, proactively document contributions in a way that makes them visible to the manager, and seek out small scope expansions (a slightly more complex task, a mentoring moment with an even newer joiner, a contribution to the team’s documentation) that create evidence of SSE-level readiness.
Employees who wait for the manager to notice their readiness and initiate a promotion conversation typically wait longer than employees who have regular check-in conversations with the manager about career progression, ask explicitly what would need to be demonstrated for promotion consideration, and then demonstrably meet those expectations over the following months.
The First Appraisal:
The first formal appraisal typically occurs approximately nine to twelve months after joining, depending on when the employee joined in relation to the appraisal cycle. The first appraisal is primarily informational for most SE freshers: it establishes the initial rating baseline and provides feedback about development areas. Few SEs receive promotions at the first appraisal; the promotion case is built over two or more appraisal cycles.
Making the most of the first appraisal means: writing a thorough self-assessment even as a first-year employee, asking the manager specific questions about what growth looks like over the next year, and leaving the appraisal meeting with a clear understanding of the one or two things to prioritize to improve the rating at the next cycle.
Senior Systems Engineer (SSE): The First Promotion
The SSE designation represents the first formal recognition that the employee has moved beyond pure execution into a higher level of contribution. The SSE is expected to independently handle more complex tasks, contribute to the design of smaller components, guide junior team members (SEs), and begin taking ownership of specific modules or workstreams rather than just assigned tasks.
Competencies Evaluated for SE to SSE Promotion:
The specific competencies assessed for the SSE promotion are documented in Infosys’s internal career framework, but the general areas of evaluation include:
Technical proficiency: has the employee developed genuine depth in the relevant technology stack? An SSE candidate should be able to independently debug non-trivial issues, write efficient and maintainable code, and understand the system architecture well enough to make sound implementation decisions for their assigned scope.
Delivery reliability: does the employee consistently deliver assigned work within defined timelines with acceptable quality? Promotion decisions are significantly influenced by whether the employee has built a track record of reliable delivery over multiple project assignments.
Communication and collaboration: can the employee communicate technical topics clearly, both in writing and verbally, to colleagues and to less technical stakeholders? Effective communication at the SSE level includes the ability to participate meaningfully in design discussions, to document technical decisions, and to provide accurate status updates without needing to be prompted.
Initiative and ownership: does the employee proactively identify and address issues rather than waiting to be directed? SSE promotions consistently go to employees who demonstrate some degree of self-direction and problem ownership, not just to employees who execute assigned tasks well.
The SSE’s Evolving Responsibilities:
After promotion to SSE, the employee’s project role shifts to include mentoring of SE colleagues, participation in technical design discussions for the workstreams they own, and the initial level of client interaction that comes with being a more senior team member. In some project contexts, the SSE also takes on the responsibility of effort estimation for their own tasks and contributes to the overall project scheduling process.
The SSE level is where the distinction between employees on a fast technical track and those on a slower, steadier track first becomes visible. SSEs who actively develop their technical depth, seek out more complex assignments, and contribute to design discussions position themselves for faster promotion to TA. SSEs who remain primarily in execution mode, handling assigned tasks reliably but not expanding their scope, may spend more years at the SSE level before the evidence base for a TA promotion is established.
Salary Jump at SE to SSE Promotion:
The salary increase at the SE to SSE promotion is a combination of the regular annual increment and the promotion-specific uplift. For an SE receiving a promotion alongside an annual increment, the combined increase typically falls in the range of 15 to 30 percent of the current CTC. A fresher SE at 3.6 LPA who is promoted to SSE with a combined increment and promotion uplift of 25 percent moves to approximately 4.5 LPA. Employees who receive higher annual increments based on strong performance ratings experience a larger jump.
Typical Tenure at SSE:
The SSE designation is where many Infosys employees spend the longest time in terms of years, partly because the range of the SSE band is wide and partly because the TA promotion requires a broader evidence base than the SE to SSE promotion. Average performers may spend three to five years at SSE before being promoted to TA. High performers with consistently strong ratings can achieve the TA promotion in two to three years from SSE. The absolute timeline from joining to TA varies, but the typical range is four to six years for strong performers and six to eight years for average performers.
Technology Analyst (TA): The Mid-Career Inflection
The Technology Analyst designation marks a meaningful inflection point in the Infosys career. The TA is expected to own technical delivery for a module or workstream, contribute to the project’s overall technical direction, and bridge between the execution done by SEs and SSEs and the strategy set by the Technology Lead or Project Manager. The TA is often the most technically hands-on senior member of the team while also beginning to take on some leadership and client communication responsibilities.
What Changes at TA:
The shift from SSE to TA is not just a title change; it involves a genuine change in the nature of contribution expected. TAs are expected to lead technical discussions, make design decisions for their scope, and take accountability for the quality of the work done by the junior team members they guide. A TA who simply does good technical work but does not effectively mentor the SEs and SSEs on their team is not fully performing at the TA level.
Client interaction becomes more regular at the TA level. In client-facing projects, TAs often participate in daily standups or status calls with client technical counterparts, respond to client queries about technical implementation, and represent the team’s technical work in review meetings. The ability to communicate technical topics clearly to people with varying technical backgrounds is a TA-level competency that directly affects client satisfaction and project relationships.
Competencies for SSE to TA Promotion:
Technical leadership: has the employee demonstrated the ability to lead a technical workstream from design to delivery? The TA promotion requires evidence that the employee has moved beyond individual task execution into genuine ownership of a body of work that others contribute to.
Mentoring effectiveness: has the employee successfully guided junior team members to better performance? This is evaluated not just by whether the SSE has technically mentored others, but by whether the people they mentored have improved and delivered better work as a result.
Problem-solving at the system level: can the employee analyze and resolve issues that span multiple components or involve architectural trade-offs? TA-level problem-solving goes beyond debugging individual code blocks to diagnosing issues in the interactions between components, in the data flows between systems, or in the architecture choices made during the design phase.
Stakeholder management: has the employee built positive working relationships with clients or business stakeholders? Even at the TA level, where direct client ownership is still limited, the quality of the working relationships built with internal and external stakeholders matters.
Salary Jump at SSE to TA:
The SSE to TA promotion typically comes with a combined increment and promotion uplift of 20 to 35 percent. An SSE earning 6 LPA who receives a 25 percent combined increase on promotion moves to approximately 7.5 LPA. The absolute salary at TA level varies significantly depending on the path taken: an SSE who was promoted quickly and has a high base salary from strong increments will be at a higher TA-entry salary than an SSE who took longer and received smaller increments.
The TA Level and the External Market:
The TA designation with four to six years of total experience is also the career stage where the gap between internal Infosys salaries and the external market often becomes most pronounced. A TA with strong skills in high-demand areas like cloud engineering or data engineering may find the external market offering significantly more than the internal Infosys salary band. This is the point at which many employees either negotiate hard for above-average increments, pursue IJP opportunities that come with salary revisions, or make a move to the external market.
Technology Lead (TL): The Senior Individual Contributor
The Technology Lead designation represents the peak of the technical individual contributor path at Infosys before the shift into full management. TLs own the technical direction for a project component or a team, manage direct interactions with client technical counterparts, contribute to project planning and estimation, and are accountable for the technical quality of everything their team delivers.
The Technical Leadership Expectation:
At the TL level, the word “lead” is meant literally. The TL does not just contribute technically; they lead the technical approach. This includes setting coding standards for the team, conducting code reviews that actually improve the code and teach the reviewer’s approach, designing the architecture of the components their team builds, representing the technical view in project meetings, and identifying and mitigating technical risks before they become delivery issues.
TLs at Infosys are also expected to bring innovation to their project context. This does not mean building entirely new systems; it means identifying opportunities to use better tools, more efficient algorithms, or more scalable patterns within the existing project scope, and making the case for these improvements to the Delivery Manager and client stakeholders.
Client Ownership:
The TL is typically the primary technical point of contact for the client technical team. This relationship involves regular communication about implementation progress, technical design choices, issue resolution, and scope discussions. Managing this relationship effectively requires a combination of technical credibility (the client must trust that the TL knows what they are talking about), communication clarity (the client must understand what the TL is communicating even when the content is technical), and professionalism under pressure (the client relationship is maintained even when the project is going through difficult periods).
TLs who build strong client relationships are significantly more effective than those who are technically excellent but cannot manage the interpersonal complexity of client communication. The client relationship is itself a career asset that opens opportunities for onsite deputation, expanded project scope, and positive references in future work.
Competencies for TA to TL Promotion:
Technical architecture capability: can the employee design not just individual components but the integration between components and the overall structure of a system? TA to TL promotions require evidence of architectural thinking at a level that goes beyond module-level design.
Team leadership: has the employee successfully led a team of more than one or two people across a complete project phase? TL promotions go to employees who have a track record of bringing teams through project deliveries, not just to strong individual technical contributors.
Project management contribution: has the employee contributed meaningfully to project planning, effort estimation, and risk management? TLs are expected to be active participants in project management activities, not passive recipients of plans made by others.
Client management: has the employee managed client technical relationships with positive outcomes? Some evidence of effective client-facing technical communication is expected for a TL promotion.
Salary Jump at TA to TL:
The TA to TL promotion typically brings a combined increment and promotion uplift of 20 to 30 percent. A TA at 10 LPA who receives a 25 percent combined increase moves to approximately 12.5 LPA. At the TL level, income tax becomes a significantly larger component of the monthly calculation, and the financial value of optimizing tax declarations through 80C, HRA, and NPS contributions becomes material.
Typical Tenure at TL:
The TL designation is where many high-performing Infosys employees spend a substantial portion of their mid-career: two to five years before either moving to the Delivery Manager track or reaching a senior TL position with commensurate compensation. The decision between the technical track and the management track (described in detail in a later section) often crystallizes at the TL level.
Delivery Manager (DM): The Management Threshold
The Delivery Manager designation represents the transition from individual contributor to full management accountability. The DM owns the delivery of a project or a significant portion of a large program, manages a team of TLs, TAs, SSEs, and SEs, handles the Infosys-client commercial relationship at the project level, and is accountable for the financial performance of the delivery engagement.
What the DM Role Actually Involves:
The day-to-day reality of the DM role is quite different from the TL role. While a TL might spend the majority of their time in technical work with some management activities, a DM spends the majority of their time in management, coordination, and client communication, with technical involvement increasingly in an advisory or oversight capacity.
DMs attend and lead project meetings, manage project financials (including tracking margins, managing billing, and controlling costs), handle escalations from both the client and from the project team, manage team composition by working with the Resource Management Group, conduct performance reviews for their direct reports, and represent Infosys’s interests in commercial discussions with the client.
The skills required for DM success are different in emphasis from TL success. Analytical ability, interpersonal effectiveness, business acumen, and the ability to manage multiple competing priorities simultaneously become more important. Technical depth remains valuable but increasingly in the form of technical judgment rather than hands-on implementation.
Competencies for TL to DM Promotion:
Delivery ownership: has the employee demonstrated accountability for an entire delivery engagement, including both technical and commercial outcomes? TL to DM promotions require a track record of successful project delivery where the employee was genuinely accountable for outcomes, not just a participant in them.
People management: has the employee managed a team and been responsible for team members’ performance, development, and satisfaction? The DM role is intrinsically managerial, and a TL who has not yet managed people at scale will find the DM role significantly more challenging than a TL who has developed people management skills progressively.
Financial acumen: does the employee understand project financials, billing structures, and the relationship between delivery efficiency and margin? This competency is explicitly evaluated for DM promotion because DMs are responsible for the financial health of their delivery engagement.
Client relationship ownership: has the employee owned a client relationship at a level that involved commercial discussions, escalation management, and multi-level client engagement? The DM role requires confidence in managing complex client relationships.
Salary Jump at TL to DM:
The TL to DM promotion is typically the largest single salary jump in the Infosys career for most employees. Combined increment and promotion uplift of 25 to 40 percent are not unusual. A TL at 15 LPA who receives a 30 percent combined increase moves to approximately 19.5 LPA. At the DM level, variable pay becomes a more significant component of total compensation, and high-performing DMs in strong business years can earn meaningfully above their base CTC through variable payouts.
Typical Tenure at DM:
The DM designation contains a wide range of seniority. A newly promoted DM and a DM with eight years of experience at that level have the same title but vastly different profiles, compensation, and scope of accountability. Many Infosys employees who make DM do not progress beyond it, not because of failure but because the DM band is large and the SDM and AVP positions above are significantly fewer in number. The career at DM level is nonetheless a meaningful and financially rewarding one.
Senior Delivery Manager and Associate Vice President
Beyond the Delivery Manager band, the hierarchy enters the senior leadership territory. These roles are fewer in number relative to the DM band and require a broader combination of business leadership, client ownership, and organizational influence than the DM role.
Senior Delivery Manager (SDM):
The SDM oversees multiple DMs, manages a larger portfolio of client relationships or a larger program with multiple workstreams, and contributes to the business unit’s strategy for client growth and retention. The SDM is typically responsible for a significant revenue portfolio and is evaluated on both delivery quality and business development outcomes.
Promotion from DM to SDM requires a track record of successful DM performance across multiple engagements, demonstrated ability to grow client relationships commercially, and the organizational credibility built through sustained high performance. The timeline from DM to SDM varies widely: some high-performing DMs with exceptional client relationships make the jump in three to five years; others remain at DM for their entire careers without a sense of career failure.
Associate Vice President (AVP):
The AVP level represents entry into the senior executive layer of Infosys. AVPs lead large business units, practice areas, or client verticals. The responsibilities at this level include people leadership at scale, business development, account strategy, P&L ownership, and representation of Infosys’s brand and capabilities to senior client stakeholders.
Compensation at the AVP level is individually negotiated and includes a larger variable component than lower levels. Industry estimates place AVP compensation at Infosys in the range of 35 to 60 LPA CTC, with the variable component and potential equity participation adding further to total compensation in strong performance years.
The path to AVP from SDM or from DM (where highly exceptional DMs may be considered for direct elevation) requires sustained outstanding performance over many years, the building of organizational influence and credibility, and typically some combination of business development achievement, client relationship elevation, and people leadership at scale. It is not a guaranteed outcome of tenure; many capable and competent Infosys employees build excellent careers without reaching the AVP level.
Vice President and Above
The Vice President designation and the senior executive levels above it represent the most senior leadership positions at Infosys. VPs lead large business units, major client accounts, or functional areas of the company. Their compensation includes a significant equity component in many cases and is structured to align individual incentives with company-level business performance.
At the VP and above level, the career is defined less by the Infosys designation hierarchy and more by the business outcomes the executive produces: the revenue generated, the client relationships sustained, the people developed, and the organizational capability built. Public information about specific compensation at these levels is limited, but total compensation for senior VPs and above at Infosys routinely reaches into the crore range for annual total compensation including variable and equity.
The path to VP requires exceptional performance sustained over a career measured in decades rather than years, along with a combination of strategic capability, commercial success, and organizational leadership that is genuinely rare. Understanding that VP is not a reasonable planning horizon for most employees is not pessimism; it is accurate calibration that allows focus on the career stages where deliberate effort produces meaningful outcomes.
The Appraisal Process: How It Actually Works
The Infosys appraisal process is the engine that drives all salary and career decisions. Understanding it in detail, rather than in the simplified version that most employees work from, is one of the most practical career management tools available.
The Annual Cycle:
The standard Infosys performance appraisal cycle runs annually, aligned with the financial year (April to March in India). The appraisal process typically begins with a self-assessment phase in January or February, where employees document their accomplishments, contributions, and learning activities for the year in the internal performance management system.
The Self-Assessment:
The self-assessment is the employee’s primary opportunity to influence their rating. Many employees write minimal entries, treating it as a formality. This is a significant missed opportunity. The self-assessment should be a detailed, specific, and evidence-based account of the employee’s contributions during the year.
Effective self-assessments include: specific project deliverables with measurable outcomes where possible (“reduced API response time by 35 percent through query optimization” is more compelling than “improved system performance”), descriptions of technical challenges solved and the approach used, evidence of mentoring or development contributions to junior team members, client feedback or appreciation where it exists, certifications completed, and any innovation or process improvement initiatives contributed to.
The manager uses the self-assessment as a starting point for the rating discussion. A well-documented self-assessment gives the manager evidence to justify a higher rating in the moderation discussions that follow. An empty or vague self-assessment leaves the manager with less to work with and may result in a rating that does not fully reflect the employee’s actual contribution.
Manager Rating:
After the self-assessment phase, managers assign preliminary ratings to each of their direct reports. The rating is based on the manager’s overall assessment of the employee’s performance during the year, informed by the self-assessment, the manager’s observations of the employee’s work, feedback from project stakeholders, and the employee’s contribution to team outcomes.
The manager rating is preliminary because it goes through a moderation process before it is finalized.
Moderation:
The Infosys appraisal moderation process is where preliminary ratings are reviewed and adjusted to ensure the distribution across the business unit follows the expected bell curve. In practice, moderation means that if a manager has rated too many employees in the top tier, some of those ratings will be pulled down to middle tiers during the moderation discussion.
The moderation process involves a panel of managers and HR representatives who review the rating distribution for the business unit and make adjustments to bring it within the expected distribution. Individual managers advocate for their top employees during this process, which means the quality of the self-assessment (which informs the manager’s advocacy) and the strength of the manager’s relationship with senior stakeholders (who participate in moderation) both influence outcomes.
Rating Communication:
After moderation, final ratings are communicated to employees by their managers in a one-on-one review meeting. This meeting is also where feedback about the employee’s development areas is discussed, and where the increment percentage for the coming year is communicated (or indicated before the formal announcement).
The Feedback Conversation:
The quality of the feedback conversation varies significantly by manager. Some managers provide specific, actionable feedback that helps the employee understand exactly what distinguishes their current rating from the next higher rating. Others provide vague or generic feedback that does not help the employee navigate the path to improvement. Employees who receive feedback should ask specific follow-up questions: “What would I need to demonstrate next year to move from this rating to the next tier?” is a direct and legitimate question that a good manager should be able to answer.
When Appraisal Results Feel Unfair:
Employees who believe their performance rating does not accurately reflect their contribution have an internal process for raising a review. This review process involves submitting a formal feedback or appeal through the HR system, which triggers a review by HR and the manager’s manager. The bar for a successful review is demonstrating specific, documented evidence that the rating criteria were applied inconsistently or that material contributions were not considered.
The review process is not commonly used and is not always successful, but it is a legitimate recourse for employees who have strong evidence that the rating was materially inaccurate. More importantly, whether or not the formal review is pursued, the post-appraisal conversation with the manager should always seek specific clarity on what higher performance looks like, regardless of whether the current rating is felt to be fair.
Mid-Year Check-Ins:
Beyond the formal annual appraisal, Infosys encourages mid-year check-in conversations between employees and managers. These check-ins are less formal than the annual review but serve as an important opportunity to course-correct if the year is not going in the direction needed for a strong appraisal, to seek feedback before it is too late to act on it, and to ensure the manager’s understanding of the employee’s contributions is current and accurate.
Employees who use mid-year check-ins proactively, bringing specific accomplishments and development questions to the conversation, consistently report better appraisal outcomes than those who have their first real career conversation with the manager only during the formal appraisal cycle.
Performance Ratings and What They Mean
The Infosys performance rating system uses a tiered structure where each tier carries implications for increment percentage, promotion eligibility, and variable pay payout. Understanding these implications concretely helps employees calibrate the actual financial and career significance of their rating.
The Rating Tiers:
The specific labels for rating tiers vary by business unit and have been revised across different versions of the Infosys performance management system. The general structure follows a five-tier model from outstanding or exceptional performance at the top through exceeds expectations, meets expectations, needs improvement, and below expectations at the bottom.
The distribution of these ratings is managed through the moderation process. Typically, the top two tiers (outstanding and exceeds expectations) are available to approximately 15 to 25 percent of the rated population, the middle tier (meets expectations) covers approximately 60 to 70 percent, and the lower tiers cover the remaining 10 to 15 percent.
Rating and Increment:
The annual increment percentage applied to each employee’s base salary is directly tied to the performance rating. Infosys announces a company-wide average increment at the beginning of the appraisal results period, and this average applies to mid-tier (meets expectations) performers. Top-tier performers receive increments significantly above the average, while lower-tier performers receive increments significantly below.
In a year where the company announces an average increment of 8 percent, a typical distribution might be: outstanding performers receive 20 to 25 percent, exceeds expectations performers receive 12 to 15 percent, meets expectations performers receive 6 to 8 percent, needs improvement performers receive 0 to 4 percent, and below expectations performers receive no increment or are placed on performance improvement programs.
The compounding effect of these differential increments over five years is dramatic. An employee who consistently receives top-tier ratings accumulates a significantly higher salary than an identically-tenured colleague who consistently receives mid-tier ratings, even starting from the same base.
Rating and Promotion:
Promotion eligibility is also tied to performance rating over multiple cycles. To be considered for promotion from one designation to the next, an employee typically needs to have demonstrated consistent performance at the mid-to-upper tier for at least two to three consecutive appraisal cycles. A single outstanding year followed by several average years is not typically sufficient for promotion; the consistency of high performance is what the promotion decision reflects.
Rating and Variable Pay:
As described in the salary structure guide, the variable pay payout is a function of both company performance and individual performance multipliers. The individual performance multiplier maps directly to the performance rating. Top-rated employees receive variable payout above the eligible amount; middle-rated employees receive the eligible amount or slightly below; lower-rated employees receive significantly reduced variable payouts.
The Psychological Dimension of Ratings:
Performance ratings at Infosys, as at most large organizations, have a significant psychological dimension. Receiving a mid-tier rating after a year of genuine effort can be demotivating, particularly if the employee believes they performed at a higher level. The forced distribution means that some employees who performed well will receive middle ratings simply because the top tier was fully allocated to others who performed even better.
The most productive response to a disappointing rating is to have a specific, outcome-focused conversation with the manager about what specifically distinguishes top-tier from mid-tier performance in the current project and team context, and to translate that understanding into a concrete development plan for the next year. Treating the rating as an arbitrary judgment rather than as information about relative performance leads to disengagement rather than development.
How Increments Are Determined
The increment determination process at Infosys involves both company-wide parameters and individual-level factors. Understanding both dimensions helps employees accurately interpret the increment they receive and plan accordingly.
Company-Wide Increment Parameters:
Infosys announces its average increment percentage for the year after the appraisal results are finalized. This announcement is typically public and reflects the company’s financial performance, competitive positioning in the talent market, and internal compensation governance. In years when Infosys reports strong financial results, average increments tend to be higher; in years with revenue pressure or margin headwinds, average increments are lower.
The average increment announced by the company is not the increment any individual employee will receive; it is the population average around which the distribution of actual increments is centered. Employees should not compare their personal increment directly to the announced average without accounting for the rating-based differential that applies.
Individual-Level Factors:
Beyond the rating-based differential, the following factors influence the individual increment:
Current position within the salary band: employees whose current salary is at the lower end of the range for their designation typically receive higher increments than employees at the higher end, as the company has more room to move lower-positioned employees toward the band midpoint. This internal equity management is a structural feature of the increment process that is not always visible to employees but operates behind the scenes.
Market adjustment considerations: in periods when the external market for specific skills has moved significantly, Infosys may apply additional increments to specific skill cohorts to reduce the risk of attrition. These market adjustments are not typically communicated as a separate line item; they are embedded in the total increment percentage.
Promotion-year increments: in years when an employee is promoted, the increment calculation includes both the regular annual increment and the promotion uplift. The combined percentage is typically higher in promotion years than in non-promotion years.
When Increments Take Effect:
Infosys annual increments typically take effect from a defined date in the financial year, often April 1 or July 1 depending on the business unit’s appraisal cycle. The revised salary appears in the first payslip after the effective date. Employees should verify that the revised salary on their payslip matches the communicated increment percentage applied to their current salary. Discrepancies should be raised with the HR helpdesk promptly rather than allowing an incorrect salary to persist for multiple months.
The Role of Certifications in Career Growth
Certifications play a meaningful but nuanced role in career advancement at Infosys. They are neither the primary driver of promotions nor entirely irrelevant. Understanding their actual impact helps employees invest in certifications strategically rather than either ignoring them or over-indexing on them at the expense of more impactful activities.
How Certifications Are Evaluated Internally:
Infosys tracks certifications completed by employees through the InfyMe and Lex platforms. An employee’s certification portfolio is visible to managers, HR, and in some cases to the Resource Management Group when project staffing decisions are made. Certifications in high-demand areas like cloud platforms (AWS, Azure, GCP), data engineering tools, DevOps platforms, and enterprise software (SAP, Salesforce) are specifically recognized in business units that work heavily in those areas.
Certifications and Appraisal:
Completing relevant certifications during the appraisal year contributes to the learning and development component of the self-assessment. While a certification alone does not move a rating from mid-tier to top-tier, it adds evidence to the employee’s profile that they are actively investing in their professional development, which is a competency that appraisers look for. The certification is most valuable when it is paired with application: a cloud certification that was followed by applying the skills in an actual project context is a stronger narrative than a certification that sits on a profile without associated project application.
Certifications and IJP Applications:
For employees applying through the Internal Job Posting system for roles that require specific technical skills, holding the relevant certifications is often a stated or implied requirement. An employee applying for a cloud architecture role through IJP without any cloud certifications is at a disadvantage relative to an equally experienced candidate who holds the AWS Solutions Architect certification. Targeting certifications specifically at the domains where IJP opportunities are likely to appear is a more strategic approach than certifying broadly without a clear career application.
Which Certifications Matter Most:
The certifications with the highest practical value at Infosys are those that are directly relevant to client-facing work in the business unit. Cloud certifications (AWS, Azure, GCP) have extremely broad applicability and are consistently valuable across most BUs because virtually every client engagement involves some cloud component. Project management certifications (PMP, PRINCE2) become relevant at the TL and DM levels where project management responsibility increases. Agile and Scrum certifications (CSM, SAFe) are practically useful in project environments that operate on Agile delivery models. DevOps and security certifications are specifically relevant in the infrastructure, cloud, and security practice areas.
Certifications from Infosys’s own certification program (delivered through Lex) are specifically recognized within the organization and contribute to the employee’s Lex learning profile, which is reviewed during appraisals.
Internal Job Postings: The IJP System
The Internal Job Posting system at Infosys is one of the most important yet underutilized career tools available to employees. Understanding how the IJP system works and using it actively is a reliable path to salary acceleration, career track changes, and access to more interesting project environments.
What the IJP System Is:
The IJP system is an internal job market where Infosys managers post open positions that are available for current employees to apply for. These positions may be at the same designation level as the applying employee (lateral moves to different projects, technologies, or business units), or at a higher designation (promotions through the IJP route), or occasionally at a lower designation where an employee wants to change domains and is willing to accept a designation adjustment to make the transition.
Who Is Eligible for IJP:
Eligibility for IJP applications requires a minimum tenure in the current role, typically six months to one year. Employees with active performance improvement programs are typically not eligible. Beyond these baseline requirements, eligibility is primarily determined by whether the employee’s current skill profile matches the requirements of the posted position.
How to Use IJP Effectively:
The most effective IJP strategy starts long before an application is submitted. Employees who want to move to a specific domain or technology through IJP should:
Build the relevant skills before applying: submitting an IJP application without the required skills is ineffective. Preparing for an IJP move means completing certifications, working on relevant self-projects, and if possible, volunteering for project tasks that use the target technology even if the primary role is in a different area.
Build a profile within the target domain: internal visibility matters for IJP success. Employees who have participated in internal technical communities, contributed to knowledge-sharing sessions, or engaged with senior members of the target domain are more likely to have their IJP application viewed favorably by the hiring manager than unknown candidates applying cold.
Get manager support where possible: while IJP applications are nominally confidential, in practice many employees inform their current manager before applying for an internal role, particularly if the manager is likely to be supportive. A manager who advocates for an employee’s IJP transition is significantly more helpful than a manager who feels blindsided by the application.
Salary Impact of IJP Moves:
IJP moves at the same designation level do not automatically trigger a salary revision, though they can be an opportunity to negotiate one if the new role has a different salary range or involves specific skills that the employee’s current salary does not reflect. IJP moves that involve a promotion include the promotion increment in addition to any applicable regular increment. Employees making IJP moves to higher-cost-of-living cities may be able to negotiate a location allowance or enhanced HRA recognition.
Technical Track vs Managerial Track
One of the most important career decisions an Infosys employee makes is whether to pursue advancement through the technical track or the managerial track. This decision is rarely made explicitly at one moment; it typically crystallizes gradually as the employee’s preferences, strengths, and available opportunities become clearer.
The Managerial Track:
The standard Infosys designation progression from TL to DM to SDM to AVP is a managerial track. Advancement along this track requires progressively developing people management, client relationship management, and business delivery ownership capabilities. The managerial track leads to the highest total compensation at the senior levels and offers the broadest organizational influence, but it requires comfort with the full range of management responsibilities.
For technically oriented employees who find people management, financial accountability, and commercial discussions less engaging than deep technical work, the managerial track can feel like an uncomfortable evolution away from the work they most enjoy. Forcing this transition primarily for compensation reasons rather than genuine interest in management tends to produce less satisfied and less effective managers than those who genuinely find the management dimension of the work engaging.
The Technical Track:
For employees who want to deepen their technical expertise without shifting into management, Infosys has a technical specialist ladder that runs parallel to the standard designation hierarchy. Designations like Principal Architect, Chief Architect, and Distinguished Member of Technical Staff recognize deep domain expertise and award compensation competitive with the managerial track at equivalent seniority levels.
The technical track is less commonly discussed within Infosys because fewer employees qualify for and reach the senior technical specialist designations, and because the internal visibility of technical specialists is lower than that of managers who own client relationships. However, for the right employee, the technical track offers a career that is genuinely aligned with their strengths and interests rather than a compromise between technical work and administrative responsibility.
Making the Choice:
The choice between technical and managerial tracks should be made based on genuine self-knowledge about where the employee’s strengths lie and what kind of work they find most engaging, not primarily on compensation considerations. Senior technical specialists at Infosys earn compensation comparable to DMs and SDMs; the choice of track does not force a compensation penalty. What it does determine is the nature of daily work, the skills that need to be developed, and the career metrics that define success.
Employees who are unsure which track to pursue should experiment deliberately: take on a team leadership or mentoring responsibility for a period to test how they respond to management activities. If the management work is energizing and the challenges are interesting, the managerial track is a natural fit. If the management overhead feels like distraction from the technical work that is most engaging, the technical track is likely the better long-term choice.
The Hybrid Reality:
In practice, the technical and managerial tracks are not perfectly separate at the TL level and below. TLs do both technical work and people management. TAs lead modules while still writing code. The clean separation between the tracks only becomes clear at the DM level and above. This means that the choice does not need to be made irrevocably at the TL stage; the DM promotion process itself will clarify whether the employee is being evaluated for a management track advancement or whether a technical leadership track is the better fit.
Employees who deliberately build both technical depth and people management capability at the TL level preserve maximum optionality. They can make the choice when the opportunity for DM-track advancement arrives, based on the actual quality and interest of the opportunities available at that time, rather than having foreclosed one track prematurely.
Architect and Principal Architect Tracks:
For employees who are deeply technically oriented, the Architect track at Infosys is worth understanding. The Senior Architect and Principal Architect designations are typically reached by employees in the TL to early DM experience range who have demonstrated exceptional technical design capability, particularly in areas like system architecture, cloud architecture, or enterprise integration design.
Principal Architects at Infosys participate in pre-sales activities (helping the company win new work by proposing technical solutions), lead technical innovation within their domain, and are recognized as technical authorities both internally and in some cases externally. The compensation at Principal Architect level is competitive with TL and early DM salaries, and the work is primarily technical rather than managerial, making it a genuinely attractive option for technically oriented employees.
Onsite Opportunities and Career Acceleration
Onsite deputation to client locations overseas is one of the most significant career accelerators available to Infosys employees. Understanding how onsite opportunities are allocated, what the criteria are, and how to position for them is important for employees who see international exposure as part of their career development plan.
How Onsite Opportunities Are Allocated:
Onsite deputation is driven by client need. When a client requires in-person engagement with Infosys team members, either for a project phase, for ongoing relationship management, or for specific technical delivery that requires proximity to the client’s systems or stakeholders, onsite positions are opened. The RMG and the DM or SDM managing the client relationship determine which team members are appropriate for onsite deputation.
The selection criteria for onsite deputation typically include: technical capability (can the employee perform effectively in the client environment), client interaction readiness (does the employee communicate professionally and confidently in English), availability (does the employee have the relevant documentation, particularly a valid passport and the ability to obtain the required visa), and in some cases specific client preferences.
The Career Impact of Onsite Experience:
Onsite experience at Infosys has a direct and lasting impact on career trajectory. Employees who have completed significant onsite stints, particularly at major clients or in high-complexity technical roles, carry a credibility marker in their profile that influences promotion decisions and IJP outcomes. The reasoning is that onsite performance demonstrates the full range of capabilities (technical, professional, interpersonal, and cross-cultural) that the Infosys career path values at senior levels.
The financial impact of onsite deputation is also meaningful: the overseas allowance and savings potential during onsite periods allow employees to accumulate capital that would take years to build at the India-based salary level, which creates financial runway for major life investments.
Positioning for Onsite Opportunities:
Employees who want onsite opportunities should ensure: their passport is valid and travel documents are in order before a need arises; their technical skills in the project’s domain are at a level that justifies client-facing exposure; their English communication is clear and professional (this is specifically evaluated when onsite selections are made); and their relationship with the DM or Project Manager on their account is strong enough that the DM would consider them for client-facing deputation.
The specific timing of onsite opportunities is not entirely within the employee’s control; it depends on the client’s need. But positioning well means the employee is consistently in the consideration set when opportunities arise rather than being considered only after the obvious candidates have been evaluated.
Onsite Experience at Senior Levels:
For employees targeting the DM and above levels, a significant onsite track record is almost a prerequisite. DMs who have never been onsite have a narrower experience base for client relationship management than DMs with multiple onsite stints across different client contexts. Senior managers who evaluate DM promotion candidates look for evidence of client management experience, and onsite experience is the most direct evidence of this.
Countries and Locations:
Infosys’s major onsite markets include the United States (the largest by volume of deputed employees), the United Kingdom, Australia, Germany, France, and Middle Eastern markets. The compensation structure for onsite varies by country: US onsite postings typically offer the highest overseas allowances relative to Indian salaries, while European and Middle Eastern markets also offer competitive allowances calibrated to local living costs.
Beyond compensation, the country of onsite posting affects the learning and career development dimension. US clients in sectors like banking, insurance, and healthcare often provide exposure to some of the most sophisticated technology environments in those industries, which builds credentials and technical depth that are valuable across the career.
How Long Onsite Postings Last:
Individual onsite postings range from a few weeks (for specific project phases or client review periods) to several years (for long-term client engagement management). The most career-significant onsite experiences are typically those that last six months or more, because the depth of client relationship and project ownership that develops over a longer period is more valuable than the brief exposure of a short-term deputation.
Multiple onsite stints across different clients and geographies build the broadest exposure. Employees who have been onsite at clients in multiple countries, managing different types of client relationships and technology environments, bring a diversity of experience to the DM and senior roles that single-market onsite experience does not provide.
Preparing for Onsite Selection:
Practical preparation for onsite readiness includes: maintaining a valid passport at all times (renewing well before expiry rather than at the last minute), understanding the visa requirements for the countries most relevant to your client portfolio, ensuring English communication skills are at a professional level for all contexts (written, verbal, and presentation), and being prepared to demonstrate the maturity and professional judgment that client-facing work requires. Employees who are known within their project team as reliable, professional, and technically capable are consistently the first considered when onsite opportunities arise.
Realistic Timelines: Top Performer vs Average Performer
One of the most practically useful pieces of information for career planning at Infosys is the realistic timeline comparison between top performers and average performers through the designation ladder. These timelines are based on typical patterns observed across the career progression, not guarantees.
Top Performer Timeline:
A top performer (consistently achieving top two rating tiers across appraisal cycles) can expect the following approximate progression:
- Joining as SE
- Promotion to SSE: 1.5 to 2 years
- Promotion to TA: 3.5 to 4.5 years total (2 to 2.5 years at SSE)
- Promotion to TL: 6 to 7.5 years total (2 to 3 years at TA)
- Promotion to DM: 9 to 12 years total (3 to 4.5 years at TL)
For an employee who joins at 22 and achieves top performer progression, DM at age 31 to 34 is a realistic outcome, which represents strong career velocity by Indian IT industry standards.
Average Performer Timeline:
An average performer (consistently achieving the mid-tier rating) can expect:
- Joining as SE
- Promotion to SSE: 2.5 to 3 years
- Promotion to TA: 6 to 8 years total (3 to 5 years at SSE)
- Promotion to TL: 10 to 13 years total (4 to 5 years at TA)
- Promotion to DM: 15 to 18 years total (5 to 5+ years at TL)
The gap between top performer and average performer timelines is significant in absolute years and in cumulative salary difference. An employee who joins at 22 on the average performer path reaches DM at 37 to 40 rather than 31 to 34. The six to eight year difference in time to DM, multiplied by the salary differential at each level that results from different increment percentages, produces a very large lifetime earnings gap.
The Impact of Lateral Moves:
Employees who make lateral moves to other companies during the early career years and then return to Infosys (or who never leave but use external offers to reset salary) can compress the financial gap between their trajectory and the top performer trajectory even without matching the top performer’s rating profile. Many Infosys employees who have made two to three external moves in their first ten years earn more than Infosys internal top performers at the equivalent designation, because the external market resets have compounded from higher bases.
External Market Comparisons:
The timelines above apply to employees who build their careers entirely within Infosys. External market comparisons are important for calibrating whether the internal Infosys progression represents competitive value. Mid-size product companies, GCCs, and well-funded technology startups often offer faster progression in both designation and salary for employees with strong skills. Employees who are aware of their external market positioning make more informed decisions about when internal Infosys progression is competitive and when an external move produces better outcomes.
The Five-Year Career Checkpoint:
The five-year mark is a useful career checkpoint for Infosys employees. At five years, most employees have completed at least one major project cycle, have gone through multiple appraisals, and have a clearer picture of their performance tier and likely trajectory than they did at joining. The five-year checkpoint is a good moment to assess: is the current designation and salary competitive with the external market for my skills and experience? Is the business unit I am in offering the growth opportunities I want? Is my manager and project environment supporting my development? Is the technical track I am on aligned with where the market is heading?
Employees who do not conduct this kind of deliberate assessment at the five-year mark often find themselves at eight or ten years with a trajectory that has quietly drifted away from what they wanted, requiring a more disruptive correction than an earlier recalibration would have required.
Making a Career Plan Concrete:
The most effective approach to career growth at Infosys is to make the career plan explicit: write down the target designation and timeline, identify the specific competencies and experiences needed to get there, map those needs to specific development actions (certifications, IJP moves, project scope expansions, mentoring relationships), and review the plan annually against actual progress.
Employees who carry their career plan only in their head tend to be less deliberate about pursuing specific experiences than those who have written it down and shared it with their manager. The act of articulating the plan creates commitment and makes the gap between current state and target state visible, which motivates action.
Final Thoughts: Owning Your Career at Infosys
The Infosys career ladder is well-defined and navigable. The designation expectations are documented, the promotion criteria are knowable, the appraisal process is structured, and the tools for career management (IJP, Lex, manager conversations, onsite opportunities) are all available. What varies is how actively and intelligently employees use these tools.
The employees who build the strongest careers at Infosys are not always the most technically gifted. They are the ones who combine genuine technical competence with deliberate career management: they invest in their self-assessments, they build real relationships with managers and senior stakeholders, they seek out scope expansions and challenging assignments, they use certifications to support genuine skill development rather than as resume decoration, and they conduct regular market calibration to ensure their career decisions are informed by accurate external benchmarks.
The difference between a career that feels like it is happening to you and one that feels like you are steering it is almost entirely a matter of deliberate intention and consistent follow-through. The Infosys career framework provides the map. The employee provides the navigation.
Common Career Growth Mistakes at Infosys
Understanding where Infosys employees most often limit their own career growth is as valuable as understanding what accelerates it.
Staying in Comfort Zones Too Long:
The most common career growth mistake at Infosys is remaining on the same project, in the same technology, doing similar work for too many consecutive years. Familiarity and comfort are natural human tendencies, but career advancement requires progressive expansion of scope, skills, and accountability. Employees who do excellent work on a three-year maintenance project but do not develop new skills or seek exposure to new challenges emerge from that period technically weaker relative to the market, less attractive for promotion, and less competitive for IJP opportunities.
Neglecting the Self-Assessment:
As discussed in the appraisal section, the self-assessment is one of the employee’s most direct levers on the rating outcome. Employees who spend five minutes on a perfunctory self-assessment consistently receive lower ratings than the quality of their work justifies, because the manager has no evidence to advocate for them in moderation discussions.
Not Managing the Manager Relationship:
The performance rating is assigned by the manager. The degree to which the manager understands the employee’s contributions, advocates for them during moderation, and supports their development and promotion aspirations depends heavily on the quality of the working relationship. Employees who maintain an arms-length relationship with their manager, rarely seeking feedback, not discussing career aspirations, and not ensuring the manager has visibility into their work and contributions, consistently receive less support than employees who invest in the relationship actively.
Waiting to Be Offered Opportunities:
Onsite deputation, IJP applications, interesting projects, and mentoring opportunities do not typically arrive uninvited for average-visibility employees. Employees who wait to be tapped for opportunities rather than proactively expressing interest and positioning for them will wait much longer than those who communicate their aspirations clearly and make themselves available for opportunities as they arise.
Pursuing Certifications Without Application:
Certifications are valuable when they are applied. An employee who collects certifications without creating opportunities to use those skills in actual project work builds a profile that is impressive on paper but does not generate the concrete delivery evidence that promotion decisions require. Every certification should be paired with a plan for how the skill will be applied in the project context or through an IJP move.
Underestimating the People Management Learning Curve:
Many technically strong employees who are promoted to TL or make the transition toward DM underestimate how different the skills required are from those that made them successful as individual contributors. Writing excellent code is a skill that does not automatically transfer into effectively giving performance feedback, managing a team member who is struggling, or handling a client escalation calmly and professionally. Employees who recognize that people management is a skill to be deliberately developed, rather than something that comes naturally from technical seniority, invest in developing it and become more effective managers faster than those who assume it will come automatically.
Not Using the Manager as a Career Partner:
The manager relationship at Infosys is the most direct lever on career outcomes: rating, promotion recommendation, access to high-visibility assignments, and onsite nominations all flow through or are influenced by the manager. Employees who treat the manager purely as a work supervisor rather than as a career partner leave significant career value on the table. A manager who knows the employee’s career aspirations, understands their strengths and development areas, and is actively advocating for them is one of the most valuable career assets an Infosys employee can have. Building and maintaining this relationship requires transparency about career goals, consistent delivery that justifies advocacy, and a professional relationship that earns the manager’s respect and trust.
Letting Skills Stagnate:
The technology landscape changes rapidly. Skills that were highly valued five years ago (certain legacy platforms, older frameworks, or superseded tools) may carry much less market value today. Employees who do not continuously update their skill portfolio risk finding that both their internal Infosys trajectory and their external market positioning have deteriorated without their noticing, because the project work itself continued at a steady state while the world around it moved on. Annual skill assessment, matched against what is currently valued in the project domains of interest, keeps the learning investment targeted where it has the most career impact.
Misunderstanding the Timeline:
Some employees expect promotion timelines that are faster than the typical patterns allow, particularly for the first promotion from SE to SSE. Expecting a promotion after one year of average performance, when two to three years is the standard for average performers, creates frustration that damages the manager relationship and sometimes leads to premature departure. Understanding the realistic timeline allows for patient, deliberate progression that produces better outcomes than frustrated exits.
Frequently Asked Questions
1. What is the minimum time required for promotion from SE to SSE at Infosys?
The minimum time for SE to SSE promotion is typically one and a half to two years for top performers with sustained outstanding performance ratings. The standard minimum tenure at SE before becoming eligible for promotion consideration is generally one year, but receiving a promotion in the first year is rare and typically reserved for exceptional early-career contributions. Most promotions from SE to SSE happen between the 18-month and 36-month mark.
2. How does the Infosys IJP process work?
The Internal Job Posting process works as follows: open positions are posted on the Infosys internal job board (accessible through InfyMe); eligible employees with the required tenure and skill profile can apply; the hiring manager for the open position reviews applications and conducts interviews; selected employees go through an internal approval process before the move is confirmed. The process typically takes two to six weeks from application to confirmation. The employee’s current manager is typically informed after the selection is confirmed, though in practice many employees inform their manager earlier.
3. Is certification mandatory for promotion at Infosys?
Certifications are not formally mandatory for most promotions, but they are a strong supporting element of the promotion case. For specific roles or IJP moves where certification is listed as a requirement, it is effectively mandatory. Generally, certifications strengthen the promotion case but the primary drivers of promotion are performance ratings, delivery track record, and demonstrated competency at the next level.
4. How does the rating distribution work at Infosys?
Infosys uses a forced distribution model where only a defined percentage of the rated population in each business unit can receive the top ratings. Typically, the top two tiers are available to approximately 15 to 25 percent of the population. The middle tier covers approximately 60 to 70 percent. This means that even in a high-performing team, not everyone can receive a top rating, and middle ratings do not necessarily reflect mediocre performance but rather reflect where the employee sits in the distribution relative to peers.
5. Can a woman on maternity leave be considered for promotion at Infosys?
Infosys’s policies protect employees from discrimination in promotion decisions based on maternity leave. Employees on maternity leave continue to accrue tenure and are not penalized in promotion timelines due to their leave period. However, the practical reality is that performance assessment requires a period of active contribution, and employees who have been on extended leave may have a shorter assessment window for that year, which can affect the evidence base for a promotion in that specific cycle. The promotion may be considered in the following cycle with a full year’s performance record.
6. What is the difference between a promotion and a designation change at Infosys?
A promotion in the standard sense means moving from one designation to the next in the hierarchy (SE to SSE, SSE to TA, etc.), with an associated salary increment and change in role expectations. A designation change can also happen through the IJP process where an employee moves to a different role that maps to a different designation, or in cases of reclassification. Promotions are the primary mechanism for career advancement; designation changes through other means are less common.
7. How does the DM manage project financials?
A Delivery Manager tracks project financials through Infosys’s internal project management systems, which capture billed hours, project costs (including team salaries allocated to the engagement), travel and operational expenses, and the revenue recognized on the engagement. The DM uses this data to manage the project margin, identify cost overruns early, and make staffing and resource decisions that maintain the engagement’s profitability within the approved parameters.
8. Is it possible to move from the technical track to the managerial track or vice versa at Infosys?
Yes, transitioning between tracks is possible but requires deliberate positioning. An employee on the technical track who wants to move to the managerial track needs to build evidence of people management and client relationship capability, typically by taking on team leadership responsibilities in their current role. An employee on the managerial track who wants to shift to a deep technical path needs to rebuild technical depth through certification, self-study, and IJP moves to technical roles.
9. How quickly can an average employee reach TL at Infosys?
For an average performer, reaching the TL designation from joining as a fresher SE takes approximately ten to thirteen years. This includes two to three years at SE, three to five years at SSE, and four to five years at TA before TL promotion. High performers can reach TL in six to eight years through consistent top-tier ratings and proactive career management.
10. What is the Infosys Distinguished Member of Technical Staff designation?
The Distinguished Member of Technical Staff (DMTS) is a senior technical track designation at Infosys that recognizes exceptional technical expertise and contribution. DMTS designees are recognized for their deep knowledge in specific domains, their contributions to Infosys’s intellectual property and technical practices, and their external reputation in the technical community. The DMTS designation carries compensation comparable to senior management levels and is rare, reserved for employees with genuinely exceptional and recognized technical expertise built over many years.
11. How do onsite opportunities affect the promotion timeline?
Onsite experience generally accelerates promotion timelines by providing richer evidence of the competencies required at higher designation levels, particularly client management, professional communication, and cross-cultural collaboration. Employees with significant onsite experience are more often considered for promotion alongside employees with longer India-based tenures. The effect is not automatic but is consistently observed as a positive factor in promotion decisions.
12. What should I do if I receive a lower-than-expected rating?
The immediate step is to have a specific, professional conversation with your manager about what would need to be different next year to receive a higher rating. Ask for specific, observable behaviors and outcomes that distinguish the next rating tier from the one you received. Document this conversation and use it as the basis for a concrete development plan. Avoid expressing the frustration as an accusation against the manager; frame it as a request for guidance on how to improve.
13. Are promotions at Infosys contingent on budget availability?
Promotions at Infosys are driven by both performance and business context. In periods of strong business performance, the promotion budget is more generous and deserving promotions are more likely to be approved. In periods of cost pressure, promotions may be deferred even for employees whose performance warrants advancement. This budget dependency means that timing can affect promotion outcomes regardless of individual performance, and employees who are passed over in a constrained year should continue building the performance record that makes their promotion compelling in the next available cycle.
14. How do I get visibility for promotion when my manager does not advocate for me?
If the current manager does not actively advocate in promotion discussions, build visibility through other channels: contribute to internal technical communities, take on visible assignments that involve senior stakeholders, develop relationships with senior managers in adjacent teams, and use the IJP system to move to an environment where a new manager can assess and advocate for the employee’s promotion independently.
15. What is the career outlook for Infosys employees who stay with the company for ten or more years?
Employees who remain at Infosys for ten or more years and maintain consistent good performance build careers that are financially solid and professionally meaningful. By the ten-year mark, most consistent performers are at the TL or early DM level with compensation in the 15 to 25 LPA range depending on performance history and onsite experience. The career offers stability, progressive growth, and the accumulated institutional knowledge that makes long-tenured employees valuable in client-facing and leadership roles. The long-tenured employee who also keeps technical and market skills current by continuously learning is in a particularly strong position, both internally and for any external moves they choose to make.
Comprehensive Designation and Salary Reference Table:
The following table provides a consolidated reference across all major Infosys designations, combining the career timeline, salary, and appraisal information covered in this guide:
| Designation | Years to Reach (Top Performer) | Years to Reach (Avg Performer) | Approx CTC Range | Key Promotion Criteria |
|---|---|---|---|---|
| Systems Engineer | Joining | Joining | 3.6 LPA | N/A |
| Senior Systems Engineer | 1.5 to 2 years | 2.5 to 3 years | 5 to 7 LPA | Technical proficiency, delivery reliability, initiative |
| Technology Analyst | 3.5 to 4.5 years | 6 to 8 years | 8 to 12 LPA | Technical leadership, mentoring, client communication |
| Technology Lead | 6 to 7.5 years | 10 to 13 years | 12 to 18 LPA | Architecture capability, team leadership, project management |
| Delivery Manager | 9 to 12 years | 15 to 18 years | 18 to 30 LPA | Delivery ownership, people management, financials, client relationship |
| Senior Delivery Manager | 12 to 16 years | 20+ years | 25 to 45 LPA | Portfolio management, business development, revenue ownership |
| Associate Vice President | 16 to 22 years | Not typical | 35 to 60 LPA | Strategic leadership, P&L ownership, large client ownership |
Note: Years shown are cumulative from joining. CTC ranges are approximate and reflect typical market levels, with significant individual variation based on performance, onsite experience, and business unit norms.
This table is a planning tool, not a guarantee. Individual trajectories diverge significantly based on performance consistency, the quality of available opportunities, the business unit environment, and the degree of career management effort invested by the employee.
Using the Table for Career Planning:
The table above is most useful when combined with a personal career position assessment. Identify where you currently sit on the ladder, compare your years-to-date against both the top performer and average performer columns, and use the gap to calibrate whether your current trajectory is on track, ahead, or behind where you want to be.
If behind the top performer timeline and the top performer timeline is your goal, the question is not whether to act but what specifically to change. The three highest-leverage changes are almost always: getting a stronger performance rating in the next appraisal cycle (which requires a better self-assessment, clearer manager communication about contributions, and often a specific capability development that moves the needle from good to excellent); moving to a project environment where the growth opportunities match career goals (which often requires an IJP application); and building external market visibility so that the Infosys career decisions are made against a backdrop of real options rather than theoretical ones.
If at or ahead of the top performer timeline, the focus shifts from acceleration to sustainability: maintaining the performance level that got you here, avoiding the common mid-career mistakes described in this guide, and beginning to invest in the capabilities needed for the next designation level before the promotion conversation arrives.
The Career at Infosys in Long Perspective:
A full career at Infosys, from SE joining to DM or TL at the fifteen to twenty year mark, represents a financially rewarding and professionally substantial journey. The company’s scale, the diversity of client work, the international exposure opportunities, and the structured career framework all contribute to a career that, when navigated well, produces strong outcomes by any reasonable measure.
The employees who look back on their Infosys careers with satisfaction are those who engaged actively with the opportunities available, managed their development deliberately, built genuine relationships, and made clear-eyed decisions about when to accelerate within Infosys and when the external market offered something better. That combination of active engagement and clear-eyed awareness is the most reliable formula for a career that delivers on its potential.