Working as a Software Engineer for Infosys - Software Engineer Infosys Employee Review

1.0
16 Apr 2010
Recommend
CEO approval
Business outlook

Pros

1. Five months training in India on luxurious campuses. Lessons are relatively easy so you have a lot of time to explore the city and make great friends. You get paid almost a full salary during training. 2. You can make 60k doing nothing for over a year if you are lucky enough to be placed on bench, i.e. you do not have a client to be contracted under. Some bench activities include living at home and relaxing, obtaining higher education, or travel the world. 3. If you get placed on a project and screw up royally, you will not get fired. You will just be put back on bench or be "unbillable" and show up at the office every day and do nothing. You can gchat, youtube, or pick up new skills like javascripting or making really good coffee. If you're really lucky, you can "work" from home. 4. If you like traveling to cities like Bentonville, Milwaukee, Dayton, Minneapolis, and Cleveland, then there is a high chance that you will get to explore those places as clients there are bountiful.

Cons

1. You might be forced to move to a city like Bentonville, Arkansas to work for Walmart while you have coworkers living at home doing nothing on bench. You can say you need to work in a certain location, but they will put you on whatever project they want, even if there is someone way smarter than you living way closer to Bentonville who is just sitting on bench as well. 2. Infosys will lie about your experience to the company you may potentially be contracted with. They will say you have 3 years experience in Java when you still think Java is a special type of coffee. When you actually show up to the client site, you have to pretend you know stuff and struggle to keep up and learn an application you probably have never seen in your life. If you can adapt to feeling stupid all the time, you may become semi productive; otherwise, you will be frustrated every day and your only consolation is the 1.5 benjamins you made that day, which you can use to wipe your tears with. The only reason Infosys wants you there is to bill the client for >2x what they actually pay you. 3. No one likes to work for Infosys. It's a toxic environment where people are always talking trash the company whenever the manager turns his back, except of course when the manager is also involved in the trash talking. 4. Your team will consist mostly of Indians straight out of India. They often speak to each other in Hindi, which creates a tangible separation between you and them. 5. The skills you learn are not useful so it makes it really hard to find another job. You learn applications that only Infosys uses. Sometimes you don't learn anything at all even if you are on a project because after they realize you don't know anything, they won't assign anything to you that requires competency in anything technical. 6. They will ask you to come in on Saturdays to "take one for the team." Compensation is under the table if given at all.

Explore other reviews about Infosys

5.0
11 May 2026
Anonymous employee
Recommend
CEO approval
Business outlook

Pros

Good company to work with

Cons

growth may be factor to consider

4.0
10 June 2026
Recommend
CEO approval
Business outlook

Pros

Job stability – Infosys is known for long-term employment and steady projects. Strong brand value – Having Infosys on your resume adds credibility and global recognition. Good learning opportunities – Access to internal learning platforms, certifications, and training programs (especially for freshers). Global exposure – Opportunities to work with international clients and global delivery teams. Structured processes – Well-defined policies, documentation, and governance. Work-life balance (project dependent) – Many teams offer reasonable working hours. Employee benefits – Health insurance, paid leaves, and wellness initiatives. Safe and inclusive workplace – Strong focus on ethics, compliance, and diversity.

Cons

Salary growth can be slow – Compensation increments may be lower compared to market standards. Limited flexibility in role changes – Internal mobility and project switches can take time. Bureaucratic processes – Decision-making can be slow due to multiple approval layers. Project allocation delays – Bench time and delayed onboarding to projects can happen. Variable learning exposure – Skill growth depends heavily on the project assigned. Less innovation in some teams – Certain projects may use legacy technologies. Onsite opportunities are limited – Compared to earlier years, onsite roles are fewer. Performance appraisal transparency – Rating systems may feel rigid or unclear.

See reviews by: Helpful|Rating|Date|All