Senior CI/CD Engineer

ABOUT SIOUX Sioux Group was founded in 1996 in the Netherlands. With over 1,400 engineers, Sioux supports or acts as the R&D partner of leading high-tech companies. We aim to add value to our clients by developing innovative and high-tech solutions that contribute to a smarter, safer, healthier, more enjoyable, and more sustainable society. Sioux has been recognized as an employer of choice, including awards such as Best ICT Company to Work For and Great Place to Work. In addition to our strong presence in Europe, Sioux is rapidly expanding in Asia, with offices in Vietnam, China, Singapore, and India. With a strong heritage and a diverse international team, Sioux is proud of our core values: Own it and make it happen, Grow and innovate together, and Surprise customers. If these values resonate with you, we would love to welcome you to our team. We are looking for a Senior CI/CD Engineer based in Asia to make our builds faster, our pipelines more reliable, and our automated testing part of every change. You will focus on build performance for our C#/.NET and C++ software and on bringing tests and static analysis into CI. You will work closely with development, verification, our test architect and IT-DevOps teams in Europe and Asia. Today, a full end-to-end pipeline runs around 200 jobs and over 10,000 automated tests and takes about 4 hours. Your main goal is to cut that time significantly (we aim for around 50% in your first year) while giving developers fast, reliable feedback on every merge request. This is a hands-on CI/CD role inside engineering, not an infrastructure DevOps role. You will spend most of your time optimising builds and pipelines, and a smaller share keeping them running. Key Initiatives - Reduce Pipeline Time: Map the critical path, remove waiting between jobs, cut per-job overhead (clone, artifact download, restore) and cancel redundant pipelines automatically. - Job Strategy: Decide what runs where and when: fast merge request checks, fuller runs on main and release branches, and complete nightly runs. Group short jobs, split long ones and parallelise long system test suites. - Tests in the Pipeline: With the test architect, place each test type in the right pipeline tier, select tests by change where safe, quarantine flaky tests and move coverage runs to scheduled pipelines. - Release Pipelines: Make release and cherry-pick pipelines fast and predictable so fixes reach customers quickly. Key Responsibilities - Build Performance: Profile and optimise MSBuild-based builds for C#/.NET Framework 4.7 and C++: incremental and parallel builds, NuGet and dependency caching, and removal of bottlenecks. - Pipeline Design: Design, standardise and maintain reusable GitLab CI pipeline templates (.gitlab-ci.yml, DAGs, multi-project pipelines) across C#, C++ and Python repositories. - Test & Verification Integration: With the test architect, development and QA/verification leads, embed unit tests, static analysis (Coverity, SonarQube) and automated test bench runs into CI, with clear results reporting. Agree jointly with the test architect which suites run in each pipeline tier. - Pipeline Reliability & Metrics: Investigate failures, remove flaky builds and tests, and track build time, failure rate and pipeline uptime on dashboards to show improvement. - Pipeline Operations: Act as first line on the engineering side when pipelines or runners go down: diagnose, restart or re-run jobs, unblock developers, and hand infrastructure issues to IT-DevOps with a clear diagnosis. - Capacity Input: Give IT-DevOps data-backed requirements for build runners and test environments, based on queue times and job durations. - Artifact & Release Automation: Automate versioning, release packaging, artifact staging and package registry management. - Developer Workflow: Advise teams on branching and merge strategies, merge request verification gates and fast feedback loops. Scope: GitLab runner management, AWS/cloud infrastructure and GitLab platform administration are owned by the IT-DevOps team. This role works with them on requirements and issues but does not own that infrastructure. It is their engineering-side point of contact: first line when pipelines are down, and input on sizing what we need.