I've tried writing this response a few times. Really I don't think this exists. Of course, you can usually resign if you don't like it inside a 3 month period with a shorter notice before the notice period goes up.
However, regardless of how you structure it, it'd still need to be something acceptable in the mind of whoever reviews your CV after you've tried out 3 or 4 companies. You might be able to talk a company into structuring it as a short contract but I don't know if that'll be possible.
As an employer, if I was recruiting for a permanent position and a candidate suggested a 3 month contract before committing to a full-time position, I'd probably pass them on because I need reliability and this structure represents a risk. I want to structure the deal from the point of view that it will work out as opposed to that it won't.
To conclude, you can structure a deal in any way you want but I think what you're talking about is a change to working culture itself which is a lot harder to do.
Well said. I’d add to this that it’s not uncommon for a developer to need 3 months to get sufficiently up to speed on processes and codebase to be meaningfully effective. Salary up to that point is an investment in future employment, and wasted if the developer leaves after that period.
Not to even mention team time spent on the hiring and onboarding process. There’s a reason most companies strongly prefer to hire people who will stay at least a couple years.
Comments
I've tried writing this response a few times. Really I don't think this exists. Of course, you can usually resign if you don't like it inside a 3 month period with a shorter notice before the notice period goes up.
However, regardless of how you structure it, it'd still need to be something acceptable in the mind of whoever reviews your CV after you've tried out 3 or 4 companies. You might be able to talk a company into structuring it as a short contract but I don't know if that'll be possible.
As an employer, if I was recruiting for a permanent position and a candidate suggested a 3 month contract before committing to a full-time position, I'd probably pass them on because I need reliability and this structure represents a risk. I want to structure the deal from the point of view that it will work out as opposed to that it won't.
To conclude, you can structure a deal in any way you want but I think what you're talking about is a change to working culture itself which is a lot harder to do.
Well said. I’d add to this that it’s not uncommon for a developer to need 3 months to get sufficiently up to speed on processes and codebase to be meaningfully effective. Salary up to that point is an investment in future employment, and wasted if the developer leaves after that period.
Not to even mention team time spent on the hiring and onboarding process. There’s a reason most companies strongly prefer to hire people who will stay at least a couple years.