Junior Quality Assurance Specialist

Most QA roles are about catching bugs.

This one is about protecting trust.

At EverTry, we help people pay for things they otherwise couldn’t, such as subscriptions, exams, and global services, from places where payments don’t just “work.” When our product fails, it’s not a minor inconvenience. Someone misses a deadline. A payment gets declined. An opportunity slips.

That’s why this role matters.

We’re hiring a Junior Quality Assurance Specialist who cares about details, but more importantly, cares about people on the other side of the screen.

What you’ll do

You won’t just “test features.” You’ll learn how the system actually works, and where it breaks.

• Write clear, simple test cases for new features and improvements
• Manually test flows across web and mobile (sign-up, KYC, payments, cards)
• Reproduce bugs consistently so engineers can fix them fast
• Track issues from discovery to resolution
• Run regression tests before releases (nothing ships blind)
• Work closely with engineers and the product team to understand why something was built, not just what
• Help us improve how we test, not just follow a checklist

What we’re looking for

We don’t expect years of experience. We care about how you think.

• You notice small things others miss
• You’re patient enough to break things properly
• You can explain a bug clearly, without noise
• You’re curious, when something fails, you want to know why
• You take ownership (you don’t say “QA passed it,” you say “this works”)

Basic requirements:

• 0–2 years experience in QA, testing, or a related role (or strong self-taught experience)
• Understanding of how web/mobile apps work
• Familiarity with writing test cases or checklists
• Comfort using tools like spreadsheets, issue trackers, or basic dev tools

Nice to have (but not required)

• Exposure to tools like Selenium, Postman, or Cypress
• Basic understanding of APIs and how to test them
• Some knowledge of how software is built (Git, deployments, etc.)
• Experience working in a startup or fast-moving team

How we work

We’re a small, focused team.

• We ship fast, but we don’t ship carelessly
• We argue about the right things (user experience, reliability, clarity)
• We care about users in Madagascar, Nigeria, Kenya, Ghana, and anywhere payments are broken

QA at EverTry isn’t a gate at the end. It’s part of how we think from the start.

Why is this role different?

You won’t be lost in a large QA team.

You’ll see the direct impact of your work:

• A failed payment you caught → someone completes their application on time
• A bug you reported → thousands of users avoid frustration
• A test you wrote → becomes part of how we scale quality

If this sounds like you

You probably:

• Get annoyed when apps are sloppy
• Try edge cases just to see what happens
• Care about doing things properly, even when no one is watching

QA Assessment

Bug Hunt: Reality Check

You are given this product requirement:

“Users can fund their wallet using either Naira or USDT.

Minimum funding amount is $5.

Transactions are instant.

Users will see a success message after payment is completed.”

Your Task

Identify as many potential issues, risks, and edge cases as possible.

• We are not looking for a short list.
• We are looking for depth.

Think in layers

Go beyond surface-level bugs. Consider:

• Logical inconsistencies
• Currency conversion problems
• Timing and “instant” assumptions
• Partial failures (money leaves, balance doesn’t update)
• Duplicate transactions
• Network interruptions
• User behavior (refreshing, retrying, impatience)
• Backend vs frontend mismatches
• Third-party dependencies (payment providers, blockchain delays)
• Error handling and messaging

Output format

Structure your answer clearly under these headings:

• Assumptions that may be wrong
• Edge cases
• Failure scenarios
• User behavior risks
• System/design gaps
• Constraint

If your answer has fewer than 15 meaningful points, you have not gone deep enough.

What we’re actually testing

• Do you question vague requirements?
• Do you think in systems or just screens?
• Can you anticipate real-world failure?
• Do you care enough to go deeper than required?

How to apply

• Do not send a CV first.
• Start with the assessment.
• Complete the QA assessment above
• Submit your answers as a clear, structured document (PDF or Google Doc)

Include:

• Your full name
• Links to any relevant work (if you have any)
• A short note (3–5 sentences max): Why this role?

Subject line: Junior Quality Assurance Specialist – EverTry

Important:

We care more about your thinking than your experience

If your submission is shallow, we won’t respond

If it’s strong, we will reach out, even if you have no formal QA background