Logo
X

Get awesome marketing content related to Hiring & L&D in your inbox each week

Stay up-to-date with the latest marketing, sales, and service tips and news

Notes in environments for project-based questions

We have introduced an option to add and view notes for environments that are created in project-based questions (I/O).

This will be helpful in storing and accessing important information or metadata related to the environments such as DB credentials, configurations, environment variables, value for properties used in a project, etc.

Notes Action Icon - I/O

Adding and viewing notes

Notes for an environment can be added/viewed by clicking the “Notes” action icon present towards the right of the environment name on the manage and select environment pages.

Users will be able to add, edit and view notes to the environments that they create. For “Mettl Environments”, users will only be able to view the notes.

Know more

To understand more about Mercer | Mettl’s project-based development environment, click here.

Plagiarism enhancements on our backend coding environment

We are extremely excited to inform that we have made major enhancements w.r.t plagiarism score calculations on our general-purpose backend coding environment (CodeLysis).

Below mentioned are the key highlights:

1. Enhanced scalability of plagiarism for large-scale drives

We will now be able to support even larger-scale drives seamlessly.

The recent changes have optimized the plagiarism calculation, thereby reducing the overall TAT drastically.

2. Improved accuracy in calculation of plagiarism scores

We have made multiple advancements and changes to improve the quality of scores calculated in order to provide valid potential matches between test-taker codes. The changes in our improvement have significantly brought-down the number of false positives.

Additionally, we have introduced new tags such as N/A and No Matches to classify test-takers basis their plagiarism scores for faster and easier filtration rather than using the traditional Acceptable and Not-Acceptable.

Find more details here: [Link]

3. Making plagiarism threshold configurable.

By default, our plagiarism threshold is fixed at 60%, but now users can customise this value basis their requirement. As soon as the threshold is configured (before or after the drive), the changes will be reflected in the reports and the test-takers will be tagged into suitable plagiarism tags accordingly.

Configure Plagiarism Threshold

Here’s a step-by-step guide: [Link]

Linking of test-taker code errors on our backend coding environment

We are excited to share that in addition to highlighting the lines having errors and warnings directly in the CodeLysis code editor, we now also provide linking of errors from the console itself. The errors/warnings are linked to their exact location in the code and clicking on the link takes the user directly to that line.

This functionality will further enhance the coding and debugging experience of test-takers and will provide them with a more feels-like-home IDE experience.

Error Linking

Next-gen of our project-based development environment

Continuing our efforts towards enhancing test-taker’s experience, we have launched the next-generation of our project-based development environment (I/O).

This comes with a new and modern UI with improved user-experience.

I/O walkthrough

It also provides a UI walkthrough highlighting the key components of the environment. This will help test-takers who are new and unfamiliar to modern IDEs based programming environments.

Hope you are as excited as we are to let the test-takers get a feel of the all new project-based coding environment!

Error highlighting in backend coding environment

In our efforts to make the user experience for test-takers even better we have made big updates to our general-purpose backend coding environment (Codelysis).

The code editor now highlights specific lines which have errors and warnings in them. It also provides the exact character location and description of the errors/warnings.

codelysis error hilighting

This functionality is meant to enhance the coding and debugging experience of test-takers who find it difficult to understand logs and will assist them in understating the issue(s) with their code.

Hackathon Platform Update : Improving Judging Experience

Hello everyone,

We are happy to share recent key product updates to Xathon. These updates have been mainly focused on use cases for hackathon judges and hackathon administrators on allocation and management of judges. Please see below:

 

 

 

 

  • Judge’s submission feedback now available to admins

An admin can now see (in UI) and download (in excel) judge’s feedback for a submission. They can see not only the latest feedback (n) but a previous one (n-1) as well, in case of multiple feedbacks given at different points in time.

 

  • Ability to restrict showing submission feedback to participants

An admin will now have the ability to restrict displaying the feedback to the participants and limiting the same to him/herself. This will help in scenarios where our customers may want to mediate the communication on evaluation of submissions.

 

 

  • Judges can now request resubmission from participants

If needed, a judge can now request a resubmission from participants. This will allow the participant to re-upload a submission for the duration of the round. This will be possible only in case of non-team events.

 

 

 

 

 

  • Manual allocation of Judges for Assessment as a Challenge

An admin can now allocate judges manually as well for assessment as a challenge in the manual evaluation round. This can be done using the existing Judge mapping sheet.

 

 

Other Key Improvement 

No ‘Team creation’ needed for participants in case of an individual event

Based on feedback from our key customers, we can altered the event registration flow for individual events. Participants will not be asked to create any team for such events. This should improve the UX in the event registration step.

 

 

 

 

Hope you are as excited as we are to try out these recent enhancements. Please feel free to reach out in case of any further information.

Cheers!

Best regards,

Kapil Malik

AVP, Products @ Mercer | Mettl

 

 

Proctoring features enhancement for I/O

We are happy to announce that the following of our proctoring and anti-cheating features are now available with I/O.

 

Browsing Tolerence
With browsing tolerence enabled you can prevent candidates from navigating away from their test window. You can set a limit to the no. of times a test taker can navigate away from their test window before their test gets automatically submitted.

 

Advanced Visual Proctoring

Proctort test using our AI-based automated proctoring technology that uses candidates’ webcams, and microphone feeds for auto invigilation. Live proctoring through expert human proctors for high-stakes exams can also be done. Candidates’ screen can also be captured and made available for future references.

 

Record and Review proctoring

Record and review proctoring is best suited for low-stakes tests. Proctors review the recorded video feed of students, ascertaining the flags generated by the AI bot.

The flags are combined into a report called the ‘Credibility Index,’ with details such as timestamps, duration, etc. Reviewers can see the video to note the instances where AI has specifically flagged suspected behavior.

Launching the Next Generation of our Backend Coding Environment

Hello everyone!

 

We are extremely excited to launch the next generation of our Backend Coding environment. Around 90% of all our technical hands-on assessments currently leverage the backend coding environment, therefore it was imperative for us to prioritize this project to provide a world class technical test taking experience!!

 

KEY UPGRADES:

 

  • Clear, minimalistic and guided coding environment walkthrough

o   User behavior we want to push: Almost zero skips of the walkthrough as it is essential to understand this coding environment clearly, to reduce test takers failing test cases due to lack of understanding of the platform.

o   A dedicated estate to the walkthrough on reaching the coding question with emphasis on taking the guided tour.

o   Simple and minimal text, highlighting important information such as what to solve?, where to solve? and how to solve?

 

  •  All new ‘Submit Code’ button

o   In addition to Compile & Test, we now have a Submit Code button that runs the graded(earlier called weighted) test cases and shares a clean summary of the result. Earlier this was internally done as a part of compile and test operation. We have now decoupled testing and submission as they serve two different intents to the test taker.

 

 

 

  • Introducing ‘Code History’ !

o   Each code submission is now going to be available to the test taker at all times during the test for reference.

o   Below is a summary screen of the code history section, it clearly mentions the language, timestamp and no. of test cases passed in that submission.

 

 

o   Below is a screenshot of a submission. The test taker can open her code in the editor in a single click with ‘Open in Editor’

 

 

 

  •   We now have two grading options

o   Customers can now choose to consider two alternatives to grading the test taker code

§  latest submission or

§  the submission where maximum marks are scored

o   With this, we aim to further reduce the test takers scoring zero scores/failed test cases due to any last minute rush leading to say a compilation failure on an earlier correct code.

 

  •   Say NO to switching between screens every time you compile your code!

o   Every time we force new screen or tab on top of another screen, it leads to reduced context, clarity and concentration for the test taker. Until now, we had the test taker move to a different screen on compile & test. The test taker had to navigate back and forth for critical tasks such as debugging errors. There were a total of 7 tabs/screens switches.

o   We have reduced the screens switches to ZERO, period!

o   Only two tabs exist at the bottom serving very clear purposes

o   Example of a compilation error within the same screen.

o   Example of a successful compile and test

 

·         Other UI/UX enhancements

o   Easy access to editor shortcuts with a single click

o   Easy access to dark mode

o   And so on…..

 

 

Hope you are as excited as we are to let the test takers get a feel of the all new Coding Environment!

 

Cheers!

Kapil Malik

AVP, Products @ Mercer | Mettl

 

Hackathon event creation experience: Upgraded!

Hello everyone!

 

Happy to share that we have done a massive upgrade to the hackathon event creation experience with the intent to make this key flow self-serviced. This is aligned to our vision for Xathon as a self-reliant platform for creating, managing and monitoring hackathons and ideathons. We know that our customers want complete control, and that is exactly what our remodeled event creation flow gives. Ease of use and practicality are at the center of this update along with other incremental usability enhancements and a new look and feel.

 

Key enhancements:

  • We have introduced a real time preview mode for our customers to visualize the event landing page as they progress, before actually making the event live.

  • We have introduced banner and logo templates for streamlining creative assets for an event.

 

  • We have restructured all the pages into more appropriate categories for ease of use. For example—clubbing relevant configurations under sections such as- event details, team details, SEO etc.

  • Implemented Mettl Design System 2.0 to make Xathon more cohesive and connected with other Mettl Products

 

 

We believe that these changes will open new markets especially in the international geos and conversations where customers want to create events on their own.

 

Cheers!

Kapil Malik

AVP, Products @ Mercer | Mettl

Stay up to date with the latest features and skills on Mercer I Mettl

Stay up to date with the latest features and skills on Mercer I Mettl