QA Engineer

About Us

FIT HUB is a venture-backed technology-driven health and wellness startup based in Jakarta, Indonesia. Founded in 2020, FIT HUB’s mission is to democratize access to Health and Wellness for all Indonesians. We believe that everyone should have access to improving their health and wellness, so we’ve built FIT HUB from the ground up to make exercising friendly, affordable, and fun for new gym‑goers and fitness enthusiasts alike.

In this role, you will be part of our growing Engineering Team. You will help the Engineering Team build and maintain our mobile application and internal tools. You will be expected to be agile, hands‑on, and willing to hit the ground with a growth mindset. You'll get a huge room for growth and an opportunity to show your skills as you will help create world‑class digital products.

• Own full lifecycle testing for your assigned stories, from refinement through production.
• Manage your own delivery without needing to be followed up.
• Write concise, complete test plans and sharpen acceptance criteria together with PMs and tech leads.
• Debug and triage bugs in the application; surface root cause context that helps developers fix faster, not just report failures.
• Execute manual and automated coverage for features, regressions, and hotfixes on time, consistently.
• Contribute to automation coverage on stable, high‑frequency flows — check‑in, payment, onboarding — under the direction of senior QA.
• Participate actively in sprint ceremonies: grooming, planning, retros as a quality voice.
• Collaborate with engineers, product, and stakeholders; share what you learn and absorb what others know.

• 3+ years in software quality engineering or QA.
• Experience with 3rd party will be a plus.
• Hands‑on experience with JavaScript or Python for test scripting (Cypress, Webdriver
  
  IO, or Cucumber).
• Having experience in Playwright will be a plus.
• Has written or contributed to automated test cases, not just manual testing.
• Mobile automation exposure:
  Appium or Katalon (even basic familiarity counts).
• Strong attention to detail and passion for writing reliable, maintainable test cases.
• Clear written communication: your test plans are readable by non‑QA teammates.
• Team player: you share what you learn and ask when you're stuck.