Skip to main content

About the role

Overview: In this role, you join a small, cross-functional team to support IronSled, a security-focused platform hosting federal applications. You will handle tenant issues, maintain platform reliability, and improve user experience, owning problems from intake to resolution while coordinating with senior engineers as needed. You’ll investigate across Kubernetes, deployments, pipelines, identity services, cloud infrastructure, and platform integrations, with opportunities to automate tasks and contribute to documentation. You work closely with product and engineering teams to evolve the platform and its support processes, with a strong emphasis on clear communication and customer outcomes.
Responsibilities: Manage tenant issues and service requests from intake to resolution Troubleshoot across Kubernetes, deployments, CI/CD, identity, networking, cloud services, and integrations Communicate status, requirements, next steps to tenants Escalate complex issues to senior engineers while maintaining ownership Document solutions and platform procedures in the knowledge base Identify repetitive tasks for automation or platform enhancements Assist with tenant onboarding, access requests, environment configuration, and deployment support Contribute to maintenance, testing, monitoring, and engineering work as skills grow
Key requirements: Active TS/SCI security clearance 1–3 years in platform/cloud engineering, DevOps, software development, systems administration, or technical support Foundational knowledge of Linux, containers, Kubernetes, cloud services, networking, CI/CD Experience troubleshooting technical issues methodically Familiarity with Git, GitLab or GitHub, CLI tools, and logs Ability to communicate technical information clearly to users with varying experience Strong ownership, organization, and follow-through for multiple issues Willingness to learn unfamiliar technologies and seek help when needed Clear communication Ownership and accountability Structured problem-solving Linux fundamentals Containers and Kubernetes Cloud services

Before you apply

Applying takes about a minute. These four things decide how fast it moves after that.

Your profile is current

It's what we read first. Occupations, seniority and locations matter more than a long history.

Two examples you can talk through

Not a portfolio — just two pieces of work where you can explain the decisions and what you'd change.

A number in mind

What you're on now and what would make you move. We negotiate better when we know both.

Your notice period

Employers plan around it, and it's the question that stalls offers most often.

Once you apply, someone reads it and calls you before anything reaches the employer — usually within two working days.

More like this