Summary
The current interview workflow reveals problem identities prematurely:
- Setup page: The recommended title is shown before starting (e.g.,
Recommended: Latency Rank Query.).
- Interview room: The underlying LeetCode reference (e.g.,
LeetCode: Two Sum, LeetCode: Add Binary) is printed directly under INTERVIEW EXERCISE.
I propose adding a Blind Mode toggle on the setup page that hides the recommended problem title and strips the LeetCode reference from the candidate panel during the session.
Motivation
- Authentic simulation: Real interviews never disclose questions in advance. Hiding the title preserves unpredictability and realistic time pressure.
- Protect problem formulation: CodeTrial wraps problems into domain scenarios. Leaking raw LeetCode names spoils the algorithmic pattern and bypasses the requirement-clarification phase.
Proposed Implementation
- Setup Page:
- Add a "Blind Mode" toggle.
- When enabled, mask the recommended title (e.g.,
Problem: Hidden (Random Medium)) while keeping Choose a specific problem instead accessible for targeted drills.
- Interview Room:
- Display the scenario text and examples as usual, but hide the
LeetCode: <Title> line under INTERVIEW EXERCISE during the interview.
- Reveal the LeetCode reference only in the post-interview feedback report for review.
Summary
The current interview workflow reveals problem identities prematurely:
Recommended: Latency Rank Query.).LeetCode: Two Sum,LeetCode: Add Binary) is printed directly underINTERVIEW EXERCISE.I propose adding a Blind Mode toggle on the setup page that hides the recommended problem title and strips the LeetCode reference from the candidate panel during the session.
Motivation
Proposed Implementation
Problem: Hidden (Random Medium)) while keepingChoose a specific problem insteadaccessible for targeted drills.LeetCode: <Title>line underINTERVIEW EXERCISEduring the interview.