Znaleziono ~12 ofert w 0.202s, strona 1 z 1
Aplikuj
19 320 - 22 680 zł

Senior IT Analyst – Nordic Payment Solutions

@emagine Polska SEPA SQL Analytical Thinking UI
Aplikuj
15 750 - 20 580 zł

Starszy Analityk Systemów Biznesowych (Płatności)

@ITDS Polska Sp. z o.o. SQL Elixir Express Elixir Sorbet SEPA Target Git Windows
Aplikuj
9 240 - 11 760 zł

Helpdesk

@Connectis_ MS Office SEPA Swift
Aplikuj
18 480 - 21 000 zł

Analityk IT

@AVENGA (Agencja Pracy, nr KRAZ: 8448) SQL Elixir SEPA
Aplikuj
15 750 - 20 580 zł

Starszy Analityk Systemów Biznesowych (Płatności)

@ITDS Elixir Express SEPA
Aplikuj
-

IT Analyst (Payments)

@ALTEN Polska Swift ISO SEPA SQL
Aplikuj
-

Senior Business Analyst

@HSBC Technology Poland Business analysis Testing SEPA
Aplikuj
22 680 - 26 040 zł

Analityk Biznesowo - Systemowy (systemy rozliczeniowe)

@7N BPMN Elixir, Express Elixir, Sorbet, SEPA, Target UML SQL REST API Git DDD BDD
Aplikuj
15 750 - 20 580 zł

Starszy Analityk Systemów Biznesowych (Płatności)

@ITDS Microservices REST settlement systems systemy rozliczeniowe DDD SEPA Elixir Sorbet
Aplikuj
8 400 - 11 760 zł

Helpdesk

@Connectis Helpdesk MS Office MS Excel Elixir Sorbnet Swift SEPA
6 400 - 9 600 zł

Payments Back‑Office Officer

@Devire Swift Sepa Sorbnet Elixir
-

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