Help & Supportcareers@gravityer.com
QA Automation Engineer with 4+ years in End-to-End BCM and GRC 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
QA Engineer with 4+ years of experience in Manual and Automation Testing. Extensive experience in end-to-end testing for BCM (Business Continuity Management) and GRC (Governance, Risk, and Compliance) platforms, ensuring high-quality delivery with zero-leakage of critical defects to production. Strong expertise in Selenium WebDriver, TestNG, REST Assured, and SQL validation.
Jawaharlal Nehru Technological University (JNTU)
B.Tech · Computer Science & Engineering
August 1, 2016 – June 30, 2020
Ascent Risk & Resilience Software Pvt Ltd
QA Engineer II
September 1, 2022 – Present
Gurgaon, Haryana, India
Conceptive Consulting Technology Pvt Ltd
QA Engineer I
August 1, 2021 – August 1, 2022
Hyderābād, Telangana, India
Enterprise Risk Management
June 28, 2026 – Present
Conducted automated and manual validation of financial risk calculation engines and database triggers.
BCM & GRC Platform Testing
June 28, 2026 – Present
Orchestrated full-lifecycle testing for Business Continuity and Risk modules, achieving high requirement traceability and ensuring zero-defect deployments for critical modules.
Cultural Fit Analysis
The candidate's experience across two companies, both in enterprise software, suggests adaptability to structured environments. The focus on risk and compliance platforms indicates a preference for domains requiring high precision and adherence to standards. The project diversity, though within a similar domain, shows breadth in applying QA principles. The role alignment with 'QA Automation Engineer' is strong given the explicit experience in designing automation frameworks and integrating them into CI/CD.
Soft Skills & Operational Fit
The candidate demonstrates strong operational fit through experience in Agile Scrum environments, optimizing JIRA workflows, and collaborating with developers. The descriptions indicate a proactive approach to improving efficiency (e.g., reducing execution time by 60%, improving defect resolution by 30%).