Infosys reviews

Good if just starting out and trying to get foot in the door. Company provides training for recent grads to get placed with client company. Provides bench pay for in between client assignments. Health care benefit is excellent. Low monthly premiums and low deductible. Although no maternity leave offered in the lower rank. Unsure if offered at all. 2 weeks PTO. 3 days sick leave. Pay was usually stable but experienced weeks without pay due to company's faulty timesheet and PTO system.

Great training, Infosys had terrible reviews online when I was considering the job, I took it and wow I was wrong. Infosys is great! They took my skills from CS in college and made me a much stronger developer through classes, and client projects. I now have the experience I would need to take on other jobs, but after 1.5 years with Infosys, I would be genuinely to leave. They invest a LOT into employees who reach out and want to learn and become better programers. But you have to show it, nobody will come digging for your internal motivations. That's what I think the people who posted negatively perhaps expected - get out there network, make genuine connections and keep up with them. Be happy to help anybody when you can and shut up and actively listen when you don't know enough to help. These types of skills separate engineers who companies want to hire and pay very well, from those they want to filter out because they just sit in the background and do as their directed - no more, no less. Be the best resource you can be and don't forget that I don't know is a completely valid and often time saving answer. Keep yourself from getting overwhelmed by utilizing others as you probably aren't the only one on the team confused. Ask questions! Unmute your mic, show your a person and a good engineer by thinking before you speak and asking yourself - 'Is what I'm about to say: (1) Relevant to the issue or topic being discussed, (2) Not just a paraphrase of an already known factor, (3) Phrased in such a way that it can be universally perceived to everyone listening( this is often very difficult but well worth the time.), (4) If recommending a solution or direction, is it conditional on unknown information? What are those unknowns? If you don't know, find out as much as you can so you can include what you need to know when you bring it to the team. And (5): Is this the best solution, the first solution, or just a solution to add to the explore list? Different times call for different measures, a brain storming meeting should be much more open to abstractions than say a Critical System Failure MIM or tech bridge regarding a bug that is causing millions of errors, losing users, and money.