Some engineering jobs are about shipping features. This one is about keeping the pipes that carry a defence mission's software running — securely, repeatedly, and without surprises. LMI is hiring a Platform Engineer to do exactly that, building and sustaining cloud-native platforms on AWS Kubernetes for a Department of War mission partner.
The role is remote, but the environment is anything but ordinary. The platforms this engineer supports connect to and operate within the Department of Defense Information Network (DODIN) — the sprawling, tightly controlled network that underpins US military communications and systems.
What the LMI Platform Engineer Actually Builds
According to the role description, the engineer will design, deploy, operate, and sustain secure cloud-native platform capabilities. In plain terms, that means creating the underlying infrastructure that other teams' applications run on — and then keeping it healthy.
The work spans platform architecture, infrastructure automation, container orchestration, application onboarding, cybersecurity compliance, observability, and continuous service improvement. It is a hands-on job: translating mission and application requirements into services that are reliable, repeatable, secure, and supportable.
Why a Kubernetes Job Inside DODIN Is Harder Than It Sounds
Running Kubernetes in a commercial cloud is a well-trodden path. Running it in an environment that must satisfy defence-grade cybersecurity compliance is a different discipline entirely.
Every automation script, every container image, every access path has to survive scrutiny that ordinary production environments never face. That is why the posting emphasises repeatability and supportability alongside raw engineering skill — the platform has to work the same way, securely, every time.
How This Role Fits LMI's Positioning
LMI describes itself as a new breed of digital solutions provider, and this posting reflects that framing. Rather than a narrow sysadmin brief, the role blends cloud engineering, security compliance, and service ownership.
For engineers, that combination is increasingly the profile government-adjacent contractors are hunting for: people who can move fluently between commercial cloud tooling and the stricter expectations of defence work.
Who This Job Is Really For
The description points to a hands-on engineer — someone comfortable in the terminal, not just in architecture diagrams. The ideal candidate can take a mission requirement and turn it into a platform service that other teams can rely on.
That means the strongest applicants are likely to have practical AWS and Kubernetes experience, a working understanding of container orchestration at scale, and exposure to compliance-driven environments. Observability and troubleshooting skills matter too, because platforms inside DODIN cannot afford silent failures.
What the Posting Confirms — and What It Doesn't
Confirmed from the role description: the position is remote, focused on AWS-hosted Kubernetes, tied to a Department of War mission partner, and operates within DODIN. Responsibilities include architecture, automation, orchestration, onboarding, compliance, observability, and service improvement.
Not confirmed: salary, contract length, clearance requirements, team size, or a hiring timeline. Those details are not disclosed in the source material and should not be assumed.
Why Defence Cloud Hiring Keeps Growing
This posting is a small but telling data point. Government and defence organisations continue to modernise onto cloud-native stacks, and that migration creates sustained demand for platform engineers who understand both the tooling and the rules.
Kubernetes has become the default orchestration layer for that modernisation. The bottleneck is rarely the technology — it is finding engineers who can operate it inside environments where compliance is not optional.
What Interested Engineers Should Do Now
If the role fits your background, the practical steps are straightforward: sharpen your AWS and Kubernetes fundamentals, be ready to talk about automation and repeatability, and prepare examples of how you have handled security compliance in production environments.
Observability experience — logging, monitoring, and tracing — is worth highlighting, since the posting explicitly names it. So is any prior exposure to government or defence-adjacent networks.
What Happens Next
LMI has not published a hiring timeline or shortlist process. Based on the description alone, the role will likely favour candidates who can demonstrate hands-on platform ownership rather than purely advisory experience.
For now, the posting stands as a clear signal of what defence-linked cloud teams are prioritising: engineers who can build secure, repeatable platforms — and keep them running.
Our Take
This is not a headline-grabbing story, but it is a useful one. It shows where the defence cloud talent market is tightening: at the platform layer, where security and automation meet.
For engineers weighing a move into government-adjacent work, roles like this are a reminder that the premium is not on knowing Kubernetes alone — it is on knowing how to run it where the rules are strictest.
Frequently Asked Questions
What is the LMI Platform Engineer role?
It is a remote engineering position focused on designing, deploying, operating, and sustaining secure cloud-native platforms on AWS Kubernetes for a Department of War mission partner, within the Department of Defense Information Network (DODIN).
What skills does the role require?
Based on the description: platform architecture, infrastructure automation, container orchestration, application onboarding, cybersecurity compliance, observability, and troubleshooting, with hands-on AWS and Kubernetes experience.
Is the position remote?
Yes. The role is listed as remote, though the work connects to and operates within DODIN, which carries its own security and compliance expectations.
What is DODIN?
The Department of Defense Information Network is the set of information systems and networks the US Department of Defense relies on for communications and operations. Working within it means meeting defence-grade security standards.
