Reply to: Apprehension about leaving permanent role to go contracting

[davenice]

Tinman, my situation this time last year was quite similar to what you described in your first post. I.e. I had been with my employer for 10+ years, marketable tech skills not as up-to-date as it should be, working in a proprietary language, 3 month notice period etc.

The following are some of the steps I took:

Read up a lot on what it means to be a contractor. Spent a lot of time on forums like this and spoke with other contractors I met.

Built up my cash reserve.

Lots of online training videos to brush up my skills. I used Pluralsight.

Prepared my CV. Focussing on the tech skills. Stripped out the stuff on corporate citizenship etc.

Contacted a couple of recruiters. Insisted on just contract roles.

Resigned. I was placed on gardening leave for 3 months.

Chilled out for a whole month.

Arranged first interview as a developer in a project and got offered the role. I’m still there today, almost a year on. I have probably picked up more new useful skills in the last year than I did in 5 years in my previous role.

Yes, there was some apprehension leaving my previous role. It was very well paid, great benefits etc. Plus I’m my family’s sole breadwinner - so it was always going to be a risky move. However, I was fully committed to going for it. I had no doubt it was what I wanted to do.

[northernladuk]

Rubbish. A bit of fear is always good. Keeps you keen, alert, aware and wanting to succeed.

Which is great but still need the skills to be able to succeed.

Have you never hesitated to jump off a tall cliff into the water, but felt better when you've done it?

But wouldn't go so well if you couldn't swim. Same situation as the OP is in.

[simes]

Rubbish. A bit of fear is always good. Keeps you keen, alert, aware and wanting to succeed.

Have you never hesitated to jump off a tall cliff into the water, but felt better when you've done it?

[SussexSeagull]

If you have any doubts about going into contracting then don't.

[Freewill]

1. Are the kind of skills I have in demand in the contract world, i'm afraid to take the leap as I cant be sure?

Most new web front-end development is being done in JavaScript/TypeScript using React or Angular. There will be contracts for your skills but they would be working on existing systems and at a lower rate.

2. I haven't worked in a proper software team before of more than 2. It doesn't bother me but it might bother a prospective employer?

Yes it would bother me if you were applying for a senior position, as you wouldn't have much experience of reviewing other developer's code and working with junior developers and that is an important part of being a senior developer.

3. Source control and continusous integration seem to standard now. I use SVN for source control but dont have the experience of using this as part of a team. Never used TFS, will this hold me back?

I would be slightly shocked to encounter a contractor who hasn't used git.

4. How do you find the skills/experience of other contractors you have worked with? Are they quickly booted out the door if they are not suitable?

In my experience people get booted quickly more because of their poor behaviour than their poor work. It depends on the client and sometimes teams will carry weak members if they are well liked.

5. How did you feel prior to your first contract? Are these fears/concerns common?

I think these feelings are normal but you should give them serious consideration. Your experience is rather one-dimensional and that may not be a problem when getting a contract initially, but eventually they will dry up as technology marches on. My advice is that you need to broaden your experience by moving to another company and working as part of a team and being a senior developer. I think that with a bit of homework you could use your current skillset to find a permanent job doing ASP.NET with React/Angular. Once you have done this I think you will get more confidence to go contracting.

[BlasterBates]

To test your marketability checkout jobserve. If the skill sets clients are looking for match yours then it should be straightforward if not then you need to skill up. Basically when you read the job descriptions they should be what you've been doing.

There would be no point if they're all looking for expert angular developers for example. The first thing they would do is test you on your knowledge.

[malvolio]

I'm going to suggest something slightly different.

I think OP can get a 'bum on seat' developer contract pretty easily. Just not that likely to command £500 a day for it with very little contract experience or team work.
The reality is a lot of contracts are actually just disguised permie (even more so for developers) roles.
Rather than the OP go for another perm role to get that experience I see no issue with going for junior dev work. In effect, no matter how good a programmer, no experience working in a team, is always going to be junior.

Do that for 6, 12, 18 months and then have a better idea of what the real worth is.

No they're not. The reality is a lot of roles are temporary resources needed to cover a specific project or similar lack of either manpower or skillset. Clients may think they are just readily disposable employees, but they aren't. A smaller set is a client - say a national broadcaster - trying to lose 20% of their employment costs, of course. Either way, it does not mean you aren't a freelance worker, you just have a crap contract.

As for the OP's question, I think you will struggle. Perhaps a permanent role to get your skills up to date would be the best option. Chances are any contract you're likely to find will be some distance away: can you (and your family) live with that?

[Old Greg]

Don't know about the tech but the Belfast contract market is pretty small. You could PM The Equalizer who is the only NI CUK bod I know of. Is Dublin an option for you (probably on a daily commute basis as contract rates are not huge but overnight stay costs are)?

Deloitte in Belfast take on contractors to sell on to GB based projects if you're up for a weekly commute and can face big firm tulipe.

CPL are a pretty decent agency but you need to deal with your three month notice.

[Lance]

I'm going to suggest something slightly different.

I think OP can get a 'bum on seat' developer contract pretty easily. Just not that likely to command £500 a day for it with very little contract experience or team work.
The reality is a lot of contracts are actually just disguised permie (even more so for developers) roles.
Rather than the OP go for another perm role to get that experience I see no issue with going for junior dev work. In effect, no matter how good a programmer, no experience working in a team, is always going to be junior.

Do that for 6, 12, 18 months and then have a better idea of what the real worth is.

[man]

I'm in the infrastructure side so I don't know what's hot on the applications/programming side (so I can't answer some of your questions) - but the information you've provided suggests that you could struggle to get your foot in the door (NB: And by that I mean actual interviews with end clients) if there's not overwhelming demand, at least until you've built your CV and confidence (I get the impression you could improve both of them if you work on it).

I was very confident in my skills when I started contracting, with (what I felt) was a decent CV - I'd been reading about the ins and outs of contracting for years and had ensured that I got myself heavily involved in a number of flagship projects with some high profile clients to fill out the CV. Yet it was a lot of hard work (and a fair bit of time) to get myself the first few contracts. And I was surprised to find that dealing with recruiters could be harder work than I was used to (2 references and your line manager's name anyone?), some of them would even try to neg me to get me to go for a lower rate or more junior contract etc (you have to be mindful it doesn't erode your confidence if you're on the bench for a bit).

You might do fantastic, but do be prepared (mentally and financially) for the possibility that you won't find work easy to get. And that you may need to learn how to market yourself quite differently than when hunting for permie jobs (it won't necessarily come to you overnight).

Whatever you decide to do, good luck.

[Hobosapien]

My skillset is .Net web applications, particularly, C#, MVC and Jquery with Bootstrap UI.

The problem with working alone is its difficult to compare skills with others, I use online training, forums etc to ensure the systems are architected properly and I follow SOLID design principals and use an agile approach with user stories. But I'm not sure where my skills are in the bigger picture.

Working alone has meant I have dealt with lots of issues in many areas however I wouldn't say I'm the best c# developer out there, but I can put together a great CRUD web application with no problems, and have no problems using the MVC framework.

Plenty of contracts for those skills, though the 3 month notice period will be tricky as no contract will wait around that long so you'd need to quit with confidence of finding a contract closer to the end of the notice period.

Alternatively if no contracts in the location you are willing to work (working away from home during the week becomes a necessity if not much locally and not much 100% WFH available) then you could get another job with a shorter notice period to make it easier to jump in future.

Don't worry about how your skills stack up against others. It's better to have delivered several proven working solutions that in itself proves you have what it takes, than to try to be the 'best' where they tend to over engineer (e.g. layers that add no value) and complicate things to prove how great they are, overlooking that ease of maintenance and keeping it simple is harder to achieve therefore requires more skill.

Search the contract/job boards for work available in your location to see what supplemental skills may be worth acquiring so when you do move on there should be some work for you whether contract or permie.

Ask yourself why you really want to jump into contracting. If it's for the money then that is the wrong reason as once all the taxes and permie benefits are added up you won't be massively better off in the long run unless you get lucky with above average rates and manage to stay outside IR35. If you just want more variety then many permies move on every few years, if there's plenty of opportunities locally, and some contractors stay at the same client longer than that, so if you're relatively happy with permie life (performance reviews etc) then weigh up the pros and cons of contracting carefully. It's more a mindset than anything else that makes contracting appeal when you get to the differences between permie and contractor.

[northernladuk]

I would suggest finding another perm job with another firm first, as it seems the tech used at your current PS client is a little dated (no surprise there).

So, either find a more bleeding edge firm to work for, or show your current employer the gaping void in their tech and push for them to budget for some new tech, and make sure you are the guy that implements it and become SME.

Then go contracting.

Totally this.

Although you may have the tech skills (which have already been commented on), you've not really got relevant experience. Clients taking contractors on are likely to be bigger organisations and will want you to carry out a particular role with a team. They'll want someone that can slot in an just get on with it. You won't be able to do that as it's all new to you.

1. Are the kind of skills I have in demand in the contract world, i'm afraid to take the leap as I cant be sure?

Others have already pointed out problems here.

2. I haven't worked in a proper software team before of more than 2. It doesn't bother me but it might bother a prospective employer?

It should bother you and yes it will bother prospective CLIENTS. They will not be your employer. You need to understand contracting a little more before you jump. They want someone that has been doing exactly what they need. They pay top dollar for a specialist that has experience. You are a guy that 'could do it, I think'. You won't have seen their processes, methods, style etc because you are a one man band checking your own work and this will come out in the interview. That doesn't fit what they are looking for and there will be plenty of people that do.

I'm not sure the 10 years in a public sector is going to help you one iota as well. Contractors seem to have a pretty dim view of public sector gigs and I wouldn't be surprised if clients in the private sector also think the same. Could be a wrong opinion but it's one you are going to run in to none the less.

Not a chance you will find a gig with a 3 month notice.

3. Source control and continusous integration seem to standard now. I use SVN for source control but dont have the experience of using this as part of a team. Never used TFS, will this hold me back?

If the client needs it then hell yes. If he wants someone to be a member of a team and you've not done it you don't have the skills. It's not all about tech knowledge. It's about hitting the ground running and delivering from day one. We aren't brought in to learn on the job.

4. How do you find the skills/experience of other contractors you have worked with? Are they quickly booted out the door if they are not suitable?

Varies. I've worked with some great contractors and some bloody awful ones that have blagged their way in. Sadly not all clients seem to understand they can shed crap people quickly and in the long run it would be better. But yes they most certainly get rid of people that can't deliver. We are an expensive resource at best, let alone when we can't deliver what they want.

There is a clause in our contracts that allow clients to walk you on the spot and you can do nothing about it. No protection out in the contracting world.

5. How did you feel prior to your first contract? Are these fears/concerns common?

Not if you have the exact skills clients are looking for. If you 'think' you can do it then you've a very good reason to be nervous I am afraid.

[Goosefeather]

I would suggest finding another perm job with another firm first, as it seems the tech used at your current PS client is a little dated (no surprise there).

So, either find a more bleeding edge firm to work for, or show your current employer the gaping void in their tech and push for them to budget for some new tech, and make sure you are the guy that implements it and become SME.

Then go contracting.

[NotAllThere]

You just have to assume that you're really good at what you do. If you have difficulty doing that, fake it.

[cannon999]

Hi Folks,

Im thinking of quitting my permanet post to go into contracting and hoping for some advice on my situation.

For the past 10 years I've been working in the public sector as a lone worker, throughout this time I've developed several web applications that are heavily relied upon in my sector. With each of these applications I have worked with each of the clients to develop requirements etc and plan the project, then actually build the applications and when built support them. The parent company has an IT department and they occasionally help with server support but apart from this I am the 'Web Department'.

My skillset is .Net web applications, particularly, C#, MVC and Jquery with Bootstrap UI.

The problem with working alone is its difficult to compare skills with others, I use online training, forums etc to ensure the systems are architected properly and I follow SOLID design principals and use an agile approach with user stories. But I'm not sure where my skills are in the bigger picture.

Working alone has meant I have dealt with lots of issues in many areas however I wouldn't say I'm the best c# developer out there, but I can put together a great CRUD web application with no problems, and have no problems using the MVC framework.

So some questions:

1. Are the kind of skills I have in demand in the contract world, i'm afraid to take the leap as I cant be sure?


2. I haven't worked in a proper software team before of more than 2. It doesn't bother me but it might bother a prospective employer?


3. Source control and continusous integration seem to standard now. I use SVN for source control but dont have the experience of using this as part of a team. Never used TFS, will this hold me back?


4. How do you find the skills/experience of other contractors you have worked with? Are they quickly booted out the door if they are not suitable?


5. How did you feel prior to your first contract? Are these fears/concerns common?




I've talking to a few recruitment agencies and they seem to think I could get a contract no problem. (But, I know they would say that!) The problem is my current post requires a 3 month notice period and all the agencies said it will be difficult to get a contract 3 months in advance.

I'd be looking for contracting roles in N Ireland, particularly Belfast. Anybody any experience here?

1. jquery is dead. MVC has been overtaken by the rising popularity of single page apps. React/Angular/Vue. With no knowledge of javascript you are unlikely to even have your CV reach the client if you want to do web development.

2. It will deffinitely bother them. I would keep that quiet.

3. Who even uses SVN?

4. I have worked with some truly terrible contractors.

5. Had no concerns, I knew I could do it. If you don't feel like you can - you probably won't.