• Always QA on staging — never live: All QA work happens on the Webflow staging environment. You never review or approve work on the live site. If staging hasn't been published by the builder, publish it yourself before starting — but never push changes to the live site during QA. • Test site builds and edits for functionality: Systematically verify that links work, forms submit correctly, integrations fire, pages load on all breakpoints, and interactive elements behave as expected. • Validate CRM integration routing: Confirm that every CTA routes to the correct destination — hero and program page CTAs must go to a CRM Calendar, Form, or PushPress Landing Page; the Drop-In CTA must link to the PushPress Drop-in plan page specifically; Contact Us must use a form, not a calendar. Hold/Cancel/Rates links must be present and visible in the footer. • Verify Google Analytics configuration: GA must be set up at the Property level. Account-level-only access is an automatic QA fail — flag immediately and return to the builder. • Verify schedule embed integrity: Right-click the embedded schedule on the site → Inspect → confirm the gym's name appears in the iframe source code. A mismatch means the wrong schedule is embedded. • Check site speed: Run Google PageSpeed Insights on the staging URL for both Mobile and Desktop. Flag the ticket if either score falls below 90 and document exact scores before moving forward. • Verify image geo-tags: Use Geoimgr or jimpl to confirm that the following images contain the gym's GPS coordinates in their Exif data: Homepage Hero, Top Programs section, Community section, Footer. Missing geo-tags are a PushPress SEO requirement — flag as an error and return to the builder. • Run Lighthouse SEO audits: Use Chrome DevTools (F12 → Lighthouse → SEO) on the Homepage, Schedule, About, Blog (if selected), Contact, and HSN Nutrition (if applicable) pages. Flag any missing meta title, meta description, or meta image as an SEO error. • QA CRM configurations: Test GoHighLevel automations, workflows, calendar bookings, and pipeline setups to ensure they function correctly end to end. • Document bugs in BugHerd: Every issue is logged directly in BugHerd on the staging site — with exact steps to reproduce, expected vs. actual behavior, browser/device info, and screenshots or screen recordings. No ambiguity. • Manage the QA queue in Linear: Track all work through Linear using the correct status workflow: QA In Progress → QA-Fail (with documented issues) → Complete: Not Live (passed QA, ready for go-live). Nothing advances without a complete checklist pass. • Build and maintain QA checklists: Develop and evolve standardized testing protocols for different work types — new site builds, edit requests, CRM setups. The checklist improves as new failure modes are discovered. • Track defect patterns: Identify recurring issues and surface them to the Implementation Leader so root causes can be addressed through SOPs, training, or automation. • Collaborate with builders on fixes: When work is returned for fixes, be available to clarify bugs and verify corrections. Your goal is first-pass resolution — work shouldn't bounce back and forth. • Test across browsers and devices: Maintain a testing matrix and ensure consistent functionality across desktop and mobile viewports.

• Review new site builds and edit requests for visual quality: You're the last visual check before anything reaches a client — covering both new site builds and ongoing edit requests. Every build gets a full visual pass; every edit that touches layout, imagery, or styling gets reviewed before it ships. • Catch visual quality issues: Identify problems with alignment, spacing, cropping, typography, color consistency, image quality, and responsive behavior. No blurry images. No awkward crops. No inconsistent padding. If it looks sloppy, it doesn't ship. • Review at every Webflow breakpoint: Check each build or edit at all breakpoints — desktop, large, medium (tablet), small (mobile landscape), and tiny (mobile portrait). Webflow styles cascade down, so a change at desktop can break layouts at smaller sizes. You catch those before they ship. • Fix what you find: For minor visual issues (spacing, alignment, cropping), fix them directly in Webflow rather than sending work back. You should be comfortable making small corrections without involving a builder. • Annotate and document issues in BugHerd: When issues require builder fixes, document them in BugHerd directly on the staging site — annotated screenshot, specific issue described, fix suggested. No vague notes. • Manage visual QA tickets in Linear: Track the status of all reviews and revisions in Linear. Work only moves forward when it passes your visual checklist in full. • Document visual standards: Help build and maintain a visual QA checklist that the team uses as a baseline. What "good" looks like should be written down, not assumed. • Provide clear, actionable feedback: When work goes back to a builder, your feedback must be specific enough that they can fix it without a follow-up conversation — "Hero image is cropped at 375px and cuts off the subject's face; needs vertical repositioning at mobile breakpoint" beats "looks off on mobile." • Track visual quality trends: Notice patterns — if the same visual issues keep appearing, flag them so the team can address root causes through SOPs or builder training. • Collaborate with the Implementation Leader: Report on visual quality metrics, surface recurring issues, and help prioritize what standards need tightening.

This description is a summary of our understanding of the job description. Click on 'Apply' button to find out more. Role Description This role involves ensuring the quality of software through various testing methodologies. - Hands-on experience in test planning and design under proven test design techniques - Knowledge and understanding in Crypto/PKI/Identity Security technology (preferable) - Design, develop, and maintain automated test frameworks for functional, regression, and integration testing - Ability to set up/manage QA environments, debug problems, and ensure builds are kept to high quality standards - Write clean, reusable, and scalable test code using languages like Java and Python - Continuously improve test coverage, test effectiveness, and reliability of automation - Oversee/guides in test case writing/execution, regression testing, performance, and stress testing - Report all observed bugs and conduct discussions with the development team to understand technical specifications - Monitor progress towards project plans and intervene as necessary - Analyze risk and quality metrics for multiple projects - Demonstrate an in-depth understanding of design to create concise/accurate test case suites - Manage, develop, and mentor individuals, growing strong leads - Be a customer advocate with a solid interest in improving customer business operations - Drive Test Automation efforts in the group and take ownership to deliver on time Qualifications - Result-oriented individual with strong analytical and problem-solving skills - Never satisfied with the status quo; sets high standards - Good presentation, communication, and interpersonal skills - Quick learner, creative, resourceful, and able to work independently - Strong experience in API Testing - Hands-on experience with Robot Framework, Selenium, or Playwright - Proficiency in Python for test scripting and automation Benefits - Competitive incentives - Health & wellness policies - Saving & investment schemes - Time off/sabbatical eligibility - Dedicated Learning & Development opportunities - Flexibility to work remotely and define own hours Company Description AppViewX is trusted by the world’s leading organizations to reduce risk, ensure compliance, and increase visibility through automated certificate lifecycle management. - Headquartered in New York City - Global footprint in India, North America, United Kingdom, and Australia - Serves Fortune 1000 companies, including top global banks and media companies - Proud to be an Equal Employment Opportunity Employer

• Manage and guide a QA team focused on evaluating customer support calls, chats, and emails; • Ensure all customer interactions meet high-quality standards and comply with gambling industry regulations; • Provide regular coaching, training, and constructive feedback to QA specialists; • Develop, calibrate, and improve QA scorecards and evaluation processes; • Track team performance metrics and prepare quality reports for stakeholders.