Znaleziono ~17 ofert w 0.209s, strona 1 z 1
Aplikuj
21 840 - 33 600 zł

Cortex & Card Systems Specialist

@People More P.S.A. switch technologies Cortex ATM systems payment network protocols card management systems
Aplikuj
-

Network Security Consultant (Pre-sales)

@Team Up Network Security routing Network Protocols Cybersecurity Grey Cortex Palo Alto
Aplikuj
18 000 - 28 000 zł

Senior Firmware Developer

@Emerson Process Management sp. z o. o. C++ Git Azure DevOps Yocto C Networking RTOS Cortex A/M/R
Aplikuj
16 800 - 21 000 zł

Senior React Developer

@BCF Software Sp. z o.o. React.js TypeScript Redux React Context Git
Aplikuj
-

C# / .NET Developer (Sekcja Produktów Dostępności Zapasu)

@Rossmann SDP .NET C# React Vue .NET 6+ Entity Framework REST API React Context hooks Redux Zustand) Vue 3 Piania Composition API Vite Vitest Axios Tanstack Query Kubernetes SQL SQL Server PostgreSQL NoSQL MongoDB Git CI/CD Prometheus Grafana Datadog TailwindCSS shadcn
Aplikuj
-

Specjalista IT/ Aplikacje Soft

@Corten Medic HL7 DICOM Systemy HISowe
Aplikuj
-

Specjalisty ds. infrastruktury IT

@Corten Medic Windows Server Linux VMware
Aplikuj
-

Kierownik/-czka działu IT​​​-Corten Medic-Warszawa

@Corten Medic ISO 27001 ISO 9001 Prince2
Aplikuj
25 000 - 26 000 zł

Frontend Team Lead (100% remote possible)

@Limango Polska React.JS React Hooks / Context API CSS3 HTML5 JavaScript REST API MOBX Redux SASS / LESS TypeScript
Aplikuj
-

SAP SD/MM/Retail Consultant | ( Remote | Part-Time Contract | Polish + English )

@DCV Technologies SD/MM and IS-Retail S/4HANA functionality Polish and English SAP Logistics processes in a retail context
Aplikuj
25 200 - 28 560 zł

Senior Frontend Engineer

@SQUARE ONE RESOURCES sp. z o.o. Office.js Next.js TypeScript JavaScript React.js Redux Contex API Rest APIs LLM integration
Aplikuj
22 680 zł

Frontend Developer (React)

@Scalo Sp. z o.o. React.js React Hooks Typescript ES6 Node React Context NextJS Webpack Jest Playwright
Aplikuj
17 400 - 20 900 zł

React Developer

@EndySoft React.js JavaScript HTML CSS Redux Context API MobX Webpack Vite Parcel Git TypeScript Jest Cypress JavaScript Next.js. Windows Linux
-

Senior/Lead DevOps Engineer

@Luxoft DXC ECS Terraform Jenkins Java (Spring Boot, vanilla Java, HLASM migration context implies legacy system knowledge is a plus but not explicitly required for the DevOps role itself, focus is on the target Java environment DevOps.)
-

Tech Lead DWH

@emagine Polska Data Platform Lakehouse MLOps Platform Cloud Technology (Azure, GCP, AWS preferred for migration context) Azure Databricks preferred for specific experience, but other cloud experience is valid for migration context knowledge. Focus on ELT for batch with custom frequency and event-driven architecture. API, Batch, Streaming data integration mechanisms. DDD for database modeling. HLD/LLD documentation. Data Security, Data Governance.
-

SAP Security Associate Manager / Manager (She/He/They)

@Accenture Polska SAP GRC SAP Cloud Identity Access Governance SAP Cloud Identity Services SecurityBridge (non-SAP security tool or SAP security tool depending on context, but listed as a tool in the SAP security context here.)
-

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