Znaleziono ~11 ofert w 0.179s, strona 1 z 1
Aplikuj
-

Senior iOS Developer (with German)

@Capgemini Polska Swift Objective-C Combine RxSwift Core Data Realm SQLite REST JSON SPM CocoaPods Git Gitflow
Aplikuj
-

Programista iOS – branża kryptowalut

@Sii Sp. z o.o. Swift UIKit SwiftUI Objective-C Unit Testing Combine xctest iOS
Aplikuj
-

Programistka (IoS) / Programista (IoS)

@VeloBank S.A. Swift SwiftUI Combine Xcode Git
Aplikuj
-

Audytorka / Audytor w Zespole Audytu Systemów Informatycznych

@VeloBank S.A. Swift SwiftUI Combine Xcode Git
Aplikuj
-

iOS Developer

@Sirocco Swift SwiftUI Combine Swift Concurrency SPM Mapbox Datadog.
Aplikuj
16 000 - 18 500 zł

iOS Developer

@Norbsoft SwiftUI iOS SDK iOS frameworks Swift Combine OOP XCode MVVM Objective-C Core Data
Aplikuj
-

iOS Developer

@Sirocco iOS Swift SwiftUI Combine
Aplikuj
15 000 - 30 000 zł

Senior iOS Developer (freelance)

@intent Swift IoT GitHub Actions Combine BLE stuctured concurrency
Aplikuj
28 600 - 40 300 zł

Mid/Senior iOS Developer

@PTT Consulting Swift Swift Package Manager MVVM MVC Multithreading ARC Bitrise Travis CI Jenkins CocoaPods Combine REST
-

Senior iOS Engineer

@Fresha SwiftUI UIKit Combine Objective-C
-

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