aspose file tools*
The moose likes Jobs Discussion and the fly likes Job requirement: not having everything listed. Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Careers » Jobs Discussion
Bookmark "Job requirement: not having everything listed. " Watch "Job requirement: not having everything listed. " New topic
Author

Job requirement: not having everything listed.

H Paul
Ranch Hand

Joined: Jul 26, 2011
Posts: 410
    
    3
1.
On a job requirement, they're 10 things required.
You only have 7, what is a reasonable answer to say?
Let's say they want 2 years of Spring MVC when you do not have it or just read a book on Spring MVC.

2.
If you have knowledge like reading a book and doing excercises without a real production experience, would you apply for the job? or let it go :-D
Bear Bibeault
Author and ninkuma
Marshal

Joined: Jan 10, 2002
Posts: 60992
    
  65

Apply for the job. Those lists are usually ridiculous kitchen sink requirements. If you are missing a vital item, they'll let you know.


[Asking smart questions] [Bear's FrontMan] [About Bear] [Books by Bear]
H Paul
Ranch Hand

Joined: Jul 26, 2011
Posts: 410
    
    3
A very encouraging answer from your part.
Chan Ag
Bartender

Joined: Sep 06, 2012
Posts: 1011
    
  15
I don't understand such requirements. I recently saw one for 2-4 yrs' experienced candidate. They expected somebody who was excellent in data structures and algorithms, multi-threading and collections, network programming, Regular expressions - good to know, J2EE, Object oriented design principles, Spring Framework, JDBC, hibernate - good to know, servlets, jsps, JavaScript - good to know.

Oh and I forgot, the 'do you know Python' and 'have you ever coded in a functional programming language before' questions.

How can a junior engineer know so many things. I mean it's just sort of not possible. I don't know if such vacancies are ever filled.
Jeanne Boyarsky
internet detective
Marshal

Joined: May 26, 2003
Posts: 30294
    
150

Sometimes they want to pay less. Sometimes they want to show they can't fill the position. Sometimes they don't know what they are asking.

As far as the do you know X questions - they might not be requirements. They might be curious. Suppose the job is 5% Python. It's great if you know it, but not a deal breaker.


[Blog] [JavaRanch FAQ] [How To Ask Questions The Smart Way] [Book Promos]
Blogging on Certs: SCEA Part 1, Part 2 & 3, Core Spring 3, OCAJP, OCPJP beta, TOGAF part 1 and part 2
Luke Kolin
Ranch Hand

Joined: Sep 04, 2002
Posts: 336
Part of what drives some of these is the "Bob Replacement" ad. Bob starts working at a company, doing X. Over time, he picks up some different skills and tasks and is doing a little bit of everything. Then Bob decides to leave, and the company puts together a list of everything Bob was doing and combines it with his starting pay and experience.

Then they wonder why they can't find anyone.

Cheers!

Luke
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: Job requirement: not having everything listed.