Software QA Engineer

Responsibilities:

1. Test Planning & Design

• Requirement Analysis: Reviewing project specifications, user stories, and design documents (like the UI/UX changes or system migrations) to ensure they are clear and testable.
• Creating Test Plans: Defining the testing strategy, scope, resources, and timelines for the project.
• Writing Test Cases: Developing detailed, step-by-step test cases and scripts based on how a user would interact with the software.

1. Test Execution

• Manual Testing: Executing test cases manually to check the look, feel, and usability of the application.
• Automation Testing: Writing and maintaining automated test scripts for repetitive tasks (like regression testing) to speed up the release cycle.
• Types of Testing: Conducting various testing types, including:
• Functional Testing: Making sure buttons, links, and workflows operate correctly.
• Regression Testing: Ensuring new updates or bug fixes haven't broken existing features.
• Performance & Load Testing: Checking if the system can handle a high volume of concurrent users without crashing (crucial for auto-scaling infrastructures).

1. Bug Tracking & Reporting

• Defect Logging: Documenting identified bugs, errors, or glitches in tracking tools (like Jira) with clear steps to reproduce them.
• Collaboration: Working closely with software developers to explain bugs, investigate root causes, and re-test the fixes once they are deployed.
• Risk Assessment: Informing project managers and stakeholders of potential quality risks before a product goes live.

1. Continuous Improvement & Alignment

• Process Optimization: Identifying gaps in the development cycle and suggesting ways to improve software quality from the start.
• Feedback Loops: Participating in team meetings (like sprint planning or project kickoffs) to advocate for quality standards and align on project success metrics.

1. Production Issue Assessment & Triage

• Live Bug Investigation: Investigates and reproduces issues reported by users in the live system to isolate the root cause.
• Triage: Assigns ticket to L3 support to ensure resolution of issues.

1. Test Planning & Writing

• Ability to read project guidelines and understand exactly how the software is supposed to work.
• Skill in writing clear, step-by-step instructions on what to test and what the correct results should be.
• Experience in writing QA test plans, QA test scripts, and UAT test scripts.

1. Executing Tests

• Familiarity with basic testing tools and a general understanding of how data moves through the system.

1. Bug Reporting & Tracking

• Ability to write clear reports when a bug is found, including the exact steps needed for a developer to recreate and fix it.
• Experience using team platforms to organize, update, and track the status of bugs from discovery to resolution.

1. Problem Solving & Live Support

• Ability to look into errors reported by real users in the live system, figure out why they are happening, and recreate them in a test environment.
• Fix Verification: Skill in quickly testing emergency fixes (hotfixes) to make sure they solve the problem without breaking other parts of the system.

1. Eye for Detail & Teamwork

• User-First Mindset: A sharp eye for catching messy layouts or confusing workflows to ensure a smooth experience for the end user.
• Good Communication: Ability to speak clearly with developers and managers so everyone is aligned on what needs to be fixed.

1. Proactiveness & Initiative

• Self-Driven Execution: A strong sense of initiative to identify gaps, start additional tasks, and improve testing processes without waiting for a direct command or assignment from a manager.

• Education: College Graduate
• Skills: Test planning and execution, bug tracking, production root-cause analysis, and a proactive, self-driven mindset to optimize software quality.