What will be your expert level when you get the job?

I was wondering that how many of us know about something when we walk in a interview to getting a job and after getting job. Suppose I get a job due to my knowledge in that field as I studied some blogs, so I got the job, I start work and eventually I work and work and learn on my own. Slowly I get expertise in that job and things goes on fluent.
In other words, suppose I am web developer and my next require JavaScript, like 90% of work is JavaScript and I don’t have much knowledge of JavaScript, still I got the job.
So is it like that in market or I am thinking wrong?

AFAICT you wouldn’t get the job in the first place – actually, I don’t think they’d even invite you to an interview. Why should they? Of course, it depends on what kind of job you’re after… as a student employee or apprentice you’re supposed to learn there, after all.

But if you want a regular job as a web developer, you’ll usually need to have studied computer science (either with focus on web development or some work experience in that area) or a completed training. You won’t get hired because you’ve read some blogs anyway.

It might be acceptable if you’re not (yet) familiar with a certain specific framework or CMS which are getting deployed there. It depends on how heavy the focus on that technology is. But you’ll certainly need to have some substantiated knowledge of the underlying languages, so that you can quickly come to grips with anything else based on that.

1 Like

There are many, many reasons you could get a job without having the requisite skillset before your onboarding.

I can rattle off a few

  • The employer is interested in your experience or resume
  • The interviewer is sold on your abilities (problem solving, self starter, teamwork, clean code writing, the list could go on forever) and believes that learning new technologies would just be a bump in the road. Many people believe in hiring talent, and not in hiring knowledge (There’s a SitePoint article about getting hired - featuring an interview with Atlassian recruiters - that discusses this. Disclaimer: I wrote the article. http://www.sitepoint.com/getting-hired-developer-tips-senior-recruiters/)
  • The company hiring you has no one there capable of the discretion needed to hire someone with the relevant skillset. Example: A small to mid sized business with an internal IT department and a .NET development team for internal and customer facing applications is hiring a PHP developer for an application they acquired, but do not realize the pervasive amount of JS framework knowledge that will be needed to fill that role - more so than the PHP work. That’s a specific example, but there are literally thousands of companies out there that, even with some internal IT workings, will not have the knowledge to hire the exact right person. It’s your job to spot that and either rise to the challenge or warn them about what they really need and move on.

That all said, there are certainly many, many times when [quote=“m3g4p0p, post:2, topic:210997”]
But you’ll certainly need to have some substantiated knowledge of the underlying languages, so that you can quickly come to grips with anything else based on that.
[/quote]
is absolutely true. It all just depends on the employer, and the situation.

FWIW if I was doing the hiring, it would depend entirely on the role. I’d lean towards hiring talent as opposed to knowledge, but if it was a mission critical, time sensitive role… I’d hire someone who could step in and know what they needed to know already.

1 Like

Yeah, you’ve made some very good point there I haven’t considered, @jeffreylees. Someone with profound experience as a web developer might certainly have little difficulties in finding such a job, even if they have no direct expertise in a certain required skill.

However, I don’t think this is the scenario as described by @nofel. First of all, I can hardly imagine that such a person doesn’t know JS, or got all their little knowledge from studying some blogs for that matter. Furthermore, it’s been stated that this certain skill is an explicit requirement (like 90%).

There may be exceptions, but as I understood the question it’s more about the usual way things go… which is more like, you’ll get a task to accomplish within a few hours and the solution will be reviewed by your prospective head. And if the task requires 90% JS… well, you might still be able impress the head, but it won’t be easy.

But I don’t want to nitpick. :slight_smile: As you’ve been doing hiring yourself, you’re certainly more of authority in that field than I am! I can only tell from what I have experienced as an employee… so thanks a lot for the interesting link! Might come in handy in future. :stuck_out_tongue:

Sorry, I didn’t at all mean to indicate that I was referring only to people with really well developed skill-sets.

I guess that’s where I find the question hard to answer. Is that the usual way things go? How do you know? I know my own limited job experience has been pretty different from employer to employer. One of them didn’t expect me to have any particularly useful code for over a month and was surprised when I did. One of them expected results on my first set of issues within days, around the paperwork and office set-up hooplah, hehe.

I agree with you that if they need someone busting out JS code from day one, and the OP comes into the job with some blog-fed knowledge, but no real handle on JS, things will unravel fast. I’m curious, though, if it’s really a high-stress/demand environment (no offense OP) how did they land the job without the requisite knowledge? Or are we being asked hypothetically if you could get the job, @nofel? If the latter… I’d say you’d be better off learning what you need first, unless you know they will allow you some onboarding time to learn their technologies. Don’t get in the awkward position of getting into a job that you just can’t do.

Haha, I said “If I was doing the hiring” - I don’t hire anyone, in my current role :smiley: It’s just me and my computer in my end-of-the-dead-end-hallway-office :smiley:

Hm, I might indeed have misunderstood (or overinterpreted) the question. If you’re candidate for a rather specific job, demonstrating your skills is quite usual IME. (Not that I’m an expert, though! :no_mouth:) But then again a company may just be looking for a general reinforcement of the team, in which case you might well “grow into” the job (which again might eventually turn out to require a lot of JS); however in this case I think they wouldn’t state clear and straight requirements such as: we need a JS programmer.

Sorry for the confusion! I concur that such situations can be very different, I just assumed that @nofel had a quite a specific scenario in mind.

Oh, d’oh on me then! :smiley:

I’d agree, that’s probably true for the most part (Unless the company doesn’t know what they’re doing, or changes your role after you start, or is simply looking for a good programmer/problem solver and willing to give you time to onboard).

Hopefully, if they are asking specifically for a JS programmer, they’d be testing for JS skills and the problem would be a moot one, as our OP would either pass or fail on merit… but then I guess there are a whole lot of professional programmers who can’t code, so… that’s disturbing too.

Oh, d’oh on me then!

Maybe I can tell my superiors that while we’re rearranging the department at a global/corporate level, I need a promotion to a managerial role because SitePoint says so? That’d work I think…

I wish :frowning:

Sidebar: I wonder what these people who masquerade and pretend to have the skills / experience they need do once they have the job? Surely someone notices sooner than later, right?

2 Likes

lol They go to SitePoint and hope others will do the work for them

Most recruiting adverts I’ve seen usually look straightforward i.e.

Lists of both “Must Have” and “Is a Plus”

I’ve always figured the “good to know” stuff is for skills that would be OK to learn after being hired and the “must haves” for skills that will be expected right away

IMHO honesty is the best policy.

I believe I know more than some but I also believe I know less than a lot of others

I can understand how when just starting out writing Hello JavaScript, PHP, Perl, Python, Java, Go, etc. etc. code gives a satisfying sense of accomplishment, but it would be folly to pass that off as “have experience with”

1 Like

Yeah. Too bad most recruiting adverts are not even written by developers.

Yeah, I usually assume that too.

This is precisely it, IMO.

You can often spot the “we don’t have a clue” ads: the “must have” includes everything known to mankind, and the “is a plus” contains anything they might have missed in the “must have” :wink:

4 Likes

This topic was automatically closed 91 days after the last reply. New replies are no longer allowed.