Get a reply from this employer
Your resume and cover letter, tailored to exactly what they’re hiring for.
YASSI in Chicago seeks a Senior QA Engineer to own quality across the web application, admin tooling, and customer integrations. This senior IC will set testing strategy, push quality earlier in development, and guide release risk judgments.
You’ll hands-on test, perform risk-based coverage decisions, and improve how the team works. The role requires deep QA fundamentals, strong communication, and experience with automation tools; you’ll own and refine the regression suite and collaborate with
We're looking for a Senior QA Engineer to own quality for a significant area of our platform — the web application, admin tooling, and the integrations our customers depend on. This is a senior individual contributor role: you'll set the testing approach for your area rather than execute someone else's, and you'll be the person the squad turns to when the question is "what could this break?" The craft here is still hands-on testing — exploratory work, risk-based coverage decisions, and the kind of deep product knowledge that catches the defect nobody wrote a test case for. What makes it senior is scope and influence: you'll define test strategy, push quality earlier into the development cycle, and make the judgment calls on release risk that others rely on.
5+ years of hands‑on software QA experience, with meaningful time testing a complex web application. A track record of owning quality for a product area independently — setting the approach, not just executing a plan handed to you. Strong risk-based testing judgment: you can articulate why you tested what you tested, and what you deliberately left uncovered. Deep command of QA fundamentals: test planning and design techniques, boundary and negative testing, equivalence partitioning, severity vs. priority, and the defect lifecycle. Excellent written and verbal communication, including the credibility and comfort to tell a room that a release isn't ready — and to explain why. Hands‑on experience with automation tools ( Github Actions, Playwright)) — enough to read, run, and evaluate a suite even if you don't build it. Working knowledge of CI/CD pipelines and where testing fits within them. Proficiency with a bug tracking and test management toolchain (Jira, confluence, github) Solid API testing skills with Postman or similar, and working with SQL for data validation. Fluency with browser developer tools and application logs — you can usually tell the team whether an issue is front-end, back-end, or data before they open it. Experience in an Agile/Scrum environment with frequent releases.