Best practices for getting the full security advantage.
Aceloop is built to be the most secure AI interview copilot on the market, but the product is only half the posture. The other half is how you run the room: light, reflections, eye placement, overlay alignment, window cleanup, and the order in which you use Solve, inline suggestions, Debug, and Optimize.
Eyes stay near the code
The safest setup keeps Aceloop's useful content close to the line you're editing. Long left-right or up-down eye jumps are the easiest human tell.
Light beats reflection
Bright, even light on your face reduces the chance that screen contrast, dark panels, or overlay expansion show up in glasses or on camera.
Use the assistant in stages
Inline suggestions, then Debug, then Optimize looks and feels more natural than reading a complete canonical solution from the start.
Handle glasses, glare, and face lighting first
Glasses are the simplest physical leak. A bright screen, a dark overlay, or a panel expanding and collapsing can create visible changes in the lenses or on your face. If you can interview without glasses, do it. Otherwise make the lighting work in your favor before the call.
- Use strong, even front lighting aimed at your face so the room light beats the screen light.
- Lower monitor brightness until opening and closing the overlay doesn't visibly change the light on your face.
- Use Aceloop dimming aggressively when the editor background and overlay background have high contrast.
- Prefer X-ray mode when you need the overlay to blend into the editor instead of creating a distinct block.
Put the overlay where your eyes already are
Eye placement is the most important habit. Aceloop makes the overlay easy to reposition for a reason: the content should sit near the code, line, panel, or prompt you're actively working on.
- When editing code, place the overlay near the exact region you're editing.
- When reading the prompt or thinking through approach, place it near the central content area.
- When you need to read for a longer stretch, keep it high and centered enough that your gaze stays natural.
- Reposition between phases instead of leaving it parked in one corner for the whole round.
Close exposed folders and stray windows
After launching Aceloop, clean the desktop. The best environment is boring: editor, browser, call, nothing else.
- Close File Explorer after running the launcher.
- Close downloads and installer folders.
- Keep only the coding platform, the call, and the tools you actually need open.
- Silence notifications before the interview starts.
Don't start by dumping the canonical answer
The strongest workflow isn't "press Solve, read the answer, type the whole thing." Prepare normally, read the problem normally, think normally, and use Aceloop as the rail that keeps your own attempt moving.
- At the start, press Solve so the context is ready, but read the prompt and reason through it yourself first.
- Use inline suggestions while implementing your own approach.
- After you have a real attempt, run Debug when tests fail or edge cases break.
- After correctness, run Optimize to tighten complexity and prepare the explanation.
- Use the generated diff and summary as the smallest correction, not as a script to perform.
Use Debug and Optimize after real work exists
Spend the first chunk understanding the problem. Implement with inline help. Let test cases expose the bug. Then use Debug for the exact diff, and Optimize once it works.
Inline
Best for staying aligned with the code you're already writing. The lowest-friction, most natural assistant surface.
Debug
Best after you have code and test output. Debug can explain the failure and give you the smallest diff that fixes it.
Optimize
Best after correctness. Optimize helps improve complexity and gives you the language to defend the better approach.
The model explains the claim. These practices earn the benefit.
The security model explains why the product can make the strongest claim in the category. These practices explain how to get the full benefit in the room.