I know Java quite well and did some of my own projects. Know a bit of JDBC and databases too. But that seems to be not enough to get an entry level job.
Interested in doing only back-end development for now. I want an entry level job (unpaid ok too) where I can learn things like hibernate ORM, Spring etc
on the job and also get some experience. Until I crack an interview, I will have to do some study (and some more projects) on my own. But there are
too many technologies to be studied. I want to get a list of topics/technologies which are bare-bones or must haves to be employable in an
entry level position.
I see that a lot of entry level java jobs ask for Java, Hibernate, Spring, XML besides REST, SOAP, JSF, JMS, JSON and so many names like these that I don't know about.
I am guessing that a basics/bare bones/must haves list has - Java, Hibernate, Spring, Eclipse, SVN/Sub Version or GIT, JDBC, SQL , XML or JSON, Any Scripting Language.
Would this be enough to get an entry level position ? Should I remove something from this list ?
As with any advice, you should take this with a grain of salt (or two).
One thing that might set you apart from other entry-level candidates is a familiarity with Agile software development techniques. Knowledge of Test-Driven Development is becoming more and more something that I look for when I do interviews. I don't really look for knowledge in specific technologies when I interview junior level candidates. What I look for is a basic understanding of principles: Object-orientation, design, testing. You should have good programming habits. Read "Clean Code" by Robert Martin to get an idea of what I'm talking about. I also try to see how well they will work with others (you'll do that a lot of that if you're a junior developer) and I like it when they are open to coaching and mentoring. The candidates who show an eagerness to learn and an ability to pick up on things that I teach them during an interview (I do something that's really more of an audition rather than an interview) are the ones who I am more likely to consider for the job.
Naturally, you want to see if any of this aligns with the culture of the company that you're applying to. Don't be afraid to ask the recruiter or someone in the department that you're interviewing for about their development environment and culture.
The best ideas are the crazy ones. If you have a crazy idea and it works, it's really valuable.—Kent Beck
Lexington Smith wrote:Interested in doing only back-end development for now.
Why? Having your heart set on a specific language (Java) is already limiting. Limiting what you want to do to back end only, restricts the possible jobs even more. If a company is interested in giving you experience, why does it have to be such a specific thing.
When I got my first job, I didn't have any language in particular in mind. I like to program. That's not language specific.