DevOps System Engineer
global channel managementAnnapolis Junction (MD)
DevOps System Engineer
Posted yesterday
global channel managementAnnapolis Junction (MD)
SENIORITY
Lead
About the role
DevOps System Engineer Annapolis Junction, Maryland, United States$ 90.00 - 91.00 (US Dollar) DevOps System Engineer needs 14+ years of experience DevOps System Engineer requires: Linux environment Scripting: Bash or Python (required) Configuration: Ansible/Puppet/Salt (required) Containerization: Docker or Kubernetes (highly desired) Terraform experience (optional) Monitoring: Nagios/Splunk (configuration of monitoring) Familiarity and experience with some of the tech stacks used by AEA Development teams: Load Balancing: HAproxy/httpd etc. Web Servers: Tomcat/Nginx/Java etc. Database: MongoDB/Postgres/MySQL etc. AWS experience or certification (Cloud Architect or SysOps Administrator) DevOps role (Scripting, Ansible/Puppet, Kubernetes, etc.)DevOps System Engineer duties: Manage system requirements and derived requirements to ensure the delivery of production systems that are compatible with the defined system architecture(s), Service-oriented Architecture (SOA), etc. Contribute to the development of sections of systems engineering documentation such as System Engineering Plans, Initial Capabilities Documents, Requirements specifications, and Interface Control Documents Assist with the development of system requirements, functional requirements, and allocation of the same to individual hardware, software, facility, and personnel components Define the methods, processes, and evaluation criteria by which the systems, subsystems and work products are verified against their requirements in a written plan Participate in the development of system engineering documentation, such as System Engineering Plans, Initial Capabilities Documents, Requirements Specifications, and Interface Control Documents Participate in establishing and gaining approval of the definition of a system or component under development (requirements, designs, interfaces, test procedures, etc.) that provides a common reference point for hardware and software developers
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.