Navigating a Career in IT without Microsoft: Is It Feasible?

In my nearly 30 years in the Information Technology (IT) field, I've rarely seen an infrastructure that completely avoided Microsoft products. Despite the prevalence of Microsoft technologies, many IT professionals find value in their robust and user-friendly nature.#8230;

Avoiding Microsoft in IT: A Pragmatic Perspective

“Avoiding Microsoft” isn’t a particularly effective and worthwhile IT strategy. Microsoft offers some very good and mature technologies that are often easier to implement and administer compared to their Open Source or non-Microsoft alternatives. Organizations that operate pragmatically use the best tech to meet their needs. This frequently means a hybrid environment that includes but is not exclusively based on Microsoft products. Most of my career has involved such hybrid environments, even in my current position in a state government IT organization.

Most experienced IT people don't really care if they work with Microsoft or not. The core of technology remains remarkably similar across platforms. What truly matters is finding stuff you like to do and being as well-rounded as possible in your technological expertise.

Practical Examples of Microsoft Integration in IT Careers

It’s theoretically possible to avoid touching anything Microsoft, but in practice, there’s no guarantee you won’t run into a Microsoft product here and there. Here are a few examples:

Embedded Systems Development

For instance, if you’re embarking on a career in embedded systems development and programming tiny microcontrollers, you would need cross-development tools. Many of these tools are only available on Windows, making it challenging to entirely avoid Microsoft products. You might also develop software for mainframe computers in large organizations where some systems run on Windows, requiring testing and software development on that platform.

Networking Jobs

In any networking job, you’ll likely need to interact with Windows desktop and/or server systems, whether you’re troubleshooting, configuring, or maintaining them.

Document Preparation and Office Work

Even as an office worker, you’ll be using a Windows-based computer for documentation. It’s exceedingly common, with at least 87% of office PCs running Windows. Additionally, tools for creating and editing documents are often tied to Microsoft Word processors, further entwining you with Microsoft technology.

Desktop and Laptop Software Development

Should you decide to develop desktop or laptop software specifically for Macs, consider that the Mac market shares less than 10% of the global desktop/laptop market. When people demand a version of your software for Windows, which has an 87% market share, you may face a dilemma and need to negotiate to port your software to Windows. Refusal could mean missing out on a huge economic opportunity and losing your position.

Isolation in Non-Commercial Roles

Even in roles that seem isolated from direct software development and IT, you’ll still encounter Microsoft products. Teaching computer-related subjects might involve using software that Microsoft developed. For example, if you specialize in curating a computer museum focusing on microcomputers before the 1981 IBM PC, you’ll likely find that most of your exhibits contain some Microsoft software, as many early systems shipped with BASIC interpreters developed by Microsoft.

The Real-World Implications

No matter how you personally feel about Microsoft, its leaders, and its products, as a professional software developer, you need to be aware that artificially limiting your opportunities by avoiding Microsoft products entirely can significantly impact your career prospects. This is especially true in industries and roles where technology is integral to the job. Embrace the pragmatic approach and be open to learning and working with a variety of technologies to maximize your professional growth and adaptability.