Release Manager (Minsk/hybrid or remote)

As a Release Manager at IDT Corporation, your primary responsibilities will include planning and scheduling software releases in collaboration with product managers and development teams. You'll manage dependencies between Jiras, maintain lists of approved updates, ensure that tests are run upon release, and enhance the change management process. Your role will be pivotal in continuously improving and automating our release processes.

To qualify for the Release Manager position at IDT Corporation, you should have a minimum of 3 years of professional experience in DevOps roles and over 5 years in software development. Proficiency with AWS, Linux, Git, and experience within a CI/CD environment using tools like Jenkins and GitHub are essential. High-level English communication skills and a strong understanding of the software development life cycle are also necessary.

A Release Manager at IDT Corporation should be familiar with tools such as Jenkins, Git, and automated testing frameworks like Cypress. Knowledge of AWS Cloud services, shell scripting on Linux, and managing version control with Git are crucial. Additionally, having experience with configuration management and security considerations is a nice added bonus!

IDT Corporation values its employees, offering competitive salaries, medical insurance, and generous vacation time of 26 days. They also provide opportunities for remote work or a hybrid model in Minsk, reimbursement for sports activities, and corporate English lessons to support ongoing professional development.

The work environment for a Release Manager at IDT Corporation is collaborative and fast-paced, surrounded by talented professionals dedicated to innovating the retail industry. The company encourages teamwork, supports autonomous work, and fosters a culture of continuous improvement. With the option to work remotely or in a hybrid capacity, you’ll enjoy flexibility alongside dynamic projects.

In response to this question, you should emphasize your hands-on experience with automated testing tools, particularly with Cypress if applicable. Discuss specific projects where you integrated automated testing into the release process, highlighting your understanding of how it ensures quality and reduces deployment risks.

When answering, discuss your methodical approach to managing dependencies. Share an example of a past project where you navigated complex interdependencies, utilized tools like Jira to track them, and employed strategies to ensure smooth coordination among teams while maintaining release timelines.

You should discuss techniques you've employed to analyze and identify bottlenecks in the release process. Talk about specific automation tools you have integrated, how you facilitated cross-team collaboration, and the measurable improvements that resulted from your initiatives.

When answering this question, provide a detailed account of a specific release that posed challenges—whether it was technical issues, time constraints, or team coordination—along with the steps you took to turn the situation around. Highlight your problem-solving skills and ability to remain calm under pressure.

Discuss your procedures for maintaining approval processes. Elaborate on your experience with managing Jiras, keeping track of approvals, and any tools or checklists you use to verify that only the necessary software reaches deployment, ensuring compliance with project standards.

You should highlight the significance of communication, thorough documentation, and testing as key components of effective change management. Discuss your experience in establishing clear protocols and facilitating discussions among stakeholders to address any concerns before implementation.

Emphasize the importance of documentation in maintaining clear records of releases, decisions made, and lessons learned. Discuss your experience in creating or improving documentation practices that support both the release process and the onboarding of new team members.

Mention various strategies you use to stay informed, such as attending industry conferences, participating in relevant online communities, reading industry publications, or taking courses. Share any specific resources that have helped you enhance your skills and knowledge in release management.

Share your experience using Git in past roles. You can explain how you’ve leveraged its features to manage software versions, collaborate with team members, and handle branching strategies to support development workflows effectively.

Provide insights into a specific situation where you had to execute a rollback. Walk through the reasons for the revert, what protocols you followed, and the communications involved. Highlight key takeaways, such as enhancing testing procedures or improving documentation to prevent future issues.