- Help Center
- Assessments: Product updates
- Release notes: HackerEarth Assessment
-
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
- Front end
- 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
-
Hiring challenges
-
Frequently Asked Questions (FAQs)
Release notes: April 7, 2023
Smart Browser
HackerEarth has introduced advanced proctoring settings that force candidates to attempt a test in a HackerEarth desktop application with stricter proctoring features than those provided by our browser test environment. This is done to offer stricter proctoring settings that can be instilled in the platform so that you can be assured about the proctoring of the tests you are conducting on our platform. To learn more about Smart Browser, read this article.
SQL schema and test case validation
HackerEarth will now be validating SQL test cases and schemas added by you when you create or edit SQL question types. You can upload invalid test cases and schema files before.
We are now validating the following:
- Individual schema files for each database type (MySQL, PostgreSQL, etc.)
- Schema files for each database against each other to check that they define the same schema. For example, MySQL schema is validated against the PostgreSQL schema.
- If test case input files match the data definitions in the schema files.
To learn more about SQL questions, read this article.