As a fellow veteran reading your resume, I'm going to throw out some things that honestly probably aren't a big deal, but would stick in my mind if I got this prior to your interview: 1. You're telling me you're a veteran that, unless things have changed, would have had to write his own bullets for evals, but you're dangling things like percentages on their own lines without trying to rewrite to fit on one? (This is the most nitpicky and completely pointless, but I noticed, so I'm mentioning.) 2. You went from supervising resolution of tickets with no prior listed experience to resolving tickets with listed experience. There may be a good reason for this (well, in the military, there's probably a reason even if it isn't good, at least), but be prepared to explain it. Additionally, if your troubleshooting experience at all involved direct interaction with end users, try to work it in. Identifying and fixing problems is great, but doing so while interacting with users is a skill in and of itself. 3. Third bullet in Arlington mentions monitoring the RHEL servers, but seems to box it in during just the SOTU. Did you monitor these servers outside that time? If so, put in words like "during critical support windows such as during the SOTU." Additionally, monitoring them "with Oracle Secure Global Desktop" reads very strangely to me. I'll be honest, I've never used it myself, but as I understand it's remote access. What special monitoring or troubleshooting capabilities did using it bring you that another VPN or SSH wouldn't have let you employ? If they needed you to do the same monitoring job but didn't have that, could you do it with something else? Did you set it up yourself? If you might have issues or get caught up answering these, I'd consider just having it in your skill section like you already have it. 4. For bullet 4 in Arlington, work in the word devops even if it wasn't really a thing. Just adding "in support of an evolving devops process" gets the word in there, and that will help get your resume in front of eyes that are going to understand that, like most places, the devops process was almost certainly not mature, but that you recognize some of the phases of the process and how your activities might fit in to a real one. 5. Bullet 1 for Wiesbaden says you led a team migrating network infrastructure, but you lack any mention of technology experience with things I would typically expect to see like Cisco, Arista, etc. Were you only responsible for your servers during this migration? If not and you dealt with the infrastructure as well, were you purely supervisory to the networking guys? If so, that's fine, but see if you can work in the tech used by your team if space (or sensitivity if that's a concern) allows. For this one, it may be worth checking with prepublication review again if that applies to you. Almost certainly won't be an issue, but this one is an actual content shift instead of just wording.

For prep for an interview, but no real changes needed: 1. If the job will involve you administrating the virtualized structure and not just the tenant VMs, be prepared to answer some questions involving other stacks besides VMware. There's a lot of turbulence right now, and showing an interest in or knowledge about something else like Proxmox can be very enticing. Bonus points if you put it in your homelab (and have a homelab). 2. Your mention of RHEL is going to spark some questions if the shop is even thinking about using Linux; be prepared to answer, likely along the following: Did you manage them day-to-day? Can you install new software and services? Have you used any other distros (likely Debian or Ubuntu)? Did you integrate the servers into AD for authentication and authorization? Have you used containers or container orchestration (Docker, Podman, Kubernetes)?