# HackerEarth Question Library: Stats, Usage Analysis and Health

DevFeed: [HackerEarth Question Library: Stats, Usage Analysis and Health](<https://devfeed.tech/articles/hackerearth-question-library-stats-usage-analysis-and-health-19997.md>)

Original publisher: [Read original article](<http://engineering.hackerearth.com/2015/10/31/hackerearth-question-library-data-analysis-and-health/>)

Published: 2015-10-31T00:00:00Z

Content type: article

Language: en

Sources: [HackerEarth](<https://devfeed.tech/sources/hackerearth.md>)

Topics: [Library](<https://devfeed.tech/topics/library.md>), [data](<https://devfeed.tech/topics/data.md>), [coding](<https://devfeed.tech/topics/coding.md>), [Programming](<https://devfeed.tech/topics/programming.md>), [Data structures](<https://devfeed.tech/topics/data-structures.md>)

Tags: [coding](<https://devfeed.tech/tags/coding.md>), [data](<https://devfeed.tech/tags/data.md>), [developers](<https://devfeed.tech/tags/developers.md>), [feature](<https://devfeed.tech/tags/feature.md>), [improvements](<https://devfeed.tech/tags/improvements.md>), [library](<https://devfeed.tech/tags/library.md>), [programming](<https://devfeed.tech/tags/programming.md>), [support](<https://devfeed.tech/tags/support.md>), [technical](<https://devfeed.tech/tags/technical.md>)

## AI overview

This article describes HackerEarth's Question Library and the development of a "Health" feature that helps recruiters identify more usable assessment questions. Health is calculated from factors including question accuracy, usage frequency, and recency of use, after data analysis and storage design.

## Source excerpt

We, at HackerEarth, cater a huge number of questions in Assessment tool. Recruiters can choose from wide varieties of Multiple Choice and Programming/Coding questions to assess candidates. Every week or two, new questions are added to the Questions Library. As the time passed, thousands of questions got stacked up and recruiters started to have a hard time figuring out what questions to choose from such a huge library. We, developers, work closely with our sales team to understand recruiters' needs. Sometimes we directly get in touch with recruiters to provide on call technical support and understand how they use the product and what improvements can be made to the product in order to make it more easier to use. That's how we figured it was about time we helped recruiters figure the best questions out of our library and hence we released a feature called "Health". What it means? Health, in context of any library question, indicates how usable the question is. It is not only about question's difficulty level. We consider various factors such as number of users attempted the question, users solved, times the question has been used and when was the question last used while determining Health of any question. Simple and short, higher the health, more usable the question. How we calculate the Health value? The whole process was split into 3 parts: Data Segregation and Analysis Data Structure to store Health data Mathematical formula to calculate Health value 1. Data Segregation and Analysis We tried to gather as much data as possible for any question. Then, filter out the ones that could help us in finding the health value. Number of tests in which the question was used When was the question last used in any test Question accuracy (Number of users who solved it correctly / Number of users attempted) Problem ratings (Ratings submitted by user for any question) Problem tags When was the question added How frequently the question is used When was the question last used We f