This is clearly in a field where that’s not true

"I only work on carbureted engines."

In my company, everybody is on Linux and if you want a Mac you need to make your case. 0 Windows laptop.

I've worked in all sizes of companies, in various industries and 3 different European countries.

In my experience it very much depends on the industry the company in, the division one is working in and the size of the company.

Engineering types in an Engineering/Tech company using Linux isn't at all unusual in smaller and mid-sized companies. Sales types or accounting, definitelly are using Window. Creatives tend to use Macs, mainly because the Adobe suite runs perfectly in it and the hardware is superior to PC hardware - designer types almost literally salivate at things like 4K monitors.

Real startups (so, not mature Tech companies that try and still be startups) will definitelly have their devs running whatever they want, whist for example big financial institutions will have everybody on Windows, except perhaps top-level management if they're quirky and prefer Mac for some reason or other.

Then to this add that the kind of professional who not only prefers Linux but can actually say "bye, bye" if they don't get it is almost certainly be a pretty senior Techie (say, a Senior Designer Developer) and even now those are pretty hard to find for a permanent employment position (you can't replace those with AI or outsourcing, not even close, and in the path to such seniority many devs who keep on progressing eventually step into management instead of staying on the Technical career track) - outside a large company (were the hiring manager doesn't have the pull to make it happen), it a pretty good idea to let them use whatever OS they want in their work machine, even if it has to be with the proviso that they won't be getting any support for it from the IT Support group (which, trust me, they will be fine with).

If a hiring manager has the pull for it and there are no regulatory reasons to make it be otherwise, it's pretty dumb not to let a rare resource like a really senior dev use whatever the fuck they want on their work PC if that's going to allow you hire/keep that person.

refuse to work on Toyotas.

Nah, the analogy that would be closer would be if the shop said you must use some overpriced but notoriously fragile tools and you'll be on the hook for any tool that breaks and any delay you incur will be your fault while they go buy a new tool. Plus the tools tend to have sharp edges on the handles for some reason and are just painful to use.

Now if the job is "you need to administrate the group policy of the company systems", then "I refuse to run Windows" is a pretty stupid take. But frequently the job is rooted entirely in Linux based infrastructure for internet facing stuff, and Windows on the entry point is just horribly awkward for that job. You can kind of/sort of get there but I haven't found a single decent 'Terminal' even compared to that being pretty trivial with Mac and Linux. WSL starts to provide something useful, but it is kind of fragile and WSLg sucks with the worst window management possible, even by the standards of Windows broadly. Meanwhile, starting from a Linux system you can use a desktop shell that is probably better for your productivity than anything Windows allows.

There's not really a whole lot of logic for a lot of "Windows required" jobs in tech. Office365 is mostly fine through a Linux browser. Onedrive works with Linux. If you have some applications that are Windows only, again, sure, but a lot of tech folks don't need any Windows only tools.

Recent example from my real world, someone was around my desk and asking questions about stuff that required me to hop between a few contexts. They were shocked how quickly I could navigate a bunch of the windows in the discussion, and asked how in the world I got Windows to do that. Of course, I couldn't.

Besides, the general tone of the conversation could have been just full of redflags about how tortuous the company was going to be. One company blocked SSH between anything saying SSH was insecure, and said that, somehow, we had to do everything through the graphical console of the Linux instances. Which meant no rsync, no scp, having to create some file serving facility to upload files to and then download from. If my daily workflow depended on such draconian crap, I'd be out of there too.