Team Lead DevOps & IT

🚀 We have an exciting opportunity to join our team as a Team Lead DevOps & IT! Starting remotely, with the possibility of relocation to Lisbon, Portugal in the future. The AnyLogic Company is an international IT company specializing in simulation modeling software. Our clients include Tesla, Amazon, Airbus, Google, and McDonald’s. We are looking for a leader who will: - Develop and drive our infrastructure and DevOps strategy - Lead and manage the DevOps / Systems Engineering team - Ensure scalability, reliability, and security of our AWS infrastructure - Collaborate with product teams on architectural decisions - Manage infrastructure budgets and optimize costs What we're looking for: - 5+ years of experience in DevOps / System Operations - Proven team management experience - Strong expertise in AWS - Experience designing and building system architectures Tech stack: AWS, Kubernetes, Docker, GitLab CI, Terragrunt / OpenTofu, Prometheus, Loki, Sentry. 📩 If you're interested, or know someone who might be a great fit, please send your CV to контакт скрыт. Looking forward to hearing from you!
Daria Liubimova’s Post
More Relevant Posts
-

Span is hiring! We're looking for great DevOps engineers in Sofia, Buenos Aires, or remote in the USA. Span is how the world's best AI-powered engineering teams observe, understand and improve their SDLC. We're proud to support leading organizations like Ramp, Carvana and OpenTable. If you're interested in shaping the future of software engineering and working with a fast-moving team of brilliant engineers, drop me a note. https://lnkd.in/gNQvXQb5 To view or add a comment, sign in
-

🚀 DEVOPS ENGINEER — NOT JUST A JOB, IT’S A RESPONSIBILITY! People often think DevOps is just about running pipelines, managing servers, and deploying applications. But the reality? It’s much more than that. 😅 One day, you're building CI/CD pipelines. The next day, you're troubleshooting Kubernetes. Then comes an infrastructure issue, a failed deployment, a security alert, or a production incident at the worst possible time. 🫠 And somehow, you're coordinating with developers, supporting business teams, managing cloud infrastructure, improving automation, and keeping production stable. ☁️ AWS 🐳 Docker ☸️ Kubernetes 🔄 CI/CD 🏗️ Terraform 📊 Monitoring & Observability 🔐 Security & Compliance 🤖 Automation Tools are important, but tools alone don't make a great DevOps engineer. It's the ability to solve problems, automate repetitive work, understand the bigger picture, collaborate across teams, and take ownership of reliability that truly matters. 💡 The real goal of DevOps isn't just to deploy faster. It's to deliver software reliably, securely, and consistently. And remember: being responsible doesn't mean being available 24×7. Sustainable engineering requires good automation, proper on-call practices, documentation, and teamwork. Different tools. One goal. Build. Automate. Scale. Deliver. 💪 What's the one responsibility in DevOps that people underestimate the most? Let’s discuss in the comments! 👇 #DevOps #PlatformEngineering #AWS #Kubernetes #Docker #CICD #Terraform #CloudComputing #SRE #Automation #DevOpsEngineer #CloudNative To view or add a comment, sign in -

We recently filled a Platform Engineer role that a few software engineers initially read as DevOps. I could see why. AWS, Terraform, containers and CI/CD were all in the brief. If you’re a developer who doesn’t want to move into infrastructure, that list could easily put you off. But the team wasn’t looking for someone to spend their days managing cloud environments. They wanted a strong software engineer to build internal tools and improve how their developers tested and released software. There was still cloud and pipeline work involved. We weren’t trying to dress that up as something else. The distinction was that they needed someone who could build software for other engineers, not just configure the tools underneath it. That became an important part of the candidate conversations. We had to explain what they’d actually be building, rather than assume the title and tech stack would do the job. It also meant looking beyond people already called Platform Engineers. A software engineer who enjoys fixing build problems, improving testing or creating tools for their team could be a better fit than someone with the right title but a purely infrastructure background. We ended up making the placement, and I’m really happy with the outcome. My takeaway wasn’t that the brief needed to be less technical. It needed to be clearer. The tools were relevant, but they weren’t the reason a software engineer would want the job. If good candidates keep misunderstanding a role, it’s worth looking at how you’re explaining it before deciding they’re the wrong people. To view or add a comment, sign in -

DevOps Engineer and Site Reliability Engineer get treated as synonyms in a lot of US job postings, and the disciplines have a real philosophical difference underneath the shared toolset. A DevOps engineer typically focuses on the pipeline: CI/CD, infrastructure as code, deployment automation, bridging development and operations. An SRE, a discipline that originated at Google, applies software engineering practices specifically to reliability — error budgets, SLOs, incident response systems, and often writing code to eliminate the operational toil that would otherwise fall on a team. Both roles touch Kubernetes, Terraform, and monitoring stacks, which is exactly why they get conflated. But an SRE without a strong reliability engineering mindset can build automation that's technically sound and doesn't actually reduce on-call burden, because reducing on-call burden was never the framework they were trained in. Clients who genuinely need SRE-style reliability engineering and staff a general DevOps profile instead often end up with excellent pipelines and the same 3 a.m. pages they had before. Is your open role asking for deployment automation, reliability engineering, or a blend — and have you said which? #DevOps #SRE #SiteReliability #CloudEngineering #ITStaffing To view or add a comment, sign in -

🚀 Great teams make all the difference. And we're growing ours at DKB Code Factory! Since joining DKB Code Factory GmbH, I've had the opportunity to work alongside talented engineers, tackle meaningful technical challenges, and contribute to building and improving our cloud platform. What I value most is the combination of technical ownership, a collaborative environment, and the freedom to bring ideas to the table. Having worked in different engineering environments throughout my career, I can genuinely say this is a team I'm proud to be part of. And now, we're looking for a DevOps Engineer to join us in Valencia! 📍 Valencia, Spain – Hybrid (2 days/week in the office) 🔗 Apply here: https://lnkd.in/emy-R3EQ If you're passionate about cloud engineering and automation, I'd definitely encourage you to apply! Feel free to reach out if you'd like to hear about my experience here. #Hiring #DevOps #AWS #PlatformEngineering #Valencia #DKBCodeFactory To view or add a comment, sign in -

Senior DevOps Engineer - Contract Contract: 6 months, with strong potential for extension Location & Work Model: Galway, Hybrid Rate: €550-€600 per day Please click on the job title below to view the Job Description and apply to it! To view or add a comment, sign in -

🚀 DevOps Engineer: Myth vs Reality — Are We Really Just Managing Pipelines and Deployments? When someone asks, "What does a DevOps Engineer do?" The most common answers are: ⚙️ Build CI/CD pipelines ☁️ Manage cloud infrastructure 🐳 Work with Docker and Kubernetes 🚀 Deploy applications But is that all? 🤔 The reality is much broader. A DevOps Engineer's work doesn't end when the infrastructure is provisioned