How to Spot Tech Job Scams: A Pre-Application and Interview Safety Checklist

Overview

Tech job scams can appear in remote software engineer jobs, freelance projects, internships, IT support roles, data positions, and other legitimate-looking listings. A polished careers page, technical vocabulary, or a friendly recruiter is not enough to prove that an opportunity is genuine. Scammers may copy company branding, impersonate recruiters, use free email accounts, or move conversations to private messaging apps before asking for money or sensitive information.

The safest approach is to treat verification as part of your job search process. Do not rely on one reassuring signal. Compare the listing, recruiter, company, interview process, payment expectations, and offer details independently. A single inconsistency may have an innocent explanation, but several inconsistencies should be treated as a reason to pause.

This checklist is useful for remote tech jobs and onsite or hybrid roles alike. It is especially important when the opportunity comes through an unsolicited message, an unfamiliar job board, a social network, or a direct email rather than through a company’s established application route.

Checklist by scenario

Before applying to an unfamiliar listing

1. Read the complete listing. Look for a specific role, reporting relationship, responsibilities, required skills, work arrangement, and a plausible application process. Vague promises about easy income or unusually rapid advancement are reasons to investigate further.
2. Compare the details. Search the company name, role title, location, and key phrases from the description. Check whether the same opportunity appears on the organization’s official website and whether the contact details match.
3. Inspect the application link. Confirm that the destination domain is what you expect. A similar-looking domain, a shortened link, or a form that requests extensive personal data before describing the role deserves caution. Do not assume that a website with a logo is controlled by the named company.
4. Research the organization independently. Use contact information found through a source you locate yourself, not only the phone number or email address in the message. Look for a consistent company identity, a real product or service, and a coherent explanation of what the role would do.
5. Record what you found. Save the listing URL, recruiter name, company domain, application date, and any promised compensation or work conditions in your remote tech job search tracker. A record makes contradictions easier to spot later.

When a recruiter contacts you

1. Verify the identity separately. Do not use only a profile link supplied in the message. Visit the company website yourself and look for a recruiting or careers contact route. You can ask the recruiter to confirm the role through an official company channel.
2. Check the email domain carefully. Minor spelling changes, extra words, unusual country domains, and free email accounts may indicate impersonation. A matching domain is helpful but is not conclusive, so compare it with the company’s public website and other verified details.
3. Ask clear questions. Request the hiring manager’s name, team, employment type, work location, interview stages, and next steps. A legitimate recruiter should be able to explain the process without requiring secrecy or immediate payment.
4. Watch the pace and pressure. Be cautious if you are told to decide immediately, keep the opportunity confidential, or skip normal screening. Urgency is not proof of fraud, but it reduces your ability to verify the opportunity carefully.

Before a technical interview

A real interview invitation should identify the role, interviewer or team, meeting method, expected preparation, and a reasonable way to reschedule. Confirm that the meeting link and sender details are consistent with the company and recruiter. Do not install unknown software, browser extensions, or remote-access tools merely to attend an interview. If a coding exercise requires access to a repository or development environment, review the requested permissions and avoid sharing private credentials.

Prepare for the interview using the same care you would apply to any technical opportunity. A structured plan for software engineer interview preparation can help you distinguish a normal skills assessment from an unusual request. A legitimate technical task should have a clear purpose and reasonable boundaries; it should not require your passwords, payment, or unpaid production work presented as an assessment.

After receiving an offer

1. Request the offer in writing, including the employer’s legal or operating name, role, compensation, work arrangement, start date, and key conditions.
2. Verify the offer through a company contact method that you found independently.
3. Never pay to receive a job, unlock training, process payroll, obtain a background check, or access required equipment without independently confirming the arrangement.
4. Be especially cautious of checks or transfers that require you to purchase equipment, send money onward, or return an alleged overpayment.
5. Share only the information needed at that stage. Delay sensitive identity or banking documents until the employer, role, and hiring process have been verified.

What to double-check

Recruiter identity: Names and profile histories can be copied. Compare the recruiter’s information across the company site, professional profile, email domain, and interview invitation. Differences do not automatically prove a scam, but they should be explained before you proceed.

Company domain: Read the domain character by character. Scammers may use substitutions, extra terms, or domains that resemble a known employer. Navigate to the company site independently rather than clicking only the supplied links.

Compensation and work arrangement: Compare the duties and requirements with the stated pay and location. For context, you can use a tech salary comparison tool guide, but compensation alone cannot establish legitimacy. A high or low figure may reflect location, contract status, experience, or incomplete information.

Interview behavior: Confirm who is interviewing you and why. A conversation focused entirely on collecting documents, opening accounts, buying items, or recruiting other people is not a normal substitute for evaluating your fit for the role.

Contract terms: For freelance or contract work, check the scope, deliverables, payment schedule, ownership terms, cancellation conditions, and client identity before beginning. The guide to comparing tech contract and freelance jobs can help you organize that review.

Common mistakes

• Trusting branding instead of verification. Logos, polished messages, and professional language can be copied.
• Sharing too much too early. A CV may need contact details and work history, but it should not include account passwords, security answers, or unnecessary financial data.
• Assuming an interview proves legitimacy. Impersonators may conduct several conversations before making a payment or information request.
• Ignoring small inconsistencies. A different company name, unexplained change in salary, mismatched location, or new payment request should be resolved before you continue.
• Continuing because you have already invested time. Previous messages and interview preparation do not obligate you to proceed. Pause when the risk changes.

If you believe a listing or message is fraudulent, stop communicating through the suspicious channel, preserve relevant messages and URLs, and report it through the job platform or company contact route. If you shared credentials or financial information, use the appropriate account-security or financial-service process promptly.

When to revisit

Use this checklist before every unfamiliar application, recruiter conversation, interview, and offer—not only once at the start of your search. Recheck the process when the recruiter changes, the conversation moves to a new platform, the company domain differs from earlier messages, or a new request for money or sensitive data appears.

Return to the checklist before seasonal hiring periods, when you begin searching in a new country or employment market, and when job platforms or communication tools change their workflows. Editors and job seekers should also refresh their verification steps after major changes to reporting procedures or common impersonation patterns.

Practical next step: copy the following short version into your job-search notes:

1. Verify the listing and company independently.
2. Confirm the recruiter through an official channel.
3. Inspect every domain, link, and interview invitation.
4. Refuse payment, money transfers, and unusual equipment schemes.
5. Share sensitive information only after the employer and offer are verified.
6. Pause and report if pressure or contradictions increase.