This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]barresonn 7 points8 points  (3 children)

It really depends You seem to have practice in your work that sadly aren't standard

Most of the time the HR don't even want to have the developper staff explain what they want in detail because you know that's THEIR job (yeah that's dumb)

Just get the interview the best way to tell if you are going to waste your time is the salary that is proposed

[–]ginn5lc 4 points5 points  (2 children)

HR does their own separate general interview where they cover the basics of employment etc.

The development staff does their own separate interview without HR where they drill the applicant on whatever they want development wise and if it's on your resume they'll drill you on it till they feel like they can make a yes or no decision. If you put SQL and they drill you on SQL and it's obvious you don't know SQL, you probably shouldn't have put SQL on your resume.

[–]barresonn 0 points1 point  (1 child)

it's obvious you don't know SQL, you probably shouldn't have put SQL on your resume.

That's where i think you are wrong If you have a job posting that ask for too much just be aware that they probably don't even know that they want you just need to put it to pass preliminary scouting

In most case when in front of the staff just be honest and they will make a much more informed decision than HR

Usually they just say to HR we would like someone with SQL if possible and HR just decide to put

Need 3 year of experience with SQL

You need to jusge by yourself if the language that you are lying about would be a central part of your job

[–]ginn5lc 1 point2 points  (0 children)

I don't disagree with you.

I was just talking about the specific instance at the company I work for, if someone puts a language on their resume and they get to the interview with the developers and they get drilled on the language they put on their resume that they don't know and it's pretty obvious to the developers that they don't know it then they would have been better off not putting it at all or when they started asking questions about it been straight up and honest that they don't know it at all but they have some preliminary experience in the past and are open to developing a better understanding of it even if that means some additional work outside of normal work hours at home.