Description of assignment 53107   Uppsala  

Back to the assignment list
The customer is a global provider of software and services for embedded development. The company delivers world-leading tools for programm[i]ng, debugging, and optimizing embedded applications, enabling customers across industries such as automotive, industrial automation, medical devices, and IoT to build reliable and high-performance software. With a strong focus on quality, performance, and long-term maintainability, they support development teams working with complex, safety-critical, and resource-constrained systems. The assignment The company is transitioning from a traditional Release Manager function towards a more modern Release Engineering model, emphasizing automation, scalability, and reduced manual coordination. Currently, releases are managed as projects with signif[i]cant coordination, handovers, and manual steps. While CI/CD cap[a]bilities exist (Jenkins, GitLab), they are fragmented and underutilized. We are seeking a consultant who can both stabilize current release operations and initiate a practical transformation toward automated release processes. This is a 6-month interim assignment with a dual objective: Operational ownership • Take over the Release Manager responsibilities from the current interim solution • Ensure stable, predictable, and high-quality releases • Manage release planning and milestone alignment with Product Management • Perform release tracking, risk management, and proactive escalation • Coordinate across development, build, and test • Ensure integration testing and release readiness • Manage release notes and final delivery Transformation foundation • Identify bottlenecks, handovers, and coordination overhead • Reduce unnecessary process complexity and shorten feedback loops • Move from project-based releases towards continuous delivery • Define how responsibilities shift across Product Management, Engineering teams, and Release Engineering • Improve and standardize Jenkins pipelines • Strengthen CI/CD usage across teams • Reduce manual steps in build, integration, validation, and release processes • Introduce clearer ownership and self-service cap[a]bilities • Document processes, pipelines, and responsibilities Expected outcomes include: • Stable and predictable release execution • Documented current and target release processes • A defined Release Engineering model and responsibilities • A prioritized and partially implemented automation roadmap • Tangible improvements in lead time, manual effort, and release quality • Structured handover to internal teams or a permanent hire Competences The following competence areas are required: • Proven experience as Release Manager, Release Engineer, or DevOps Lead • Demonstrated success in modernizing release processes and moving from manual coordination to automated pipelines • Experience working in complex, multi-team environments • Strong hands-on experience with Jenkins (pipeline development and optimization) • Experience with Git-based workflows (e.g., GitLab) • Solid understanding of CI/CD design and best practices • Strong understanding of build systems and dependency management • Experience working with C++ environments • Scripting experience (e.g., Ruby, Python or similar) • Strong communication and stakeholder management skills • English; spoken and written Additionally, it is beneficial if the candidate has experience in: • Transitioning from project-based releases to continuous delivery • Test automation and integration testing strategies • Coaching teams in DevOps and release practices • Swedish; spoken and written Assignment length Start: May 2026 Duration: Approximately 6 months, with potential for extension. Hybrid
Log in to apply for this assignment
Username
Password