Manual QA Engineer

About the role

You'll be the quality owner for mobile, web, and backend user journeys—turning product requirements into crisp test scenarios, executing deep exploratory tests, validating data flows (APIs + events), and keeping releases ship-ready in a fast-moving fintech environment.

• Translate PRDs/user stories into risk-based test plans, test cases, and checklists; maintain coverage maps for features and regressions.
• Execute functional, regression, smoke, usability, and exploratory testing across Flutter, React Native, and Web apps on real devices/emulators and multiple browsers.
• Validate APIs and event flows for Go microservices: request/response correctness, auth/roles, idempotency, retries, and Kafka consumer‑producer behaviors (ordering, DLQs).
• Perform data validation in Postgre
  
  SQL/Dynamo
  
  DB; verify caches in Redis; sanity-check S3/artifact links where relevant.
• Own release readiness: test runs, sign‑offs, sanity on staging/pre‑prod, hotfix verification, and post‑release monitoring.
• Use observability tools (logs/metrics/traces in Cloud Watch/Grafana/Open Telemetry) to triage defects and provide high‑signal bug reports.
• Conduct payments & fintech flows testing (KYC, OTP, subscription/renewals, refunds, recon), including edge/negative cases and network variability.
• Manage test data (synthetic/masked), environments, and device/browser matrix; track defects in Jira and drive bug triage with engineering/PM.
• Leverage GenAI (Copilot/OpenAI or similar) to draft test scenarios, generate boundary cases, summarize logs, and convert requirements to Gherkin—while protecting PII.
• Contribute to acceptance criteria (Given/When/Then), regression suite upkeep, and lightweight smoke checks in CI (even if authored by automation peers).

• Strong manual testing across mobile + web + API; excellent exploratory testing instincts and defect isolation.
• API testing with Postman/Newman; comfort with JSON, HTTP, auth flows, headers/cookies, and schema diffs.
• Mobile testing: real devices/emulators, deep links, push notifications, permissions, app upgrades, and crash triage (Crashlytics/Instabug).
• Web testing: multi‑browser sanity (Chromium/Firefox/Web Kit), responsive layouts, cookies/storage, and feature flags.
• Data & tools: SQL for Postgres, basics of Dynamo
  
  DB queries, reading Kafka messages, and validating Redis keys/TTL.
• Debugging toolkit:
  Charles/Proxyman/Fiddler, browser devtools, adb/xcode tools, log scraping (Cloud Watch/Kibana), and network throttling.
• Process:
  Jira + Test Rail/Zephyr, clear bug reports (STR, actual vs expected, env, logs, attachments), and versioned test assets.
• Security & compliance awareness: PCI‑DSS basics, PII handling, data masking, and session/auth testing.
• Comfortable using GenAI safely to speed up test design and failure summaries (prompt hygiene, no sensitive data in prompts).

• Gherkin/BDD exposure; writing acceptance tests alongside PM/Dev.
• Basic performance smoke testing (k6/Locust) and accessibility checks (WCAG basics).
• Familiarity with contract testing concepts and CI quality gates.
• Understanding of Kafka patterns (exactly‑once semantics, consumer lag, retries) and how they impact testing.
• How we'll measure success
• High‑priority defects caught pre‑prod; defect leakage trending down.
• Clear coverage maps per feature; fast, reliable regression cycles.
• Actionable bug reports with logs/har files/screens that cut developer MTTR.
• Release cadence maintained with zero P0/P1 post‑release on owned areas.

• 3–4 years in Manual QA for consumer/mobile‑first products (fintech a plus).
• Hands‑on across mobile, web, and API test cycles in agile teams.
• Strong written/spoken communication; crisp documentation and ownership mindset.
• Tools you'll likely use
• Jira, Test Rail/Zephyr, Postman/Newman, Charles/Proxyman/Fiddler, Browser Stack/Firebase Test Lab, Crashlytics/Instabug, Cloud Watch/Grafana, Git basics, OpenAI/Copilot for test productivity.