0% found this document useful (0 votes)
117 views3 pages

QA Lead: Ensuring Software Quality

Uploaded by

alexisfinebox
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
117 views3 pages

QA Lead: Ensuring Software Quality

Uploaded by

alexisfinebox
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 3

Quality Assurance Lead

The Quality Assurance Lead is a member of the R&D department's team and
reports to the department’s Head of Development.

Role Objective: Ensuring the quality of software products by standardizing


testing processes in development teams. Implementing new testing tools and
methodologies. Optimizing testing processes.

Responsibilities and Tasks:

1. Testing Process in the Development Team:

 Developing a testing strategy for software products;

 Regularly monitoring the effectiveness of testing processes, optimizing


and improving them;

 Implementing advanced tools, innovative approaches, and accepted


standards in enterprise product testing;

 Creating metrics that ensure the required level of testing quality;

 Developing and maintaining the relevance of testing guidelines and


standards adopted in the company;

 Ensuring the release process.

2. Product Quality:

 Controlling the quality of functionality;

 Controlling the quality of test scenarios and test code;

 Establishing standards for writing test scenarios, keeping them up-to-


date.

3. Development of professional competencies of teams, developing


and maintaining of test team engagement:

 Participating in QA recruitment;

 Onboarding and training new QA staff;

 Mentoring QA in the scrum teams;

 Conducting training events – training sessions, clubs, masterclasses.

Professional Competencies:

 Knowledge and skills in test automation: Testing architecture:


developing a product testing strategy at different levels (API, E2E,
performance, mobile, visual). Knowledge of testing framework
architecture. Infrastructure: Understanding and knowledge of the
department’s CI/CD pipeline projects. Test design: Using BDD principles.
Applying other test design techniques;

 Knowledge of programming languages/technologies: Programming:


JavaScript/TypeScript; OOP; Design Patterns. WEB technologies:
HTML/CSS; Selectors; HTTP/HTTPS; REST; DB; Docker. IIS web server;

 Knowledge of testing tools: Chrome DevTools, Postman. MS SQL


Server Management Studio: Restore DB, Backup. TeamCity/Jenkins:
Running main jobs (Build, Automated Tests), Configuration steps, MS build
targets, passing parameters between jobs, creating chains, creating
TeamCity configurations. SQL Server Profiler. PowerShell. Writing scripts
for use in TeamCity in test plans. Fiddler. Libraries/Frameworks/Packages.
Selenium - Grid, WebDriver, Allure. Test Runners; Test Reporters: Mocha,
Cucumber, Protractor. Package Management: NPM. Version Control
Systems: SVN, Git;

 Load testing: Configuring JMeter. Running and debugging scripts. Non-


GUI mode. Conducting regression and performance stress testing. Using
Pre-Processors: User parameters, Sample Timeout, RegEx User
Parameters, Constant Timer. Configuring JMeter. Environment variables,
dump size, memory usage management, plugin connection.
Administering Performance UI testing tools;

 Managerial competencies: Planning: Setting quality standards and


metrics, control points, and measurable criteria to ensure quality at all
development stages. Monitoring: Evaluating the state of testing, code
coverage by tests, compliance with acceptance criteria. Visualizing the
readiness of developed components. Control: Code review of tests.
Corrective and preventive measures to reduce technical debt. Daily
monitoring of test execution. Determining the allowable limit of failing
tests, reducing their number. Release management: Planning, controlling,
and optimizing the department’s product release processes. Risk
management: Ability to timely identify risks, including technical ones, and
organize effective work with product quality. Hiring staff: Conducting
technical interviews for the QA Engineer position;

 Leadership competencies:

Mentoring and Training: Develop systematic processes for nurturing


QA engineers and helping them reach their full potential. Identify training
needs, including both hard skills and soft skills. Provide guidance,
coordination, and motivation to team members.
System and Process Building: Propose and implement sustainable and
scaling processes to support quality management.

Execution: Identify and select the top priority projects, focus on


generating results quickly and with minimal resources, ensuring high
quality and timely delivery.

Communication: Engage in effective communication with QA, scrum


teams, and management, ensuring clarity and understanding.

Flexibility and Collaboration: Show flexibility in interactions and foster


collaboration within the team to achieve common goals.

Conflict Resolution: Resolve conflicts appropriately, minimizing their


impact on team performance.

Delegation: Efficiently and accurately delegate tasks and


responsibilities, assigning them to engineers based on their skills and
interests.

Feedback: Provide constructive feedback to QA, development team and


top management.

Motivation: Inspire QA engineers towards continuous improvement and


development, including exploring new methods for automating testing
and daily processes.

Proactive Collaboration and Problem-Solving: Adopt a proactive


approach to collaboration and resolving issues, anticipating challenges,
and addressing them effectively. Escalate to the top management the
issues and project that require attention.

Knowledge Assessment: Evaluate the technical skills of QA engineers


effectively, ensuring they meet the required standards.

Basic Requirements Necessary for This Role: (for external candidates)

 Experience as a technical team leader for more than 3 years;

 Understanding of enterprise product testing standards;

 Experience working in a team of 5 or more people.

You might also like