🎁 Before you apply, rehearse this interview. Create your free WorkMundi account and get an Interview Training on HelpsYouSpeak — no cost, no card. I want my training →
Job Description At Tieto Caretech youll get a chance to provide patients and end users with product offerings that help them in their life, reinventing the world for good. If that sounds interesting, please keep on reading. About us Tieto Caretech is modernizing the Nordic health and social care sector with modular, open, and interoperable software. We develop and deliver high-quality software solutions and services that enable healthcare and welfare professionals to do their work even better and with higher efficiency - have more time to care. We are a global team of professionals working on providing products and services to different sectors from intensive care to laboratory and social care. In addition to working closely with our customers, we also have our own products that we build and develop for various fields in society. From enabling healthcare professionals to spend more valuable time with their patients to providing data for professional athletes to achieve even better results, we make all that possible. With us you can build technology for the good of society and make your mark on the health and wellbeing of people in need. About the role As a product development company with a multi-year history of building robust platform and clinical products, we are shaping the future of European healthcare using healthcare open standards. To support this vision, we are engineering a strictly cloud-agnostic web application and require a Lead DevOps Engineer having 7-9 years of hands-on experience in the field of DevOps to define and drive our infrastructure, deployment, and automation strategies. Our engineering culture emphasizes high autonomy, flat team alignment, and pragmatic problem-solving principles inspired by Nordic corporate standards. You will join at a critical transition period to lead our repository migration from Azure DevOps (ADO) to GitHub and architect an AI-native development environment. Your strategic decisions regarding Kubernetes and Terraform will ensure our product deploys seamlessly across both managed cloud and self-hosted environments. Technology Stack Infrastructure & Provisioning: Kubernetes (K8s), Terraform, networking, capacity planning, load balancing, high availability (HA), and disaster recovery (DR). CI/CD & Source Control: ArgoCD, Azure DevOps (ADO), GitHub (Transitioning), GitHub Actions AI Tooling: GitHub Copilot, Claude (for AI-native/agentic development workflows) Application Development Technologies: Fundamental knowledge of .NET 10, C#, Angular, and TypeScript is nice to have. Responsibilities Design CI/CD solutions to enable continuous and seamless application delivery. Infrastructure Strategy: Define the Infrastructure as Code (IaC) governance using Terraform and Kubernetes, strictly maintaining a cloud-agnostic posture that fully supports self-hosted deployments and Mult cluster environment management. Release on Demand Architecture: Architect and govern Release on Demand capabilities, decoupling continuous deployment from business releases. Design feature toggle strategies, blue/green deployments, and canary rollouts that align with healthcare compliance and SAFe delivery cadence. DevSecOps & Compliance: Architect compliance-as-code, integrating automated security gating (SAST, DAST, dependency scanning) directly into GitHub workflows to meet strict European healthcare regulations (e.g., GDPR, NIS2). Unified Observability: Define a vendor-neutral telemetry and monitoring strategy (utilizing standards like OpenTelemetry) to ensure consistent logging, metrics, and tracing across both cloud and self-hosted deployments. Troubleshooting: Ability to diagnose and resolve deployment issues by analyzing application and system logs. Workflow Architecture: Design and implement robust GitHub Copilot workflows and automated pipeline architectures that support our shift toward agentic and AI-native development. Strategic Migration: Architect and lead the end-to-end repository migration strategy from Azure DevOps to GitHub without disrupting active development cycles. Disaster Recovery (DR) Architecture: Design and govern multi-region failover strategies, automated backup architectures, and RTO/RPO standards to ensure the continuous availability of critical clinical systems. Technical Leadership: Act as the primary DevOps authority within our SAFe/Agile Scrum framework, providing fact-based, pragmatic guidance and mentoring to the broader engineering team. Technical Qualifications: Extensive Containerization & IaC: Proven architectural experience designing and managing production workloads using Kubernetes and Terraform. Demonstrated ability to decouple infrastructure from specific cloud vendors. Advanced Deployment Strategies: Deep architectural knowledge of zero-downtime deployment patterns and feature flag management systems tailored for enterprise platform rollouts. CI/CD Mastery: Deep structural understanding of Azure DevOps pipelines .
Here's how to pick the right one and stand out in your application.
144.883Jobs
31.687IN
81%EN
That number is real. WorkMundi's database shows 144,883 open engineer roles across the world. India has the most with 31,687 jobs, followed by the United States with 30,084. If you just finished reading one job ad and felt paralyzed by choice, you're not alone—but this scale is actually an advantage. It means you can afford to be selective.
Start by geography and language. The majority of engineer ads—117,837 of them—have the job posting text written in English. Use that as one filter, but remember: the ad text language tells you nothing about whether the role actually requires you to speak English day-to-day. Read the job description carefully. Then check which countries have the volume you're targeting. Singapore, Poland, and Australia round out the top five after India and the US.
Next, learn who's hiring. Accenture has posted 2,801 engineer roles. andurilindustries, speechify, and jobgether are also actively recruiting. If you're applying to one of these names, research their hiring patterns and interview style before you apply. That homework pays off.
When you interview, expect the question every engineer hears: 'Tell me about a time you had to debug a problem that wasn't in your job description.' Have a specific story ready—not a general one. Name the tools, the deadline pressure, and what you learned. Hiring managers listen for whether you see problem-solving as part of the role itself, not a favour.