See what's new

Testlify
System compatibility & setup
Last updated on: 16 November 202613 min read

Remote diagnostics for remote work: what to check and how

What remote diagnostics checks on a remote worker's device and network, when to run it, which minimums to set and how to keep it private.

Remote diagnostics for remote work: what to check and how

Remote diagnostics is the practice of checking a device, connection or system from a distance, without anyone touching it. In remote work, remote diagnostics means confirming that a person's laptop, browser, camera, microphone and home network can handle the work, the interview or the assessment before it starts, so problems are found by a check instead of a failed session.

The need is not shrinking. Gallup's hybrid work indicator shows that, as of August 2026, 25% of US employees with remote-capable jobs work exclusively remote and 54% work hybrid. Every one of them depends on a setup the employer never sees.

TL;DR:

  • Remote diagnostics checks a remote device and connection from afar and compares each reading with a minimum you set in advance.
  • Check five areas: device, operating system and browser, camera and audio, network, and security. Security needs IT's endpoint tools, not a browser check.
  • Run it at three moments: before an assessment or interview, before day one, and on an ongoing basis by IT.
  • Set minimums from the work itself. Microsoft recommends 1.5 Mbps up and down for one-to-one HD video in Teams, and Windows 11 needs at least 4 GB of RAM.
  • A remote readiness assessment only counts on the real setup: the exact device and network the person will use, retested after every fix.
  • Diagnostics is a readiness check, not monitoring. Tell people what is collected, why and for how long.
Summarise this post with:ChatGPTGeminiClaudeGrokPerplexity

What is remote diagnostics?

Remote diagnostics is the process of finding and confirming technical problems on a device or system from a different location, using data the device sends over a network. Car makers, equipment makers and IT teams all use it. For remote work, a remote diagnostic checks a person's computer, browser, peripherals and connection against a defined standard before work begins.

The general idea is the same in every field: collect readings, compare them with what is expected, flag anything outside the range and fix it before it causes a breakdown. What changes is the "machine". For a fleet manager, it is a truck. For an HR or talent acquisition team it is the laptop and home connection a candidate or new hire will use for a video interview, a skills test or their first week.

Remote diagnostics differs from remote support. Support starts after something breaks: a technician takes control of the screen and fixes it. Diagnostics runs before the session, so the person never reaches a broken interview.

Build your dream team — Book a product demo

How do remote diagnostics work for remote work?

Remote diagnostics for remote work runs in four steps: set a minimum standard, send the person a check, compare each reading with the minimum, and decide. A pass clears the person for the session. A fail names the parameter that missed the bar, so the person can fix it and retest before anything depends on it.

  1. Set the standard: Agree the minimum device, operating system, browser, camera, microphone and network the work needs.
  2. Send the check: Share one link or invite. The person runs it on the exact device and network they will use.
  3. Compare: Each reading (for example upload speed or RAM) is compared with the minimum, parameter by parameter.
  4. Decide: Pass and continue, or fix the named problem and run the check again.
Pro tip: Ask people to run the check from the room and the network they will use on the day. A check run from the office Wi-Fi tells you nothing about a shared home connection at 7 pm.

What should a remote diagnostic check?

A remote diagnostic should check five areas: the device, the operating system and browser, camera and audio, the network, and security. The first four decide whether a session will work. Security decides whether the device is safe to connect to company systems, and it usually needs IT's own tools.

Area

What to check

Sensible minimum

Who owns it

Device

Processor, cores, RAM, free storage, power

Meets the OS minimum, with headroom for video calls

IT sets, HR shares

Operating system and browser

OS version, supported browser and version

A supported OS still receiving updates; a current browser

IT

Camera and audio

Camera, microphone, speakers or headset detected and working

Clear video and audio in a test recording

TA ops for hiring, IT for staff

Network

Download and upload speed, connection type, stability

Enough for HD video both ways, with margin for other users at home

TA ops and IT

Displays

Monitor count and resolution

One screen for proctored tests; resolution the tools need

TA ops

Security

Antivirus, disk encryption, patch level, VPN access

Company policy

IT only

For the device row, use a published baseline instead of a guess. The Windows 11 requirements on Microsoft Learn list a 1 GHz processor with two or more cores, 4 GB of RAM, 64 GB of storage, TPM 2.0 and a 720p display, and note that Teams needs a camera, microphone and speaker. Treat that as the floor, then add headroom for video, browser tabs and any test software.

Key takeaway: Set minimums from what the work needs, not from the best machine in the office. A bar that is too high rejects people for no reason; a bar that is too low lets sessions fail.

When should you run remote diagnostics?

Remote diagnostics pays off at three moments: before an assessment or interview, before a new hire's first day, and on an ongoing basis. Each moment has a different owner and a different checklist, which is why one tool rarely covers all three.

When to run remote diagnostics: before the assessment, before day one and ongoing, with owners

From ensuring candidates can complete online assessments to preparing new hires for their first day, HR and IT need to work together to prevent avoidable disruptions. Here are three key stages where technology readiness checks matter:

  • Before the assessment or interview: TA or recruiting ops checks the candidate's device, browser, camera, microphone, speed and screens. A failed setup here costs a reschedule, a lost candidate or an unfair score. Our guide to running a system check before an online assessment covers the candidate side in detail.
  • Before day one: HR and IT confirm the company laptop or personal device, VPN and single sign-on access, and video call quality, so the first morning is spent meeting the team, not on the helpdesk. Add the check to your onboarding checklist, and agree a policy if people use their own devices (BYOD).
  • Ongoing: IT tracks patches, endpoint protection and recurring network problems through its device management and monitoring tools.

For high-volume remote roles, such as contact center agents in BPO, the first two moments matter most. A connection that drops during a voice simulation fails the candidate today and the customer later.

What can a browser-based check see, and what can it not?

A browser-based check can see what the browser is allowed to read: camera and microphone (after the person grants permission), connection speed, browser and operating system, screen size and monitor count, and a rough device profile. A browser cannot see antivirus status, disk encryption, patch level or installed software. Those need an agent that IT installs on the device.

What a browser-based remote diagnostic can see versus what needs IT endpoint tools

Permission is built into the web platform. The getUserMedia reference in MDN Web Docs explains that a page must ask the user before it can use a camera or microphone, and only over a secure (HTTPS) connection. That limit is a feature for hiring: a candidate can run a check without installing anything, and the employer learns only what the session needs.

The practical split looks like this:

  • For people you have not hired yet: Use a lightweight check that asks for nothing beyond the session's needs. You have no right, and no reason, to inspect a candidate's antivirus.
  • For company devices: Leave security checks to IT's endpoint management, which covers encryption, patches and blocked software across every device.

How do you run a remote readiness assessment step by step?

A remote readiness assessment runs in five steps: define the standard with IT, configure the check, send it early, review the results, and fix and retest. Done well, the person knows days ahead whether their setup works, and nobody discovers a broken camera at the start of an interview.

Step 1: Define the standard with IT

Write down the minimum device, operating system, browser, camera, microphone, speed and screen setup for each type of session. Keep separate standards for different work: a typing test needs far less bandwidth than a live coding interview with screen sharing.

Step 2: Configure the check

Enter the thresholds in your diagnostics tool and choose which parameters count as required. Use network numbers from the software the person will actually use. The Microsoft Teams network guidance sets one-to-one video at a minimum of 150 kbps and a recommended 1,500 kbps each way, and meetings at a recommended 2,500 kbps up and 4,000 kbps down.

Step 3: Send the check early

Send it 24 to 48 hours before the session or with the onboarding pack, not five minutes before. People need time to borrow a laptop, move closer to the router or switch to a wired connection.

Step 4: Review results

Read the result for each parameter, not only the overall status. "Upload speed below threshold" and "no microphone detected" need different fixes and different messages.

Step 5: Fix and retest

Send a short fix list for each failure: use a wired connection, close other apps, update the browser, switch devices. Then ask for a fresh check. According to Microsoft's Teams guidance, Wi-Fi and VPNs are often not designed for real-time media, so a wired connection and a split-tunnel VPN fix many failures.

How do you choose a remote system diagnostics platform?

Choose a remote system diagnostics platform by the moment you need to cover. Pre-assessment checks suit hiring, device management tools suit company laptops, and network monitoring agents suit teams with recurring connection problems. Most organizations need the first and one of the other two, not a single tool for everything.

Platform type

Best for

Checks

Install needed

Pre-assessment system check

Candidates before tests and interviews

Device, OS, browser, camera, mic, speed, screens

No, or a light one-click launch

Device management (MDM / RMM)

Company devices for staff

Patches, encryption, endpoint protection, software, logs

Yes, an agent on each device

Network monitoring agent

Remote teams with ongoing call or VPN issues

Latency, jitter, packet loss, path to the ISP

Yes, an agent or probe

Ask five questions before you buy:

  1. Coverage: Does the platform check every parameter your standard lists, and can you switch parameters on or off per session?
  2. Result clarity: Does each failure name the parameter and the reading, so the person knows what to fix?
  3. Candidate effort: How long does the check take, and does it need an install or admin rights?
  4. Integration: Do results land where the team already works, such as the ATS or the assessment dashboard?
  5. Privacy: What data is stored, who sees it and when is it deleted?

How does Testlify run remote diagnostics before an assessment?

Testlify runs remote diagnostics through its system compatibility check, a one-click check that runs in under a minute before a remote assessment. The check covers the candidate's device, browser, camera, microphone and internet connection, and recruiters see the results in the Testlify dashboard.

System compatibility check

The parameters Testlify reads include processor vendor, series, generation and cores; RAM; operating system and version; internet type; download and upload speed; network location (IP, network provider and country); monitor count and resolution; and sound card and audio output.

Post image

Each parameter is validated against the standard you set for that assessment, with a simple Pass or Fail per parameter.

Post image

The check sits alongside Testlify's 20+ proctoring checks, which include an internet speed check, a live environment check and multi-monitor restriction, described on the anti-cheating and proctoring page. For teams that want the wider picture of online test integrity, our guide to remote proctoring explains how the pieces fit.

Testlify's check is built for the hiring stage. Security checks on company laptops, such as encryption and patch level, stay with your IT team's device management tools.

How do you keep remote diagnostics fair and private?

Remote diagnostics stays fair and private when people know what is checked, why, who sees it and how long it is kept, and when the check collects only what the session needs. Treat it as a readiness check, never as a hidden way to watch people.

  • Collect the minimum: System and network readings, not files, browsing history or screen contents.
  • Say it up front: Explain the check in the invite: what it reads, why, and what happens on a fail.
  • Offer a fix, not a rejection: A failed check should lead to help, a loaner device or a new slot. Hardware should not decide who gets hired.
  • Set retention: Delete readings once they have served their purpose, in line with your data policy.

UK employers have a clear reference point. Guidance from the UK ICO on monitoring workers says employers must tell workers about monitoring, choose the least intrusive means and run a data protection impact assessment before high-risk monitoring. A one-off readiness check is light; continuous tracking is not.

Ongoing checks such as a remote employee connectivity test sit closer to employee monitoring, which brings its own rules on consent, purpose and trust.

What mistakes make remote diagnostics fail?

Remote diagnostics usually fails for process reasons, not technical ones. The same five mistakes come up again and again.

  1. Running it once: Setups change. Retest before each high-stakes session and after every fix.
  2. Testing the wrong setup: A check on a phone or the office network says nothing about the laptop at home.
  3. Ignoring upload speed: Video interviews and proctored tests send video out, so upload matters as much as download.
  4. Copying someone else's thresholds: Set minimums from your own tools and sessions.
  5. Sending a fail with no fix: Every failed parameter needs a plain next step, or people simply drop out.

Ready to check candidate setups before the test?

Testlify checks each candidate's device, browser, camera, microphone and connection in under a minute, then shows a Pass or Fail per parameter next to their assessment. Explore the system compatibility check or start a 7-day free trial, no credit card needed. For a walkthrough with your own roles, book a demo.

Frequently asked questions (FAQs)

Jiten Modi
Jiten Modi

Co-Founder and CTO

Jiten Modi is Testlify's CTO and leads a 50-person engineering organization. He writes on technical hiring, evaluating developers with real-world assessments, and building engineering teams.

LinkedIn

Get started.

Hire on proof, not resumes.

Run your first skills-based assessment free — no credit card required.

We use cookies to enhance your browsing experience, serve personalised ads or content, and analyse our traffic. By clicking "Accept All", you consent to our use of cookies.