
Functional QA Specialist
PushPress
full-time
Posted on:
Location Type: Remote
Location: Philippines
Visit company websiteExplore more
About the role
- 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.
Requirements
- Systematic testing mindset — you follow a process, not your gut. Every test has a checklist, every result is documented
- Experience with web testing — you understand how websites work (forms, links, redirects, responsive behavior, JavaScript interactions) and know where things commonly break
- Familiarity with Webflow — you can navigate published and staging sites, understand how Webflow components behave, and identify when something isn't rendering correctly
- Familiarity with GoHighLevel (GHL) or similar CRM platforms — you can test automations, workflows, form integrations, and calendar setups, and understand how CTA routing should be configured
- Proficiency with BugHerd — you'll use it daily to document and annotate bugs directly on staging sites. Prior experience preferred; ability to get up to speed immediately required
- Proficiency with Linear — you'll manage the QA ticket queue in Linear throughout each workday. Familiarity with Linear or similar project management tools is expected
- Clear, precise bug documentation — your reports include steps to reproduce, expected vs. actual behavior, and supporting evidence (screenshots, recordings). A builder can fix the issue from your report alone, without follow-up questions
- Strong written communication in English — your documentation needs to be unambiguous and professional
- Comfort with repetitive, detail-oriented work — this role tests a high volume of deliverables daily and requires sustained accuracy
- Solid understanding of browser developer tools — you can check console errors, inspect network requests, verify iframe source content, and confirm form submissions via Chrome DevTools
Benefits
- Work fully remote from anywhere in the world — we're a distributed team with flexibility built into our culture
- Inherit and improve an established operation — you're joining an existing team and helping raise the quality bar
- Direct leadership access — you'll work side by side with leadership with full context on company strategy
- Above-market compensation — we pay above market intentionally. We want the best, and we pay for it.
- AI-native operation — automation is core to how this team works, not an afterthought. You'll operate at the frontier of how implementation teams are built in 2026.
- Impact that compounds — catching bugs before clients see them means better product quality, lower churn, and happier clients. Your work has a direct line to business outcomes.
Applicant Tracking System Keywords
Tip: use these terms in your resume and cover letter to boost ATS matches.
Hard Skills & Tools
web testingQA methodologiesCRM integrationGoogle AnalyticsSEO auditsdefect trackingbrowser developer toolsJavaScript interactionsresponsive behaviorchecklist development
Soft Skills
systematic testing mindsetstrong written communicationdetail-oriented workcollaborationproblem-solvingdocumentation skillsprocess-orientedclarity in reportingadaptabilitytime management