-
Assessments: Recruiters
- Getting started
- Account settings
- Admin management
- Creating tests automatically
- Creating tests manually
- Test settings
- Sections and question pooling
- Libraries
- Multiple Choice Questions (MCQs)
- Programming
- Full stack
- SQL
- Data science
- Machine Learning (ML)
- DevOps
- Python project questions
- Selenium
- Java Project
- C# project questions
- Subjective
- Approximate
- Diagram
- File upload
- Invites
- Reports
- Billing
- HackerEarth Reports: Admins, Tests, and Teams
-
FaceCode
-
Assessments: ATS integrations
-
Assessments: Product updates
-
Assessments: Best practices
-
SSO
-
Upskilling
-
Assessments: Candidates
-
Problem setting for HackerEarth
-
Campus
-
Hackathons and Hiring Challenges
-
Frequently Asked Questions (FAQs)
Best practices
Your business is only as good as the people who keep it going.
Hiring the right people is a problem that every organization struggles with and it all starts with creating the right test to screen candidates. The right test not only reduces the effort put in by the recruitment team but also saves countless man-hours and money that is spent on interviewing the wrong candidate.
This section comprises the best practices that we recommend that you use while creating a test on the HackerEarth Recruit platform.
Note: We strive to ensure that you have the best experience while using HackerEarth Recruit and therefore this section will be updated regularly.
We have compiled the following best practices for you: