Stick with what you know, or do something new?

[Crossroads]

Hi,

First time posting here, but been lurking for a while. Currently have a bit of a dilemma and I'd appreciate views from those who have been in a similar situation.

I'm a lead technical architect / consultant with some skills and project experience that has seen me deliver some very complex projects, and some of the largest ones in my particular field.

My main specialism is quite niche and currently I'm in a role which is related to my technical skills but is not as big a project as I would usually be leading (and I'm not even leading this one!). As such, I'm a bit bored, a bit frustrated and my rate is around 20% lower than I would normally be charging. The client however "looks good" on the CV, and there is probably at least 6 months+ work there for me (already been there 5 months), and all in all, it's not that bad.

However, a former client has approached me for an 18 month role at a very good rate. However the role is quite far removed from what I would normally do - much more man management / service delivery than technical architecture.

It seems like a good opportunity to do something new, and it is at a major FTSE and on a flagship project with worldwide recognition - so it could lead to bigger things.

However, it would mean that I am potentially wasting my existing skills.

My gut feeling it to make the move - otherwise it will always have been "what if", but would be interested to know what others think...

[Diestl]

if (OtherRole.Rate > CurrentRole.Rate)
takeit();
else
stay();

[ChimpMaster]

If your current niche skill is likely to be in high demand over the next few years then you should perhaps remain in that field and try to find a contract that gives you a rate you're happy with.

If however you believe that your niche is a risk factor rather than a long trm income generator then it might be preferable to grow out of this niche and proliferate your skillset with a good FTSE company.

I am in a niche in a dying technical skillset, and am currently (slowly) growing out of it into a more general banking architect type of role. I am becoming less hands-on and more involved with general architecture etc. I used to be an architect in my niche field only.

The niche will earn you more money - certainly - but of course with it being a niche the risk is that you may be out of a job sooner rather than later.

[Crossroads]

if (OtherRole.Rate > CurrentRole.Rate)
takeit();
else
stay();

That is certainly part of the logic ;-)

[Crossroads]

Sensible stuff...

Similar situation for me I guess, in as far as my field is slowly being eroded from various angles - competitors, market need, diversification of vendors etc...one advantage I guess I have is that if I move now, and then decide I don't like it, I could return to what I do pretty quickly and see it out to the bitter end!

[ChimpMaster]

Similar situation for me I guess, in as far as my field is slowly being eroded from various angles - competitors, market need, diversification of vendors etc...one advantage I guess I have is that if I move now, and then decide I don't like it, I could return to what I do pretty quickly and see it out to the bitter end!

Yes good point.

There is also the direction that I approached this dilemma from - which is to make the good money while you can and then move on to something else, where you might not make as much money but you'd be financially OK by then and can perhaps be a bit more choosy about where you head next.

[ratewhore]

...and it is at a major FTSE and on a flagship project with worldwide recognition - so it could lead to bigger things.

There is a flip side to this remember...

[lukemg]

No question - if the location suits, go for the new job. If need be, you can make the 18 monther look a bit more technical in the future. You are being approached to do the job, makes it much easier. Fresh challenge is always worth going for, even if it's scary at first.
And the money is better, what are you waiting for ?