Latest listings · updated daily · September 1, 2026
Remote Jobs No Phone Calls: Non Phone Work From Home Jobs and No Call Center Remote Work
No US occupation is genuinely phone-free, but the spread is enormous, and almost every job recommended for this search sits at the wrong end of it. The federal O*NET database asks workers in 894 occupations how often they have telephone conversations and scores the answer from 0 (never) to 100 (every day). Software developers score 61. Data entry keyers score 80. Word processors and typists score 100. So do customer service representatives. The listicles have this backwards.
This page shows the engineering and design roles currently on our board, which are the two functions where that score runs lowest and where the deliverable is something you build or write rather than something you say. Every listing publishes a salary range, comes from a company we verified by hand, and was posted in the last 30 days. The sections below give the full occupational data so you can check any role you are considering, including ones we do not list.
The latest remote jobs with no phone calls
30 shown · newest first · salary on every listingEvery listing above is under 30 days old and comes from a verified remote-first company. See all remote jobs on today's board.
Remote jobs with no phone calls: typical salary ranges
| Role | Typical range (per year) |
|---|---|
| Junior Software Engineer | $72k to $92k |
| Junior Product Designer | $62k to $82k |
| QA Automation Engineer | $88k to $115k |
| Content Designer | $92k to $120k |
| Senior Backend Engineer | $150k to $195k |
Ranges reflect salary bands published on current and recent listings in this category on Latestremote. Every listing shows its own range.
Which remote jobs actually have no phone calls?
Skilled technical and creative work has the least phone contact of any remote-capable occupation: video game design, computer programming and software development score lowest in the federal data, at 58 to 61 out of 100. Nothing reaches zero. In O*NET, the occupational database sponsored by the US Department of Labor, workers are asked "How often do you have telephone conversations in this job?" and the responses are scaled so that 100 means every day, 75 means once a week or more but not every day, 50 means once a month or more but not every week, and 0 means never.
The table below is that score for the occupations that matter to a remote search, read at onetonline.org on 23 August 2026 (site last updated 19 May 2026). It is worth reading in both directions, because the surprises are at the top.
| Occupation | O*NET telephone score | Roughly how often |
|---|---|---|
| Video game designers | 58 | Between monthly and weekly |
| Computer programmers | 60 | Between monthly and weekly |
| Software developers | 61 | Between monthly and weekly |
| Fine artists and illustrators | 62 | Between monthly and weekly |
| Proofreaders and copy markers | 66 | Closer to weekly |
| Interpreters and translators | 66 | Closer to weekly |
| Software QA analysts and testers | 77 | Around weekly |
| Special effects artists and animators | 77 | Around weekly |
| Operations research analysts | 78 | Around weekly |
| Technical writers | 79 | Around weekly |
| Web developers | 79 | Around weekly |
| Data entry keyers | 80 | More than weekly |
| Business intelligence analysts | 80 | More than weekly |
| Medical transcriptionists | 84 | Most days |
| Graphic designers | 87 | Most days |
| Information security analysts | 87 | Most days |
| Writers and authors | 92 | Most days |
| Bookkeeping and accounting clerks | 95 | Nearly every day |
| Insurance claims processing clerks | 96 | Nearly every day |
| Accountants and auditors | 96 | Nearly every day |
| Customer service representatives | 100 | Every day |
| Word processors and typists | 100 | Every day |
Two things follow. The first is that engineering and design are the honest answer to this search, which is why they are the slice of the board this page lists. The second is that the gap between the top and the bottom of that table is much smaller than people hope. A software developer still averages a phone conversation somewhere between weekly and monthly. If your requirement is literally zero calls, no occupation in the federal data delivers it, and the ones scoring under 20 are all hands-on factory work, cutting, molding and machine tending, that cannot be done remotely at all.
Why data entry, typing and transcription are the wrong place to look
Search this phrase and you will be told to look at data entry, typing, transcription and bookkeeping. Every one of those scores in the top third of the table above: data entry keyers 80, medical transcriptionists 84, bookkeeping clerks 95, word processors and typists 100. They are among the most telephone-heavy occupations in the American economy, not the least.
The reason is structural rather than surprising once you see it. Those roles sit inside administrative and back-office teams where the phone is the escalation path for everything the process could not handle. A data entry clerk calls a branch to confirm an illegible figure. A bookkeeper calls a vendor about an invoice that does not reconcile. A transcriptionist calls a clinic about an inaudible passage. The typing is the visible part of the job and the calling is the part nobody puts in the description.
There is a second problem with that advice, which is that these are exactly the job titles scam listings imitate. High-volume, low-credential, work-from-home roles are the easiest to fake, and a listing that promises no phone contact and no experience is doing two things at once to lower your guard. Our guide to how to tell if a remote job is a scam covers the pattern in detail. If you want the genuinely low-credential end of this board instead, entry level remote jobs lists the roles that hire without a track record, and remote jobs no degree required covers the ones that skip the diploma filter.
The honest reframe: the amount of phone work in your day is set by what your role is accountable for, not by how much typing it involves. Roles accountable for a customer relationship, an unblocked process or an urgent exception will reach for the phone. Roles accountable for a shipped artifact, code, a design, a test suite, a document, mostly will not.
Remote jobs that don't require talking on the phone: screen the employer, not the job title
Occupation only explains part of it. O*NET scores a job title as it is practiced across every employer in the country, most of them onsite and meeting-driven. Two software engineering jobs at two companies can differ more from each other than a software job differs from a design job. So the higher-leverage filter is the employer, and you can read it before you apply.
- Look for written-first process in the listing itself. Phrases like async, written proposal, design doc, RFC, or "we write things down" are not culture-fluff, they are a description of how decisions get made. A company that decides in documents does not need to call you.
- Count the meetings the listing admits to. Descriptions that mention daily standups, a weekly all-hands, sprint ceremonies and one-to-ones are describing four recurring synchronous commitments before any ad hoc call.
- Check whether the role is customer-facing at any tier. A backend engineer who owns an integration will end up on a call with the partner. The same engineer on an internal platform team will not. Scope matters more than title.
- Check the time zone requirement. A role advertised as open to any time zone cannot depend on calls, because there is no hour that works for everyone. A role requiring four hours of overlap with Pacific time is telling you it has meetings.
- Ask directly at the screen. "How many recurring meetings does this role have in a normal week, and are they video or written?" is a completely normal question and the answer is a good hiring signal in both directions.
One distinction worth making before you start, because it changes the search entirely: no phone calls and no video meetings are not the same requirement. Most people typing this phrase mean they do not want a job answering customer calls all day, which is very achievable. A smaller group mean they do not want to speak to anyone in real time at all, which almost no professional salaried role offers. Decide which one you are, because the first opens up all of engineering, design and analysis, and the second narrows you to contract and piecework. Browse the remote first companies behind these listings if you want to see which ones publish how they work before you apply.
Remote chat jobs, no call center work and the support roles that stay written
Customer service representatives score a flat 100 on telephone frequency, so support looks like the last place to search. That average hides a real split, though, and it is worth understanding if support is the function you are actually qualified for.
Software companies have largely moved first-line support to email tickets and live chat, while call centers in insurance, healthcare billing, utilities and collections still run on the phone. The O*NET score averages both. A support role at a product company can be genuinely written work all day, and the listing will usually say so by naming the tools: a ticketing system, a chat widget, a help center it expects you to maintain. A listing that mentions call volume, average handle time, a dialer or a headset is the other kind, and no amount of hoping will change it.
| Support role type | Primary channel | Realistic phone load |
|---|---|---|
| Product support at a software company | Email tickets and live chat | Occasional scheduled screen share, rarely inbound calls |
| Technical support engineer | Tickets, escalation, reproduction cases | Some scheduled debugging calls with customers |
| Community and forum moderation | Written, public | Effectively none |
| Content and documentation support | Written, internal | Effectively none |
| Call center and BPO customer service | Inbound and outbound phone | The entire shift |
| Collections, claims and utility service | Phone with a dialer | The entire shift, often with a quota |
The chat and ticket end of that table is also the part of support that keeps growing, because the phone tier is the part employers are automating first. If written support is what you want, remote customer service jobs lists the current openings and the listings state their channel. For a fuller comparison of which specific roles to target and what they pay, we go deeper in the best remote jobs with no phone calls.
Two adjacent slices worth a look if scope is flexible: remote software engineering jobs is the lowest-telephone function in the whole federal table, and remote design jobs pairs low call load with a portfolio-based hiring process rather than an interview-heavy one. If you want reduced hours alongside low phone contact, part time remote jobs carries the hourly roles, several of them in these same two functions.
There is a second federal measure worth putting next to the telephone score before you commit to a support career, because the two together change the picture. The same O*NET database scores occupations from 0 to 100 on freedom to make decisions without supervision. Customer service representatives score 51, the lowest of any remote-capable occupation we have looked at, against 85 for technical writers, 86 for web developers and 88 for writers and authors. And the Bureau of Labor Statistics projects customer service representative employment to fall 5 percent between 2025 and 2035, with a May 2025 median wage of $21.53 an hour and about 289,500 openings a year, all of them from replacing people who leave. So the occupation that dominates this search is simultaneously the most phone-heavy, the least autonomous and the fastest shrinking of the realistic options. Written support at a software company is a genuinely different job from a call center seat, and the screening advice above is how you tell them apart, but if you are choosing a lane rather than a job, choose one of the other lanes. Career changers arriving here from the classroom will find the same three measures laid out role by role on our remote jobs for teachers page.
Questions about remote jobs with no phone calls
- Are there remote jobs with no phone calls?
- Not literally zero, but close. In federal O*NET data no occupation scores below about 58 out of 100 for telephone frequency among remote-capable work, and the lowest are video game designers at 58, computer programmers at 60 and software developers at 61. That is roughly one call somewhere between weekly and monthly, against 100 for a customer service representative.
- What remote jobs don't require talking on the phone?
- Software development, programming, QA testing, web development, technical writing, animation, illustration and proofreading all score in the bottom third of the federal telephone-frequency table. What they share is that the deliverable is an artifact you produce rather than a conversation you have, so the work can be reviewed asynchronously.
- Are there remote data entry jobs with no phone calls?
- Fewer than the advice suggests. Data entry keyers score 80 out of 100 for telephone frequency in O*NET, and word processors and typists score 100, because the phone is the escalation path when a record cannot be resolved from the document alone. Data entry is one of the more phone-heavy back-office occupations, not one of the least.
- What are the best remote jobs with no phone calls?
- For low call load with a real salary, software engineering and product design lead by a wide margin, followed by QA testing and technical writing. Junior openings in these functions on this board run about $62,000 to $92,000, and senior engineering roles reach $150,000 to $220,000. All four hire through work samples rather than phone screens in most cases.
- Are there remote jobs no phone calls no experience?
- Yes, though fewer than the search volume implies. QA testing, community moderation and junior design are the realistic entry points, because each is judged on output that a beginner can produce. Be cautious with no-experience listings that also promise no phone contact and unusually high pay, since that combination is a common shape for fake postings.
- What remote jobs are not call center jobs?
- Any support role where the channel is tickets or chat rather than a dialer. Product support at software companies, community moderation and documentation work are written all day. The tell in a listing is the vocabulary: average handle time, call volume, headset and dialer describe a call center, while ticketing system, help center and live chat do not.
Keep browsing
New remote jobs with no phone calls land here the day they post. Get them in your inbox.
Free for job seekers. One email a day at most.