DevOps Engineer (Observability Focus)

KUBO

Gdańsk, Lęborska 3 +1 więcej
Hybrydowa
B2B
☁️ AWS
🔄 DevOps
Prometheus
Grafana
CloudFormation
Terraform
Loki
💼 B2B
Hybrydowa
freelance
Loki'
'Grafana'
'Tempo'
'Mimir' (LGTM stack) - Note: This is a common grouping but not a single tool
so listed as a descriptive string for clarity within tags if needed
or individual tags if preferred for strictness. For this schema
a descriptive string is used as it represents a suite of tools often used together for observability. If strict adherence to single tools is required
'Loki'
'Prometheus'
'Mimir' would be separate tags. Given the prompt's phrasing
this combined tag reflects the intent. If individual tools are preferred
please specify. For now
using the prompt's phrasing as a tag for context. Let's refine this to individual tags for better machine readability as per typical schema practices. Re-evaluating: The prompt lists 'LGTM stack (Loki
Tempo
Mimir)'. It's best to tag the individual components if the schema allows for multiple tags
which it does. So
individual tags are better. Let's list them individually. However
the prompt also mentions Prometheus separately. So
the list should be: Prometheus
Mimir
OpenTelemetry
☁️ AWS X-Ray
CloudWatch
ADOT. Let's ensure all mentioned technologies are captured. The prompt also mentions IaC tools like Terraform or CloudFormation
and CI/CD tools like GitHub Actions
GitLab CI
☁️ or Azure DevOps
🐳 Docker
🚢 Kubernetes. These should also be included as technology tags. The main focus is Observability
🤖 so that's the main_technology. The rest are supporting technologies. Let's compile the full list of relevant technologies from the job description for the tags. Technologies mentioned: Prometheus
LGTM stack (Loki
Mimir)
ADOT
GitHub Actions
☁️ Azure DevOps
🚢 Kubernetes. The core focus is Observability
🤖 so that's the main_technology. The tags should encompass the specific tools and concepts. Let's refine the tags to be specific and actionable. The prompt asks for 'technology_tags'. It's best to list the specific tools and concepts. Let's re-evaluate the 'LGTM stack' part. Since it's a collection
it's better to list the individual components if the schema allows for multiple tags
'Mimir' should be separate tags. Prometheus is also mentioned. OpenTelemetry
ADOT are also mentioned. IaC tools: Terraform
GitHub Actions
☁️ Azure DevOps. Containerization: Docker
🚢 Kubernetes. The main_technology is clearly 'Observability'. The tags should cover the specific technologies. Let's make sure the tags are concise and representative. The prompt mentions

Job description

Together with company focused on aerospace and defense technology we are seeking a DevOps Engineer with focus on Observability tools to join its team. The organization supports mission-critical systems and software for both civil and defense aviation, operating in international, high-security, and high-performance environments. This role focuses on building and maintaining cutting-edge observability solutions for complex cloud-native systems, contributing to the stability, transparency, and continuous delivery of scalable platforms.

Key responsibilities:

  • Design and manage observability solutions in cloud environments, collaborating closely with development and operations teams.

  • Implement and maintain monitoring, logging, and alerting systems using tools such as Prometheus and the LGTM stack (Loki, Grafana, Tempo, Mimir).

  • Automate the collection and visualization of telemetry data (metrics, logs, traces) to ensure high system visibility and reliability.

  • Develop and optimize CI/CD pipelines to seamlessly integrate observability into the development process.

  • Provision and manage infrastructure using Infrastructure as Code (IaC) tools like Terraform or CloudFormation.

  • Define observability best practices including metric selection, alert thresholds, and documentation standards.

  • Contribute to internal knowledge bases, documentation, and training around observability and monitoring tools.

  • Stay informed on emerging trends in cloud observability, monitoring tools, and DevOps methodologies.

  • Support automation of deployments through CI/CD platforms like GitHub Actions, GitLab CI, or Azure DevOps.

Ideal candidate profile:

  • Bachelor’s degree in Computer Science, Information Technology, or related field (or equivalent practical experience).

  • 3–5 years of experience in DevOps, Cloud Engineering, or related roles, with a focus on observability.

  • Solid experience with AWS cloud services, especially in observability and monitoring contexts.

  • Hands-on experience with OpenTelemetry, AWS X-Ray, CloudWatch, ADOT, and Grafana.

  • Familiarity with containerization and orchestration tools such as Docker and Kubernetes.

  • Strong troubleshooting skills and the ability to work effectively within cross-functional teams.

Preferred:

  • Experience with CI/CD practices and platform engineering.

  • Understanding of cloud security best practices.

  • Familiarity with Agile development environments.

  • A proactive attitude towards knowledge sharing and continuous improvement.

  • Strong communication skills, especially in presenting complex ideas to non-technical audiences.

Conditions:

  • Form of cooperation: B2B contract

  • Salary: negotiable, according your expectations

  • Location: Gdańsk, hybrid model

  • Multisport, private medical care, life insurance

Recruitment steps:

  • Phone call or Online meeting with a Recruiter (20 - 30 min.)

  • Interview with Client (2 rounds)

  • Decision and feedback

Wyświetlenia: 9
Opublikowana8 dni temu
Wygasaza 22 dni
Rodzaj umowyB2B
Tryb pracyHybrydowa
Źródło
Logo
Logo

Podobne oferty, które mogą Cię zainteresować

Na podstawie "DevOps Engineer (Observability Focus)"