SRE Engineer— Observability & Monitoring

Company Background: Genuine Parts Company founded in 1928 and based in Atlanta, Georgia, is a leading specialty distributor engaged in the distribution of automotive and industrial replacement parts and value-added services. The Company operates a global portfolio of businesses with more than 10,000 locations across the world, employing 60,000 people. The GPC Global Technology Center in Krakow, established in 2022 by Genuine Parts Company is an innovative research and development facility supporting GPC’s digital transformation efforts. The hub is focused on the development of advanced technologies and solutions that support GPC's operations and growth. The GPC Global Technology Center team works on a wide range of projects assisting in areas such as e-commerce and data platforms, supply chain solutions, selling systems, and cyber security. This is home to a team of highly skilled IT engineers who are dedicated to driving innovation and delivering cutting-edge solutions for GPC. Position Purpose: SRE Engineer with strong hands-on observability expertise, responsible for the reliability of our growing eCommerce platform across its full stack — security, CDN, DNS, servers, databases, caching, and monitoring. Primary domain — observability and monitoring. Must have proven, hands-on experience building monitoring from the ground up: instrumentation, dashboards, alerting that catches problems before users do, and SLIs/SLOs established where none exist. Deep experience with a modern observability platform is essential — New Relic (our stack) is a strong plus, but solid hands-on experience with Datadog, Grafana/Prometheus, ELK, or similar is equally welcome, as long as it transfers. Requirements: 3+ years of hands-on SRE / Platform / Observability engineering, with a proven track record of building monitoring and observability from scratch — not just maintaining existing dashboardsDeep, hands-on command of the three pillars — logs, metrics, and traces — and the judgment to know which to reach for whenStrong experience with modern observability platforms: New Relic — a strong plus), Datadog, Grafana/Prometheus, and log platforms such as Elasticsearch / OpenSearch (ELK)Distributed tracing and instrumentation — hands-on with OpenTelemetry (or vendor agents), able to instrument services and follow a request across service boundariesDesigns alerting that actually works — symptom-based, actionable, tied to user impact, and tuned to avoid noise and alert fatigueAble to define and drive SLIs/SLOs, dashboards, and thresholds — and to establish them where they don't yet existObservability-as-code — managing monitors, dashboards, and alerts declaratively (Terraform or similar)Working knowledge of CI/CD (GitHub Actions), containers (Docker), and Azure — enough to instrument, deploy, and integrate observability independentlyScripting in Python and/or Bash Good communicator — partners with the SRE lead and works directly with dev teams to instrument their servicesOwnership mindset — treats observability as a product and drives it forward proactively Nice to have: Azure ACA; OpenTelemetry Collector pipelines; observability cost control (data volume, retention, sampling); incident response and post-incident review experience; e-commerce or high-traffic environments.