Fiserv
Wavity, Inc Interview Questions and Answers
Q1. What would you do if there is a release scheduled tomorrow and QA identifies a bug and dev has fixed it in develop. This bug is critical for one of the application that is not widely used however this release i...
read moreRecommend prioritizing the critical bug fix and delaying the release for the application
Prioritize the critical bug fix for the application that is not widely used
Coordinate with QA and dev teams to ensure the bug fix is thoroughly tested
Communicate with stakeholders about the delay in release and the reasons behind it
Q2. What kind of Devops tools you have used for release management
I have experience using tools like Jenkins, Git, Docker, and Ansible for release management.
Jenkins
Git
Docker
Ansible
Q3. Describe list of deployment strategies and their methodologies.
Deployment strategies include blue-green deployment, canary deployment, rolling deployment, and feature toggles.
Blue-green deployment involves running two identical production environments and switching between them.
Canary deployment gradually rolls out changes to a small subset of users before deploying to the entire infrastructure.
Rolling deployment updates a subset of servers at a time, ensuring continuous availability.
Feature toggles allow features to be turned on or off ...read more
Q4. How do you decide branching strategy
Branching strategy is decided based on project complexity, team size, release frequency, and risk tolerance.
Consider project complexity - simple projects may only need a main branch, while complex projects may require feature branches.
Take team size into account - larger teams may benefit from feature branches to work on separate tasks concurrently.
Evaluate release frequency - frequent releases may warrant a branching strategy that supports parallel development.
Assess risk to...read more
Q5. How do you manage release process
I manage the release process by coordinating with development, testing, and operations teams to ensure smooth deployment.
Coordinate with development, testing, and operations teams to plan release schedule
Ensure all necessary documentation and release notes are prepared
Perform risk assessment and mitigation strategies
Use version control systems to track changes and releases
Communicate with stakeholders about release status and any issues
Monitor deployment process and address a...read more
Q6. What is Nexus and why is it used.
Nexus is a repository manager that allows you to proxy, collect, and manage dependencies of many different types.
Nexus is used to store and manage software artifacts such as JARs, WARs, and Docker images.
It helps in controlling access to repositories and ensures that only approved artifacts are used in builds.
Nexus can also act as a proxy to other repositories, reducing build times and improving reliability.
It provides a central location for teams to share and distribute depe...read more
Q7. How do you prepare release documentation
I prepare release documentation by creating detailed release notes, updating user guides, and communicating changes to stakeholders.
Create detailed release notes outlining new features, bug fixes, and any known issues
Update user guides to reflect changes in the new release
Communicate release changes to stakeholders through emails, meetings, or documentation
Ensure all documentation is clear, concise, and easily accessible
Q8. Explain your experience with release engineering
I have extensive experience in release engineering, including managing release cycles, coordinating with cross-functional teams, and ensuring smooth deployments.
Managed release cycles for multiple software products
Coordinated with development, QA, and operations teams to plan and execute releases
Implemented release automation tools to streamline the release process
Ensured compliance with release management best practices and standards
Resolved release-related issues and commun...read more
Reviews
Interviews
Salaries
Users/Month