Senior Quality Engineer
at Underscore
Boston, MA, USA, senior, full time, USD 1,40,000–1,80,000 / year, 8+ years
posted 29 Oct 2026
- Java
- GitHub Actions
- Playwright
- JavaScript
- Databricks
- Zephyr Scale
- RESTful APIs
- AWS
- Jira
- Python
- SQL
About the role
TetraScience
Quality Assurance
Boston, MA, USA
USD 140k-180k / year
Posted on Oct 29, 2026
What you would do
As a Senior Quality Engineer, you are the quality authority for your use cases. Your responsibilities will include:
• Own quality for your use cases and sign off their releases. Hold QE sign-off authority, including the decision to withhold it, against the criteria Compliance sets.
• Verify that what we built is what the customer asked for. Trace delivered work back to the documented requirements and make sure the evidence actually demonstrates them — not that a test merely ran.
• Make sure the SDLC is followed. Requirements, design review, test evidence and traceability are in place and in the right order, in a validated environment.
• Build and own test automation. Design robust, workflow-based automated tests across UI, API and database layers in our Playwright framework, and build them to be maintained and extended rather than rewritten.
• Keep improving how we test. Continuously raise the test and automation approach — coverage, cycle time, and where quality is known in the development cycle — rather than running the same suite faster.
• Use AI to do all of this better. Build automation with AI assistance, use it to generate and strengthen test cases and to improve the quality process itself, and apply judgement about where AI-generated work can and cannot stand as release evidence.
• Contribute to verifying the AI in your use cases. Help establish that evaluation thresholds were set before results were known, that test data was genuinely held out, and that the claims made match what was measured.
• Shape decisions before code is written. Raise testability, failure modes and risk in the squad while they are still cheap to change, using escape and defect patterns as your evidence.
• Own the hard testing. Performance, security, tenant isolation and resiliency, including failure and degradation behaviour, balanced against functional, integration and regression work. Test manually and exploratorily where that is the right tool — automation is a means to coverage and cycle time, not an end in itself, and the failures nobody wrote a requirement for are usually found by hand.
Read from jobs.underscore.vc, last seen 3d ago.