I'm a U.S. servicemember working on a specialized Windows network that relies heavily on PowerShell. I've built and maintained several production tools, and I'm interested in joining the engineering team responsible for the network's larger script ecosystem. Before applying, I'd like feedback on my portfolio and suggestions for skills or projects I should add.
Because the work involves a controlled military network, I can only describe the functionality rather than share the source code. My projects include:
- A large module for creating Windows Forms GUIs in PowerShell, including simplified object creation, rendering, and coordinate positioning.
- Emergency power-on and power-off automation for an entire network, including physical infrastructure, checkpoints, and customizable functions.
- A GUI tool that removes Windows profiles through WMI while allowing administrators to exempt selected profiles.
- A script that gathers information from multiple network servers into a JSON-based data store and lets administrators locate a device's switch and interface using an IP address, client name, or MAC address.
- A two-sided access-request system for Active Directory groups. Users submit requests through a GUI, while administrators review them through a custom command-line interface. Approved requests add the user to the group, and the requester receives the decision by email.
- Installer scripts for my larger application-style packages, with configurable initialization settings, network-specific values, and no hard-coded FQDNs or mail servers. Credentials are handled securely, and data is generally stored in XML or JSON.
- More traditional automation for correcting Active Directory user configurations, sending reminders, managing software installations, updating certificates, and monitoring certificate expiration.
These tools are used regularly by administrators and are designed to work across different Windows-based environments. What important skills or areas of experience am I not demonstrating yet, and what would make this portfolio stronger for a PowerShell-focused engineering or automation role?
3 Answers
Your next steps depend on the role you want after military service. Some organizations do need people who maintain large PowerShell environments, but many employers want broader infrastructure or DevOps experience and may not want to maintain a huge collection of custom scripts. Treat PowerShell as an important specialization within a wider systems skill set.
Build evidence that you can work with Git, REST APIs, databases, Windows and Linux administration, cloud services, and deployment pipelines. If you’re targeting a specialized internal engineering team, emphasize scale, uptime, operational risk, and how many administrators or systems use your tools. If you’re targeting the private sector, translate the military environment into neutral descriptions of the size, complexity, and business impact.
PowerShell can absolutely be the main focus of a job, but employers will usually classify the role as systems engineering, administration, automation, or DevOps rather than simply “PowerShell engineer.” Your projects sound substantial, especially because they support real operations. Present them in terms of the problems solved, scale, reliability, security controls, testing, and measurable time or error reductions—not just the fact that they are scripts.
To broaden your profile, add experience with source control and collaboration workflows, automated testing, code review, documentation, CI/CD, logging, error handling, and deployment. PowerShell is one tool in the toolbox, so familiarity with Python, SQL, APIs, cloud platforms, and configuration-management tools would also help.
That makes sense. I’ve mainly focused on making the tools useful and reusable, but I need to document the engineering practices behind them more clearly. I’ll also start organizing examples around outcomes and operational impact rather than just listing features.
The portfolio sounds more advanced than a typical collection of administrative scripts. The GUI framework, network automation, approval workflow, and installer system show that you understand reusable design and application-style development. The biggest challenge is proving that the work is maintainable by someone other than you.
For each project, show a sanitized architecture diagram, a README, sample configuration, a testing strategy, version history, and a short explanation of security decisions. Public demonstration projects could use mock servers or simulated data so you can show the design without exposing restricted information. Also be ready to explain how you handle partial failures, retries, rollback, concurrency, permissions, secrets, and changes to dependencies.
There are specialized PowerShell-heavy jobs, but they’re uncommon. A broader title such as automation engineer, systems engineer, or DevOps engineer may give you more opportunities while still letting you use PowerShell heavily.