HackerRank's desktop app does far more than open a coding test. We looked at what the macOS app does during an assessment, what it can see on your machine, what candidates should check before and after installing it, and a phone-based workaround that keeps extra help off your Mac entirely.
Some employers now ask candidates to take HackerRank assessments in a desktop app instead of a browser tab. That is a real change. A web page lives inside the browser's sandbox. An installed app with broad permissions can see much more of your computer.
Most candidates install it minutes before a test that affects their job search, so few stop to ask what they are agreeing to. This post describes what we found in the macOS app and what you can do about it.
It takes over your screen
When an assessment starts, the app switches to a frameless kiosk window that stays above everything else, follows you across workspaces, and can't be moved, resized, or closed while the test is active.
It also intercepts common macOS shortcuts, including app switching, Spotlight, and quit. Every half second, it checks whether its window still has focus.
If you connect a second monitor, the app doesn't just note it. It immediately opens its own locked window on that display and blacks it out.
A lockdown like this is normal for a proctored test. But it means you lose easy access to the rest of your computer during the assessment, so handle anything you may need first.
It clears your clipboard
The app clears the system clipboard when a session starts, when it ends, whenever its window loses focus, and before it quits.
That is the whole macOS clipboard, not just text copied inside the test. If you have something important copied, such as a password or a draft, it will be gone. Clipboard managers may keep their own history, but don't assume so.
Inside the test, HackerRank's proctoring code also stores hashes of what you copy and cut, so it can tell when pasted text came from somewhere else.
It looks at what is running on your machine
This is the part most candidates won't expect. During monitoring, the app regularly:
- Lists open windows and running processes
- Asks macOS for your foreground apps through AppleScript
- Maps running processes to their app bundles and checks code signatures
- Runs system tools to count your active displays
- On recent macOS versions, samples per-process network traffic to look for AirPlay mirroring
The network check deserves attention. An assessment app is measuring what the processes on your computer are sending over the network, which is a long way from watching a test window.
It compares what it finds against a built-in list and a signed configuration downloaded from HackerRank's servers. The built-in list targets AI assistants and remote-control tools, so legitimate remote support software can get caught too. That configuration can change without an app update, so what the app looks for today may not be what it looks for next month.
It reads which apps can record your screen
The app requests Full Disk Access, one of the most powerful permissions on macOS. It uses that access to read the system TCC database, where macOS keeps track of which apps you've given privacy permissions.
Specifically, it queries for apps with Screen Recording permission, then flags running apps that have it. That can include ordinary tools you use every day, such as video calling apps and screen recorders.
Full Disk Access is also not limited to that one query. The permission lets an app read most of the protected data in your user account, including mail and message databases. We are not saying the app reads those. The point is that macOS only offers this permission as all-or-nothing, so you are trusting the app's code, and every future update to it, with everything the permission covers.
It can close your apps
If the app finds software that isn't allowed, it can try to kill those processes. On macOS it also shuts down Siri, a system feature you didn't choose to run as part of a test. Unsaved work in those apps may be lost. It then reports what it found back to the assessment, so an app you left open could become part of your test record.
It checks your hardware
The app reads your system's hardware profile to detect virtual machines. If you were planning to keep the test isolated in a VM, expect that not to work.
A workaround that stays off your Mac: the /mobile web view
Everything above has the same shape: the proctoring runs on your Mac, so it watches your Mac. That is also why installing another helper app on that same computer is a poor answer — it adds one more process for the app to list, flag, and possibly close, and often asks for broad permissions of its own.
Interview Solver Mobile takes the other route. Open interviewsolver.com/mobile in your phone or tablet browser — it's a web app, so there is nothing to install on the Mac being tested and no Interview Solver process, window, or permission for the HackerRank app to find there. It runs entirely on the separate device:
- Set it up before the test. Open
/mobileon your phone, sign in, and try it once so microphone and camera access are already granted. - Listen from the phone. Tap the microphone button and it transcribes the conversation on the phone. Tap Get answer and the answer streams back to the phone while listening continues.
- Photograph the problem instead of capturing the screen. Use the phone's camera to add up to three photos of a question and get an answer from them, with the recent transcript as context. Nothing is screen-captured, copied, or pasted on the Mac, so there's no clipboard event or screenshot hotkey on the monitored machine either.
That sidesteps the invasive part of this proctoring — the process lists, TCC database reads, per-process network sampling, clipboard clearing, and force-quitting described above are all scoped to the Mac, and the phone browser is not on it.
What to do before and after
If you decide to install it, a few steps will limit your exposure:
- Read what the employer tells you. Ask what data is collected, who sees it, and how long it's kept. You can also ask if there's an accommodation or alternative if you're not comfortable.
- Save and quit everything first. Close apps you don't need before the test so nothing gets force quit.
- Don't rely on your clipboard. Move anything you care about somewhere safe.
- Use a separate macOS user account if you can. Full Disk Access is system-wide, so this won't fully contain it, but a clean account keeps your personal apps from running during the test.
- Revoke permissions afterward. Go to System Settings → Privacy & Security → Full Disk Access and turn the app off. Do the same for any other permissions you granted, such as Screen Recording, Camera, and Microphone.
- Uninstall it when you're done. If you need it again, you can reinstall it and make the decision again.
- Keep other tools off the tested Mac. If you use something like Interview Solver Mobile, set it up on your phone beforehand rather than installing another monitored app — and only if the assessment rules allow it.
Why this matters
Employers have a legitimate interest in assessment integrity. Candidates also have a legitimate interest in knowing what software is doing on their personal computers, and those computers hold far more than an interview.
What's missing is clarity. Before you install the app, you should be told in plain language that it will read your permission database, inspect your running software, clear your clipboard, and may close your apps. Then you can make an informed choice.