Ruehie Jaiya Karri

Author
Ruehie Jaiya Karri

Blogs
Always interested in the “road less traveled”, she went from being a developer to a writer - her dream career. Her writing is simple and uncomplicated, two things she strives to achieve in her life. When not writing, you’ll find her curled up on her couch watching a rom-com or reading a book. A believer of dancing away her blues and a lover of coffee, she is also super passionate about baking.
author’s Articles

Insights & Stories by Ruehie Jaiya Karri

From code to content, Ruehie Jaiya Karri brings a unique perspective to tech and talent assessment. Explore her articles for insightful, easy-to-read takes on hiring trends, recruitment best practices, and the ever-evolving world of technology.
Clear all
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.
Filter
Filter

Recruiters Versus Bias: Who’s Winning This War?

Gender. Race. Caste. You name it and people will find a way to be biased about it. Bias is part of the human psyche. It comes inbuilt, ingrained and imprinted within the human brain. Instead of furiously denying that you are biased, start recognizing the fact that you are, indeed biased, whether consciously or unconsciously.

Why am I ranting about bias, one may wonder. To tackle the concept of bias in recruitment in the tech space, I need to first get it out of my system. Get out the fact that I cannot abide by people who put a negative spin on everything. Get it out that I am biased about coffee. Get it out that I am biased, period.

Now I can take a deep breath and aim to answer the age-old question of ‘Recruiter vs bias: Who’s winning this war?’

Saying it out loud that bias exists is the first step. Not all biases are bad. We need to identify the biases that are unrelated to the task at hand, and give them a good kick in the shin. With that out of the way, we can get on with our job.

Staying neutral is either a myth or a robot. To some extent.

What is bias in recruitment?

Recruiters and hiring managers come across several candidates in a day during the recruitment process. It’s not hard to imagine the various ways in which their choices can be influenced when hiring an employee.

Be it the gender of the person, a fancy pedigree on a resume, or a varied ethnic culture, you are constantly making decisions based on first impressions.

In simpler terms, bias affects your ability to make decisions, either positively or negatively. When you start looking at criteria that are unrelated to the performance of an employee, you might make the wrong choice.

Why is all the talk about unconscious bias?

The year 2020 saw a wave of incidents that arose out of bias, be it George Floyd, the BLM movement to counteract it, the election results or the subsequent protests in the US. While systemic bias has been ingrained in the society for decades now, these incidents served as a catalyst for every sector to sit up and take note of their own unconscious biases.

Unconscious bias is more harmful than biases related to gender, ethnicity and race because most people don’t realize that they are unintentionally harboring prejudices.

We would like to believe that we are ethical and unbiased and good decision makers but sadly, that is not the case. There are stereotypes and biases simmering away under the surface and the sooner we bring it to light the better.

The representation of minorities in the tech industry has always been low. Facebook has an African-American workforce of 3.8%. Google stated that 5.9% of its employees are Latinos and 3.7% are African-Americans. These numbers are the same or dip even lower across all the big tech companies.

It's the easiest thing for a recruiter to relate more warmly to a candidate from his alma mater than one who is not. Psychologically, this is known as affinity bias in recruitment. If the person shares values and traits similar to his predecessor, he is more likely to get the role. This is an example of similarity bias. A Yale University study showed that both male and female recruiters showed preference to male applicants and were willing to pay them $4000 more than the women.[ebook_further_read]

How to avoid the murky waters of bias in recruitment?

When stirred, the murky waters of prejudice and stereotypes only get murkier. It is highly encouraging for me to see that many tech recruiters don’t mind getting their feet muddied. Tech hiring is undergoing a radical shift with recruiters realizing that the academic pedigree of a developer or where one works from doesn’t matter.



How recruiters are tackling bias



We, at HackerEarth have put out a report on developer recruitment, which showed that recruiters are prioritizing geographic-unspecific hiring. They are moving towards blind hiring as shown by the dramatic increase in the use of our technical interview solution FaceCode.

It enables you to conduct structured interviews for all candidates where there are pre-determined scoring systems. FaceCode allows you to define evaluation parameters. They act as a scorecard for interviewers to manually assess candidate skills during the interview. This helps reduce discrimination issues or bias during hiring.
Recommended read: State of Developer Recruitment 2020
We should all take a leaf out of the Boston Symphony concept. I came across this concept while reading Claire Cain Miller’s article in the New York Times magazine. In the 1970’s, the Boston Symphony Orchestra decided to test the outcome of blind auditions. This was due to the fact that orchestras were dominated by white men. Musicians, both male and female auditioned behind screens so the judges had no idea who was auditioning. Once anonymity was embraced, the results were a lot more fairer than before. Women musicians became more likely hires than men (between 25-46%).

Adopt a blind resume evaluation process where contact and personal information about the candidate is removed. By making use of our application screening software, it is possible to keep the hiring process blind for a large part.

Also, implement a collaborative hiring process. People with different backgrounds and perspectives interview candidates together. This helps make the recruitment process as unbiased as possible.

The scales are tipping in favor of…

Ways to win the war against bias

Recruiters attempting to stop bias in its tracks. The lengthy, heated discussions around hiring bias and its consequences lead me to believe that it is one step in the right direction. Instead of shying away from uncomfortable conversations around bias, people are trying to build a system devoid of bias.

At HackerEarth, we believe skills trump everything else and there is no room for bias. The stats shown in our study and the increasing numbers using our remote interviewing software, FaceCode reinstates my faith in people. They are willing to commit to change, bringing us a lot closer to winning the war against bias, than ever before.

Contribute To The HackerEarth Blog!

Guest Post Blogging Guidelines

As a guest contributor, you agree to allow HackerEarth to publish original articles written by you on HackerEarth’s website.The content HackerEarth accepts must: comprehensively cover a topic, be presented from a neutral and unbiased position, and provide informative and educational content for our readers.Example topics include:
  • industry best practices
  • tech hiring trends & updates
  • hiring biases and information for recruiters
  • diversity and inclusion
  • coding insights for developers
  • personal insights/opinions on the tech hiring process to the extent that it doesn’t defame or libel
These are just some of the topic ideas you can write about. We are open to your suggestions if they meet the criteria above and serve our primary goal; to support recruiters and hiring managers in staying up to date on advanced recruiting insights, trends, and best practices.When writing your article, please keep in mind the guidelines below to ensure your article will be accepted and published.

Guidelines for the content within the article

1. We require you to send an outline for the approved topic. You can begin writing the draft once the outline is approved.

2. Submissions should be kept between 1500 – 2000 words. We use American English in our posts.

3. Formatting of the blog: The blog title should be in the Title case. All headers should be in sentence case, not title case. This means all headers should be lowercase except for the first word of the header and any proper nouns or acronyms.

Title case: A simple example would be Lord Of The Flies, where the first letter in each word is capitalized.

Sentence case: A simple example would be Lord of the flies, where only the first letter in the first word is capitalized.

4. Tone of voice: You must write in second-person, not first-person. This means the content should be written in the “you/your” voice, not the “I/me/my/mine” voice. The article must remain completely non-promotional. Additionally, we prefer an informal, conversational tone. Use contractions and list out all acronyms you write.

5. Readability: Please ensure no paragraph is longer than 4 sentences. Use short sentences and keep the sentence length to less than 20 words. Write in Active voice.

6. Please run a thorough Grammarly check and make sure the score is above 95.

7. Please provide a meta description of 140-160 characters explaining your article.8. How to email your guest post to us:
  • The completed post must be a Google doc
  • Send your posts to blog@hackerearth.com
9. The blog post/article must be your own original work that has not been published on any other website, forum, chat, or social media network.10. Plagiarism or copyright infringement is not permitted. When quoting others, please make sure to cite your source properly.11. All blog posts are reviewed and approved by HackerEarth before posting. HackerEarth reserves the right to edit blog posts where necessary.12. All content must be completely vendor-neutral. If a blog post submission is inappropriate or needs improvements, a HackerEarth representative will let you know and offer suggestions so that it may be published later.

Guidelines for SEO

13. The primary keyword should have a 1000 monthly search volume & 5 secondary keywords must have a 500 monthly search volume, which must be shared along with the outline.14. We accept 2 external links (do-follow) + 1 external link (no-follow) within the article. Links to any third-party site must be relevant to the topic and approved by HackerEarth.15. The target external link should have more than 30 DA and 40 DR.16. Anchor text for backlinks should not be related to our core business keywords.17. Links should not be in the first paragraph of the blog article.18. The target URL must be a blog article, product pages for the target URL are not allowed.19. All search engine optimization ("SEO") information, such as anchor text or alt tags, will be reviewed and subject to inclusion at the discretion of HackerEarth.

Guidelines for Author Bio

20. [IMPORTANT] Blog post writers may submit a short bio statement (no more than 50 words). Please also send in a square headshot (at least 200x200) to be used on your profile.21. Blog post writers will be allowed to have one link to their website and one link to their social profile within the author acknowledgment.

Guidelines for distribution on social media

22. We ask that you ensure to share the guest article on all relevant social media platforms like LinkedIn, Instagram, and Twitter. Post that, we will do the same on our official company social media.23. Additionally, we can discuss a newsletter swap if you have a newsletter with a sizeable number of subscribers.

Additional guidelines for the overall collaboration

24. Once the post has been submitted to HackerEarth, you may not publish it anywhere online, in part or in whole, including your own website or blog, without the consent of HackerEarth.25. HackerEarth will share and promote the blog post but does not guarantee any site or audience reach.26. If HackerEarth uses your guest post, you may promote it on your own website, Facebook, Twitter, or other social media forums. Promoting does not mean you post the entire article on these forums. You may include a link to your guest post and a short explanation of the article.27. Posts will acknowledge your authorship but will be the property of HackerEarth.28. Affiliate links shall not be included in guest post submissions. HackerEarth reserves the right to add its own affiliate links where appropriate.29. Excessive links or links that appear to be affiliated or spam-related will be removed at the discretion of HackerEarth.30. We do not pay for submissions. If you decide to submit a post to our site, you do so with the knowledge that you shall not be entitled to any compensation for writing the post or for any other compensation related to the post.31. HackerEarth reserves the right to refuse publication or remove a blog post without prior notice to the blog post writer.32. By providing a blog post to HackerEarth, you agree that you are in no way becoming a part of the website or company, nor shall you hold yourself out to be a member of the HackerEarth website or company.33. We expect to receive all submissions on time. If you miss your deadline, your post will not be published. If you need an extension to your deadline, please let us know ahead of time.