Job Description & Details
This is a solid mid-to-senior level QA role where you'll be embedded in Washington, DC, balancing hands-on test execution with supporting Java and .NET environments. It's not just a click-buttons kind of job; you'll be actively writing scripts from scratch, digging into backend databases, and making sure complex enterprise systems don't break in production.
What You'll Actually Be Doing
Expect to spend your days knee-deep in crafting test plans, spinning up manual and automated scripts, and validating data integrity across web applications. You'll be executing everything from standard regression tests to heavy load testing. When things inevitably break—because they always do—you'll be the one writing up the defect reports, tracking issues in Jira, and jumping into design reviews to call out requirement gaps before they hit code.
The Core Tech Stack
You need to bring a solid foundation in manual testing with a clear track record of migrating into automation using tools like Test Complete, Ready API, SOAP UI, and Jira. SQL proficiency is non-negotiable here; you'll be querying databases directly to validate backend results. If you already know your way around Java, .NET, and MQ messaging, or tools like Insomnia and TOAD, you're going to hit the ground running.
Interview Expectations
Expect them to throw a complex database scenario at you, asking you to write a complex SQL join on the spot to track down a data discrepancy; they want to see if you can debug backend data issues without holding your hand. They'll also likely grill you on how you approach building automated test scripts from scratch, looking for your strategy on handling flaky tests and structuring execution suites.
Application Advice
Make sure your resume doesn't just list QA tools, but highlights actual scenarios where you built scripts from scratch and handled complex backend SQL queries. Toss in keywords like SDLC, regression testing, Jira, and API testing tools like SOAP UI or Ready API so you easily clear the ATS parser, but frame your bullet points around how you successfully caught critical defects before production.