Either it is a good product or a sad product
Either it is a good product or a sad product
If you are working on a good product, you will be busy.
If you are working on a bad product, prepare to get downsized,adios, or lucky – someone might take you in for your talent.
If you are doing a good product, you will be very busy, but it's okay. Time goes by fast, and you are happy.
If you are working on a crap product or one that does not sell, you still work like crazy, just not rewarded.
Good and bad ones...
Ppl managers are juggling between ridiculous shoe-shiners or sad, silent people that perform well. Sometimes, you just don't get rewarded because you don't know how to shine shoes.
In this case, to work here, bring a good, branded shoe shiner.
I had it worse locally, but my offshore manager rewarded me because she sees my talent despite being 25,000 miles away. The local managers are sad jokes.
Additional Ratings
Was this helpful?
IBM Interview Questions
IBM Interview Experiences
Senior Software Engineer
Telephonic interview, followed by 3 rounds of face-to-face interviews. Lot of time went into waiting at their office for my turn, as they had called 20 candidates for the same job opening.
Senior Software Engineer
The interview process was very good. There were two technical rounds. In the first round, there were many technical questions related to technical skills, and they also asked some questions about programming. The second round focused on the project
Senior Software Engineer
In my opinion, it was very short. There were two parts: * An over-the-phone interview. * A flight to a location with other interviewees. I must say it seemed organized, but crunched for time. It felt more like something from the 1980s.
Senior Software Engineer
Bengaluru, Karnataka, IndiaJune 1, 2011Telephonic interview, followed by 3 rounds of face-to-face interviews. Lot of time went into waiting at their office for my turn, as they had called 20 candidates for the same job opening.
Senior Software Engineer
IndiaMarch 21, 2022The interview process was very good. There were two technical rounds. In the first round, there were many technical questions related to technical skills, and they also asked some questions about programming. The second round focused on the project
Senior Software Engineer
New York, New York, United StatesOctober 1, 2012In my opinion, it was very short. There were two parts: * An over-the-phone interview. * A flight to a location with other interviewees. I must say it seemed organized, but crunched for time. It felt more like something from the 1980s.
