QA engineer, QA analyst,SDET

DEVENDER NALLABEEMI

QA Automation Engineer

+1-470-***-**** **********@*****.*** Denton, Texas, USA LinkedIn: linkedin.com/in/devendernallabeemi

PROFESSIONAL SUMMARY

QA Automation Engineer with 5+ years of experience in manual and automated testing of enterprise, banking, fintech, and SaaS applications. Experienced in designing and maintaining automated test suites, functional and regression testing, API, UI, backend, integration, and exploratory testing. Strong background in test planning, test case design, test data, execution, defect management, and QA reporting. Experienced working with developers and Business Analysts to understand requirements, define test coverage, and validate end-to-end business workflows. Hands-on experience with Tricentis Tosca, Selenium, Playwright, API testing, SQL, JIRA, and CI/CD tools, with strong knowledge of SDLC, STLC, BDD, and Agile/Scrum .

CORE COMPETENCIES

Automation Frameworks:Tricentis Tosca, Selenium WebDriver, Playwright, Python, Cucumber BDD, Page Object Model (POM) Languages: TypeScript, JavaScript, Python, Java, SQL

Testing Types: Functional, Regression, API, Integration, End-to-End, Mobile, Smoke, Sanity, UAT Support, Exploratory, Boundary Value Analysis (BVA)

API Testing: REST APIs, Postman, REST Assured, Response & Schema Validation, Negative Testing, Authentication Testing

QA Process: Test Planning, Test Strategy, Test Scenario/Case Design, Test Execution, Test Reporting, Defect Lifecycle Management, Root Cause Analysis

Database: SQL, Backend/Data Validation, Transaction Verification

Tools & CI/CD: JIRA, Git, Jenkins, GitHub Actions, Azure DevOps

CERTIFICATIONS

•AZ-104: Microsoft Certified Azure Administrator Associate

•DHS Trusted Tester Certification — Accessibility Testing (Section 508 / WCAG Compliance)

PROFESSIONAL EXPERIENCE

QA Automation Engineer Intuit — TX (Remote)Mar 2025 – Present

•Used Tricentis Tosca to design, maintain, and execute automated test cases for critical application workflows. .

•Created reusable Tosca modules and test cases to improve automation coverage and reduce repetitive manual testing. .

•Worked with developers and Business Analysts to understand requirements and convert manual scenarios into automated Tosca test cases. .

•Designed functional and regression test suites and maintained them as application features changed.

•Used Tosca for end-to-end validation across UI, API, and backend workflows.

•Performed manual and exploratory testing to identify issues outside the automated coverage.

•Created and tracked defects in JIRA, including reproduction steps, expected/actual results, severity, and supporting evidence .

•Integrated automated testing into Jenkins/GitHub Actions/Azure DevOps CI/CD workflows. .

Environment: Tricentis Tosca, Selenium, Playwright, Python, REST Assured, Postman, SQL, JIRA, Jenkins, GitHub Actions, Azure DevOps, Git, Agile/Scrum

QA Automation Engineer SMBC Bank — Charlotte, NCJan 2024 – Feb 2025

•Tested banking applications handling real customer transactions and account activity — the kind of environment where a missed edge case actually matters.

•Wrote automated scripts in Selenium, Python, and Cucumber BDD, and reused step definitions across features instead of rebuilding the same steps every time.

•Kept the regression suite current as the app changed, so core transaction flows stayed covered release after release instead of drifting out of date.

•Handled functional, integration, regression, smoke, and end-to-end testing ahead of each release.

•Checked REST APIs in Postman and REST Assured — response codes, payloads, schema, business rules — before anything hit production.

•Ran SQL queries against transaction and payment data to make sure backend processing lined up with what the app displayed.

•Worked with developers and BAs early on requirements so we caught ambiguous or risky areas before they turned into rework mid-sprint.

•Joined defect triage and dug into root cause on production issues instead of just reporting symptoms.

•Tracked test execution and defects in JIRA so the team always had a clear read on where we stood before a release.

•Helped stakeholders through UAT — walking through business scenarios with them rather than just handing over a test script.

•Took repetitive manual test cases and turned them into automated ones, freeing up time for actual exploratory testing.

•Covered smoke testing and production verification for payment workflows and account management after each deploy.

Environment: Selenium WebDriver, Python, Cucumber BDD, REST Assured, Postman, SQL, JIRA, Git, REST APIs, Agile/Scrum, SDLC, STLC

QA Engineer Tata Nexarc — Hyderabad, IndiaAug 2020 – Dec 2022

•Split time between manual and automated testing on web-based enterprise applications.

•Wrote test plans, scenarios, and cases from functional requirements, and kept execution reports stakeholders could actually follow.

•Automated the repetitive parts of regression testing using Selenium and Python, which freed me up to spend more time on the trickier scenarios.

•Ran smoke, sanity, functional, regression, and integration testing across several app modules.

•Tested API responses in Postman to make sure services were talking to each other correctly.

•Used SQL to check data accuracy on the backend rather than trusting the UI alone.

•Logged and tracked defects in JIRA and kept them traceable back to the original requirement.

•Worked directly with developers to reproduce bugs and confirm fixes actually held.

•Took part in sprint planning, standups, and reviews as part of the regular Agile rhythm.

•Did exploratory testing on the side to catch the edge cases scripted tests tend to miss.

Environment: Selenium WebDriver, Python, Postman, REST APIs, SQL, JIRA, Git, Agile/Scrum

KEY ACHIEVEMENTS

•Cut a large share of manual regression time by moving core test suites over to Selenium and Playwright.

•Built API test suites (REST Assured, Postman) that other teams ended up reusing instead of writing their own from scratch.

•Got automated suites running inside CI/CD (Jenkins, GitHub Actions, Azure DevOps) so regression checks happen on every build, not just before release day.

•Known on the team for digging into root cause rather than stopping at 'it's broken' — helped shorten how long production issues stayed open.

EDUCATION

Master's in Advanced Data Analytics

University of North Texas, Denton, TX CGPA: 3.88

Contact this candidate