QA / Automation Engineer

Why this role matters

Help the team discover important failures before users encounter them. Combine exploration with a small dependable automation suite for one agreed product. Your contribution is clear risk assessment, reproducible findings and release evidence people can inspect.

A typical working day

• Turn a story into observable checks with its owner.
• Explore permission, mobile and recovery paths using isolated fictional data.
• Verify fixes and distinguish unstable tests from product defects.

Your responsibilities

• Define risk-based acceptance checks with engineering and founders.
• Automate core browser/API regressions and maintain reproducible bug evidence.
• Verify mobile, accessibility, permissions and safe production-release checks.
• Communicate progress and dependencies early; agree scope changes before taking on another workstream.

Ownership boundaries

Not responsible for writing all product code, independent penetration certification or guaranteeing zero defects.

What you bring

• 2+ years of testing evidence, exploratory testing and clear bug reports.
• Playwright or equivalent, API testing and test-data isolation.
• Understand flaky tests, authorization failures and release risk.

AI with judgment

Use AI to expand test ideas, then verify assertions and avoid sending private customer data to unapproved tools.

Evidence and assessment

A sanitized test suite, three useful bug reports and a short risk-based test plan.

A paid sandbox exploration followed by one automated critical-path test and prioritized findings. Agree payment and a time cap before starting. Use fictional data, no live credentials and no free production work.

How we work

Remote-first with an agreed collaboration window with the Nigeria-based team. Physical sessions require an agreed location, notice and travel arrangements; weekly office attendance is not assumed. Eligibility, engagement type and availability are confirmed individually.

The work you can shape

Practical problems, visible ownership and collaboration across product, design and operations. Together we agree a focused scope and the evidence that will show it is working.

First 30 days

1. Days 1-5: agree top risks and prepare fictional fixtures for one journey.
2. Days 6-15: provide reproducible findings and two dependable high-value automated checks.
3. Days 16-30: repeat the test pass, verify fixes and deliver a concise release-risk report and test instructions.