When can I realistically start to specialize?
When I started my first job I learned PHP because most of the work was PHP-based.
I'm not that fond of PHP though so I asked my employer for Java work. Unfortunately the projects we got at the time was all PHP based so I started looking for new employment. About a year ago I got a new job and was lead to believe that I will be doing Java work. However since I started I have not gotten much exposure to Java (on the plus side I'm not doing PHP anymore).
I'm worried that switching jobs too often will hurt my resume, but I also don't want to get stuck. My goal is to specialize in Java security systems but I'm not going to get a job as a Java developer if I haven't worked with it and in the mean time I'm passing up more senior PHP positions so as not to be labeled as a PHP developer or even a web-developer. The last time I asked my current employer for Java work he actually laughed and said "I can't promise you that."
Maybe I'm being naive but I think it is very unfair to employ someone as a Java developer and then give him other tasks simply because he is able to do them. Furthermore if I quit my job every few months I'm the one stuck with a bad reputation.
In a few months I will have four years experience and I feel like I'm not growing at the speed or in the direction I want to grow. Is this normal? When should I realistically expect to start specializing? And how much can I switch positions before I go from "a driven individual" to "an unreliable employee?"
Posted Aug 17, 2014, 2:52 PM UTC
Never used it myself, but, if you are stuck building web apps - show your boss Java Play! Show him how quickly you can build some sweet app-action, fulfill the requirements of the project ( hopefully ) in record time, and, work in Java. Java play seems like a good fit for your situation.
As for your situation - if I was you I'd move on. When you negotiate your next contract ensure there is a clause pertaining to time spent working with a particular language - if you are hired as a Java Software Engineer - you should be at least working in Java for 50% of your time.
Make sure when you are hired, through contract negotiation, that you are not the company's new "jack of all the shit jobs." You are responsible for your own career. In future job interviews you can address your employment record as such. No one is going to look at you poorly for ensuring your own career management and progression - especially if your previous employers tried to send you down a path you didn't want to travel. Just be honest about these facts when you speak with future potential employers.