Sr. Quality Engineer

Versant Media · Englewood Cliffs, NJ · 4 wk ago

On-siteEngineeringFull-time

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections where there is real specific content. We must not repeat job title. No metadata like Job ID. Remove boilerplate: company description? The description includes company description but not needed? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." But we can remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The company description may be considered substantive? It's about the company; maybe we keep it as part of About the role? The "About the role" heading is for section headings like About the role, Responsibilities, etc. The company description could go under About the role. The job description includes "The Opportunity" etc. We'll parse. We need sections: - About the role: could include company description and overview of role (The Opportunity, Why This Role Matters, This is a fully remote role, etc). Must not include placeholder. - Responsibilities: list of duties from "What You'll Do". Use

. - Requirements: maybe from "Qualifications" and "What You Bring". Could combine. - Skills: maybe list of specific skills/experience like frameworks, tools, AI-assisted, hardware testing, etc. Could be separate. - Benefits: The posting mentions "Why You'll Love It Here" and maybe benefits like health insurance etc in Additional Information. There's mention of compensation and benefits: "Actual compensation will be based on factors ... and may include additional forms of compensation and benefits such as health insurance, retirement plans, paid time off, etc." That's benefits info. Also "Why You'll Love It Here" includes opportunity to shape quality engineering, etc. That's more about role. Benefits section should be included if there is real specific content: health insurance, retirement plans, paid time off. That's specific enough. - Pay: The posting includes "VERSANT Media is committed to fair and equitable compensation practices. We include a good faith pay range for each position to comply with applicable state and local pay transparency laws..." but does not give actual numbers. It says "Actual compensation will be based on factors such as the candidate's skills, qualifications, experience, and location". No specific pay range given. So we should NOT create Pay section because no specific pay info. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. Benefits we have some specifics (health insurance, retirement plans, paid time off). So we can include Benefits. - Schedule: The posting mentions "This is a fully remote role. Team members should be comfortable working effectively in a distributed environment and participating in in-person collaboration opportunities, including team meetings, planning sessions, or other business needs, with travel of up to approximately 10% per quarter." Also later: "This position is fully remote, with opportunities for meaningful in-person collaboration based on team and business needs. Travel may be required up to approximately 10% per quarter for team gatherings, planning sessions, or other collaborative work." That's schedule/remote/travel info. So we can include Schedule section with that info. We must not include placeholder like "commensurate with experience". We have specifics. Now we need to output HTML fragment only, no markdown fences. Structure:
About the role

Company description ... plus role overview.
We need to decide what to put in About the role paragraph: combine company description and role overview (The Opportunity, Why This Role Matters, remote nature). Ensure we preserve all substantive information, not invent. Let's extract company description paragraph: "Company Description VERSANT (Nasdaq: VSNT) is an industry-changing media and entertainment business and home to trusted brands that shape culture, inform audiences, and build lasting connections. It operates across four core markets: political news and opinion, business news and personal finance, golf, and sports and genre entertainment. These markets are served through a powerful portfolio of iconic and innovative brands, including CNBC, MS NOW, USA Network, Golf Channel, Oxygen, E!, SYFY, and Versant's sports division USA Sports, along with complementary digital assets including Fandango, Rotten Tomatoes, GolfNow and GolfPass." We can keep that. Then role overview: "The Opportunity We are seeking a highly technical, curious, and experienced Senior Quality Engineer to help deliver reliable, scalable, and high-quality products and experiences. In this role, you will serve as a senior quality advocate, proactively identifying product, integration, and release risks before they affect customers while helping shape how quality is built into the software development lifecycle. You will combine hands-on testing with automation, end-to-end validation, risk-based quality strategy, and AI-assisted quality engineering practices. You will partner closely with Engineering, Product, DevOps, Security, and other stakeholders to establish thoughtful testing approaches, improve release confidence, and continuously strengthen our quality engineering capabilities." "Why This Role Matters The quality and reliability of our products directly influence the experiences of our customers and partners. As a Senior Quality Engineer, you will play an important role in ensuring complex software, hardware, POS device, API, and third-party integrations perform as intended across critical customer journeys. Your work will help teams identify risk earlier, make better-informed release decisions, and scale quality practices as our products and technology evolve. This is a fully remote role. Team members should be comfortable working effectively in a distributed environment and participating in in-person collaboration opportunities, including team meetings, planning sessions, or other business needs, with travel of up to approximately 10% per quarter." We can combine. Now Responsibilities: list from "What You'll Do". Each sentence starts with a verb. We'll make each as
. List: - Own and evolve comprehensive, risk-based test strategies across functional, integration, API, hardware, POS device, and end-to-end workflows, with particular focus on business-critical customer journeys and complex system dependencies. - Design, build, and maintain scalable automated testing solutions for smoke, regression, integration, and end-to-end coverage, while improving test reliability, maintainability, and execution efficiency. - Integrate automated quality checks into CI/CD pipelines and partner with engineering teams to establish effective quality gates, earlier defect detection, and continuous validation throughout the development lifecycle. - Lead exploratory testing, defect triage, root-cause analysis, release readiness assessments, and quality risk reviews, clearly communicating technical risks, tradeoffs, and recommendations to cross-functional stakeholders. - Validate complex integrations spanning software, APIs, hardware, POS devices, and external systems, identifying edge cases and failure scenarios that may not be captured through traditional testing approaches. - Advance quality engineering practices by evaluating and applying AI-enabled tools to accelerate test creation, test maintenance, failure analysis, coverage identification, and engineering productivity while mentoring teammates and contributing to broader quality standards and best practices. Now Requirements: maybe combine "Qualifications What You Bring" and the bullet list of Trust, Teamwork, etc? Those are more like competencies/values. Could be under Requirements or Skills. The instruction: Use sections only when posting has real specific content. We have qualifications list. We'll put them under Requirements. List: - 5+ years of experience in software testing, quality engineering, SDET, or a related technical quality role, with demonstrated ownership of testing strategy for complex products or systems. - Strong hands-on experience designing and maintaining automated test solutions using frameworks such as Playwright, Cypress, Selenium, or comparable technologies. - Experience testing APIs and distributed system integrations using tools or frameworks such as Postman, REST Assured, or similar solutions. - Experience integrating automated tests with CI/CD platforms such as GitHub Actions, Jenkins, GitLab CI, or comparable tooling. - Strong understanding of software development lifecycle practices, test architecture, risk-based testing, Agile development methodologies, and modern quality engineering principles. - Demonstrated ability to uncover high-impact defects and complex failure scenarios through a combination of exploratory, manual, automated, integration, and end-to-end testing. - Strong analytical and troubleshooting skills, with the ability to investigate complex issues, identify root causes, and communicate quality risks clearly to technical and non-technical partners. - Experience using AI-assisted tools to improve test design, automation development, failure analysis, or other quality engineering workflows. - Experience testing hardware devices, POS systems, or complex software-to-hardware integrations is a plus. Then the Trust, Teamwork, Transparency, Agility, Entrepreneurial Spirit, Accountability bullet list: those are more like behavioral competencies. Could be under Skills or maybe under Requirements as well. But we already have a Skills section maybe for technical skills. Let's decide: We'll put those under Skills as they are soft skills/values. Skills: - Trust: Exercise sound judgment, protect the integrity of our products and testing practices, and raise quality concerns constructively and early. - Teamwork: Partner effectively across Engineering, Product, DevOps, Security, and other teams, recognizing that quality is a shared responsibility. - Transparency: Communicate defects, release risks, test coverage, and tradeoffs clearly so teams can make informed decisions. - Agility: Adapt testing approaches as requirements, technologies, and business priorities evolve, balancing speed with appropriate risk management. - Entrepreneurial Spirit: Look beyond established processes to identify opportunities for better automation, smarter testing, stronger tooling, and innovative uses of AI. - Accountability: Take ownership of quality outcomes, follow issues through resolution, and continuously improve the effectiveness of quality engineering practices. Now Benefits: we have "Actual compensation will be based on factors such as the candidate's skills, qualifications, experience, and location and may include additional forms of compensation and benefits such as health insurance, retirement plans, paid time off, etc." Also "Why You'll Love It Here" includes opportunity to shape quality engineering practices, etc. That's more about role. Benefits we can list health insurance, retirement plans, paid time off. We'll put: - Health insurance - Retirement plans - Paid time off Now Schedule: we have remote role, travel up to approx 10% per quarter for in-person collaboration. We'll put: - Fully remote role with opportunities for in-person collaboration. - Travel required up to approximately 10% per quarter for team gatherings, planning sessions, or other collaborative work. Now we must not include duplicated lines. Ensure we didn't repeat. Now output HTML fragment. We'll wrap each section with
heading and then
or

Sr. Quality Engineer

About the role

About the role

Responsibilities

Requirements

Skills

Benefits

Schedule

Similar jobs