🎁 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 →
N-iX is looking for Lead DevOps Engineer (AWS Migration & Security) - to join the team About the client Our client is a leading European online car marketplace, serving over 30 million monthly users across 18 countries. As a Lead DevOps Engineer – AWS Migration & Security, you will play a pivotal role in modernizing the platform that powers their business — migrating core services to AWS and strengthening the security posture that protects their customers and data at scale. About the role We are looking for two experienced engineers to drive a cloud migration and security-hardening initiative through the end of the year. This is a hybrid role, split roughly 50/50 between SRE/operations work and hands-on software development. You will work cross-functionally with multiple teams, migrating services to AWS while identifying and remediating security issues along the way. This role suits someone who is equally comfortable writing Terraform as they are debugging application code, and who enjoys the pace and ownership that comes with a focused, time-boxed engagement. This is a hands-on project-based role combining platform engineering, cloud migration, DevOps, and security remediation. You will work across multiple engineering teams, helping migrate services to AWS, implement infrastructure on EKS, improve deployment processes, and address security issues. The role may have a stronger focus on infrastructure and platform engineering or on development and DevOps, depending on the candidate’s background and the needs of the assigned domain. This position does not include on-call, incident response, or traditional SRE responsibilities. Responsibilities: Migrate existing services from Azure and potentially other platforms to AWS. Design, implement, and maintain cloud infrastructure using Terraform. Work with AWS EKS, Kubernetes, Docker, and containerized workloads. Configure and maintain AWS networking, including VPCs, subnets, security groups, IAM, and load balancing. Support migration activities across AWS accounts, environments, and engineering teams. Identify and remediate security issues related to secrets, keys, dependencies, and infrastructure configuration. Apply security fixes, patches, and library updates, including Dependabot-driven remediation. Contribute to CI/CD pipelines and deployment automation using GitHub Actions. Work with existing observability tools, including Datadog and New Relic, while supporting the migration toward Grafana. Make application-level configuration or code changes where required to support migration and security activities. Collaborate with development, platform, and infrastructure teams to coordinate migration activities with minimal disruption. Document infrastructure changes, migration procedures, and security remediation work. Use AI-assisted development tools, including Codex, to improve engineering productivity and delivery speed. Requirements: 6+ years of commercial DevOps experience Strong hands-on experience with AWS in production environments. Proven experience with Kubernetes and AWS EKS. Practical experience with Docker and containerized workloads. Strong Terraform and infrastructure-as-code skills. Experience with cloud migration projects, ideally involving migration from Azure to AWS and/or re-platforming. Solid understanding of AWS networking, IAM, security groups, load balancing, and related services. Practical experience with security remediation, including secrets and keys management, vulnerability remediation, dependency patching, and infrastructure hardening. Experience with GitHub Actions or comparable CI/CD tools. Ability to work across multiple teams, services, and codebases. Familiarity with PHP, Python, or TypeScript is beneficial for communication with development teams and understanding application-level changes. Fluency with Codex or comparable AI-assisted coding tools. Excellent English communication skills Ability to work during Toronto timezone business hours, with reliable EST/EDT overlap. Nice to have: Experience with Datadog, New Relic, or Grafana. Experience with Dependabot or automated dependency management. Experience with RDS and other AWS data services. Experience working with multi-account AWS environments. Prior contract or consulting experience with clearly defined deliverables. We offer*: Flexible working format - remote, office-based or flexible A competitive salary and good compensation package Personalized career growth Professional development tools (mentorship program, tech talks and trainings, centers of excellence, and more) Active tech communities with regular knowledge sharing Education reimbursement Memorable anniversary presents Corporate events and team buildings Other location-specific benefits not applicable for freelancers
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.