Candidate Flow
What candidates experience from invite link to final submission.
Candidates start from an invite link for one assessment. They do not need to create a Merge account.
- Candidate opens the invite link.
- Candidate reviews the instructions, timing, and browser requirements.
- If proctoring is enabled, the browser requests camera permission.
- Candidate reviews the code context and leaves comments.
- Candidate submits the review.
- Merge records the submission and prepares the result for the hiring team.
Candidate Requirements
Section titled “Candidate Requirements”Candidates should use a modern desktop browser. If proctoring is enabled, they also need:
- a working webcam
- camera permission for the assessment origin
- stable network access
What Candidates Should Submit
Section titled “What Candidates Should Submit”A strong submission is specific and actionable. Candidates should explain:
- what is wrong
- why it matters
- how severe it is
- what they would change
- what assumptions they are making
Common Candidate Issues
Section titled “Common Candidate Issues”Camera permission denied: Reset site permissions in the browser and reload the invite link.
Invite expired: Ask the hiring team to send a new invite.
Lost network: Reconnect and reload. The app should preserve normal browser state, but candidates should submit only after confirming comments are visible.
Submitted too early: The hiring team should decide whether to issue a fresh invite. Merge should not silently alter an existing final submission.