SUMMARY:

• Well organized, oriented on details, customer focused and highly motivated quality assurance analyst with Agile environment experience, specializing in requirements eliciting, analysis and maintenance, testing artifacts creation (Test Strategy, Checklists, Test Cases, Test Matrices, Traceability matrices) and maintenance, functional testing of Web - based Application using the best practices and different approaches, defects reporting.
• Experienced at effort estimations, results analysis (QA metrics, root cause analysis) and work in tight deadlines.
• Extremely good team player with experience of work in the globally-distributed teams and strong communication skills.

AREAS OF EXPERTISE:

• Functional Testing
• Non-Functional testing
• Requirements Eliciting and Analysis
• Requirements management and communication
• Test plan/test strategy creation
• Writing Test Reports
• Root cause analysis
• Agile/Scrum Methodology
• Effort Estimation
• Analytical thinking
• Attention to detail
• Ability to Work in Fast Paced Environment with Cross-Functional Teams
• Communication including adapting communication to the needs and level of user
• Flexibility
• Quick learner
• Persistence
• Proactive
• Willingness to learn new technologies

TECHNICAL SKILLS:

Tools: / Testing tools: Jira, Version One, Projector, Visual Studio/TFS, Fiddler, Soap UI, Selenium (IDE, WebDriver), MS Office (Excel, Word, Visio Power Point), Adobe Acrobat XI Pro, Google Docs, EPAM Cloud, Virtualbox, Saucelabs

Languages: Java (Basic Level), SQL (Basic Level of SQL and relational database concepts)

Technologies: XML, Java SE 8

Platforms: Insurance, Financial Services

Domains: Windows, iOS

PROFESSIONAL EXPERIENCE:

Confidential

Software Testing Engineer

Responsibilities:

• Improved quality of existing requirements by performing detailed analysis, filling gaps, reducing ambiguity and conducting requirements management (establish requirements change control process, perform impact analysis on requirements changes, maintain a history of requirements changes, track the status of each requirement, maintain a requirements traceability matrix)
• Reduced development and testing effort by documenting requirements of different types in a consistent, accessible, and reviewable way that is readily understandable by team members
• Improved description, regulation and planning of testing process by creation detailed Test Plans and introducing QA metrics as a quality indicator
• Extended test coverage by developing accurate and economical Test cases, including scenarios found during Risk analysis
• Decreased costs and time of testing by providing accurate, reasonable and justified effort estimates
• Increased number of found issues/defects and enhanced defect containment indicator performing different test types, approaches and techniques on various levels of testing (Functional Testing, Regression testing, Compatibility testing, System testing, E2E testing, Performance testing, Positive/Negative testing, Exploratory testing, Risk Based testing, All Pairs testing, Equivalence partitioning and Boundary value analysis)
• Facilitated problem solving, defect resolution processes and reduced number of reworks by building and sustaining a strong communication with cross-functional resources
• Minimized numbers of defects caused by changes, enhancement, defect fixes by introducing Regression testing as a required testing activity in each Sprint
• Prevented defects in the later phases by execution of Root Cause analysis
• Improved stakeholders’ satisfaction by providing accurate, clear and timely reports (Test results report, Test Summary Report, Status Report, UAT approval and Release notes)
• Decreased cost and time of testing for a particular part of application which previously assigned to another team for testing in order of priority by learning necessary technology and tool and performing required testing personally
• Reduced time for Regression and Smoke test by developing automation scrips using Selenium
• Adjusted Sprint processes by active participating in daily stands-up meeting, Planning, Grooming, DoD (Definition of Done), retrospective sessions and providing valuable point of view and feedback from QA side
• Contributed to reducing time for adaptation and project understanding of rookies by developing detailed and clear Newcomers Handbook

Confidential

Junior Software Testing Engineer

Responsibilities:

• Improved quality of existing requirements performing test of requirements, filling gaps and creation a list of inconsistences to the Business Analyst
• Extended test coverage by developing accurate and economical Test cases, including scenarios found during Risk analysis
• Decreased costs and time of testing by providing accurate, reasonable and justified effort estimates
• Increased number of found issues/defects performing different test types, approaches and techniques on various levels of testing (Functional Testing, Regression testing, Compatibility testing, System testing, E2E testing, Performance testing, Positive/Negative testing, Exploratory testing, Risk Based testing, All Pairs testing, Equivalence partitioning and Boundary value analysis)
• Improved stakeholders’ satisfaction by providing accurate, clear and timely reports (Test results report, Test Summary Report, Status Report)
• Adjusted Sprint processes by active participating in daily stands-up meeting, Planning, Grooming, DoD (Definition of Done), retrospective sessions and providing valuable point of view and feedback from QA side

Confidential

Business analyst/Specialist

Responsibilities:

• Handled business documents and flows from analyst side: Documents eliciting, requirements analysis and transformation to the appropriate format
• Provided simple UML diagrams to capturing and presenting ideas to stakeholders
• Timely requested changes based on the business environment changes
• Executed testing across multiple testing phases, including SIT (system integration testing), UAT (user acceptance testing), and Regression
• Communicated with software vendor regarding defects and enhancements.
• Trained accounting staff to work with a new software
• Supervised the accounting section as a separate team