Is This Take-Home or Recruiter Real? How to Check an Interview Request Before You Run Anything
A ten-minute routine to check a recruiter message or take-home before you run any code: find the company yourself, read the repo, run it somewhere disposable.
A message arrives: a recruiter likes your profile, the role pays well, and there is a short technical exercise to "get started". Most of these are real. Some are not, and the fake ones have got better. This year candidates have reported take-home tests that were really malware, delivered as a repo with a setup script or as an editor extension you had to install to "begin". Others have found that the data they handed over in a hiring process ended up somewhere they never agreed to.
You do not need to be paranoid. You need a ten-minute routine you run before you run anyone's code.
1. Find the company yourself, not through the message
Do not use the links in the email or the DM. Open a new tab and go to the company's own website. Check that:
- the role is on their careers page, or at least that the team and the kind of work exist;
- the recruiter's email domain matches the company's real domain (look-alike domains swap a letter or add "-careers" or "-jobs");
- if the recruiter works for an agency, the agency exists and names the recruiter on its own site.
If you cannot connect the person to the company through a route you found yourself, reply and ask. A real recruiter can tell you who the hiring manager is and point you to the posting.
2. Notice what they ask for, and when
Real processes have a shape. Usually there is a conversation before any test. Be wary when, before you have spoken to a human:
- you are asked to install something: a binary, a browser or editor extension, a "test runner", a remote-access tool;
- the exercise only works if you run a script with admin rights, or disable a security warning;
- you are asked for your ID document, bank details or a "refundable equipment deposit".
None of those are needed to see whether you can write code. ID checks and payroll details come later, through the employer's own systems, once there is an offer.
3. Read the repo before you run it
If the take-home is a repository, read it like a code review before anything executes:
- open
package.json,setup.py,Makefile,.vscode/and anypostinstall,prepareorpreinstallscripts. Install hooks run code the moment you install dependencies; - look for anything obfuscated, base64 blobs, downloads from raw IP addresses, or a dependency with a name one letter off a popular one;
- be suspicious of an exercise whose README insists you run one specific command first "to set up the environment".
When your editor asks whether you trust the authors of a folder you did not create, the answer for a stranger's take-home is no. Restricted mode still lets you read everything.
4. Run it somewhere you can throw away
If you do run it, do it in a disposable place: a fresh container, a virtual machine, or a cloud dev environment you delete afterwards. Not on the laptop that holds your SSH keys, your password manager, your crypto wallet and your current employer's VPN. Do not sign in to anything personal inside that environment.
A real employer will not mind if you say "I ran it in a container". Many will be pleased you thought of it.
5. Decide what you share, and with whom
The other half of trust is your data. Before you upload a CV, record a video or connect an account, ask:
- who will see this: the hiring team only, or anyone they forward it to?
- how long do they keep it, and can you ask them to delete it?
- if you send a link, can you take it back later?
A link you control and can withdraw is better than a file you can never recall. And anything you record for practice should stay with you.
6. If it smells wrong, it is allowed to stop there
You can say "I don't install software for a first-round exercise; can I share a repo link or do this on a call instead?" A real team will find another way. A scam usually goes quiet.
If you did run something you now doubt: disconnect, rotate the passwords and tokens that machine could reach (Git hosting, cloud, email), revoke SSH keys, and report the account to the platform it came from.
Where Hyrr fits
Hyrr is an interview platform, so it is fair to say what we ask of you, in the same terms.
- Practice and interviews run in your browser tab. There is nothing to install.
- A practice interview is recorded so you can watch it back, but it never counts against you and no employer ever sees it. Only you can see the report and the recording. Practice costs credits.
- A Verified Résumé is published only when you confirm it. Anyone with the link sees it, and you can withdraw it at any time. The recording is not included unless you choose to include it, and a skill that did not reach its level is never shown.
If you want to rehearse a technical round without handing anything to anyone, start a practice interview in your browser:
Practise in a browser tab, privately
Do you interview engineers at work? Hyrr runs the first-round interview for your open roles, out loud, and gives your team a report on every candidate. Create an employer account