Real remote tech jobs mostly come from companies that are already distributed, from hybrid companies hiring outside their office cities, and from contract and consulting work. Getting one takes the same skills as any tech job plus proof that you work well in writing, without supervision, across time zones, and the competition per opening is usually wider because the employer can hire from a whole country.
This guide covers where to look, how the process differs from office hiring, what "remote" means legally and practically in the US, how to avoid the scams that target remote job seekers, and how to stand out.
Where remote roles actually come from
Remote openings tend to come from a few distinct sources, and each behaves differently.
| Source | What it looks like | Things to check |
|---|---|---|
| Remote-first companies | Whole team distributed, written processes, async by default | Which countries or states they can hire in, core overlap hours |
| Hybrid companies hiring remotely | Most staff near an office, some fully remote roles | Whether remote staff get the same access to projects and promotion |
| Contract and consulting work | Agencies, staffing firms, direct contracts | Employment status (W-2 vs independent contractor), length, rate |
| Remote roles at large employers | Specific teams or roles approved for remote | Whether the approval is tied to the role or to a manager who may leave |
Some occupations lend themselves to remote work more than others. Software development, data, security analysis and technical writing are routinely done remotely. Roles that touch physical equipment, such as many IT support and network positions, are more often onsite or hybrid; the Bureau of Labor Statistics notes that some computer support specialists can telework while others must be onsite or travel to clients.
Where to search. Company career pages are the most reliable source, because postings there are real and current. Job boards and aggregators are useful for discovery, but go to the company's own site to apply when you can. Your network matters even more for remote roles than office ones: with so many applicants per posting, a referral from a current employee gets your resume read by a person.
How remote hiring differs
The core loop (recruiter screen, technical interviews, behavioral round) is the same as in our interview preparation guide. What changes is the emphasis.
Location still matters. "Remote" rarely means "anywhere." Many US companies can only employ people in states where they have set up payroll and comply with local employment rules, so a posting may say "Remote, US (excluding certain states)" or list approved states. Read that line before applying. Some companies also adjust pay by location, so ask how the range is set.
Written communication is assessed throughout. Your emails to the recruiter, your take-home README and your answers to async questions are all evidence. Sloppy writing hurts more in a remote process because writing is how the team will work with you.
Expect questions about how you work. Interviewers often ask how you plan your day, how you handle being blocked when your teammates are offline, how you keep stakeholders informed, and how you would handle an incident at an inconvenient hour. Have concrete answers drawn from real experience.
Video interviews are the whole process. Test your setup: a stable connection, a working microphone, a camera at eye level and a quiet room. Have a backup (phone hotspot, phone dial-in number) ready.
Time zones in practice
Most remote teams need some overlap. A common arrangement is a few hours of shared "core hours" each day for meetings and quick questions, with the rest of the day flexible. A company with most staff on US Eastern time may ask West Coast employees to start earlier, or the reverse.
Ask early: which time zone is the team centered on, what are the expected overlap hours, and is there an on-call rotation? On-call is common for software developers, systems administrators and security teams, and a rotation that lands at 3 a.m. in your time zone is a real cost to weigh.
Contractor or employee: what it means in the US
Plenty of remote roles are offered as contract work, so understand the difference before you accept.
An employee (paid on a W-2) has taxes withheld by the employer, and the employer pays its share of Social Security and Medicare. Benefits such as health insurance, retirement contributions and paid leave usually come with employee status.
An independent contractor is paid without withholding. The IRS explains that whether someone is an employee or contractor depends on the whole relationship, using three categories of evidence: behavioral control, financial control and the type of relationship. A company cannot make you a contractor just by calling you one if it controls how, when and where you work like an employee.
The cost difference is substantial. Self-employed people pay self-employment tax of 15.3% (12.4% for Social Security and 2.9% for Medicare) on net earnings, covering both the employee and employer halves, and they pay for their own health insurance, equipment and unpaid time off. A contract rate needs to be meaningfully higher than an equivalent salary to come out even. Run the numbers, or ask a tax professional, before comparing offers.
A third arrangement is a W-2 contract through a staffing agency: you are the agency's employee, placed at the client company for a fixed term. Taxes are withheld, but benefits vary widely by agency.
Avoiding remote job scams
Remote job searches attract scammers because the whole process happens online and applicants expect to never meet anyone in person. The Federal Trade Commission's job scams guidance and recent consumer alerts describe the common patterns. The ones most relevant to tech job seekers:
- Paying to get a job. The FTC states that "honest employers, including the federal government, will never ask you to pay to get a job." That includes paying for "training," certification fees the employer requires you to cover, or equipment.
- Equipment and check schemes. A "new employer" sends you a check to buy a laptop or home office gear from their approved vendor, or asks you to pay first and be reimbursed. The FTC warns that a fake check will bounce, and the bank will want the money back from you.
- Unsolicited messages. The FTC's April 2026 alert advises people to ignore generic and unexpected texts, WhatsApp, or Telegram messages about jobs.
- Personal email addresses. The FTC notes that recruiters generally email from a corporate account, not from a personal address such as Gmail or Yahoo.
- Sensitive data too early. Requests for your Social Security number, driver's license or bank details "for paperwork" before any real interview are a red flag in the FTC's guidance. Legitimate employers collect this after an offer, through a formal onboarding process.
- Chat-only interviews and instant offers. An offer after a short text chat, with no technical interview and no conversation with the actual team, is not how real tech hiring works.
To verify an opportunity, find the company's official website yourself (not from a link in the message), check that the role is listed on its careers page, and contact the company through a phone number or address you found independently. Search the company or recruiter name along with words like "scam" or "complaint," as the FTC suggests. If you have been targeted, report it at ReportFraud.ftc.gov.
What makes remote applicants stand out
Hiring managers for remote roles are trying to answer one extra question: will this person be effective without someone sitting next to them? Give them evidence.
Show remote or async experience on your resume. If you have worked on a distributed team, say so, and mention the specifics: "Worked across US and EU time zones," "Ran async design reviews in written RFCs." See our tech resume guide for how to write bullets that hold up.
Have public, written work. A well-documented GitHub project, a technical blog post, a clear README or open source contributions with good pull request descriptions all demonstrate the written communication remote teams depend on. For technical writers this is the whole application; for engineers it is a strong supporting signal.
Write a short, specific note when you apply. Three or four sentences: what role, why this company, the one or two most relevant things you have done. Generic cover letters are ignored; specific ones are read, especially at smaller companies.
Respond quickly and clearly. In a remote process, how you handle scheduling emails is part of the impression. Reply within a business day, confirm times with time zones stated, and keep messages short.
Be honest about your setup and availability. If you can only overlap four hours with the Eastern time zone, say so up front. Mismatches discovered after an offer waste everyone's time.
A practical next step
Pick ten companies you would genuinely want to work for that hire remotely in your state, and check their careers pages weekly rather than relying on job board alerts. For each, find one current employee in a role near yours and read what they publish or share. When a matching role opens, you will already know enough about the company to write a specific application, and possibly someone to ask for a referral.