Observability Engineer
for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Preserve all substantive info.
We need to parse the job description.
Key sections:
- About the role: maybe a paragraph summarizing role. The description starts: "Everforth ECS is seeking a Observability Engineer in our Fairfax, VA office in a hybrid capacity. Everforth ECS Federal is seeking a Observability Engineer to support development and operationalization of enterprise observability, telemetry visualization, operational analytics, and monitoring capabilities within a federal healthcare environment supporting the DOW." Also later: "The Kibana/Observability Engineer will act as the principal subject matter expert for designing, deploying, and maintaining the Elastic Observability solution (Logs, Metrics, APM, and Uptime/Synthetics) across Department of DOD/DISA Enterprise and cloud environments."
We can combine into About the role paragraph.
- Responsibilities: list of duties: "Initiatives with hands-on Kibana dashboard and visualization development experience Design and develop native and complex Kibana dashboards, visualizations, analytics workflows, and operational reporting capabilities Architect, engineer, and scale Elastic environments specifically tuned for time-series metrics, distributed tracing, and high-volume application logs Deploy and instrument Elastic APM agents across diverse application stacks (Java, .NET, Node.js, Python) to trace transactions and isolate performance bottlenecks Configure advanced alerting rules and leverage Elastic Machine Learning (anomaly detection) to identify system degradation before it impacts end-users Collaborate with engineering and security teams to normalize telemetry and improve observability coverage Build intuitive, role-specific Kibana dashboards and Canvas workpads that unify logs, metrics, and traces for rapid root-cause analysis by IT operations Monitor system activity and identify anomalous or suspicious operational trends Support:Operational awareness, incident monitoring, and continuous monitoring activities Implementation and monitoring of Service Level Indicators (SLIs) and Service Level Objectives (SLOs)Training and knowledge transfer for operational stakeholdersDevelop reporting and visualization strategies supporting executive and operational stakeholders"
We need to break into bullet list.
- Requirements: likely the mandatory qualifications: "U.S. Citizen.Active DoD Secret security clearance.Required active certifications:DoD 8140 IAT Level II Security+ (or higher) or CISSP.AWS Certified CloudOps Engineer - AssociateAWS Certified Solutions Architect - AssociateBachelor’s degree in Cybersecurity, Information Technology, Engineering or Computer Science, 7+ years of experience experience."
Also maybe "Ability to support 10-15% travel" etc. But travel could be requirement.
- Qualifications: maybe overlapping with requirements. But we need to decide sections: The instruction says use headings for those categories if content present. We can combine some. However we must not create thin sections. We need to decide which sections have substantive content.
We have:
- About the role: yes.
- Responsibilities: yes.
- Requirements: yes (citizenship, clearance, certifications, degree, experience).
- Qualifications: maybe we can treat as "Preferred qualifications" or "Desired Skills". The posting has "Desired Skills" section with list of preferred certifications and experience. That could go under Skills or Qualifications. The instruction says we have headings for Skills, Benefits, Pay, Schedule. So we can put desired skills under Skills. Required skills maybe under Requirements? Actually there is a "Required Skills" heading in the raw text: "Required Skills U.S. Citizen.Active DoD Secret security clearance.Required active certifications:..." That's basically requirements. Then later "Desired Skills" list.
Thus we can map:
- Requirements: mandatory (citizenship, clearance, certifications, degree, experience, maybe travel).
- Skills: desired skills (preferred certifications, experience with certain tools, etc.)
- Benefits: The posting mentions "General Description Of Benefits" but no details. It says "General Description Of Benefits" then no specifics. Since no actual benefit details, we should NOT create Benefits section because it would be filler. The rule: never create Pay/Schedule/Benefits sections unless posting actually states them. It only says "General Description Of Benefits" with no detail, so we should omit Benefits.
- Pay: Salary is mentioned: "Note: Salary is commensurate with skillset, qualifications, experience, and educational background. Salary Range: $140,000-165,000". So we have Pay section with that info.
- Schedule: hybrid capacity mentioned: "in our Fairfax, VA office in a hybrid capacity." Also maybe mention travel 10-15%. So we can include Schedule section with hybrid work and travel.
We must not repeat job title as heading. So no heading for Observability Engineer.
We need to output only HTML fragment.
Structure:
About the role
...
Responsibilities
- ...
...
Requirements
- U.S. Citizen
- Active DoD Secret security clearance
- Required active certifications: DoD 8140 IAT Level II Security+ (or higher) or CISSP
- AWS Certified CloudOps Engineer - Associate
- AWS Certified Solutions Architect - Associate
- Bachelor’s degree in Cybersecurity, Information Technology, Engineering or Computer Science
- 7+ years of experience
- Ability to support 10-15% travel
But note travel maybe schedule. However we can keep travel under Requirements or Schedule. Since schedule section will cover hybrid and travel. Might be better to put travel under Schedule. Let's decide: Schedule section: hybrid work (Fairfax, VA office hybrid capacity) and 10-15% travel.
Thus Requirements exclude travel.
Now Skills: desired skills list.
We need to parse desired skills:
"Desired Skills One or more related certifications preferred:AWS Certified Cloud PractitionerElastic Certified Engineer or Elastic Certified Observability Engineer AWS Certified Security or Microsoft Azure Security Engineer Equivalent cybersecurity or cloud certificates AWS Certified DevOps Engineer - Professional or equivalent certification.Hands-on experience supporting observability platforms within AWS GovCloud or other regulated cloud environments.Experience with:Elastic Stack, Amazon CloudWatch, AWS X-Ray and OpenTelemetry.Monitoring Kubernetes, Amazon EKS, containers and distributed microservices.Proficiency with Terraform, CloudFormation or comparable infrastructure-as-code tools.Familiarity with SRE practices, including SLIs, SLOs, error budgets, incident response and root-cause analysis.Scripting or development experience with Python, Java, PowerShell or similar languages.Knowledge of NIST 800-53, FedRAMP, FISMA, RMF and DISA STIG requirements."
We need to break into bullet list.
Also there is "General Description Of Benefits" but no details, so omit Benefits.
Pay: we have salary range and note about commensurate.
Schedule: hybrid capacity and travel.
Now we need to ensure we don't duplicate content. Also we need to preserve all substantive info. Let's extract all substantive sentences.
From description:
- Everforth ECS is seeking a Observability Engineer in our Fairfax, VA office in a hybrid capacity.
- Everforth ECS Federal is seeking a Observability Engineer to support development and operationalization of enterprise observability, telemetry visualization, operational analytics, and monitoring capabilities within a federal healthcare environment supporting the DOW.
- The Kibana/Observability Engineer will act as the principal subject matter expert for designing, deploying, and maintaining the Elastic Observability solution (Logs, Metrics, APM, and Uptime/Synthetics) across Department of DOD/DISA Enterprise and cloud environments.
- Initiatives with hands-on Kibana dashboard and visualization development experience
- Design and develop native and complex Kibana dashboards, visualizations, analytics workflows, and operational reporting capabilities
- Architect, engineer, and scale Elastic environments specifically tuned for time-series metrics, distributed tracing, and high-volume application logs
- Deploy and instrument Elastic APM agents across diverse application stacks (Java, .NET, Node.js, Python) to trace transactions and isolate performance bottlenecks
- Configure advanced alerting rules and leverage Elastic Machine Learning (anomaly detection) to identify system degradation before it impacts end-users
- Collaborate with engineering and security teams to normalize telemetry and improve observability coverage
- Build intuitive, role-specific Kibana dashboards and Canvas workpads that unify logs, metrics, and traces for rapid root-cause analysis by IT operations
- Monitor system activity and identify anomalous or suspicious operational trends
- Support:Operational awareness, incident monitoring, and continuous monitoring activities
- Implementation and monitoring of Service Level Indicators (SLIs) and Service Level Objectives (SLOs)
- Training and knowledge transfer for operational stakeholders
- Develop reporting and visualization strategies supporting executive and operational stakeholders
- Note: Salary is commensurate with skillset, qualifications, experience, and educational background. Salary Range: $140,000-165,000
- General Description Of Benefits (no detail)
- Required Skills U.S. Citizen.Active DoD Secret security clearance.Required active certifications:DoD 8140 IAT Level II Security+ (or higher) or CISSP.AWS Certified CloudOps Engineer - AssociateAWS Certified Solutions Architect - AssociateBachelor’s degree in Cybersecurity, Information Technology, Engineering or Computer Science, 7+ years of experience experience.
- Experience with the following:Supporting Elastic observability, telemetry analytics (e.g., OpenTelemetry, SIEM/log architectures) and operational monitoring implementations.Developing executive dashboards, operational reporting, and visualization strategies.Cloud architecture, system administration, and infrastructure-as-code principles.Familiarity with SIEM, telemetry analytics, metrics, distributed tracing, and observability concepts.Knowledge in software engineering and development methodologies (essential for deep APM and code-level tracing).Ability to apply analytical reasoning to comprehend complex distributed systems, microservices architectures, and telemetry data.Understanding of Federal cybersecurity and compliance environments preferred.Excellent written, presentation, and stakeholder engagement skills Ability to support 10-15% travelStrong problem-solving and decision-making capabilities, with a proven ability to weigh the relative costs and benefits of potential actions and identify the most appropriate solution.Highly developed interpersonal and oral/written communication skills, with the ability to effectively and professionally interact with a diverse set of stakeholders (from peers to end-users to executive management).
- Note: Salary is commensurate with skillset, qualifications, experience, and educational background. (duplicate)
- Desired Skills One or more related certifications preferred:AWS Certified Cloud PractitionerElastic Certified Engineer or Elastic Certified Observability Engineer AWS Certified Security or Microsoft Azure Security Engineer Equivalent cybersecurity or cloud certificates AWS Certified DevOps Engineer - Professional or equivalent certification.Hands-on experience supporting observability platforms within AWS GovCloud or other regulated cloud environments.Experience with:Elastic Stack, Amazon CloudWatch, AWS X-Ray and OpenTelemetry.Monitoring Kubernetes, Amazon EKS, containers and distributed microservices.Proficiency with Terraform, CloudFormation or comparable infrastructure-as-code tools.Familiarity with SRE practices, including SLIs, SLOs, error budgets, incident response and root-cause analysis.Scripting or development experience with Python, Java, PowerShell or similar languages.Knowledge of NIST 800-53, FedRAMP, FISMA, RMF and DISA STIG requirements.
- #EverforthECS1 ECS Federal LLC is an equal opportunity employer ... (boilerplate)
- Everforth ECS is the federal segment of Everforth, a $4B global organization with over 10,000 employees. Our nearly 3,
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Preserve all substantive info. We need to parse the job description. Key sections: - About the role: maybe a paragraph summarizing role. The description starts: "Everforth ECS is seeking a Observability Engineer in our Fairfax, VA office in a hybrid capacity. Everforth ECS Federal is seeking a Observability Engineer to support development and operationalization of enterprise observability, telemetry visualization, operational analytics, and monitoring capabilities within a federal healthcare environment supporting the DOW." Also later: "The Kibana/Observability Engineer will act as the principal subject matter expert for designing, deploying, and maintaining the Elastic Observability solution (Logs, Metrics, APM, and Uptime/Synthetics) across Department of DOD/DISA Enterprise and cloud environments." We can combine into About the role paragraph. - Responsibilities: list of duties: "Initiatives with hands-on Kibana dashboard and visualization development experience Design and develop native and complex Kibana dashboards, visualizations, analytics workflows, and operational reporting capabilities Architect, engineer, and scale Elastic environments specifically tuned for time-series metrics, distributed tracing, and high-volume application logs Deploy and instrument Elastic APM agents across diverse application stacks (Java, .NET, Node.js, Python) to trace transactions and isolate performance bottlenecks Configure advanced alerting rules and leverage Elastic Machine Learning (anomaly detection) to identify system degradation before it impacts end-users Collaborate with engineering and security teams to normalize telemetry and improve observability coverage Build intuitive, role-specific Kibana dashboards and Canvas workpads that unify logs, metrics, and traces for rapid root-cause analysis by IT operations Monitor system activity and identify anomalous or suspicious operational trends Support:Operational awareness, incident monitoring, and continuous monitoring activities Implementation and monitoring of Service Level Indicators (SLIs) and Service Level Objectives (SLOs)Training and knowledge transfer for operational stakeholdersDevelop reporting and visualization strategies supporting executive and operational stakeholders" We need to break into bullet list. - Requirements: likely the mandatory qualifications: "U.S. Citizen.Active DoD Secret security clearance.Required active certifications:DoD 8140 IAT Level II Security+ (or higher) or CISSP.AWS Certified CloudOps Engineer - AssociateAWS Certified Solutions Architect - AssociateBachelor’s degree in Cybersecurity, Information Technology, Engineering or Computer Science, 7+ years of experience experience." Also maybe "Ability to support 10-15% travel" etc. But travel could be requirement. - Qualifications: maybe overlapping with requirements. But we need to decide sections: The instruction says use headings for those categories if content present. We can combine some. However we must not create thin sections. We need to decide which sections have substantive content. We have: - About the role: yes. - Responsibilities: yes. - Requirements: yes (citizenship, clearance, certifications, degree, experience). - Qualifications: maybe we can treat as "Preferred qualifications" or "Desired Skills". The posting has "Desired Skills" section with list of preferred certifications and experience. That could go under Skills or Qualifications. The instruction says we have headings for Skills, Benefits, Pay, Schedule. So we can put desired skills under Skills. Required skills maybe under Requirements? Actually there is a "Required Skills" heading in the raw text: "Required Skills U.S. Citizen.Active DoD Secret security clearance.Required active certifications:..." That's basically requirements. Then later "Desired Skills" list. Thus we can map: - Requirements: mandatory (citizenship, clearance, certifications, degree, experience, maybe travel). - Skills: desired skills (preferred certifications, experience with certain tools, etc.) - Benefits: The posting mentions "General Description Of Benefits" but no details. It says "General Description Of Benefits" then no specifics. Since no actual benefit details, we should NOT create Benefits section because it would be filler. The rule: never create Pay/Schedule/Benefits sections unless posting actually states them. It only says "General Description Of Benefits" with no detail, so we should omit Benefits. - Pay: Salary is mentioned: "Note: Salary is commensurate with skillset, qualifications, experience, and educational background. Salary Range: $140,000-165,000". So we have Pay section with that info. - Schedule: hybrid capacity mentioned: "in our Fairfax, VA office in a hybrid capacity." Also maybe mention travel 10-15%. So we can include Schedule section with hybrid work and travel. We must not repeat job title as heading. So no heading for Observability Engineer. We need to output only HTML fragment. Structure:
About the role
...
Responsibilities
- ... ...
Requirements
- U.S. Citizen
- Active DoD Secret security clearance
- Required active certifications: DoD 8140 IAT Level II Security+ (or higher) or CISSP
- AWS Certified CloudOps Engineer - Associate
- AWS Certified Solutions Architect - Associate
- Bachelor’s degree in Cybersecurity, Information Technology, Engineering or Computer Science
- 7+ years of experience
- Ability to support 10-15% travel