QA Automation Engineer with 3+ years in Playwright, Selenium & API Testing
AI is analyzing your overall score…
Identifying your key strengths…
Evaluating your skill match against the job requirements…
Assessing your cultural and operational fit
Highly accomplished QA Automation Engineer with over 3.5 years of experience in designing, implementing, and maintaining robust automation solutions(Jest). Proven expertise in Playwright/Selenium/Appium WebDriver (Java, Python, JavaScript) and UI and API testing, leading to a 20% increase in test coverage and a 10% reduction in production bug reports. Skilled in architecting frameworks using Page Object Model (POM) and integrating quality gates into CI/CD pipelines to streamline the software development lifecycle.
Govt SKSJTI college Bangalore
Bachelor of engineering
N/A – June 30, 2020
Abhyas congnitive labs limited
QA automation engineer
August 1, 2024 – December 1, 2025
India
Technoforte software limited
Software engineer
May 1, 2022 – July 1, 2024
India
Quality Metrics
Unknown
June 1, 2026 – Present
Design-to-Test Efficiency
Unknown
June 1, 2026 – Present
Performance
Unknown
June 1, 2026 – Present
Design Systems
Unknown
June 1, 2026 – Present
Error reduction
Unknown
June 1, 2026 – Present
Cultural Fit Analysis
The candidate's experience spans different companies and technologies, indicating adaptability. The focus on improving test coverage, reducing defects, and optimizing performance aligns with a culture that values quality and efficiency. The breadth of skills across UI, API, database, and performance testing, along with CI/CD exposure, suggests a well-rounded individual who can contribute to diverse aspects of a QA team. The certifications listed (though future-dated) also show an interest in continuous learning and improvement.
Soft Skills & Operational Fit
The candidate's resume highlights collaboration with developers to troubleshoot defects and optimize processes, indicating good teamwork and problem-solving skills. The focus on reducing production bugs and improving efficiency suggests a results-oriented approach. The ability to manage both frontend and backend code changes within a microservices architecture demonstrates adaptability and a holistic understanding of software development.