DEV Community

loading...

Discussion on: You're not worth hiring unless...

Collapse
iwelch profile image
Isaac Welch

My company's job postings include the requirement of being proficient in any major framework. (React, Angular, Vue) even though we use Angular primarily. We do this because we look for good talent and our okay investing in educating someone with potential on the ins and outs of a certain framework. In fact most of our developers came from a react background. (including me)

Collapse
saturniusmons profile image
Shane

I see adverts saying things like "We'll take people with no experience in foo, as long as they can show experience in bar" followed by a tech test that must be done in foo.

Why waste people's time???

Thread Thread
iwelch profile image
Isaac Welch

I agree that that is a really bad practice on those companylies' parts. My company does have a coding challenge, but we let people use whatever framework they are comfortable with. (We have gotten some and passed candidates with coding challenges in all major frameworks)

Collapse
jennrmillerdev profile image
Jen Miller • Edited

I think the primary framework is important to state. I'm starting to see job postings that list almost every technology under the sun or none at all (in a way to be inclusive), but in reality, they make deciding to apply or not confusing, espically, if you ideally want to go to a place that uses a modern component based framework (React, Angular, etc).

For example when places list both jQuery and React.

Thread Thread
tsigie profile image
Tsigie

I understand why some companies ask for jQuery and React because our company is working on the project updateting clients' projects from jQuery to React. In order to do that you have to understand both libraries very well.

Thread Thread
jennrmillerdev profile image
Jen Miller

hmm, yah that's totally fine. In fact, my past job, I did that (upgraded older apps) - so I think it was my fault I wasn't clear in my example.

My main point of issue is when organizations are not up front about the 'primary' technology when they list dozens of wildly different stacks to for the sake 'inclusiveness'.

IE if a dev wanted react knowledge but ended up working on jquery their whole time, they would probably not be to happy.

Collapse
devingoble profile image
Devin Goble • Edited

As long as that intent is clearly communicated in your postings. Otherwise, I feel like I still want to see specifics of what I'd actually be asked to use. It helps juniors decide where to specialize, and it gives established folks the flexibility to be more picky. If the company was awesome, I'd be willing to go for it if I didn't know a particular framework. I'd like the opportunity to address that in my cover letter and in my early conversations.

EDIT: A short anecdote... Last year, we interviewed two people for one position. One person had a veritable 💩-storm of keywords in their resume. The second person had a more focused resume. The boss ended up hiring the first person because they theoretically ticked more boxes. The resulting 💩-storm caught the boss completely off guard.

Thread Thread
willsams profile image
Will Sams

I believe I'm working with that 💩-storm at the moment...

Thread Thread
codefi profile image
Frank Owusu-Agyemang

I know one 💩-storm, he feels bossy about one framework and thinks it will work for all without looking at the cons