> Markdown version of [/jobs/ext/1741244-sr-test-engineer](https://www.wearedevelopers.com/jobs/ext/1741244-sr-test-engineer). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md).

---

# Sr. Test Engineer

- **Company:** UNITECH CONSULTING, L.L.C.
- **Location:** United States (Remote available)
- **Experience:** Expert
- **Contract:** Permanent contract
- **Skills:** Testing (Software), Java (Programming Language), Agile Methodology, Automation of Tests, Software Bug Management, Software Documentation, CompTIA Security+, Java Platform Enterprise Edition (J2EE), Operational Databases, Regression Testing, Smoke Testing, SQL Databases, Test Scripts, Servicenow
- **Published:** July 3, 2026
- **Apply:** https://diversityjobs.com/main/sendform/8/8/28176/1/17480180?backUrl=%2Fcareer%2F17480180%2FSr-Test-Engineer

## About the Role

Senior Software Test Engineer with federal application sustainment, IV&V support, smoke testing, regression testing, release validation, and test documentation experience.

Strong preference: Testing experience for Entellitrak/Tyler, Java/JEE case management, Health IT, DoD, DHA, workflow systems, reporting systems, SQL-backed applications, and identity/authentication changes. Experience testing DR, data refresh, sanitized production data, Pre-Prod, Production, and release/change package deployment is highly valuable.

Functional experience required in resume: Smoke Test Script & Report development; test and validation scripts for critical modules; release change package testing; patch/configuration change testing; Pre-Prod validation; Production downtime-window smoke testing; defect triage; severity 1/2 defect tracking; regression testing; user acceptance support; traceability to user stories; automated test tools if available; ServiceNow ticket validation. The PWS requires a Smoke Test Script & Report after each release change package, patch, or configuration change, with standardized Test & Validation scripts covering critical modules and functionality.

Minimum Experience: Ten or more years of software testing, IV&V, QA, or test engineering experience on production applications.

 * The candidate must have experience creating test scripts, executing smoke/regression/functional tests, documenting test results, supporting release validation, and coordinating with developers during defect correction.

Certifications to prioritize: ISTQB, CSTE, CSQA, SAFe/Agile, Security+, SQL, or test automation certification.

## Description

* Message type: Informational; you will receive text messages regarding your application and potentially regarding interview scheduling.
 * No mobile information will be shared with third parties/affiliates for marketing/promotional purposes.
 * Message frequency will vary depending on the application process.Msg & data rates may apply.
 * OPT out at any time by texting "Stop".


## Related Videos

- [Implementing smoke testing and proactive monitoring in production](https://www.wearedevelopers.com/videos/171-implementing-smoke-testing-and-proactive-monitoring-in-production)
- [Proactive monitoring and smoke testing in your production environment](https://www.wearedevelopers.com/videos/139-proactive-monitoring-and-smoke-testing-in-your-production-environment)
- [SMART Test Automation - the experience of legacy transformation](https://www.wearedevelopers.com/videos/100215-smart-test-automation-the-experience-of-legacy-transformation)
- [Applying Agile Principles to Incident Management ](https://www.wearedevelopers.com/videos/101-applying-agile-principles-to-incident-management)
- [Are Classical Automation Frameworks Dead? How AI Agents Are Transforming QA](https://www.wearedevelopers.com/videos/100243-are-classical-automation-frameworks-dead-how-ai-agents-are-transforming-qa)
- [How to add test automation to your project: The good, the bad, and the ugly](https://www.wearedevelopers.com/videos/1668-how-to-add-test-automation-to-your-project-the-good-the-bad-and-the-ugly)

## Related Articles

- [The 8 Best Code Testing Tools](https://www.wearedevelopers.com/magazine/402-the-8-best-code-testing-tools)
- [Integration And E2E Testing: Are They Complementary or Interchangeable?](https://www.wearedevelopers.com/magazine/86-integration-and-e2e-testing-are-they-complementary-or-interchangeable)
- [What is a Test Plan: Guide to Test Planning](https://www.wearedevelopers.com/magazine/191-what-is-a-test-plan-guide-to-test-planning)
- [How We Built a Worry-Free System That Runs for 10+ Years – And What We’d Do Again](https://www.wearedevelopers.com/magazine/751-how-we-built-a-worry-free-system-that-runs-for-10-years-and-what-we-d-do-again)
- [How to create a test plan for software testing](https://www.wearedevelopers.com/magazine/56-how-to-create-a-test-plan-for-software-testing)
- [Should senior developers refuse interview coding challenges?](https://www.wearedevelopers.com/magazine/29-should-senior-developers-refuse-interview-coding-challenges)