A young part-time employee has been using Arch Linux on a personal laptop and needs frequent help getting basic work tools running, including spending about 30 minutes troubleshooting the VPN client. I appreciate that he wants to learn Linux, and I would be happy to help with Ubuntu, Debian, or another distribution we already understand. However, we cannot reasonably spend paid work time teaching core Arch administration or troubleshooting an unsupported setup. How would you handle this? Should we require a company-provided laptop with the standard operating system, or allow Arch only if the employee maintains it independently?
5 Answers
It may be worth separating work from learning. Provide the normal environment for daily tasks, then offer scheduled training time, a spare laptop, or a virtual machine for experimenting with Arch. That supports the employee’s development without turning billable hours into open-ended distro support.
If there is a legitimate reason to allow a different operating system, set the expectation in writing that the employee owns the workstation and is responsible for keeping every work tool functional. Give them a clear deadline to prove that the VPN and required applications work reliably. If they cannot, provide the standard corporate laptop rather than letting the rest of the team become their troubleshooting service.
The same principle applies even if the employee is technically capable. A rolling-release distribution can change unexpectedly, and the organization may need reproducible configurations, managed updates, endpoint controls, and predictable vendor support. Use an approved distribution that matches the team’s infrastructure, or make the unsupported setup explicitly the employee’s responsibility.
Use a company-owned, company-managed device configured like everyone else’s. Standardization exists so the team can support the system efficiently, and it also avoids security, liability, and data-loss problems that come with troubleshooting personal laptops. If the employee wants to experiment with Arch, a separate machine or virtual machine is a much better place for that.
Be direct about the support boundary: Arch is not a supported work platform, so the employee needs to switch to the standard image or resolve Arch-related issues without consuming team time. This is less about whether Arch is good or bad and more about whether the organization has the expertise, tooling, and security controls to support it.
That makes sense. The main issue is that this is currently being treated as a work device even though it is personal, which creates both support and responsibility problems.