This description is a summary of our understanding of the job description. Click on 'Apply' button to find out more. Role Description We are hiring a Director of Quality Engineering interested in being a part of our rapidly growing engineering team. Our engineering team releases new software every week, moves at a fast pace, and works directly with our design and customer-facing teams to imagine and build the new experiences our customers love. We have an expansive software suite that supports all of our customers’ mission-critical workflows. Because of that, you’ll get a rewarding variety of projects to work on. Responsibilities - Define the long-term vision for quality at Qualia, using a combination of traditional testing and automation to create a comprehensive quality engineering approach - Take full responsibility for complex, high-liability quality initiatives - Establish robust feedback loops and post-incident processes to ensure the organization learns from technical mistakes - Mentor and provide support for both QA Analysts and SDETs - Work directly with product, engineering, and design teams to ensure new experiences meet our high standards Qualifications - 8+ years of experience in quality engineering or software quality assurance - At least 3+ years in a senior leadership role managing multiple teams or a large organization - Strong hands-on technical leadership in building automated testing suites for full-stack, customer-facing products - Proven ability to make key architectural decisions for large-scale test infrastructure and diverse software integrations - Keen product sense and a passion for the impact of the software you build - A background in enterprise software and fintech is preferred Requirements - Experience making key architectural decisions regarding test automation frameworks - Ability to perform research to back up architectural decisions - Experience in establishing processes to proactively address architectural weaknesses Benefits - Comprehensive health plans - 401k program - Commuter benefits - Professional development opportunities - Parental leave - Flexible time off policy - Robust online onboarding program - Biweekly all hands meetings - A variety of internal virtual events to keep employees connected

• Own and execute QA activities across DRM-protected platforms and services • Validate DRM implementations to ensure secure, compliant content delivery • Design, execute, and maintain test plans, test cases, and test scenarios for complex systems • Identify, log, track, and retest defects, working closely with engineers to ensure timely resolution • Support regression, integration, and release testing across ongoing platform development • Provide clear quality assessments and risk analysis ahead of releases • Contribute to improving QA processes, documentation, and overall quality standards • Work collaboratively within cross-functional teams while maintaining strong attention to detail

• 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.