Znaleziono ~73 oferty w 0.165s, strona 2 z 2
Aplikuj
25 200 - 26 880 zł

Senior DevOps Engineer

@SCALO Kubernetes Docker Terraform IaC AWS Azure DevOps GCP
Aplikuj
-

GCP Cloud Data Architect

@in4ge sp. z o.o. GCP Data Architecture SQL Python IaC CI/CD Machine Learning
Aplikuj
-

Senior Site Reliability Engineer (SRE)

@EPAM Systems Unix DevOps Git IaC ITIL Azure ServiceNow Kubernetes Splunk Python
Aplikuj
17 018 zł

Data Engineer (with Microsoft Fabric)

@Sigli Microsoft Fabric Data Factory REST API ETL/ELT SaaS Python Azure IaC CI/CD
Aplikuj
25 000 - 32 500 zł

DevOps Engineer

@LetzCode Troubleshooting Ansible Python Bash Jenkins DevOps IaC CI/CD Kubernetes GitLab
Aplikuj
25 000 - 36 000 zł

Senior System Admin / DevOps Engineer

@AI INVESTMENTS sp. z o.o. Kubernetes Linux SQL Docker Helm ELK Stack GitOps IaC MySQL MongoDB Ansible Terraform TeamCity Jenkins RabbitMQ Bash Python Linux
Aplikuj
20 000 - 27 000 zł

DevOps Engineer

@in4ge sp. z o.o. Python Docker CI/CD IaC Linux Ubuntu Terraform Bash Ansible Git
Aplikuj
21 800 - 28 600 zł

Fullstack Developer (.NET + Angular)

@Lumicode (Grupa Pentacomp) .NET Angular TypeScript Unit testing SQL Server Azure Playwright IaC
Aplikuj
21 840 - 25 200 zł

Senior Cloud DevOps Engineer/Admin

@SCALO Kubernetes Jira Confluence GCP Ansible Jenkins IaC
Aplikuj
-

Senior Cloud Engineer with Cross-System Perspective

@emagine Polska Azure Powershell Bicep IaC ARM template Python
Aplikuj
-

Cloud Engineer

@Vodeno PostgreSQL Linux Docker Infrastructure as Code (IaC) Google Cloud Platform (GCP) Kubernetes / GKE Python Bash Go
Aplikuj
-

Senior Site Reliability Engineer (SRE)

@EPAM Systems Unix DevOps Git IaC ITIL Azure ServiceNow Kubernetes Splunk Python
Aplikuj
15 000 - 28 000 zł

Architekt / Inżynier Azure

@in4ge sp. z o.o. DevOps Azure DevOps Azure Terraform CI/CD IaC
Aplikuj
-

Konsultant(ka) ds. biznesowo - technologicznych

@Semantive Project Management AI Sales IaC DevOps
Aplikuj
-

Senior DevOps Engineer

@ERGO Technology & Services Azure DevOps Powershell Ansible Terraform IaC Kubernetes German Dataiku
Aplikuj
-

SAP Solution Architect

@EPAM Systems JavaScript AWS SAP HANA IaC CI/CD ABAP SAP Azure GCP Java
24 000 - 27 200 zł

Senior Azure DevOps Engineer

@Develocraft DevOps IaC Terraform PowerShell
23 000 - 31 000 zł

Senior DevOps Engineer

@Kitopi aws Infrastructure as Code (IaC) kubernetes
24 000 - 28 000 zł

Technical Project Manager (Cloud)

@Verita HR agile cloud Infrastructure as Code (IaC) jira migration project project management
-

Cloud Engineer

@The Dot Collective AWS GCP IaC Serverless
-

Tech Strategy & Client Growth Advisor

@Semantive cloud devops Infrastructure as Code (IaC)
-

Cloud DevOps Engineer/Admin

@Scalo CI/CD Ansible Jenkins IaC (Terraform, Ansible, Chef, etc.)
-

DevOps Engineer (Observability Focus)

@KUBO DevOps AWS Prometheus 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, 'Grafana', 'Loki', 'Prometheus', 'Tempo', '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, Grafana, 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, Loki, Grafana, Tempo, 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, Grafana, Tempo, Mimir), OpenTelemetry, AWS X-Ray, CloudWatch, ADOT, Terraform, CloudFormation, GitHub Actions, GitLab CI, Azure DevOps, Docker, 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, which it does. So, 'Grafana', 'Loki', 'Tempo', 'Mimir' should be separate tags. Prometheus is also mentioned. OpenTelemetry, AWS X-Ray, CloudWatch, ADOT are also mentioned. IaC tools: Terraform, CloudFormation. CI/CD tools: GitHub Actions, GitLab CI, 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
← Poprzednia strona