Reaction to React.JS Job Descriptions?

Are you a ReactJS developer?

If so, the opportunity summaries you might be seeing in the marketplace may appear to look the same.

Need some of the job responsibilities to help you recall? How about these bullet-points:

  • “Experience with popular React.js workflows (such as Flux or Redux)
  • Familiarity with newer specifications of EcmaScript
  • Experience with data structure libraries (e.g., Immutable.js)
  • Knowledge of isomorphic React is a plus
  • Familiarity with RESTful APIs”

These look familiar?

If they do that is because there are many react.js job postings that include these bullet-points within them. Don’t believe me? Copy and paste between the quotes, and you should get a few returns that demonstrate what I mean.

OK, so maybe some of these responsibilities are the same, but that does not mean the job descriptions are….right?

Copy and paste this into your favorite search engine:

“We are looking for a great JavaScript developer who is proficient with React.js. Your primary focus will be on developing user interface components and implementing them following well-known React.js workflows (such as Flux or Redux). You will ensure that these components and the overall application are robust and easy to maintain. You will coordinate with the rest of the team working on different layers of the infrastructure. Therefore, a commitment to collaborative problem solving, sophisticated design, and quality product is important.”

What did you find?

If you got the same results I did, there were a number of Job Opportunities that looked exactly the same. They not only had the same bullet-points, but also the same descriptions (it appears to be a template from here).

OK, why am I trolling on this? 

I am trolling on this because right now, ReactJS developers are in high demand, which is probably why some of these posts even exist. While I understand the potential reasons in using a post like this to attract a React developer to your organization, how are you differentiating yourself against the many other companies looking for this type of talent (like your competition)? If your job description looks like everyone else, your company will not stand out. That is why I am trolling on this type of job description…it is basic and offers virtually no employee value proposition, nor does it address some of the technical-business challenges your company faces, which will help attract the talent you are seeking.

With developers in short-supply and very high-demand, in my opinion, a job description like this will get you around the same amount of quality candidates as the effort that was put into it….very little.

What are your thoughts? Comment and share!

One thought on “Reaction to React.JS Job Descriptions?

  1. As a note, I will self-admit I am not the best at writing job descriptions, and I do see the value of using a template; however, some-level of customization should exist within their usage.


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s