Znaleziono ~20 ofert w 0.290s, strona 1 z 1
Aplikuj
21 000 - 25 200 zł

Migration Senior IT Project Manager

@ITDS Polska Sp. z o.o. Microsoft Project Jira Confluence SharePoint Clarity Windows
Aplikuj
17 825 zł

Program Manager

@LANCESOFT POLAND SPÓŁKA Z OGRANICZONĄ ODPOWIEDZIALNOŚCIĄ Planview Clarity etc. JIRA Microsoft Excel SharePoint
Aplikuj
10 000 - 18 000 zł

Product Owner

@BLUEBINARY SPÓŁKA Z OGRANICZONĄ ODPOWIEDZIALNOŚCIĄ Jira Asana Google Analytics Hotjar Microsoft Power BI Clarity Microsoft Figma Miro Windows
Aplikuj
-

Data Web Analyst

@ALAB laboratoria Tableau Microsoft Clarity Google Analytics 4 SQL Microsoft Power BI QuickSight Looker AWS RedShift
Aplikuj
18 480 - 20 160 zł

Project Manager Support

@CRESTT sp. z o.o. Microsoft Excel PowerPoint SharePoint MS Project Jira Confluence Clarity PlanView Azure DevOps Trello Tableau
Aplikuj
30 240 - 33 600 zł

Programme Manager

@emagine Polska Clarity Jira Confluence aris MS Excel
Aplikuj
-

Project Manager | Branża Bankowa

@Edge One Solutions Sp. z o.o. MS Project Clarity Jira SharePoint Confluence
Aplikuj
25 200 - 31 920 zł

Senior Project Manager (Data Center Migration Program)

@CRESTT sp. z o.o. SDLC MS Project Jira Clarity SharePoint Confluence
Aplikuj
-

Teamcenter Quality (TCQ) Support Engineer

@Capgemini Polska Teamcenter Clarity Jira ABAP SAPUI5 Java Node.js PI CPI
Aplikuj
-

Teamcenter Quality (TCQ) Support Engineer

@Capgemini Polska Teamcenter Clarity Jira ABAP SAPUI5 Java Node.js PI CPI
Aplikuj
-

Teamcenter Quality (TCQ) Support Engineer

@Capgemini Polska Teamcenter Clarity Jira ABAP SAPUI5 Java Node.js PI CPI
Aplikuj
-

Teamcenter Quality (TCQ) Support Engineer

@Capgemini Polska Teamcenter Clarity Jira ABAP SAPUI5 Java Node.js PI CPI
Aplikuj
20 000 - 23 000 zł

Senior Project Manager

@Madiff Sp. z o.o. Jira Confluence Clarity
Aplikuj
-

Operational Resilience and Transformation Analyst

@HSBC Service Delivery Confluence Jira Clarity DORA IT service continuity planning technology risk operational resilience Cloud environments IT Infrastructure
Aplikuj
25 200 - 31 900 zł

Senior Project Manager (Data Center Migration Program)

@Crestt Jira Confluence Project management Sharepoint Software Development Life Cycle Project Clarity
Aplikuj
-

IT Project Management Officer

@HSBC Service Delivery Project Management PPTs Excel Discover BI Clarity PPM Top-Level Management ManCo ExCo Business management
Aplikuj
-

Staff Channels Business Manager

@HSBC Service Delivery Jira Confluence Pioneer Discover GPDM Clarity HIBS People Management
Aplikuj
24 360 zł

Scrum Master

@emagine Polska Scrum Master Agile Kanban Scrum Jira Confluence Clarity MS Excel
Aplikuj
10 000 - 15 700 zł

Specjalista Wiodący / Specjalistka Wiodąca ds. UX i badań użytkowników (UX Designer)

@TAURON Obsługa Klienta sp. z o.o. Figma Adobe XD Miro Axure Sketch HTML CSS Hotjar Google Analytics Clarity Windows
-

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