What you’ll do:

• Keep CI/CD pipelines running across multiple repositories and teams.
• Improve and standardize pipelines: reusable templates, consistent steps, fewer surprises.
• Maintain and improve developer tools such as Azure DevOps, GitHub Enterprise, and SonarQube (or comparable tools).
• Add practical checks to pipelines: tests, code quality gates, and basic security scanning.
• Help developers when pipelines fail: find the cause, fix it, and prevent repeats.
• Support moving and aligning repositories, pipelines, and tooling across teams.
• Write clear documentation so teams can help themselves.
• Grow step by step into more advanced topics like IaC, platform tooling, and cloud automation.

What you should already know (basics are enough))

• First hands-on experience with CI/CD (Azure DevOps Pipelines, GitHub Actions, GitLab CI, Jenkins—any is fine).
• You can automate small tasks with scripts (Bash, PowerShell, or Python).
• You understand Git workflows (branches, pull requests, reviews).
• You’ve touched build/test automation in at least one ecosystem (e.g., .NET, C++, Delphi, Java, Node.js).
• You’ve seen code quality tooling (SonarQube or similar).
• You have a basic grasp of cloud/infrastructure concepts (what environments are, what deployment means, why permissions matter).

Nice to have (not required)

• Experience with Azure DevOps organizations/pipelines/boards.
• Any exposure to GitHub Enterprise administration or repo management.
• Docker basics.
• Interest in AWS or cloud platforms.