<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0">
  <channel>
    <title>Observability Engineer - fortice RSS Feed</title>
    <link>https://jobs.co.uk/job/observability-engineer-fortice--2bdeca2d-cc30-436d-8034-f7a96e87669f</link>
    <description>RSS feed for Observability Engineer at fortice.</description>
    <language>en-gb</language>
    <lastBuildDate>Sun, 24 May 2026 19:49:55 GMT</lastBuildDate>
    <item>
      <title>Observability Engineer - fortice</title>
      <link>https://jobs.co.uk/job/observability-engineer-fortice--2bdeca2d-cc30-436d-8034-f7a96e87669f</link>
      <guid>https://jobs.co.uk/job/observability-engineer-fortice--2bdeca2d-cc30-436d-8034-f7a96e87669f</guid>
      <pubDate>Fri, 22 May 2026 11:52:43 GMT</pubDate>
      <description>Location: Telford | Salary: 581.75-581.75 Daily | Type: Contract | Observability Engineer  Clearance Required: SC Eligible  Duration: 6 months  Location: Telford - 2 days min per month  IR35 Status: Mandated PAYE only  Role Description:    As an Observability Engineer, you will be responsible for designing, implementing, and supporting monitoring solutions across a range of technologies and platforms, ensuring service stability, performance insight, and proactive incident management.  Key Responsibilities:   Translate high-level monitoring and non-functional requirements (NFRs) into actionable configurations in Dynatrace.   Deliver full-stack observability solutions, including application-aware network performance monitoring (NPM), synthetics, log analytics, and infrastructure metrics.   Collaborate with architects and project teams to integrate monitoring into solution designs and test strategies.   Maintain and enhance dashboards, alerts, and visualisations to support proactive service management.   Participate in continuous improvement initiatives and tooling exploitation to enhance operational efficiency within immature teams.    Required Skills and Experience:  Strong understanding and experience in SRE principals and methodologies  Strong un...</description>
      <category>Contract</category>
    </item>
  </channel>
</rss>