Articles
Mercer Mettl Coding Test: Format, Proctoring, and Preparation (2026)
Mercer Mettl coding test guide: formats, scoring, proctoring, Secure Browser, system checks, hidden cases, and a practical preparation plan.
A Mercer Mettl invitation can feel frustratingly vague. You may know the test is "technical" without knowing whether that means two algorithm problems, a SQL simulator, frontend implementation, multiple-choice questions, or a monitored coding project.
That uncertainty is part of the platform: Mercer Mettl provides the assessment environment, but the employer controls the format. The company can choose the questions, duration, languages, scoring, proctoring rules, and whether candidates receive results.
Once you receive the Mettl email, treat its instructions as the final source of truth.
Quick Verdict
Prepare for Mercer Mettl as an employer-configured coding assessment, not as one predictable exam. Expect an in-browser coding environment with compilation and test cases, but the actual experience may involve backend algorithms, SQL, frontend work, a project-style IDE, or knowledge questions.
Proctoring also varies. A test may be unproctored, watched live, recorded for review, monitored by AI, or launched through Mettl Secure Browser. Read the invitation, run the compatibility check early, and do not assume that another candidate's setup applies to yours.
What Is a Mercer Mettl Coding Test?
Mercer Mettl is an assessment platform used by employers and educational organizations. Its coding products include general-purpose backend programming, database query, frontend, and application-development simulators. Employers can also mix coding questions with other assessment types.
The official coding platform describes automated grading through predefined test cases and employer reports with code analysis. A separate campus assessment shows two coding problems in 40 minutes, but that is one published template for entry-level hiring, not a universal Mercer Mettl format.
Mercer Mettl Test Formats
| Possible Module | What You May See | How to Prepare |
|---|---|---|
| Backend coding | Problem statement, editor, compiler, and predefined test cases | Practice arrays, strings, maps, sorting, parsing, and edge cases in one language |
| Database or SQL | Query editor, database engine, output, and test-case validation | Practice joins, aggregation, subqueries, window functions, nulls, and duplicates |
| Frontend simulator | HTML, CSS, and JavaScript tabs with live results and console | Build small interfaces under time pressure without external snippets |
| Code project | Project explorer, multiple files, IDE, and possible database connection | Practice reading an existing structure, implementing requirements, and running tests |
| Knowledge questions | MCQ or short questions mixed with hands-on tasks | Review language behavior, OOP, debugging, complexity, and role fundamentals |
Some assessments let you choose among supported languages; others restrict the options for a particular question. Confirm the available language inside the invitation or practice environment instead of relying on the platform's full language list.
How Coding Questions Are Scored
In the general backend simulator, submitted code runs against predefined test cases. Each case can carry a grade, and the question score is the sum of the grades for passed cases. SQL and frontend simulators can also use matched test cases, while project and frontend tasks may support manual evaluation.
This means a solution that passes the visible example is not necessarily complete. Test your own cases for empty input, minimum and maximum values, duplicates, invalid assumptions, overflow, ordering, and performance. A compiling partial solution is usually more valuable than an unfinished optimal idea.
What employers may see
Mercer Mettl's Code Playback report can show how code evolved, compilation results, time taken, marks, language, and a plagiarism score. Employers may therefore evaluate both the final output and the path you took to reach it.
Do not paste memorized code or try to disguise copied structure. The platform documents code-similarity checks, and proctoring rules may separately restrict copy-paste or leaving the test window.
How Mercer Mettl Proctoring Works
A test can be non-proctored or proctored. According to Mercer Mettl's documentation, proctoring can involve a live human, record-and-review, automated monitoring, or a combination of AI and human review.
| Mode | What It Can Involve | Candidate Action |
|---|---|---|
| Non-proctored | No live webcam feed streamed for monitoring | Still follow all employer rules and test-window restrictions |
| Live manual | Proctor views video and test screen and may use chat | Stay visible and watch for legitimate proctor messages |
| Record and review | Session video can be reviewed after the attempt | Maintain the same exam conditions throughout |
| Auto proctoring | Video and audio analytics can flag suspicious events | Use good lighting, keep your face visible, and remove distractions |
| Mettl Secure Browser | Lockdown mode can block other sites and applications | Install and test it before exam day if the invitation requires it |
Published AI flags include face not visible, another person, moving away from the window, looking away, partial face visibility, candidate absence, suspected impersonation, and mobile-phone detection. A flag is a signal for review, not proof that a candidate cheated.
Browser movement and lockdown
Assessment owners can configure browsing tolerance, which counts navigation away from the test window and may warn or terminate an attempt when a limit is exceeded. Secure Browser can also close active applications and prevent access to unauthorized websites or software.
Do not test these limits. Put your phone away, close unnecessary applications, disable notifications, and keep permitted reference materials ready only if the employer explicitly allows them.
System Requirements and Pre-Test Setup
Run the invitation's Check System Compatibility flow at least one or two days early. Mercer Mettl currently recommends a recent supported browser and lists a minimum 512 kbps upload bandwidth for non-proctored and AI-proctored tests, with higher bandwidth for media or authorization flows.
If webcam proctoring is enabled, test the camera, microphone, lighting, and permissions. If Secure Browser is required, install the supplied version and confirm that your operating system is supported. Employer instructions override generic help-center guidance.
Strategy During the Coding Test
Read before coding
Spend the first minutes identifying input and output contracts, constraints, scoring clues, and whether every question carries the same weight. For project or frontend work, inspect the existing files and run the starting code before changing anything.
Get a correct baseline
Implement the simplest correct approach that fits the constraints. Compile early, use small custom tests, and keep the program runnable. Optimize only after correctness is stable.
Reserve time for hidden cases
Before final submission, revisit boundaries, duplicate data, null or empty values, large inputs, and language-specific failure modes. Remove debug output and confirm that your function signature and return format exactly match the prompt.
A 5-Day Preparation Plan
On Day 1, map the likely format from the job description and invitation. Choose your strongest permitted language and run the system check.
On Day 4, complete a full mock using the expected duration. Include compilation, self-written test cases, and five minutes for review. If the role includes data work, add targeted SQL interview practice.
On Day 5, review mistakes instead of collecting new problems. Prepare the room, remove your phone, close background applications, confirm webcam and microphone access, and sleep.
Results, Pass Scores, and Retakes
There is no universal Mercer Mettl passing score. The employer chooses the assessment, weightings, cutoff, and how results fit into the hiring process. A platform score can also be combined with resume review, later interviews, or manual evaluation.
Retake rules are also employer-controlled. If a technical failure interrupted the test, document the time, take a permitted screenshot of the error if possible, contact the test administrator or Mercer Mettl support, and avoid starting a second attempt unless instructed.
FAQ
How many questions are in a Mercer Mettl coding test?
There is no fixed number. One official campus example contains two coding problems in 40 minutes, but employers can build different assessments with coding, SQL, frontend, project, or knowledge questions.
Does Mercer Mettl record the screen?
It can. Live proctoring may include the test screen, record-and-review can preserve session video, and SecureProctor configurations may require screen sharing. Your invitation and compatibility flow should show the permissions required for your test.
Can Mercer Mettl detect switching tabs?
The platform documents configurable browsing tolerance that counts movement away from the test window. Mettl Secure Browser can further prevent leaving the test or opening unauthorized applications and websites.
Do candidates see their scores?
Not always. Mercer Mettl generates reports for assessment owners, but the employer decides whether and how results are shared with candidates.
Final Preparation Advice
Combine that technical preparation with behavioral and leadership practice for the rounds that follow the assessment.
Official Sources
Mercer Mettl coding tests | Coding simulators | Remote proctoring | Mettl Secure Browser | System requirements | Code Playback reports