A young part-time employee brought in a personal laptop running Arch Linux and has needed a lot of help getting basic work tools configured, including spending around 30 minutes troubleshooting the VPN. I'm glad they're interested in learning Linux, and I'd be happy to help with a familiar distribution such as Ubuntu or Debian when there's time for it. However, we're being paid to work, not spend hours learning or troubleshooting an unsupported operating system. I use Mint and macOS myself, so I'm not opposed to Linux, but I'm unsure how to handle this professionally. Should we require a more familiar distribution, provide a company laptop, or allow Arch with the expectation that the employee supports it independently?
4 Answers
The important distinction isn’t whether Arch is good or bad. It’s whether your team supports it. Be direct: “We support these operating systems; Arch is not one of them.” If the employee wants to use Arch, they can maintain it themselves, but work must still be completed on a supported setup without consuming everyone else’s time.
Give the employee a company-owned laptop configured like the rest of the team. Work devices should use the operating system, security tools, management platform, and applications your organization actually supports. Personal devices create security, liability, and troubleshooting problems that aren’t worth the risk.
Exactly. If the device isn’t company-owned and managed, it shouldn’t be used for client work or access to internal systems.
Standardization exists for a reason. Have the employee use the same environment as the rest of the team, whether that means a managed Windows or macOS laptop, Ubuntu, Fedora, or whatever your organization has chosen. If there’s a spare machine or virtual machine available, Arch can be used there for learning and experimentation outside production work.
If the employee is already experienced enough to maintain Arch and it doesn’t interfere with their work, there’s no need to ban it just because it’s unconventional. But establish a firm boundary: the company supports the work applications, not the employee’s personal operating system. If the setup prevents them from doing the job efficiently, move them to the standard image.
That’s a much clearer conversation than simply saying you would prefer a more user-friendly distribution. Set expectations around support and productivity.