Most engineers who join Infosys as freshers understand their starting designation clearly. What very few of them understand - until they have spent two or three years inside the organisation - is how the career ladder actually works: what separates a top performer from an average one at each level, what the appraisal process genuinely evaluates beyond the official criteria, how long each designation realistically takes to move through, and what the practical salary and responsibility differences are at each rung. The difference between a career that plateaus at Technology Analyst and one that reaches Vice President is not mostly luck or politics. It is a set of specific, learnable competency signals, career decisions, and relationship investments that become visible only when the entire promotion architecture is understood as a system.

Infosys Career Growth and Promotion Path

This guide maps that system in full. It covers every designation from Systems Engineer through Vice President and beyond, with honest assessments of what each level requires, what the appraisal process actually measures, how the rating system feeds into promotions, what the salary jumps look like, and what separates a five-year journey through the ladder from a twelve-year one. Whether you are a fresher planning your first two years, a mid-career professional trying to diagnose why promotions have slowed, or an experienced employee evaluating whether Infosys can support your leadership ambitions, this guide provides the framework.

Table of Contents

  1. Understanding the Infosys Designation Architecture
  2. The Appraisal Process: How Infosys Measures Performance
  3. The Rating System Explained
  4. Systems Engineer: The Foundation Level
  5. Senior Systems Engineer: The First Promotion
  6. Technology Analyst: The Mid-Level Transition
  7. Senior Technology Analyst: Technical Credibility Established
  8. Technical Lead and Technology Lead: The Leadership Gate
  9. Delivery Manager: Entering Senior Leadership
  10. Senior Delivery Manager, AVP, and VP: The Executive Tier
  11. The Technical vs Managerial Track Decision
  12. How Certifications Affect Promotion Timelines
  13. Internal Job Postings (IJP): How the System Works
  14. Onsite Opportunities and Career Acceleration
  15. Top Performer vs Average Performer: Realistic Timeline Comparison
  16. Salary Jumps at Each Promotion: What to Expect
  17. Frequently Asked Questions

Understanding the Infosys Designation Architecture

Infosys’s designation hierarchy is not a simple linear ladder. It is a two-dimensional structure with a vertical dimension (seniority and compensation level) and a horizontal dimension (technical track versus managerial track). Understanding both dimensions is prerequisite to navigating the career system strategically.

The primary designation bands. The Infosys designation hierarchy, from entry level to executive leadership, follows this progression: Systems Engineer (SE), Senior Systems Engineer (SSE), Technology Analyst (TA), Senior Technology Analyst (STA), Technical Lead (TL), Technology Lead (TEL), Delivery Manager (DM), Senior Delivery Manager (SDM), Associate Vice President (AVP), and Vice President (VP). Beyond VP, there are Senior VP and Executive Leadership roles, though these are sufficiently rare and individually shaped that generalising about them has limited practical value.

Each designation corresponds to an internal grade or band level. The band determines the compensation range, the variable pay percentage, the authority level within delivery operations, and the scope of responsibility expected. Movement from one band to the next is what constitutes a promotion in the Infosys context.

The two tracks within the hierarchy. From approximately the Technology Analyst level onward, the career path bifurcates. One direction leads toward the technical specialist track, where the primary identity is as a deep technology expert - an architect, a principal engineer, a domain specialist. The other direction leads toward the delivery and people management track, where the primary identity is as a leader of delivery teams, a people manager, and a client relationship manager. Both tracks exist within the same designation hierarchy (a Technical Architect and a Delivery Manager may be at similar compensation levels), but the day-to-day work, the competencies evaluated for promotion, and the ultimate career ceiling differ significantly.

The bifurcation point is not a permanent, irrevocable decision. Employees who start down the technical specialist path can transition to the managerial track later (typically with a client-facing delivery role as the bridge), and some employees move in the other direction (strong delivery managers who return to technical roles through architecture positions). But in practice, the specialisation tends to deepen with seniority, and the transition becomes progressively harder as the skills and relationships relevant to each track diverge.

What “promotion” means at Infosys. In the Infosys context, promotion means a formal change in designation band, accompanied by a revised compensation structure, an updated designation title on the employee’s Infosys profile, and a shift in the role expectations and authority level associated with the new band. It is distinct from an increment (which is a salary increase within the current band without a designation change) and from a title change without band movement (which does not constitute a promotion in the compensation or authority sense).

The promotion process at Infosys is governed by three gates: performance rating (the employee must have achieved a minimum rating threshold), time-in-band eligibility (each band has a minimum tenure requirement before promotion is eligible), and headcount availability (the target band must have an open slot in the relevant business unit or practice). All three gates must be open simultaneously for a promotion to happen. This is why promotion timelines at Infosys are probabilistic rather than certain, and why two employees with identical performance ratings can have different promotion timing based solely on the headcount availability in their respective units.

The Appraisal Process: How Infosys Measures Performance

The performance appraisal process is the central mechanism through which Infosys determines who gets promoted, who gets high increments, who gets placed on high-visibility projects, and who receives the leadership development investment that accelerates senior career growth. Understanding how this process actually works - not just the official description but the lived mechanics - is the foundation of strategic career management at Infosys.

The appraisal cycle. The Infosys financial year runs April to March. The annual appraisal cycle for performance rating assignment concludes in the first quarter of the new financial year, with revised salaries typically effective from April or July depending on the band and business unit. The increment and promotion letters are communicated to employees after the final rating is assigned.

The self-assessment phase. The appraisal process begins with the employee completing a self-assessment in Infosys’s performance management system. The self-assessment captures: the goals set at the beginning of the performance year (typically in a goal-setting session with the manager in April or May), the employee’s self-rating against each goal, a narrative of achievements and contributions, and a reflection on developmental areas and progress on previous improvement targets.

The self-assessment is the employee’s primary advocacy document in the appraisal process. A vague, underselling self-assessment (“completed assigned tasks, supported team”) leaves the manager with insufficient material to advocate effectively during calibration. A specific, impact-quantified self-assessment (“led the migration of four microservices to AWS Lambda, reducing API response latency by 35 percent with zero production incidents; mentored two junior engineers who subsequently passed their cloud practitioner certification”) gives the manager concrete, credible content to argue for a higher rating at the calibration table.

The most common self-assessment mistake at every level is confusing activity with impact. Describing what was done (activities) rather than what changed because of it (impact) undersells the contribution. Every achievement in the self-assessment should be expressed as: the context, the action taken, and the measurable result. This structure makes the contribution visible and defensible during calibration.

The manager review phase. After the self-assessment is submitted, the manager reviews it, compares it against their own observations of the employee’s performance over the year, and forms a preliminary rating recommendation. The manager’s assessment of the employee is influenced by: day-to-day observation of delivery quality, feedback from project leads and client counterparts (where applicable), the employee’s contribution to team capability (mentoring, knowledge sharing, code review quality), and the employee’s professional conduct and communication effectiveness. Managers who manage large teams often have more limited direct observation of each individual employee’s work, which makes the self-assessment’s clarity and the employee’s visibility throughout the year (through progress updates, shared accomplishments, and proactive communication with the manager) disproportionately important.

The calibration session. The calibration session is the most consequential and least visible part of the appraisal process. In calibration, all managers in a business unit present their team members’ preliminary rating recommendations to a calibration panel, which typically includes the business unit head, HR business partners, and senior managers. The calibration panel enforces a forced distribution: only a defined percentage of employees can receive the top rating category, a defined percentage can receive the second category, and so on.

The forced distribution means that individual performance is rated not in isolation but relative to peers in the same calibration pool. An employee who would receive a top rating in a pool of weaker performers may receive a middle rating in a pool of exceptionally strong performers. Conversely, a strong performer in a pool of weaker peers may receive a rating that does not reflect their absolute capability so much as their relative standing.

The practical implication is that the rating reflects both absolute performance and the composition of the calibration pool. Employees on high-visibility, high-performing accounts are in calibration pools where the competition for top ratings is intense. Employees on lower-visibility accounts may find it easier to stand out within their pool. Neither situation is inherently advantageous in isolation; the rating must be paired with the visibility and business impact that influences future project allocation and leadership development investment.

The rating communication. After calibration, each employee receives their final rating through the Infosys HR system, typically accompanied by a discussion with the manager. The rating is final once communicated; the formal rating dispute mechanism exists but is rarely successful in changing the outcome. Employees who believe their rating was inaccurate should use the communication with the manager to understand the specific basis for the rating and to identify what, concretely, would need to be demonstrated differently in the next performance year to achieve a higher rating. This conversation, done constructively, is more career-useful than a grievance about the current rating.

The goal-setting investment. The appraisal cycle is only as useful as the goals set at its beginning. Employees who set vague, easily fulfilled goals at the start of the performance year create a ceiling on the appraisal’s ability to reflect exceptional performance - if all goals are met easily, the self-assessment cannot credibly argue for an “Outstanding” rating. Employees who set ambitious but achievable goals, tied to specific business outcomes, create the headroom in the self-assessment to demonstrate genuine over-performance.

Goal-setting should be done as a genuine collaborative conversation with the manager rather than as a formality. The goals that resonate most with calibration panels are those that are tied to business outcomes the business unit leadership cares about: client satisfaction improvement, account revenue growth, team capability building that reduces delivery risk, and technical innovation that differentiates the account’s offering. Goals framed in these terms are more impactful in the appraisal than goals framed in purely internal delivery metrics.

Building visibility through the year: The performance narrative. The calibration panel evaluates rating recommendations in a compressed period and relies heavily on the manager’s presentation. The manager’s presentation is based on their recollection of the employee’s contributions over the year, supplemented by the self-assessment. An employee who makes their contributions consistently visible to the manager throughout the year - through brief monthly updates, highlight communications when significant achievements occur, and proactive sharing of client or peer feedback - is significantly easier for the manager to advocate for than one who delivers equally well but silently.

The monthly update does not need to be a formal document. A brief message to the manager noting a completed milestone, a client’s positive comment on the team’s work, or a successful knowledge transfer session is sufficient. Accumulated over 12 months, these touchpoints become the evidence base that the manager draws on during the calibration presentation. Employees who provide this ongoing visibility take an active role in shaping the performance narrative rather than leaving it entirely to the manager’s recollection.

Building the Career Case at Each Level

Beyond the formal appraisal process, successful career progression at Infosys requires deliberate investment in the career case - the accumulated evidence across multiple dimensions that makes the promotion recommendation compelling to the calibration panel and the business unit leadership.

The promotion readiness conversation. One of the most underutilised career tools at Infosys is the direct conversation with the manager about promotion readiness. Many employees assume that strong performance will automatically translate into promotion advocacy; many managers assume that employees who are ready to discuss promotion will bring it up directly. This mutual assumption creates a gap where neither party initiates the conversation, and the promotion case is never formally constructed.

Employees who want to accelerate their promotion should have an explicit conversation with their manager approximately 12 months before they estimate they will be eligible, asking: “What specific evidence would you need to see from me over the next 12 months to advocate for my promotion to [next designation] in the next appraisal cycle?” This question transforms the promotion from a vague aspiration into a specific, actionable development plan. The manager’s answer tells the employee exactly what to work on, and it commits the manager to the conversation in a way that creates mutual accountability.

The peer and stakeholder reputation. The calibration panel does not know most of the employees being discussed from direct interaction. They know them through the manager’s presentation, which is influenced by the manager’s own reputation and the reputation they describe. Where the manager can supplement the rating recommendation with specific stakeholder feedback - a client executive’s testimonial about the employee’s contribution, a peer architect’s assessment of the technical design quality, a project manager’s comment on the delivery leadership - the recommendation becomes more multi-dimensional and harder to challenge.

Building a positive reputation with a specific set of stakeholders - the client counterpart, the senior architect on the account, the HR business partner - is a deliberate investment that yields specific, citable evidence in the appraisal. Employees who are universally pleasant but distinctively memorable to no particular stakeholder have a less compelling promotion case than those who have made a specific, named impression on two or three relevant stakeholders.

The business unit leadership relationship. At the TA level and above, having a relationship with the business unit head or the practice leader (not just the direct manager) significantly improves the promotion outcome in competitive calibration situations. These senior leaders are on the calibration panel and their independent knowledge of the employee’s contribution - even if brief - adds weight to the manager’s advocacy. Building this relationship requires intentional effort: participating in practice-level initiatives, contributing to business unit knowledge sessions, seeking opportunities to present work or insights to senior leadership forums, and ensuring that any significant client or delivery achievement is communicated upward through appropriate channels.

Infosys’s performance rating system uses a categorised scale (rather than a numerical score) that places each employee in one of a small number of performance bands. The specific labels for these bands have evolved over the organisation’s history, but the functional structure is consistent.

The rating categories. The standard Infosys performance rating distribution includes five categories, commonly described as:

  • Outstanding (or Exceptional): The top performance category. Awarded to employees who have significantly exceeded their goals, created substantial business impact, demonstrated leadership beyond their role level, and are identified as high-potential talent. The forced distribution limits this to a small percentage of the eligible population, typically in the range of 5 to 15 percent.

  • Excellent (or High Performer): The second performance category. Awarded to employees who have exceeded their goals in meaningful ways, demonstrated strong delivery quality, and contributed to team and unit capability beyond their individual delivery. This category typically covers 20 to 30 percent of the eligible population.

  • Meets Expectations (or Performer): The baseline performance category. Awarded to employees who have met their committed goals, delivered reliably, and met the conduct and competency expectations of their current role. The majority of employees receive this rating in most business units, typically covering 40 to 60 percent of the population.

  • Partially Meets Expectations (or Development Required): Below-baseline performance. Awarded to employees who have fallen short of their goals in some meaningful dimension - either in delivery quality, quantity, or professional conduct. Employees in this category typically receive performance improvement support and close monitoring in the subsequent performance year.

  • Does Not Meet Expectations: The lowest performance category. Awarded to employees with significant underperformance. Sustained performance at this level triggers formal performance management processes that can include employment action.

How the rating affects promotions. For a promotion to be initiated, the employee must typically hold a minimum rating of “Meets Expectations” for the current year, and in many promotion cases, must have at least one “Excellent” or “Outstanding” rating in the preceding two performance years. The precise requirement varies by band level (the bar rises with seniority) and by business unit policy.

An “Outstanding” rating significantly accelerates promotion eligibility by satisfying the performance criterion strongly and by generating advocacy from the manager and business unit leadership during promotion discussions. A “Meets Expectations” rating satisfies the minimum criterion but does not generate active advocacy - the promotion depends primarily on the time-in-band eligibility and headcount availability rather than managerial push.

How the rating affects increments. The increment percentage is directly determined by the rating category, applied according to a grid that varies annually (based on company performance and industry benchmarks). Broadly, “Outstanding” earns the top increment percentage range (typically 12 to 20 percent of fixed pay), “Excellent” earns the second range (8 to 12 percent), “Meets Expectations” earns the middle range (4 to 8 percent), and below-baseline categories earn minimal or zero increments.

The multi-year rating trajectory. A single year’s rating is less determinative than the trajectory over multiple years. An employee who receives “Meets Expectations” for three consecutive years is in a very different position than one who received “Outstanding,” “Excellent,” and then “Meets Expectations” - even if the most recent year is identical. The rating trajectory influences how managers advocate for their reports, how HR business partners classify them in the talent pipeline, and how senior leaders assess them for stretch assignments or leadership development programmes. Managing the multi-year trajectory intentionally - understanding that a below-expectations year creates a recovery burden that requires two years of strong performance to genuinely overcome - is a dimension of career management that many employees discover only after experiencing the setback.

Systems Engineer: The Foundation Level

The Systems Engineer designation is the standard entry point for engineering freshers joining through campus placement, off-campus application, or the InfyTQ pathway. It is the foundation level of the career ladder, and what happens in this band sets the trajectory for everything that follows.

Time in band: Typical and accelerated. The standard time spent at the Systems Engineer level before promotion to Senior Systems Engineer is two to three years for an employee with consistent “Meets Expectations” ratings. Top performers who achieve “Excellent” or “Outstanding” ratings in their first one to two years can be promoted in as little as 18 to 24 months. Employees with “Partially Meets” ratings may remain in the SE band for three to four years or longer.

What is being evaluated at the SE level. The SE performance evaluation focuses on: technical foundation (can the employee write working code, debug effectively, and understand the system they are working on?), delivery reliability (does the employee complete assigned tasks within committed timelines with acceptable quality?), learning agility (is the employee progressing through Infosys’s mandatory training and certification requirements?), and communication (can the employee clearly communicate status, blockers, and questions to the project team?).

At the SE level, the evaluation is fundamentally about reliability and growth trajectory. Infosys is not expecting an SE to independently design systems or manage client relationships. It is expecting the SE to be a dependable contributor who learns quickly and demonstrates the foundation for the next level’s responsibilities. The most common SE-level performance gap is not technical - it is communication. SEs who do not proactively update their team lead on blockers, who do not ask for help when stuck, or who do not document their work clearly create delivery risk that is observed and noted by managers even when the eventual code quality is acceptable.

Accelerating growth at the SE level. The SE who wants to reach SSE at 18 months rather than 30 months should focus on: achieving at least one meaningful technical certification (cloud practitioner level, database associate, or a platform-specific certification aligned with the project stack) within the first year; volunteering for ownership of a specific module or component within the project beyond the assigned tasks; and building visibility with the manager through regular, specific updates on work progress and through demonstrating initiative on team-benefit activities (documentation, knowledge sessions, code review participation).

The Mysore foundation and its relevance. The technical foundation from the Mysore training is genuinely relevant in the first project. Java competence, SQL ability, and Git fluency are expected to be functional from day one of project deployment. SEs who supplemented their Mysore learning with independent practice in the specific technology stack of their allocated project adapt faster to the project environment and are given more complex responsibilities sooner. The first 90 days on a project are the evaluation window where the manager forms the impression that will shape the first appraisal cycle - investing in preparation for this window specifically is among the highest-return early career activities.

Senior Systems Engineer: The First Promotion

The Senior Systems Engineer designation is the first promotion within the Infosys career ladder, and it marks a meaningful shift in the expectation level even though the day-to-day work may not change dramatically in the first weeks after promotion.

Time in band: Typical and accelerated. The standard time at SSE before promotion to Technology Analyst is two to three years for consistent performers. Accelerated performers with sustained “Excellent” or “Outstanding” ratings can reach TA in 18 to 24 months from SSE, meaning they are at TA just three to five years from joining as SE. Average performers may spend three to four years at SSE.

What changes at SSE. The SSE is expected to operate with greater independence than the SE. Rather than receiving task-level instructions, the SSE receives story-level or feature-level requirements and is expected to decompose them into tasks independently, raise architectural or design concerns where the requirements are ambiguous, and manage the delivery of the feature with limited supervision. The SSE also begins to take on informal mentoring responsibilities for SE-level team members: reviewing code, answering technical questions, and helping newer joiners navigate the project context.

Skills and competencies evaluated for SSE promotion. At the SSE level, the promotion evaluation focuses on: independent delivery capability (has the SSE consistently delivered features of moderate complexity without close supervision?), technical depth progression (has the SSE developed genuine expertise in the project’s primary technology stack, beyond surface-level familiarity?), collaborative contribution (has the SSE contributed to team quality through code reviews, knowledge sharing, and peer mentoring?), and communication maturity (can the SSE communicate technical concepts to non-technical stakeholders in client-adjacent roles?).

The certification landscape at SSE. By the SSE level, having at least one relevant technical certification is effectively table stakes for promotion. The specific certification should align with the technology stack of the current project or the desired stream for future projects. AWS Solutions Architect Associate, Azure Developer Associate, GCP Associate Cloud Engineer, Oracle Certified Associate (for Java), and database-specific certifications are the most commonly valued. A certification achieved and relevant to delivery is worth more in the appraisal context than a generic certification pursued purely for resume padding.

Salary at SSE. The SSE salary range typically spans 5.5 to 8.5 lakhs CTC, reflecting the increment from SE’s 3.6 to 4.65 lakh starting CTC. The promotion itself often coincides with a larger-than-typical annual increment - the promotion increment at Infosys involves a band adjustment that can represent a 30 to 60 percent increase in total CTC depending on the individual’s specific position within the SE band at the time of promotion.

Technology Analyst: The Mid-Level Transition

The Technology Analyst designation is the first genuinely mid-level band and the point at which the career begins to differentiate meaningfully between those who will progress to technical leadership and those who will plateau in a comfortable but limited individual contributor role. The TA transition is the most consequential designation change in the early-to-mid career.

Time in band: Typical and accelerated. The standard time at TA before promotion to Senior Technology Analyst is two to three years. Top performers who have been on high-visibility accounts, have achieved meaningful certifications, and have begun taking on informal technical leadership responsibilities can reach STA in two years. Average performers may spend three to four years at TA.

What changes at TA. The Technology Analyst is expected to own technical components, not just features. This means taking responsibility for the architectural decisions within a bounded scope, representing the technical approach of that component in team discussions, interfacing with senior architects and delivery leads on design questions, and providing technical guidance to SSE and SE team members working within the same component. The TA is the technical point of contact for a specific domain within the project, even if they do not carry a formal technical lead title.

Skills and competencies for TA promotion. Moving from SSE to TA requires demonstrating: technical ownership (has the employee operated as the go-to technical resource for a specific domain on the project?), architectural thinking (can the employee discuss design decisions at the system level, not just the function level?), stakeholder communication (has the employee communicated directly with client counterparts or business analysts in a technically credible way?), and team capability building (has the employee actively contributed to team upskilling through knowledge sessions, documentation, or formal mentoring?).

The hidden gate at TA promotion. The TA promotion is where the headcount availability gate becomes most visible and most frustrating for employees who are technically ready. In a business unit with limited high-complexity delivery, the TA band headcount may be constrained because there are fewer positions that genuinely require TA-level ownership than there are SSE-level employees ready for promotion. Employees in this situation have three options: wait within the current account while demonstrating readiness (relying on the manager’s advocacy), pursue an internal job posting to a different account where TA-level headcount is available, or consider whether the external market can provide the next designation without the headcount constraint.

Income at TA. The TA salary range is 9 to 14 lakhs CTC. The SSE-to-TA promotion typically represents a 25 to 50 percent CTC increase depending on the employee’s specific SSE salary at the time of promotion. The TA band is also where variable pay begins to be a meaningfully larger proportion of the total package, with variable targets in the range of 10 to 12 percent of CTC.

Senior Technology Analyst: Technical Credibility Established

The Senior Technology Analyst designation is the level at which technical credibility is expected to be fully established. An STA is considered an experienced professional who can be trusted to handle the technical dimensions of a workstream independently, mentor others systematically, and begin contributing to pre-sales or proposal activities where technical expertise shapes client engagements.

Time in band: Typical and accelerated. The standard time at STA before promotion to Technical Lead or Technology Lead is two to three years. Top performers in high-demand skill areas can move faster, particularly if they are leading significant technical initiatives and have developed a visible external profile (certifications, published articles, conference presentations) that strengthens the internal promotion case.

What changes at STA. The STA operates at the level of a workstream technical owner rather than a component owner. In an agile delivery context, the STA might be responsible for the technical approach of an entire squad or feature team, making architectural decisions, reviewing all major technical changes, and serving as the technical escalation point for the team. In a more traditional delivery model, the STA might lead a team of five to ten engineers across a defined scope of the project.

The STA is also expected to contribute beyond the current project: participating in internal communities of practice, contributing to Infosys’s knowledge management repositories, supporting pre-sales technical proposals, and potentially contributing to Infosys Springboard content or similar internal enablement activities.

Certifications at the STA level. At STA, a portfolio of certifications is expected rather than a single credential. This portfolio should demonstrate: depth in the primary technology stack (a professional or expert level certification, not just associate level), breadth across adjacent areas relevant to the project and market (cloud architecture, DevOps, security, or domain-specific credentials), and commitment to ongoing learning as the technology landscape evolves. Employees without a meaningful certification portfolio at the STA level face a visible gap when their promotion case is presented to the calibration panel, where STA-to-TL promotion is a competitive selection process.

Salary at STA. The STA salary range is 14 to 20 lakhs CTC, with variable pay targets in the range of 12 to 15 percent. The TA-to-STA promotion represents a 20 to 40 percent CTC increase and begins to push employees into the income range where tax planning through a thoughtful old-versus-new regime analysis and maximisation of available deductions becomes a meaningful financial management activity.

Technical Lead and Technology Lead: The Leadership Gate

The Technical Lead (TL) and Technology Lead (TEL) designations together represent what is commonly called the leadership gate in the Infosys career progression - the band where the individual contributor model gives way to a delivery leadership model, and where the skills required for further advancement shift significantly from technical depth to influence, accountability, and people leadership.

The distinction between TL and TEL. The Technical Lead (TL) and Technology Lead (TEL) represent adjacent but distinct bands. The TL is the first formal leadership designation, typically leading a team of five to fifteen engineers in a defined technical domain. The TEL is the senior form of this, leading larger teams, managing more senior engineers (including TL-level team members), and carrying programme-level technical accountability. Both are within the broad “Technology Lead” tier but represent different seniority levels within it.

Time in band: TL and TEL. The standard time at TL before promotion to TEL is two to three years. Time at TEL before promotion to Delivery Manager is typically two to four years. Top performers with strong client relationships, demonstrated programme delivery, and visible leadership of significant business impact can move faster. Average performers may spend four or more years at each level.

What changes at TL. The Technology Lead carries formal people management responsibilities in many (though not all) TL roles. This includes: managing the team’s technical direction, conducting one-on-one discussions with direct reports, providing performance inputs for their appraisals, resolving technical conflicts within the team, interfacing with the Delivery Manager on project status and technical risk, and representing the team’s technical capabilities to clients in relevant discussions.

The TL is also the first level at which client relationship ownership begins. A TL often has named client counterparts - client developers, architects, or technical project managers - with whom they maintain regular working relationships. The quality of these relationships influences account health scores, which feed into the TL’s own appraisal.

Skills and competencies for TL promotion. The STA-to-TL promotion evaluation is among the most competitive in the entire hierarchy because it is the gate between individual contributor and leadership tracks. The evaluation focuses on: people leadership evidence (has the employee formally or informally led and developed a team?), delivery accountability (has the employee owned a delivery commitment and managed the execution risk associated with it?), client relationship quality (has the employee developed trusted relationships with client technical counterparts?), technical breadth (has the employee expanded from deep expertise in one area to working knowledge of the broader technology and architecture landscape?), and business development contribution (has the employee contributed to account growth, proposal writing, or new business conversations?).

The last criterion - business development contribution - is one that surprises many STA-level employees who are focused purely on delivery. At the TL level and above, the expectation is that technical leaders contribute to Infosys’s commercial outcomes, not just the technical quality of existing engagements. This might mean supporting the pre-sales process for new work at an existing client, contributing technical sections of a proposal document, or participating in demonstrations or proof-of-concept development to win new business. Employees who have never engaged with this dimension of the business before the TL promotion evaluation are at a disadvantage compared to those who have sought opportunities to contribute to pre-sales activities as an STA.

Salary at TL and TEL. The TL salary range is 18 to 28 lakhs CTC. The TEL range extends to 25 to 40 lakhs. The STA-to-TL promotion typically represents a 20 to 35 percent CTC increase. Variable pay as a proportion rises to 15 to 20 percent at TL, making the actual payout in high-performance years significantly higher than the base package suggests.

People management at TL: The learning curve. For employees who have been purely technical contributors up to the TL level, the people management responsibilities of the role represent a genuine learning curve. The transition from being responsible for one’s own code to being responsible for the output of a team requires new skills: giving developmental feedback that is specific and actionable, managing team members who have different working styles and capability levels, navigating performance issues with HR support, and motivating a team through challenging delivery periods. Infosys provides some management development training for newly promoted TLs, but the bulk of this learning is on the job. TLs who invest in management skill development - through formal programmes, reading, mentorship from senior leaders, and deliberate reflection on their management interactions - build the capability that differentiates the TLs who progress to TEL from those who plateau.

Delivery Manager: Entering Senior Leadership

The Delivery Manager designation is the first genuinely senior leadership level in Infosys’s hierarchy, and the transition from TEL to DM represents one of the most significant role transformations in the entire career progression. At the DM level, the primary identity shifts from technical leader to business leader.

Time in band: DM. The standard time at DM before promotion to Senior DM or AVP is three to five years. The DM level is also the first at which the career progression timeline becomes significantly less predictable, because the promotions above DM depend heavily on business context (account growth, new engagement wins, strategic positioning) in addition to individual performance.

What changes at DM. The Delivery Manager owns a client account or a significant portfolio of engagements from an operational and relationship perspective. Their responsibilities include: managing the overall project delivery health (timeline, budget, scope, quality), maintaining the client relationship at the senior stakeholder level, managing the performance and career development of all team members across the account, driving account growth through identification of expansion opportunities, managing escalations and resolving them before they reach crisis level, and ensuring the account contributes positively to Infosys’s financial metrics (margin, revenue, utilisation).

The DM is evaluated on financial metrics in a way that lower levels are not. The account’s margin contribution, revenue run rate, and growth trajectory are visible to the DM’s manager (typically an AVP or VP) and are direct inputs to the DM’s performance evaluation. A DM whose account underperforms financially for reasons within their control faces significant appraisal consequences regardless of client satisfaction scores.

Skills for DM promotion. The TEL-to-DM promotion gate is the most selective in the hierarchy. The evaluation includes: commercial acumen (demonstrated understanding of project economics, margin management, and account growth dynamics), senior stakeholder management (has the employee built and maintained relationships with client decision-makers at the VP or C-suite level?), strategic delivery planning (has the employee managed multi-year programme roadmaps, not just sprint-level delivery?), people development at scale (has the employee built and developed a team of 20 or more engineers across multiple specialisations?), and executive presence (can the employee represent Infosys credibly in senior client and internal executive conversations?).

Salary at DM. The DM salary range is approximately 35 to 70 lakhs CTC, with variable pay constituting 25 to 35 percent of the total package. At this level, the variable payout in a high-performing year can represent a very significant cash event (potentially 10 to 20 lakhs in a single variable tranche), making the DM-level compensation significantly more variable than lower levels.

Senior Delivery Manager, AVP, and VP: The Executive Tier

The Senior Delivery Manager, Associate Vice President, and Vice President designations represent the executive tier of Infosys’s employee hierarchy, though it is important to note that the Infosys executive leadership (C-suite) is a separate tier entirely.

Senior Delivery Manager. The SDM leads a portfolio of accounts or a large, complex single account. The SDM is responsible for strategic client relationship management at the CXO level, portfolio-level revenue and margin management, talent strategy for a practice area or geography, and contribution to Infosys’s positioning in specific industry verticals or technology practices. The SDM’s compensation is in the range of 60 to 1 lakh+ CTC (annualised), with variable pay constituting 30 to 40 percent.

Associate Vice President. The AVP is a senior leadership role responsible for a business segment, a practice vertical, or a geographic delivery operation. The AVP leads multiple DMs and SDMs, manages a large revenue portfolio (typically several hundred crores in annual revenue), and represents Infosys to clients at the strategic partnership level. AVP appointments are selective and are often tied to specific business circumstances: a major account win requiring new leadership structure, an expansion into a new market vertical, or a strategic talent retention situation.

Vice President and above. The Vice President level involves executive accountability for a significant business unit. VP roles are scarce (the number of VPs in any large organisation is a small fraction of the total employee base) and are filled through a combination of internal development and external lateral hiring at specific skill requirements. The compensation at VP level often includes equity components (RSUs or ESOPs) in addition to the fixed and variable pay structure of lower levels.

The path to AVP and VP. The realistic path to AVP from a Systems Engineer entry begins with consistent top-performance execution through the ladder, typically taking 15 to 22 years for the most successful internal career trajectories. This timeline is reduced for employees who combine internal progression with strategic onsite experience, lateral moves that build broader business exposure, and consistent delivery of commercially significant outcomes. The VP level from SE entry is a 20-to-30-year journey for those who reach it through purely internal progression.

Candidates who assess the Infosys career path against this timeline and find it does not match their ambitions typically pursue lateral moves to other organisations at the DM or early AVP equivalent level, where the external market offers roles with faster leadership exposure. This is a rational choice, and the career capital built through Infosys’s progression system is directly transferable to these external opportunities.

The Technical vs Managerial Track Decision

The decision between the technical specialist track and the delivery management track is one of the most consequential career decisions an Infosys employee makes, typically between the TA and STA levels when the differentiation begins to become meaningful.

The technical track at Infosys. The technical track within Infosys leads to designations such as Technology Architect, Senior Architect, Principal Architect, and Distinguished Engineer in some practice areas. These roles are evaluated primarily on technical thought leadership, architectural contribution to complex client programmes, publication and community contribution (conference presentations, Infosys knowledge repositories, patent filing), and the depth of domain expertise that makes the individual indispensable for specific categories of client problems.

The technical track’s compensation progression is not identical to the management track. At the Technology Architect level (roughly equivalent to the TEL-to-DM range of the management track), the compensation is broadly comparable. Above this level, the management track’s financial ceiling (particularly the variable pay and equity components at DM and above) often exceeds the technical track’s ceiling for employees who are not among the very top technical specialists in the organisation.

The management track at Infosys. The management track leads from TL through TEL, DM, SDM, AVP, and VP. It is evaluated on delivery outcomes, client relationships, account commercial performance, and people leadership. The management track’s ceiling is higher (the most senior delivery and account management roles carry very significant total compensation), but the progression is highly dependent on business context and is less within the individual’s control than the technical track, which rewards demonstrated expertise more directly.

How to choose. The choice should be based on honest self-assessment of motivation and strength. Employees who are genuinely energised by technical problem-solving, who enjoy the depth of mastering complex systems, and who find people management energy-draining rather than fulfilling are likely to be more effective and satisfied on the technical track. Employees who are energised by the complexity of managing delivery at scale, who enjoy developing teams and relationships, and who find technical depth engaging but not all-consuming are likely to be more effective and satisfied on the management track.

The worst choice is to pursue the management track purely for compensation reasons while having a fundamentally technical orientation. People management requires genuine investment and capability; a technical expert who manages people reluctantly produces poor team outcomes that surface in appraisal results even when the individual’s technical contribution is strong.

The hybrid path. Some Infosys employees navigate a hybrid path where they carry technical architect responsibilities within a delivery leadership role - effectively operating as a delivery lead with deep technical credibility in a specific domain. This hybrid path is available in practice areas where technical depth and delivery leadership are both valued, and it produces some of Infosys’s most effective senior professionals. However, it is demanding because it requires genuine capability on both dimensions simultaneously, and the time demands of deep technical work and effective people leadership are both substantial.

The technical track ceiling and its realities. The honest assessment of the technical track’s career ceiling in an IT services organisation like Infosys must acknowledge a structural reality: the highest compensation and most senior designations in any services delivery organisation are on the management track, because the management track is directly tied to revenue generation, account growth, and client retention - the commercial engines of the business. The most distinguished individual technical contributors can reach comparable compensation to DM-level delivery managers, but the TEL and above level on the management track generally outpaces the technical track in both compensation and organisational authority.

This reality is not an argument against the technical track - it is an argument for choosing the track based on genuine motivation and strength rather than financial ceiling optimisation. Technical specialists who are doing work they find intrinsically meaningful, who are well-compensated (even if not at the absolute ceiling of the organisation), and who have career stability based on rare and valuable expertise have excellent careers by any reasonable measure. The comparison to the management track’s ceiling is only relevant if the individual’s primary aspiration is organisational authority and maximum compensation, which is not a universal career goal.

Making the track decision at the right time. The practical advice for employees at the TA to STA transition - where the track decision begins to matter - is to make the decision based on an honest assessment of what they genuinely find energising after two to three years of project experience. Three years of actual work is enough evidence to determine whether the technical problem-solving or the team and client leadership dimensions of the role are the ones that produce genuine engagement. Employees who have not had enough project exposure to make this assessment clearly at the TA level should seek project experiences that expose them to both dimensions - taking on a team lead role on a stream while also doing deep technical work on a complex problem - before committing to a direction.

Certifications occupy a specific and practical role in Infosys’s promotion ecosystem that is different from their role in the broader job market. Understanding this specific role avoids both overestimating and underestimating their value in the internal career system.

Certifications as a mandatory baseline. Infosys has mandatory certification requirements at different band levels, tracked through the learning management system. These mandatory certifications are not optional - they are requirements that must be fulfilled before a promotion can be formally processed. An employee who is otherwise eligible for promotion (performance rating, time in band, headcount) but has not completed mandatory certifications will find the promotion delayed until the certification gap is addressed. Maintaining currency with mandatory certification requirements is therefore a career management basic, not an exceptional achievement.

Certifications as a promotion differentiator. Beyond the mandatory baseline, voluntary certifications in high-demand technology areas function as differentiation signals in competitive promotion situations. When a calibration panel is evaluating two STA-level employees for a single TL headcount, the one with an AWS Solutions Architect Professional certification (vs an Associate certification) and a Kubernetes Administrator certification is more likely to win the case than the one with only the mandatory baseline. The certification signals not just the skill but the investment in skill development and the commercial relevance of the capability.

Which certifications matter most. The certifications that carry the most weight in Infosys’s promotion calculus are those aligned with areas of active business demand. Cloud certifications (AWS, Azure, GCP) at the Professional or Expert level are universally valued because Infosys’s cloud practice is one of its fastest-growing revenue streams. Kubernetes and DevOps certifications (CKA, CKS, HashiCorp certifications) are valued in delivery-engineering-oriented roles. SAP certifications matter significantly for the SAP practice. Domain-specific certifications (TOGAF for architects, PMP for delivery managers, financial domain certifications for BFSI practice) matter within their respective contexts.

Certifications that are widely held and do not represent meaningful differentiation - entry-level cloud practitioner certifications, foundation-level certifications that all employees are required to hold - add less value to the promotion case at mid and senior levels because they are baseline rather than differentiating credentials.

The certification-to-project alignment principle. A certification that is directly relevant to the current project or the next target role is worth more in the promotion context than a certification in an unrelated area, regardless of how prestigious the latter might seem in the broader market. A Technology Analyst on a Java microservices project who achieves an AWS Developer Associate certification is building directly relevant capability. The same TA who achieves a Salesforce Administrator certification (unrelated to the current project or the next targeted role) has added a credential that does not strengthen the promotion case for the next band.

Infosys-sponsored certifications vs self-funded. Infosys provides certification funding and study support for designated certifications through its learning platform and certification assistance programme. Employees who proactively pursue certifications within this support structure are simultaneously building skills and demonstrating the learning initiative that appraisals reward. Self-funded certifications in areas outside the sponsored programme are also recognized and respected, but the sponsored programme is the most efficient path for certifications that are clearly aligned with Infosys’s priority technology areas.

Internal Job Postings (IJP): How the System Works

The Internal Job Posting system is one of the most underutilised career management tools available to Infosys employees. Understanding how it works, when to use it, and what its limitations are can materially accelerate the career trajectory for employees who approach it strategically.

What IJP is. The Internal Job Posting system is Infosys’s formal mechanism for posting open positions across the organisation and inviting internal employees to apply. Positions are posted on the internal career portal and include the designation level, the required skills and experience, the project and business unit context, and the application process. Any employee who meets the eligibility criteria can apply.

Eligibility to apply via IJP. The standard IJP eligibility requires: a minimum of one year of service in the current project (sometimes 18 months for senior-level positions), a minimum performance rating of “Meets Expectations” in the most recent appraisal, and no active performance improvement plan. Some IJP postings have additional eligibility criteria specific to the role (particular technology certifications, prior experience in a specific domain).

When IJP is most valuable. IJP is most valuable in two specific situations:

The first is when the current project has a headcount constraint that is blocking a promotion the employee is otherwise ready for. Moving to a different account via IJP where the target designation has an open slot can unlock a promotion that would have taken another year to materialise in the current context.

The second is when the current project’s technology or domain is not aligned with the employee’s career direction, and a lateral move via IJP to a more relevant context is needed before the promotion case can be built on the right foundation. A Technology Analyst on a legacy infrastructure project who wants a career in cloud architecture cannot build the cloud architecture portfolio needed for senior promotion without moving to a cloud-focused project. IJP is the formal mechanism for making this move.

The IJP process in practice. Applying via IJP is initiated through the internal career portal. After the application is submitted, the hiring manager of the IJP role reviews the application, and if the candidate appears promising, they proceed to a brief technical or fit discussion (often a 30 to 60 minute conversation with the hiring manager or a technical panel). If selected, the formal IJP transfer is processed through HR, which requires the releasing manager’s agreement.

The releasing manager dynamic. The releasing manager’s agreement to the IJP transfer is formally required but is supposed to be a formality - Infosys’s policy does not allow releasing managers to block IJP transfers that are otherwise process-compliant. In practice, a releasing manager who strongly wants to retain the employee may delay the release, negotiate the timeline, or make the process uncomfortable. Employees who anticipate this dynamic should communicate the IJP application to their manager as a professional decision rather than a surprise, maintain the relationship constructively during the transition period, and use HR as the mediator if the release is being unreasonably delayed.

IJP vs external application. Some employees use an external offer as leverage for an internal move or salary adjustment rather than going through the IJP process. This approach can produce faster results in retention-motivated situations, but it carries relationship risk with the manager and the business unit and creates a perception of the employee as a retention risk that persists beyond the immediate situation. The IJP process, slower as it may feel, is the more career-sustainable path for employees whose primary goal is a better-aligned internal opportunity rather than an exit.

Onsite Opportunities and Career Acceleration

Onsite deployment to client locations outside India is one of the most powerful career accelerators available to Infosys employees, and its impact on the promotion timeline and compensation trajectory is more significant than most employees realise before their first onsite experience.

What onsite means financially. An Infosys employee deployed onsite to a client location in the US, UK, Europe, or Australia receives their regular Indian base salary plus a per diem allowance in the local currency that covers accommodation, food, transportation, and daily living expenses. The per diem amount is calibrated to provide a comfortable standard of living in the respective country, which means the employee’s monthly Indian expenses virtually disappear (they are living and eating in the client’s country at company-provided rates) while the Indian salary continues to be paid and accumulate. For many employees, an 18-month to two-year onsite posting represents more wealth accumulation than the preceding three to four years of India-based employment combined.

What onsite means for career acceleration. Beyond the financial impact, onsite deployment significantly accelerates the career for three reasons:

First, client relationship depth. An employee working onsite at a client location develops direct, sustained relationships with client stakeholders that are simply not possible through remote delivery. These relationships produce CSAT (client satisfaction) feedback that is specific, credible, and influential in promotion cases. A promotion case that includes a specific testimonial from a client executive carries qualitative weight that a strong delivery metric alone does not.

Second, cross-functional exposure. Onsite employees see how the client organisation works from the inside - how decisions are made, what the business priorities driving the technology requirements are, and how Infosys’s work fits into the client’s strategic agenda. This exposure builds the business acumen and client context that is one of the most valued competencies at the TL level and above.

Third, visibility to senior Infosys stakeholders. Onsite delivery leaders (account managers, delivery leads) see the employee’s work directly and build an impression that is communicated back to the India-based delivery hierarchy. An employee who performs strongly onsite and develops positive visibility with the onsite account leadership has multiple advocates in the promotion discussion rather than just the direct manager.

Seeking and securing onsite opportunities. Onsite opportunities are not automatically distributed based on seniority or performance. They arise from project demand and are allocated based on a combination of skill alignment (does the employee have the specific skills the onsite role requires?), client preference (has the client specified any requirements for who they work with?), and internal availability (is the employee’s India-based work structured in a way that allows them to be released for an onsite period?).

Employees who want onsite exposure should communicate this aspiration explicitly to their manager and to the account delivery lead. Building the skills specifically relevant to the onsite context (client communication fluency, knowledge of the client’s industry domain, familiarity with the client’s technology environment) makes the case for the specific employee’s onsite deployment more compelling. Employees who wait passively for an onsite opportunity to appear are less likely to get one than those who have explicitly prepared and communicated their availability.

The onsite-promotion connection. Returning from a successful onsite stint is one of the strongest promotion triggers available in the Infosys system. An employee who has spent 18 months onsite at a major client, been directly responsible for a significant delivery outcome, developed senior client relationships, and returned with specific commercial impact on the account’s growth is a compelling promotion candidate at almost any level. The onsite experience accelerates the promotion case not by bypassing the evaluation criteria but by dramatically strengthening the evidence on multiple criteria simultaneously.

Top Performer vs Average Performer: Realistic Timeline Comparison

The timeline difference between a top performer and an average performer through the Infosys hierarchy is substantial, and understanding this difference in concrete terms helps candidates set realistic expectations for their own career planning.

The top performer trajectory. A top performer - defined as an employee who consistently achieves “Excellent” or “Outstanding” ratings, seeks and receives onsite exposure, builds a portfolio of high-demand certifications, and takes on increasing scope and leadership responsibility proactively - can expect the following approximate timeline:

SE to SSE: 18 to 24 months SSE to TA: 20 to 28 months TA to STA: 22 to 30 months STA to TL: 24 to 36 months TL to TEL: 24 to 36 months TEL to DM: 30 to 48 months

On this trajectory, a top performer could reach the Delivery Manager level in approximately 10 to 15 years from joining as a Systems Engineer. This is consistent with the fastest internal progression tracks seen in Infosys, and it requires sustained, deliberate performance at each level combined with the business context (account growth, favourable headcount availability) that makes each promotion feasible when the performance is ready.

The average performer trajectory. An average performer - defined as an employee who consistently achieves “Meets Expectations” ratings, delivers reliably but without the initiative and visibility that generates strong appraisal advocacy, and progresses through certifications at the minimum required pace - can expect:

SE to SSE: 28 to 36 months SSE to TA: 30 to 42 months TA to STA: 36 to 48 months STA to TL: 42 to 60 months TL to TEL: 42 to 60 months

On this trajectory, reaching the Technology Lead level takes approximately 15 to 20 years, and the Delivery Manager level may be approached in the 20 to 25 year range, if at all. Many average performers plateau at the Technology Lead level and have productive, reasonably compensated careers without reaching the Delivery Manager designation.

The variable that derails trajectories: a below-expectations year. The most common trajectory disruption is a single “Partially Meets Expectations” rating, which occurs more often than most employees anticipate - typically following a project challenge, a difficult manager relationship, or a personal life event that affected work performance. The recovery from a below-expectations rating requires two consecutive strong years to rebuild the rating trajectory and re-establish managerial advocacy. Employees who experience this disruption and treat the recovery year as a career investment (high engagement, visible contribution, active skill development) recover more fully than those who coast back to “Meets Expectations” without deliberate effort.

The impact of lateral moves. Employees who make lateral moves to other organisations and return to Infosys, or who make lateral moves at points where the Infosys system is constraining their progression, can reset the timeline in ways that pure internal progression cannot. A Technology Analyst who leaves Infosys and joins another organisation at the Senior TA or TL equivalent level, gaining three to four years of progressively senior experience, may return to Infosys (or to a comparable large IT services organisation) at the TL or TEL designation, effectively compressing the progression timeline by the period of external experience. This is a legitimate and commonly observed career strategy, and it does not carry the stigma within IT services hiring that it might in other industries.

The compounding benefit of early investment. The most important career management insight from the top-performer versus average-performer comparison is that the trajectory difference compounds early and is very difficult to reverse later. The employee who invests in certifications, visibility, and deliberate contribution in the first two years of the SE band gains a promotion at 20 months rather than 30, enters the SSE band with a higher base, and begins accumulating the next band’s increment on a larger CTC. Over a 15-year horizon, these compounding effects produce a total career earnings difference that is several times larger than the magnitude of the early investment required to create them. The most powerful career management action available to any employee at any level is to be genuinely excellent at the current level - not in a performative way, but through the deliberate investment that builds real capability and visible impact.

The salary jump at each promotion is a composite of two elements: the band adjustment (the shift from the current band’s salary range to the new band’s range) and the performance increment applied within the new band at the time of promotion. Together, these produce the total CTC change at promotion.

The general pattern. The band adjustment at each promotion typically represents a 20 to 40 percent increase in fixed pay, with the higher percentage applying to employees who were near the top of the current band (and therefore crossing into the new band’s lower range produces a larger relative jump) and the lower percentage applying to employees who were already at the bottom of the current band.

Promotion salary jumps by designation transition:

Promotion Typical CTC Before Typical CTC After Approximate Increase
SE to SSE 3.6 - 4.65 L 5.5 - 8.5 L 30 - 60%
SSE to TA 5.5 - 8.5 L 9 - 14 L 25 - 50%
TA to STA 9 - 14 L 14 - 20 L 20 - 40%
STA to TL 14 - 20 L 18 - 28 L 20 - 35%
TL to TEL 18 - 28 L 25 - 40 L 25 - 40%
TEL to DM 25 - 40 L 35 - 70 L+ 30 - 60%

The ranges are wide because individual circumstances vary significantly: the specific position within the band at the time of promotion, the employee’s performance rating history, the business unit’s compensation benchmarking against the market, and whether any off-cycle adjustment was made in the preceding period all affect the specific number.

Variable pay scaling with promotion. The variable pay component as a percentage of CTC increases with each promotion, which means the total compensation growth from promotion is larger than the fixed CTC increase suggests. An employee at STA with 12 percent variable who is promoted to TL with 18 percent variable has a larger total compensation increase than the fixed pay band change alone implies - the combination of a 25 percent fixed pay increase and a 50 percent increase in variable pay percentage produces a meaningfully larger total upside in a good performance year.

When promotions come without full band adjustment. Occasionally, promotions at Infosys include a designation change without the full band adjustment that would theoretically accompany it. This happens most commonly when the employee is already at the top of the current band’s range and the new band’s floor is close to the current salary, or when business unit compensation budget constraints limit the adjustment in a given period. Employees who receive a promotion with a smaller-than-expected salary increase should clarify whether an off-cycle adjustment is planned or whether the next annual increment will be applied to the new band’s scale. A promotion with minimal salary adjustment is still a career milestone, but understanding the compensation mechanics clearly prevents false expectations.

Frequently Asked Questions

1. How long does it typically take to become a Technology Lead at Infosys from joining as a Systems Engineer?

The timeline from Systems Engineer to Technology Lead (either TL or TEL designation) ranges from approximately 8 to 14 years depending on performance trajectory. A top performer who consistently receives “Excellent” or “Outstanding” ratings, takes on increasing responsibility, builds a strong certification portfolio, and has advantageous project and headcount contexts can reach the TL designation in 8 to 10 years. An average performer following the standard progression timeline reaches TL in 12 to 16 years. This is why the distinction between consistent top performance and average performance compounds so significantly over time.

2. Can I be promoted at Infosys without my manager’s support?

In theory, the promotion process is governed by performance criteria that are evaluated by the calibration panel, not solely by the manager. In practice, the manager’s advocacy during the calibration session is the most important single factor in whether an otherwise eligible employee is promoted in a given cycle. The manager presents the case, responds to questions from the panel, and their credibility with the calibration audience influences the outcome. An employee who has a poor relationship with their manager but a strong performance record should consider whether an internal job posting to a different account would provide a fairer promotion environment, rather than relying on a reluctant manager to advocate effectively.

3. How does the IJP process differ from being moved to a new project by Infosys?

An IJP application is employee-initiated - the employee identifies an internal opening and applies for it. A project change initiated by Infosys (due to project closure, staffing need, or bench management) is employer-initiated and does not require an IJP application. The distinction matters for the releasing manager dynamic: employer-initiated moves do not require the releasing manager’s agreement in the same way that employee-initiated IJP moves do. Both can result in new project assignments, but the career management intentionality is higher in the IJP case.

4. Does an onsite posting automatically lead to faster promotion?

Onsite deployment does not automatically produce a promotion, but it significantly improves the conditions for promotion by strengthening multiple evaluation criteria simultaneously. The client relationship depth, cross-functional business exposure, and visibility to senior stakeholders that onsite experience provides are each independently valuable in promotion cases. Employees who leverage onsite time by deliberately building these dimensions - not just delivering work but building relationships, seeking client feedback, and ensuring their contributions are visible to both onsite and India-based account leadership - convert the onsite opportunity into accelerated promotion more reliably than those who treat it purely as a financial event.

5. What is the minimum number of “Excellent” ratings needed to be considered for promotion at each level?

Infosys does not publish a specific minimum excellent-rating count for promotion eligibility at each level. The pattern observed across many promotion cycles is: at SE to SSE, a single “Excellent” in two years of service is often sufficient with strong delivery evidence. At SSE to TA, having “Excellent” in at least one of the past two years is generally expected for the promotion to be actively advocated. At STA to TL and above, the competition for limited headcount means that “Excellent” in the most recent year and a trajectory of above-average ratings over multiple years is the typical profile of successful promotion candidates.

6. Can I negotiate my salary at the time of promotion at Infosys?

The promotion compensation adjustment at Infosys is determined by the band structure and the appraisal cycle’s increment grid rather than through individual negotiation in the typical sense. However, employees who have received a competing external offer during the promotion period and who communicate this to HR through the retention management process can sometimes receive a larger adjustment than the standard band movement. This approach works most reliably for employees in high-demand skill areas where the retention risk is credible. Using an external offer as a lever should be done honestly and with genuine openness to the alternatives - fabricating external offers for negotiation purposes is an integrity risk that can backfire significantly.

7. What happens to career progression if I take a sabbatical or extended leave?

Extended leave (more than three months) impacts the performance year and the time-in-band calculation for promotion eligibility. The appraisal for a year with extended leave is typically rated for the actual days worked, which can reduce the total impact visible in the self-assessment and the performance record. The time-in-band eligibility may or may not count the leave period depending on the type of leave (medical leave, maternity/paternity leave, and certain approved sabbatical types are treated differently). Employees planning extended leave should clarify with HR how the leave type will be handled for appraisal and promotion eligibility purposes before commencing the leave.

8. Is it better to stay at Infosys for growth or move externally at certain points?

Both paths have merit at different career stages. For employees in the first five years, staying at Infosys and building a strong track record within the structured system is generally the more sustainable foundation - the training, the project exposure, and the professional network building at this stage is valuable. From the Technology Analyst level onward, the calculus becomes more individual: employees in high-demand skill areas who are willing to manage the risk of transitions can accelerate designation and compensation growth externally by 30 to 50 percent compared to the Infosys internal timeline. The decision should factor in personal risk tolerance, the specific external opportunities available, the value of benefits like the PF corpus and gratuity accumulation, and the employee’s genuine assessment of how much Infosys’s current trajectory aligns with their career ambitions.

9. How does the Infosys appraisal process handle employees on different shifts or locations?

The appraisal process is location-agnostic in its formal structure - all employees, regardless of whether they are in India, onsite, or in offshore-dedicated shift roles, go through the same self-assessment, manager review, and calibration process. The practical challenge is that employees in less visible roles (night shift support, remote locations with limited manager interaction) may be less visible in the calibration discussion, and their self-assessments need to be even more specific and impact-quantified to compensate for the reduced informal visibility. Employees in these contexts should invest extra effort in maintaining communication with their manager throughout the year rather than relying on casual office interaction to build the performance impression.

10. What is the role of Infosys’s internal leadership development programmes in career growth?

Infosys runs several internal leadership development programmes, including the Management Trainee programme for certain entry-level cohorts and leadership development initiatives for employees identified as high-potential within their bands. Selection for these programmes is typically based on appraisal performance, manager recommendation, and HR business partner assessment of the employee’s potential trajectory. Being selected for a formal leadership development programme accelerates career growth by providing executive exposure, leadership coaching, and visibility to senior Infosys leadership that is not available through the standard career path. Employees who aspire to senior leadership roles should understand these programmes exist, understand the selection criteria, and make it known to their manager that they are interested in being considered for them.

11. How does Infosys decide which employees get high-profile projects vs routine maintenance?

Project allocation at Infosys is a supply-demand matching exercise managed by the practice delivery team, not a purely merit-based assignment. The factors that influence whether an employee gets high-profile versus maintenance work include: the training grade and stream allocation from Mysore (which shapes initial project assignment), the current project’s account manager’s assessment of the employee’s capability for more complex work, the employee’s certification profile and its alignment with the target project, and the employee’s manager’s advocacy with the allocation team. Employees who want more complex project exposure should communicate this aspiration explicitly, build the skills that make the allocation case compelling, and consider IJP as an active tool to move to higher-profile accounts.

12. Does the DSE or Power Programmer starting designation provide a permanent career advantage over SE hires?

The starting designation advantage provides a meaningful but not permanent career differential. DSE and PP hires start higher in the band structure, which compresses the early promotion timeline and produces a higher salary base at each subsequent band. However, from the Technology Analyst level onward, the performance rating, the nature of project work, the certifications, and the client relationship quality are the dominant career determinants for all employees regardless of their entry designation. An SE-track employee who has been consistently excellent, built strong certifications, and taken on increasing ownership over five to seven years is in a comparable or superior career position to a DSE-track employee who entered higher but coasted on the entry advantage without sustained investment. The entry advantage is real and financially significant in the near term; it is not a permanent differentiator over a 10 to 15 year career.

The Infosys career system is more transparent and more navigable than most employees believe when they are inside it. The promotion criteria are real, the appraisal mechanics are consistent, and the tools for acceleration - certifications, IJP, onsite exposure, manager visibility, and self-assessment quality - are all accessible to employees who approach their career as an active project rather than a passive experience. The employees who reach senior leadership from an SE starting point are not primarily the ones who were luckiest or the best politically positioned. They are the ones who understood the system, invested in the right competencies at the right levels, maintained consistently strong appraisal profiles, and made deliberate use of every career acceleration mechanism the organisation makes available.