I'm a U.S. servicemember who learned PowerShell while supporting a highly specialized Windows network. I'm interested in joining the engineering team that develops and maintains the network's large collection of scripts, but I don't have a college degree and want to strengthen my portfolio before applying.
My experience includes a reusable PowerShell module for quickly building and positioning Windows Forms interfaces; scripts that coordinate emergency power-on and power-off procedures across physical and virtual infrastructure; a GUI utility for removing Windows profiles with exclusion options; and a tool that gathers data from multiple servers into JSON so administrators can locate a device's switch and interface using an IP address, client name, or MAC address.
I've also built a two-sided workflow for requesting and approving Active Directory group membership, including administrative review and email notifications. My larger projects include installer scripts, configuration options, initialization steps, portable settings instead of hard-coded infrastructure values, secure credential handling, and XML or JSON-based storage. Other automation includes correcting Active Directory user configurations, sending reminders, managing software installations, updating certificates, and monitoring certificate expiration.
The scripts are used operationally, but I can't share the source code because it is tied to a military network. What skills, technologies, documentation, testing practices, or portfolio projects should I add to demonstrate that I'm ready for a PowerShell-focused engineering role?
3 Answers
Be aware that some private-sector organizations may not want to maintain a large collection of PowerShell applications, and the title may vary considerably. Your experience could transfer well to Windows administration, identity and access management, endpoint engineering, platform engineering, or DevOps. Ask what kind of work you want after military service and build toward that target. Learning how to work with APIs, cloud platforms, infrastructure as code, containers, and databases will make your PowerShell experience much more marketable.
Your projects sound more substantial than ordinary one-off administration scripts. The reusable GUI framework, configurable installers, approval workflow, infrastructure automation, and device lookup tool all demonstrate application design. To make the portfolio convincing without showing classified code, create sanitized demonstrations or smaller public versions. Include architecture diagrams, sample inputs and outputs, setup instructions, test cases, failure scenarios, version history, and a clear explanation of the security decisions you made. A few polished repositories are more valuable than a long list of vague project descriptions.
PowerShell can absolutely be the main focus of a job, but employers usually hire for the broader role rather than for the language alone. Position yourself around systems administration, automation, identity, endpoint management, or DevOps, with PowerShell as your strongest tool. Add evidence of Git usage, code reviews, testing, CI/CD, logging, error handling, security, SQL, and at least one additional language such as Python. Also document the scale and impact of your work—how many systems it supports, how much time it saves, and how you made it safe to operate.
That makes sense. The scripts support a fairly large environment, so I’ll focus more on explaining the engineering practices and operational impact without exposing sensitive implementation details.
PowerShell specialists do exist, especially in environments with extensive Windows automation, but they’re relatively uncommon. That makes broad infrastructure knowledge important if you want more options.