WTF Gyms
Website:
wtfgyms.com
Job details:
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
WTF GYMS — QA ENGINEER (MANUAL + AUTOMATION)
Witness The Fitness Private Limited | Noida, Uttar Pradesh
Full-Time | On-Site | Tech Team | 2 Openings
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
🏋️ ABOUT WTF GYMS
WTF Gyms — Witness The Fitness — is India's largest centrally-controlled
fitness operator. We run 50+ company-owned gym locations, 60+ Powered Gym
partner locations, and 16 business verticals under one roof — from physical
gyms and fitness education to digital fitness, supplements, corporate
wellness, and franchise operations.
We appeared on Shark Tank India Season 3. We have crossed ₹40.8 crores in
Annual Recurring Revenue. Our entire technology stack is built in-house —
Node.js, Express, PostgreSQL (486+ tables on AWS RDS), React, Next.js,
Flutter (iOS + Android), AWS infrastructure, and a suite of internal
products including WTF OS, the WTF Member App, the Guru Trainer App,
Fitty AI, Amplify CRM, and more.
We are scaling fast. Every product we build goes live to real users across
50+ gym locations. Quality is not optional — it is the difference between
a smooth member experience and a crisis at 6am when a gym cannot open
because the attendance system is down.
We are hiring two QA Engineers to join our tech team and own quality
across our entire product ecosystem.
📌 THE ROLE — QA ENGINEER (2 OPENINGS)
We are looking for two mid-level QA Engineers — people who genuinely
understand quality assurance end to end, who take personal ownership of
the products they test, and who are as comfortable writing test cases
from scratch as they are running regression suites.
This is not a checkbox-testing role. You will be working on real,
production-critical systems — a member app used by 26,000+ members,
a gym operating system running 50+ gym locations, an AI-powered sales
and renewal system, and a growing portfolio of internal and customer-
facing products.
The right person for this role understands that QA is not about finding
bugs after development is done. It is about being involved from
requirements through release — questioning assumptions, catching edge
cases before they hit production, and building a quality culture in
the team rather than just a quality gate at the end.
We want testers who think like users, reason like developers, and care
like owners.
📚 WHAT YOU WILL OWN
MANUAL TESTING
→ Write detailed, structured test cases from scratch based on
requirements, user stories, and design documents — not just
test plan templates
→ Execute functional testing across web applications (React/Next.js),
mobile apps (Flutter — iOS and Android), and backend APIs
→ Perform regression testing across all product areas after every
sprint release — ensuring nothing that worked before is broken
→ Conduct end-to-end testing of critical user journeys:
- Member app: sign-up, membership purchase, workout tracking,
AI coach interaction, community features, push notifications
- WTF OS: lead management, member check-in, renewal flows,
payment processing, analytics dashboards
- Guru Trainer App: session logging, attendance, goal tracking
- Amplify CRM: lead capture, partner management, campaign flows
- Fitty AI: WhatsApp automation, renewal triggers, sales sequences
→ Perform exploratory testing — going beyond the test cases to find
what the test cases did not cover
→ Cross-browser and cross-device testing — ensuring consistent
behaviour across Chrome, Safari, Firefox, and across Android
and iOS device variations
→ Database validation — verifying that data written to PostgreSQL
matches expected outcomes for critical transactions
→ API testing using Postman or equivalent — validating request/
response structure, status codes, error handling, and edge cases
→ Performance testing basics — identifying slow-loading screens,
high-latency API calls, and memory issues in the mobile app
→ Accessibility and usability checks — does the product work as
intended for a real user in a real gym environment?
AUTOMATION TESTING
→ Build and maintain automated test suites for regression coverage
on critical user flows — you are not just running automation,
you are writing it
→ Work with tools such as Selenium, Playwright, Cypress, or
Appium — you should be hands-on with at least one of these
→ Integrate automated tests into the CI/CD pipeline — tests run
on every deployment, not just on demand
→ Maintain test data management — ensuring test environments have
clean, consistent data for repeatable test execution
→ API automation — automated API test suites using Postman Newman,
RestAssured, or equivalent
→ Contribute to expanding automation coverage sprint by sprint —
prioritising the highest-risk flows first
BUG REPORTING & TRACKING
→ Log defects clearly and completely in Jira or equivalent —
steps to reproduce, expected vs actual behaviour, environment,
severity, priority, and screenshots or video recordings
→ Follow up on logged bugs through to resolution — you own the
defect lifecycle, not just the initial report
→ Distinguish between a bug, a design inconsistency, and a feature
gap — and communicate the difference clearly to developers
and product owners
→ Maintain a defect metrics dashboard — open bugs by severity,
age, component, and sprint
TEST MANAGEMENT & DOCUMENTATION
→ Maintain the test suite — keep it current as features change and
new features are added
→ Write and update test plans for new features before development
begins — QA involvement starts at requirements, not at release
→ Participate in sprint planning and grooming — raise questions
about edge cases, missing acceptance criteria, and testability
before a single line of code is written
→ Produce release sign-off reports — clear documentation of what
was tested, what passed, what failed, and what risks remain
QUALITY CULTURE
→ Work closely with developers to reproduce and understand bugs —
not to assign blame but to fix things fast
→ Raise the quality bar over time — build checklists, testing
standards, and processes that make every sprint better
than the last
→ Contribute to code reviews from a quality and testability
perspective when invited
🛠️ TECH STACK YOU WILL TEST ON
Products : WTF Member App (Flutter), WTF OS (React/Node.js),
Guru Trainer App (Flutter), Amplify CRM (React),
Fitty AI (Node.js/WhatsApp), TV App, CCTV AI System
Backend : Node.js + Express APIs on AWS
Database : PostgreSQL (AWS RDS) — 486+ tables
Frontend : React, Next.js
Mobile : Flutter — iOS and Android
Cloud : AWS (EC2, RDS, S3, CloudFront)
Payments : Razorpay + UPI integrations
Auth : JWT, biometric authentication
Messaging : WhatsApp (WWebJS/WATI), Push Notifications (FCM)
Tools you will use:
→ Jira — bug tracking and test management
→ Postman — API testing
→ Playwright / Cypress / Selenium — automation (at least one required)
→ Appium — mobile automation (preferred)
→ Git — version control for test code
→ Google Sheets / Excel — test reporting
→ Chrome DevTools — network and console debugging
→ BrowserStack / real devices — cross-device testing
👤 WHO WE ARE LOOKING FOR
REQUIRED
→ 2 to 4 years of hands-on QA experience — manual testing is your
foundation and you are solid on it. You have tested real products
in production, not just training environments.
→ Strong manual testing skills — you can write a comprehensive test
plan for a new feature from a two-paragraph requirement, and your
test cases cover happy paths, edge cases, and error states equally
→ API testing experience — you have tested REST APIs in Postman and
you understand HTTP methods, status codes, headers, and payloads
→ Automation experience — you have written automated tests using
at least one framework (Selenium, Playwright, Cypress, Appium)
and you understand what to automate vs what to test manually
→ Bug reporting discipline — your bug reports are clear enough that
a developer can reproduce the issue without asking you a single
question
→ Mobile app testing experience — iOS and/or Android, real device
testing, understanding of platform-specific behaviour
→ Database basics — you can write a SELECT query to validate data
in PostgreSQL and you understand what a foreign key relationship
means for test data setup
→ Basic understanding of CI/CD — you know what a pipeline is,
why automated tests run in it, and how a failed test blocks a release
→ Familiarity with Agile/Scrum — you have worked in sprints,
participated in stand-ups, and know how to work within a sprint
cycle without slowing down the team
PREFERRED
→ Experience testing Flutter mobile applications
→ Experience with Playwright or Cypress specifically
→ Experience testing payment gateway integrations
→ Experience testing WhatsApp or messaging automation systems
→ Knowledge of AWS services from a testing perspective
→ Experience with performance or load testing tools
(JMeter, k6, Locust)
→ Basic understanding of JavaScript or Python — enough to read
automation code and write simple scripts
MINDSET
→ You are genuinely curious about how things can break — you do not
just test the happy path because it is easier
→ You take ownership of quality, not just of your test cases —
if something goes to production broken, you feel it personally
→ You communicate clearly with developers — no ego, no blame,
just a shared goal of shipping quality software
→ You are organised and self-directed — you manage your own
testing schedule within the sprint without needing constant
direction
→ You are comfortable with ambiguity — requirements are sometimes
incomplete. You ask the right questions to fill the gap rather
than waiting for perfect documentation.
💰 COMPENSATION & DETAILS
Salary : ₹4 LPA – ₹7 LPA
(based on experience, test writing quality, and
automation proficiency demonstrated in interview)
Openings : 2 positions
Location : Sector 9, Noida — full-time, on-site
Working Hours : Standard tech team hours. Release days may require
extended hours — this is the nature of the role.
Reporting To : Engineering Lead / Co-Founder & CTO
Joining : Immediate to 30 days preferred
Click on Apply to know more.