- Infosys salary in India for 2026: freshers typically earn 3.6–5.2 LPA CTC. Chennai pay, skills, and in-hand explained.
- Use the table of contents to jump to cost tables, variables, and FAQs.
- Talk to Asmorix mentors if you want a course or project plan tailored to your goals.
Infosys salary in India for 2026 sits in a planning band, not on a single official card. For Infosys fresher hiring, freshers with real project proof typically see about 3.6–5.2 LPA as CTC. Early-career professionals with two to four years often see 6–11 LPA. People with five or more years, and with ownership of a system, often see 12–22 LPA. These figures are candidate-reported ranges used for planning. They are not an offer letter, a campus circular, or a promise from any employer.
Use this page to compare fixed pay, variable pay, and city. A higher CTC in Bangalore can lose to a cleaner fixed salary in Chennai after rent. A fresher who can demonstrate Programming fundamentals and SQL is the person who reaches the upper half of 3.6–5.2 LPA. A fresher who only lists tool names usually stays near 3.6 LPA.
Infosys campus and early lateral offers are service-company packages. The fresher band in this guide is a planning range, not a promise that every college drive pays the top number. Specialist or digital-style hiring can sit higher than a general systems role. Training location, bond terms if any are in your letter, and variable pay change the first-year cash. Compare the fixed part of the Infosys letter with the fixed part of any other letter, including Zoho or a Chennai product team.
Infosys salary bands in India (2026)
| Experience | Typical CTC | Rough monthly in-hand |
|---|---|---|
| Fresher (0–1 year) | 3.6–5.2 LPA | about Rs 21,000 to Rs 33,800 |
| Early career (2–4 years) | 6–11 LPA | from about Rs 36,000 at the low end |
| Experienced (5+ years) | 12–22 LPA | from about Rs 70,000 at the low end |
Read the fresher row first. 3.6 LPA is the low planning number. 5.2 LPA is the high planning number for a strong fresher, not the average of every offer in India. CTC is the annual cost to the company. It includes employer provident fund, sometimes gratuity, insurance, and a variable portion. It is not twelve times the amount that reaches your bank.
A practical in-hand check for the fresher band: take fixed pay as roughly 75 to 85 percent of CTC if the letter is clean, then subtract employee PF and tax. On a 3.6 LPA CTC, many freshers see on the order of Rs 21,000 a month before they count rent. On a 5.2 LPA CTC, the monthly figure can approach Rs 33,800 only when most of the package is fixed. If a large slice is variable, do not spend that money in your head until it is credited.
Two letters can both say they are “around the Infosys fresher band” and still differ by thousands of rupees a month. Letter A at 3.6 LPA with almost all fixed pay can beat letter B at a higher CTC if letter B hides a joining bonus paid once and a variable plan paid only if the project stays billed. Ask for the annexure: basic, HRA, special allowance, employer PF, variable, and the month variable is paid.
What Infosys work looks like
A company salary page is not a job-title page. The same employer can hire a tester, a Java developer, and a support engineer in one Chennai campus drive, and those three offers will not match. Use the band as the campus and early lateral range, then ask which business unit the offer belongs to.
On this path the skills that show up in Chennai job descriptions are Programming fundamentals, SQL, Aptitude, Communication. A fresher resume should prove those skills with one project, not with a grid of icons. The day-to-day work is smaller than the job title sounds: a ticket, a page, a query, a bot, a case, or a pipeline, finished well enough that a senior does not rewrite it.
Service companies in Chennai and across India hire more Infosys freshers than product companies do. Service offers cluster near 3.6 to the middle of the fresher band. Product teams, specialist units, and scarce skills cluster near 5.2 LPA and sometimes above it for an exceptional project. Startups may quote a lower fixed salary plus an unverified upside. Count the fixed salary.
Infosys salary in Chennai, Bangalore, Hyderabad, and Pune
Chennai tracks the India band closely for Infosys fresher hiring. A fresher offer in Guindy, OMR, or a Chennai delivery centre is usually inside 3.6–5.2 LPA unless the team is a product group with a harder interview. Rent in a shared room is often lower than in Bangalore, so the same CTC can leave more cash after housing.
Bangalore product teams sometimes quote 10 to 20 percent more CTC for the same fresher skills. That does not automatically mean a better first year. Add rent, deposits, and the variable clause. Hyderabad is often close to the India band and can match Chennai for service-company Infosys roles. Pune sits near the India band with a strong service and product mix. Coimbatore and smaller Tamil Nadu cities can quote the lower half of the band and still be a fair start if the work teaches Programming fundamentals.
If you are choosing between a Chennai offer at 3.6 LPA fixed-heavy and a Bangalore offer at 5.2 LPA with a large variable, write both monthly in-hand numbers on paper. Include a rent estimate. Freshers lose money when they optimise the headline CTC and ignore the city. The Infosys title is the same. The cash is not.
Who pays the low end and the high end
The low end, near 3.6 LPA, is common when the interview tested only definitions, the project was a tutorial, or the role is a support-heavy version of Infosys. Mass campus drives land here when the stack is taught after joining. There is nothing wrong with that start if the letter is fixed pay and the team lets you touch real work in the first six months.
The high end, near 5.2 LPA for freshers and 11 LPA after a few years, shows up when you can defend a project, write or test without a senior in the room, and communicate the result. Specialist stacks on this page move faster than generic ones. Experienced pay near 12–22 LPA is for people who own a module, a pipeline, a dashboard, or a client conversation, not for people who repeated the same fresher task for five years.
Negotiation at fresher level is narrow. You will not move a campus grid by arguing. You move it before the interview, with a project and clean fundamentals. After two years, switching teams is how people leave 6 LPA for the upper half of 6–11 LPA. Keep a record of what you shipped. That record is the negotiation.
Skills that change a Infosys offer
Each skill below is a filter Chennai and India panels use before they pick a number inside 3.6–5.2 LPA. Read the proof, put it in a project, and practise saying it in two minutes.
Programming fundamentals for a Infosys
Use variables, a loop, and a function without notes. That is the proof a panel can score. For a Infosys fresher, Programming fundamentals is not a line in a skills box. It is a reason to move from 3.6 LPA toward 5.2 LPA.
In the interview, expect a small task, not a speech. Do the smallest correct version of Programming fundamentals, then mention one bug you already hit while practising. Candidates who recite a definition and then go quiet stay at the bottom of the band. Candidates who narrate a check they ran are the ones panels mark as ready for the upper half.
Make Programming fundamentals the headline of your project. The README should show the command, the input, and the output. If a reviewer cannot run or watch that proof in five minutes, it will not affect the offer.
SQL for a Infosys
Join two tables, filter a date, and explain the grain of the result. That is the proof a panel can score. For a Infosys fresher, SQL is not a line in a skills box. It is a reason to move from 3.6 LPA toward 5.2 LPA.
In the interview, expect a small task, not a speech. Do the smallest correct version of SQL, then mention one bug you already hit while practising. Candidates who recite a definition and then go quiet stay at the bottom of the band. Candidates who narrate a check they ran are the ones panels mark as ready for the upper half.
Aptitude for a Infosys
Practise timed sets and review every wrong question the same day. That is the proof a panel can score. For a Infosys fresher, Aptitude is not a line in a skills box. It is a reason to move from 3.6 LPA toward 5.2 LPA.
In the interview, expect a small task, not a speech. Do the smallest correct version of Aptitude, then mention one bug you already hit while practising. Candidates who recite a definition and then go quiet stay at the bottom of the band. Candidates who narrate a check they ran are the ones panels mark as ready for the upper half.
Communication for a Infosys
Explain the project in ninety seconds, then stop. That is the proof a panel can score. For a Infosys fresher, Communication is not a line in a skills box. It is a reason to move from 3.6 LPA toward 5.2 LPA.
In the interview, expect a small task, not a speech. Do the smallest correct version of Communication, then mention one bug you already hit while practising. Candidates who recite a definition and then go quiet stay at the bottom of the band. Candidates who narrate a check they ran are the ones panels mark as ready for the upper half.
Projects that justify the higher fresher band
For a company drive, one project is enough if you can explain it without notes. Pick a project that uses the stack that company actually interviews: a small Java or Python service with a database, a test report with real bugs, or a problem-solving writeup. Recruiters in Chennai campus drives score communication and fundamentals before they score framework trivia.
Tie the project to money without exaggerating. You are not claiming the project is worth 5.2 LPA by itself. You are showing that you can do the first month of a Infosys job. Include one metric: rows cleaned, cases automated, a page that works on a phone, a query that got faster, a bot that logged bad rows, or a model error you wrote down. Metrics beat adjectives.
Avoid a group project where you cannot explain your part. Panels in campus drives ask “what did you do?” three times. If the answer is “we used Programming fundamentals,” the offer stays near 3.6 LPA. If the answer is a specific decision and a bug, you are in the conversation for the higher number.
A week in a Infosys seat
Monday starts with a small Infosys task, not a classroom lecture. You open yesterday's note and pick up Programming fundamentals. Use variables, a loop, and a function without notes. A senior looks at the result, not at how many tools you can name. If the result is wrong, you write the failing case before you change anything. That habit is what teams in Chennai mention when they defend a fresher offer near 5.2 LPA instead of 3.6 LPA. By the end of Monday you can say what moved, what broke, and what you will show tomorrow.
Tuesday starts with a small Infosys task, not a classroom lecture. You open yesterday's note and pick up SQL. Join two tables, filter a date, and explain the grain of the result. A senior looks at the result, not at how many tools you can name. If the result is wrong, you write the failing case before you change anything. That habit is what teams in Chennai mention when they defend a fresher offer near 5.2 LPA instead of 3.6 LPA. By the end of Tuesday you can say what moved, what broke, and what you will show tomorrow.
Wednesday starts with a small Infosys task, not a classroom lecture. You open yesterday's note and pick up Aptitude. Practise timed sets and review every wrong question the same day. A senior looks at the result, not at how many tools you can name. If the result is wrong, you write the failing case before you change anything. That habit is what teams in Chennai mention when they defend a fresher offer near 5.2 LPA instead of 3.6 LPA. By the end of Wednesday you can say what moved, what broke, and what you will show tomorrow.
Thursday starts with a small Infosys task, not a classroom lecture. You open yesterday's note and pick up Communication. Explain the project in ninety seconds, then stop. A senior looks at the result, not at how many tools you can name. If the result is wrong, you write the failing case before you change anything. That habit is what teams in Chennai mention when they defend a fresher offer near 5.2 LPA instead of 3.6 LPA. By the end of Thursday you can say what moved, what broke, and what you will show tomorrow.
Friday starts with a small Infosys task, not a classroom lecture. You open yesterday's note and pick up Programming fundamentals. Use variables, a loop, and a function without notes. A senior looks at the result, not at how many tools you can name. If the result is wrong, you write the failing case before you change anything. That habit is what teams in Chennai mention when they defend a fresher offer near 5.2 LPA instead of 3.6 LPA. By the end of Friday you can say what moved, what broke, and what you will show tomorrow.
The week is deliberately narrow. A Infosys fresher who finishes five small proofs is easier to trust than a fresher who watched five courses. Keep a single document with the five proofs. Take it to the interview. The document is more persuasive than a line that says you know Programming fundamentals.
Infosys interview questions and solid answers
How would you prove Programming fundamentals in a Infosys interview?
Start with the proof, not the definition. Use variables, a loop, and a function without notes. Then connect it to the job: a Infosys fresher is paid inside 3.6–5.2 LPA to do that kind of task without a senior rewriting it. Close with one mistake you already made while practising Programming fundamentals and how you checked the fix. Panels trust a specific failure more than a perfect speech. If you have not practised Programming fundamentals this week, say so and show the nearest proof you do have.
How would you prove SQL in a Infosys interview?
Start with the proof, not the definition. Join two tables, filter a date, and explain the grain of the result. Then connect it to the job: a Infosys fresher is paid inside 3.6–5.2 LPA to do that kind of task without a senior rewriting it. Close with one mistake you already made while practising SQL and how you checked the fix. Panels trust a specific failure more than a perfect speech. If you have not practised SQL this week, say so and show the nearest proof you do have.
How would you prove Aptitude in a Infosys interview?
Start with the proof, not the definition. Practise timed sets and review every wrong question the same day. Then connect it to the job: a Infosys fresher is paid inside 3.6–5.2 LPA to do that kind of task without a senior rewriting it. Close with one mistake you already made while practising Aptitude and how you checked the fix. Panels trust a specific failure more than a perfect speech. If you have not practised Aptitude this week, say so and show the nearest proof you do have.
How would you prove Communication in a Infosys interview?
Start with the proof, not the definition. Explain the project in ninety seconds, then stop. Then connect it to the job: a Infosys fresher is paid inside 3.6–5.2 LPA to do that kind of task without a senior rewriting it. Close with one mistake you already made while practising Communication and how you checked the fix. Panels trust a specific failure more than a perfect speech. If you have not practised Communication this week, say so and show the nearest proof you do have.
Infosys interview rounds
Company fresher loops in India usually run aptitude, a technical round, and an HR round. Aptitude is timed. The technical round asks you to write a small program or explain a project. HR checks whether you will join, relocate, and stay through the training period. Speak in short sentences and do not invent a CTC you saw on a forum.
A typical loop is three steps. First, a screen or aptitude check. Second, a technical round on Programming fundamentals, SQL, Aptitude. Third, HR: joining date, location, and whether you understand the CTC split. For Infosys, prepare one project story with a start, a problem, and a result. Prepare one honest gap. “I have not used that tool yet; here is the adjacent thing I have built” is a stronger line than a bluff.
After the technical round, write down the questions you missed the same day. The second company will ask a cousin of that question. Freshers who do this for two weeks move bands. Freshers who collect offer screenshots do not.
Salary growth from fresher to five years
Year zero is the fresher band, 3.6–5.2 LPA. The goal in year one is not a job hop. The goal is proof: tickets closed, pages shipped, queries trusted, bots that handle bad rows, or a module you can describe. Without that proof, year two still looks like a fresher resume and the pay stays near the bottom of 6–11 LPA.
Years two to four are the early-career band, 6–11 LPA. People reach the top of it by owning a small system and by interviewing outside their first team. A switch with no new skill just resets the title. A switch with Programming fundamentals at a deeper level is what prints the higher number.
Year five and beyond is 12–22 LPA in this planning guide. That band assumes you can lead a slice of work: estimate it, review someone else, and talk to a client or a product manager. It is not an automatic increment. People who repeat the same fresher task stay below it even with five years on the resume.
How to read a Infosys offer letter
Put the letter next to this band. If the CTC is under 3.6 LPA, ask what the role actually is. It may be support, internship stipends counted as CTC, or a training period. If the CTC is far above 5.2 LPA for a fresher, look for a one-time bonus, a long variable plan, or a bond. High numbers that are not monthly fixed pay are not the band.
Check the work location. A Chennai letter and a Bangalore letter are different lives at the same CTC. Check probation, the notice period, and whether the variable depends on company profit or your project. Check insurance and PF so you are not surprised by the first payslip. The first payslip, not the PDF header, is the truth.
When you compare two offers, make a three-line note: fixed monthly pay, city and rent, and what you will learn in six months. For Infosys, learning Programming fundamentals on a real ticket is worth more than a slightly higher CTC on a desk where you only watch. The next band, 6–11 LPA, is earned from that work.
A 90-day plan before you apply
Ninety days before a company drive: week one to four, close programming fundamentals and SQL; week five to eight, finish one project and a one-page resume; week nine to twelve, sit mock aptitude and a mock technical round out loud. Apply to the role the project actually supports.
Every week, write five lines: what you built, what broke, what you will show in an interview. At day 90 you should be able to demo the project, answer questions on Programming fundamentals, SQL, Aptitude, Communication, and explain why your expected fresher CTC is inside 3.6–5.2 LPA instead of a random number from social media.
If you are already in a job under the early-career band, use the same ninety days on one deeper skill, not on five new tools. Depth is what moves 6 LPA toward 11 LPA. Breadth without a story does not.
Train for Infosys in Chennai
Asmorix mentors in Chennai train this path with projects and placement practice. The related course is a fit when you want a timetable instead of a pile of videos. Look at the syllabus, match it to Programming fundamentals and SQL, and join if you will finish the project. A course you do not finish will not change a Infosys offer.
