Browser-side code execution for interviews

Most interview code is small: arrays, maps, recursion, parsing, and a few test cases. That makes browser-side execution a strong fit.

DiscussCode uses two runtime paths:

• JavaScript runs through QuickJS compiled to WebAssembly.
• Python runs through Pyodide.

Why not run everything on a server?

Server execution gives more control, but it also adds cost, queueing, sandboxing risk, and cold-start complexity. For algorithmic interviews, local browser execution is often enough.

The important safety detail

Execution should not run on the UI thread. A candidate can write an infinite loop by accident. The editor must stay responsive, and the interviewer needs a way to stop the run.

That is why DiscussCode runs code inside disposable Web Workers with a timeout guard.