TCS
TCS
on
TwirlyJellybean
TwirlyJellybean
8mo
by

It is not 35 days, it is 255 days.

I have been reading comments not only on this forum but in mes, social media platforms also. Please note that it is 255 days in last 12 months means Gap of 35 days must not exceed among all projects in last 12 months.

So if you changed project first time and the gap is 25 days, and now if you are getting released, you are left with 10 days ONLY. Is this the catch and risk.

8mo ago
SwirlyPanda
SwirlyPanda
7mo

What you have failed to consider is you can also start looking for a project before the release. In my case, I got project almost a month before my release, though got future allocation only a week before release. Changed project and was on bench for 0 days.

Despite all this, I also started getting calls from other projects before release. So if someone is interested in working, opportunities are there.

There may be a few genuine cases which will get impacted, but if you have the skills and intention, 1 month is a long time to be on bench and not getting a project.

TwirlyJellybean
TwirlyJellybean
7mo

Is this not applicable to all skills. It is not true for all kind of roles and skills.

WigglyMuffin
WigglyMuffin
7mo

Correct. But for Generalized skills like Java, .NET , Cloud

SparklySushi
SparklySushi
8mo

Upcoming 10-12 days and until the next quarter end will be crucial and we have to see what will happen

TwirlyJellybean
TwirlyJellybean
8mo

Yes

SparklySushi
SparklySushi
8mo

We have to wait and watch the entire implementation of the policies in the upcoming days

TwirlyJellybean
TwirlyJellybean
8mo

Agree. But this policy will really be used to exploit and lay off silently under the name of 255 allocation

Discover more
Curated from across