Jobs · Engineering · Virginia

Mid - Systems Engineer – MECM / Site Reliability Engineering (SRE) (w/ active Secret)

CriticalSolutions, LLC · Norfolk, VA · 1 mo ago
Engineering$85k–$110k/yrFull-time
We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must only include sections that have real specific content. The posting includes location, clearance, type, salary range, primary roles and responsibilities (list), basic qualifications (list), preferred qualifications (list), key metrics of success (list), additional info (clearance requirement, citizenship, pay and benefits). We need to avoid repeating job title as heading. No Job ID. Remove boilerplate (cookie/navigation/legal/EEO etc). Not present. We need to decide sections: Could have About the role (maybe a brief paragraph summarizing role). Responsibilities (list of duties). Requirements (basic qualifications). Qualifications (maybe preferred qualifications). Skills (maybe combine). Benefits (benefits snapshot). Pay (salary range). Schedule (maybe full-time on-site). The posting says Type: Full-time, On-site. So schedule could be Full-time, On-site. We must not create sections with filler like "commensurate with experience". We have actual salary range, so Pay section is okay. Benefits: we have benefit snapshot. Schedule: we have full-time on-site. We need to preserve all substantive info; not invent or summarize away detail. So we need to include details from responsibilities, qualifications, etc. We must use
  • for any list of duties/requirements/benefits, and

    for prose. We need to avoid duplication. Let's extract content. Location: Norfolk, VA and Pearl Harbor, HI. Clearance: Secret. Type: Full-time, On-site. Salary Range: $85,000 - $110,000. Primary Roles And Responsibilities: a paragraph with many sentences. We'll turn into list items? The instruction: Use

    • for any list of duties/requirements/benefits. The responsibilities are a paragraph with many sentences separated by periods. Could treat each sentence as a list item. Better to keep as

      maybe? But they said use

      • for any list of duties/requirements/benefits. The responsibilities could be considered a list. We'll break into items. Let's list responsibilities sentences: 1. Work alongside the development and operations teams to ensure speedy and reliable software deployments, monitor systems, and improve overall reliability of the platform. 2. In addition, as you discover and document system bugs, you have the motivation to go off and fix them yourself. 3. Develop features utilize the AI coding tool and repository of scripts to automate, scale, test, and secure the cloud infrastructure and the pipelines. 4. Enhance performance monitoring of the various systems via Splunk or other dashboard reporting tools. 5. Identify performance bottlenecks and optimize the performance of cloud infrastructure. 6. Contribute to continuing our SRE journey by suggesting ways to improve engineering build, maintenance, automation and reliability across the platform with SRE/DevOps tools and Infrastructure-as-Code. 7. Develop and code high-quality pipeline automation workflows to support inside and outside the cloud platform that are appropriate for business and technology strategies. 8. Develop and execute test strategies that simulate real-world failure scenarios, including network disruptions, hardware failures, and system overloads. 9. Create, script, and run performance tests to measure system behavior under varying levels of load and traffic. Identify bottlenecks, performance degradation, and areas for optimization. 10. Design, implement, and maintain automated test suites for infrastructure and application components. Ensure that testing is integrated into the CI/CD pipeline to validate system reliability with every release. 11. Build automated systems for continuous performance testing, stress testing, and load testing. 12. Work closely with SREs, developers, and operations teams to define reliability goals and develop appropriate testing strategies to validate those goals. 13. Ensure that new services and features undergo thorough testing for performance, reliability, and failure recovery before deployment to production. 14. Validate that monitoring, logging, and alerting mechanisms are functioning correctly by testing systems under failure conditions. 15. Ensure that Service Level Indicators (SLIs) and Service Level Objectives (SLOs) are accurately measured and tracked through automated testing frameworks. 16. Resolve most conflicts between timeline, budget, and scope independently but intuitively raise sophisticated or consequential issues to senior management. That's many items. Basic Qualifications: list of requirements. We'll turn into list. - Requires BS degree and 5-10 years of prior relevant experience or Master's with 4-8 years of prior relevant experience. - Currently possess and ability to maintain an active DoD Secret security clearance. - Minimum of DoD 8570.01 IAT Level II Certification required prior to onboarding and must maintain certification while supporting the SMIT Contract. - Must be able to support program execution in classified environments and access SIPRNet from an NMCI location on short notice (local travel). - Experience with automated script design, coding, debugging, and maintenance skills (using bash, python, etc.) preferred - Experience designing, deploying, and maintaining Microsoft Endpoint Configuration Manager (MECM) environments at enterprise scale. - Proven ability to optimize MECM infrastructure for performance, reliability, and high availability. - Hands-on experience creating and managing MECM device collections, task sequences, applications, packages, and operating system deployment images. - Expertise in automating MECM administrative tasks using PowerShell, APIs, and infrastructure-as-code tooling. - Strong background in Windows endpoint management, including patching strategies, compliance baselines, configuration items, and reporting. - Demonstrated ability to improve endpoint reliability through monitoring, observability tooling, and proactive remediation. - Experience integrating MECM with cloud-based services such as Intune, Azure AD, and Windows Update for Business. - Ability to troubleshoot complex MECM client and server issues using logs, diagnostics, and platform health data. - Experience supporting enterprise-wide operating system deployments and in-place upgrades using MECM automation pipelines. - Knowledge of SQL Server administration relevant to maintaining MECM databases and enabling performance tuning. - Experience contributing to system reliability through continuous improvement, infrastructure monitoring, and configuration drift reduction. - Strong understanding of networking concepts supporting MECM components such as DP distribution, boundary groups, and PXE services - Ability to work in a highly collaborative, forward thinking, and innovation-driven environment - Knowledge of Agile and DevSecOps/SRE concepts and best practices, with a desire to grow that knowledge - Hand-on experience with Atlassian products (Jira, Confluence, Bitbucket, etc.). - Experience creating JIRA and/or Azure DevOps workflows, projects, custom configurations - Experience administrating/maintaining SRE platform via Ansible playbooks (e.g. upgrading Jenkins) - Experience in automating tasks with scripting languages like PowerShell, or Python - Integrating/maintaining with various 3rd party CI/CD tools like Jenkins and Gitlab. - Experience with commercial cloud infrastructure deployment environments such as AWS and Azure. - Experience with automated provisioning and configuration tools like Terraform, Cloud Formation, Chef, Puppet, Ansible, or similar technologies. - Working knowledge of the Risk Management Framework (RMF), DISA STIGs Preferred Qualifications: list. - Previous work experience providing support to the NGEN-NMCI program - Experience with Infrastructure as Code (IaC) tools such as Terraform, Ansible, or CloudFormation for automating test environments. - ITILv4, Scrum Master, or Agile SAFe certification(s) or applicable experience Key Metrics Of Success For The Team: list. - Improved system reliability, as measured by adherence to Service Level Objectives (SLOs) and reduced Mean Time to Recovery (MTTR). - Comprehensive and regularly updated automated test coverage for all critical systems and infrastructure components. - Timely identification and resolution of performance bottlenecks and failure points. - Integration of automated testing into the CI/CD pipeline, ensuring continuous reliability validation. - Increased scalability and performance of systems under high load due to effective performance testing. Additional Information: includes clearance requirement, citizenship, pay and benefits. We already have Pay and Benefits sections. We need to include location, clearance, type maybe in About the role paragraph. Let's craft About the role: a short paragraph summarizing role: "This full-time on-site position is based in Norfolk, VA and Pearl Harbor, HI, requiring an active DoD Secret clearance. The role involves working with development and operations teams to ensure reliable software deployments, monitoring systems, improving reliability, developing automation, testing, and contributing to SRE initiatives." We must not repeat job title. That's fine. Now sections: About the role (

        About the role

        ...

        ), Responsibilities (

        Responsibilities

          ...)
        , Requirements (

        Requirements

          ...)
        (or Qualifications?). The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can choose which to include. We have basic qualifications (requirements) and preferred qualifications (qualifications/skills). We could map Requirements to basic qualifications, Qualifications to preferred qualifications, Skills maybe not needed. But we could combine skills into Qualifications. However we should not create thin sections. We have substantive content for Requirements and Qualifications. Benefits and Pay we have. Schedule we have (Full-time, On-site). So we can include Schedule section. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay, Schedule. We must not include empty sections. Now we need to ensure we don't include boilerplate like "US CITIZENSHIP IS REQUIRED." That's substantive; we could include in About the role or Requirements? It's a requirement. Could add to Requirements list: "US citizenship is required." Also clearance requirement already in About the role but also could be in Requirements. We'll keep in About the role. We must not repeat info unnecessarily but preserve all substantive info. It's okay to mention clearance in both About and Requirements? Might be duplication but okay. Better to include in Requirements as well. Let's extract US citizenship requirement: "US CITIZENSHIP IS REQUIRED." Also "Must possess an active DoD Secret Clearance. In addition, selected candidate must undergo background investigation (BI) and finger printing by the federal agency and successfully pass the preceding to qualify for the position." That's clearance details. We'll include in Requirements list. Now Benefits: "BENEFIT SNAPSHOT: 100% premium coverage for Medical, Dental, Vision, and Life Insurance, Supplemental Insurance, 401K matching, Flexible Time Off (PTO/Holidays), Higher Education/Training Reimbursement, and more." We'll make list items. Pay: "Salary range $85,000 - $110,000. The salary range for this position represent the typical salary range for this job level and this does not guarantee a specific salary. Compensation is based upon multiple factors such as responsibilities of the job, education, experience, knowledge, skills, certifications, and other requirements." We'll put in

        . Schedule: "Type: Full-time, On-site." We'll put in

        . Now ensure we don't include any markdown fences. Output only HTML. Let's craft. We need to escape any HTML special characters? Not needed. Let's produce:

        About the role

        This full-time on-site position is based in Norfolk, VA and Pearl Harbor, HI and requires an active DoD Secret clearance and US citizenship. You will work alongside development and operations teams to ensure speedy and reliable software deployments, monitor systems, improve reliability, develop automation, test infrastructure, and contribute to SRE initiatives.

        Responsibilities

        • Work alongside the development and operations teams to ensure speedy and reliable software deployments, monitor systems, and improve overall reliability of the platform.
        • As you discover and document system bugs, motivate yourself to fix them.
        • Develop features using the AI coding tool and repository of scripts to automate, scale, test, and

Similar jobs