Speaking personally... If I'm presented with the CV of some candidate, and they only have these "core" skills, then I'll "file" the document and not even consider them for a phone interview.
Why? In the case of someone who's new to the field, it looks very sycophantic and lacking in imagination. Is aiming for the lowest common denominator of "most" employers really the best you can aspire to? I'm also coming to view Java + Spring + Hibernate very much as a legacy stack, not exactly what I'm after from a graduate or junior developer who I'd expect to bring some fresh new dynamic ideas to the table. In this example, I'd actually rate someone without Spring and Hibernate more highly!
In the case of a senior developer, it's only to be expected that they'd know legacy systems. After all... once upon a type Spring was very new and interesting :) On the other hand, if you've spent that much time without anything else to show for it, then you'll look like a 9-5er who lacks initiative and who takes no joy in programming besides the financial renumeration it offers. i.e. Not the sort of person that I'd consider hiring.
Whether consciously or not, I believe that any employer *worth working for* is looking to "raise the average" with every single hiring decision they make. So you want to have some talent, or ability, or skillset, or specialist knowledge such that the average ability of a company in your chosen area will be improved by employing you. All you have to do is decide what you have best to offer; it should preferably be something that you have a genuine passion for!
On 27 June[masked]:50, Richard Gomes <[address removed]>
I think that Kevin and Craig already exposed very relevant aspects.
I prefer to talk about three other aspects to consider... and I'm
going to talk about technology at all.
1. What you like to do.
You perform better when you do what you enjoy.
Consider this. If you find that list boring... please do a favor to
yourself and do not take that list.
If you find that list fine... go ahead. No problem, in principle.
(please continue reading)
2. Where the money is.
Once you have selected what you like to do, find opportunities which
need your skills and are willing to pay well for your skills. if you
are not able to find companies paying what you are aiming... then
you have a problem. Return to step 1 and reconsider that list, or
find another list.
Reinvent yourself all the time. This is business, not technology.
Is that list what you'd like to do? Is that list what you enjoy? Are
there other things you enjoy? Are there enough opportunities paying
the amount of money you'd like to receive? What an 'opportunity'
really means? Have you considered self-employment? Do you have a
great idea? Do you have good business contacts?
Again... think strategically. Consider the effort you will have to
employ learning a long list of things against the effort refining
what you already have. Consider opportunities willing to pay well
for things you already have... or things you can reach more or less
easily, starting from what you already have.
Again... think strategically. What, in 5 years time, will pay well
for your efforts today?
Consider the difficulties to breaking into the best paying jobs
against the difficulties of breaking into the not-that-good-wages
jobs. You eventually find that differences in effort are small if
compared with differences in wages.
Also... remember that 'opportunity' does not mean necessarily...
You have the advantage of having a blank canvas in front of you.
Paint the best work of art you can!
I hope it helps :)
mobile : [masked]
Skype: dial skype2ippi then dial[masked] when prompted.
GTalk: dial [address removed] then dial[masked] when prompted.
SIP : dial [address removed]
iNUM : [masked]
On 27/06/12 12:20, Kevin Wright wrote:
With just that list, you'll
stand out about as much as a small pebble on a motorway. Is
it the quantity of potential interviews that you want to
maximise, or their quality?
Java/Maven/Spring are taken for granted nowadays, almost
everyone has them on their CV and they're not much worth
Struts and Ant are largely superseded, so should probably
go under whatever heading you use for Cobol, Basic and your
bronze swimming certificate.
Much more importantly, you want to disambiguate yourself.
Go to conferences and meetups, expand your network of
contacts, commit to an open-source-project or ten, have
projects of your own (publicly visible) on GitHub, make sure
your have some genuine real-world experiences of problems
you've encountered - and solved - when programming.
If you really want to shine, start to look outside just
the Java language. Try your hand at web development with
Erlang, etc. write a small project in one of these and
*publish it on GitHub*. Demonstrate that you can do Test
and broader technologies? Can you do a RESTful website?
What about Big Data(tm), with Hadoop perhaps? Any
experience of NoSQL? Do you have an opinion on MongoDB vs
CouchDB vs Cassandra vs Redis vs ...?
On 27 June[masked]:02, alexander
sharma <[address removed]>
I have another question regarding Java.
What Java JEE technologies are most common to get
a job in london:
In my view they are:
mail: [address removed]
gtalk / msn : [address removed]
vibe / skype: kev.lee.wright
"My point today is that, if we wish to count lines of code, we should not regard them as "lines produced" but as "lines spent": the current conventional wisdom is so foolish as to book that count on the wrong side of the ledger" ~ Dijkstra