I have recently signed up for a Cloud Code project - to build my skillsets around coding.
There was a good discussion around Contract to Hire roles and if it’s worth it.
Here’s a take from Conrad Monreal: https://www.linkedin.com/in/conradmonreal/.
I liked his thought process and wanted to share with you.
There are many variables when it comes to the type of work you can get in the Tech industry. Many states have various considerations when a company is trying to move into an area and purchase a new division or an established company.
The first thing you may get is a layoff of duplicate workers after the purchase.
There could also be new laws that may impact your work/job.
Consequently, you might find more stable work, then full-time employment by doing consulting/temporary work/work-for-hire type work.
Work-for-hire does not mean guaranteed employment, it may be as simple as a new contract did not materialize, so a company can't hire, and you may be the one to be released.
Benefits: you might be able to earn more money and take longer vacations if you work as a consultant/temporary worker/work-for-hire type work. The shorter the contract, higher the rate you should charge. Rates always depend on market competition and your proven track record (skill set).
If a company doesn't give you what you want after the trial period, you can move on, but understand it is a two way street. You can't make promises (accept a contract) and then break your promise (don't take the offer) because you can make more money elsewhere. It is a negotiation, so you have to be honest with what you expect and what your looking for to be hired. Otherwise, both parties realize you will move on to other contracts. "Honest and Open Communication." is the key!!
My take: Choose your client like you would choose your partner. As Conrad mentioned above, it is a 2-way street. I put learning and doing something challenging as my priority. That way I get paid for something I want to learn at the same time build my skillset.
Hence, I like to choose not just the client but the project as well based on that metrics. Besides the money aspect of it, here’s what I would question myself:
Can I see myself going out for a dinner or for a drink with this client? (I got this framework from Alexander Lapa)
What is something new I’m learning from this specific project with the client?
Does the project sound exciting and fun? (Last thing I want to be is bored.)
Is it helping me to move towards my goal? (whatever that might be: be Technical Lead, Solution Architect, Senior Developer, knowing the business, starting a company)