Junior QA Analyst

About MedaVida

MedaVida is building the payments-enabled operating system for modern cash-pay
healthcare. Our platform connects credential verification, patient care, prescriptions,
payments, suppliers, communication, and practice growth within one unified ecosystem.

We are a fast-moving healthcare technology and fintech startup preparing to bring
multiple products to market. We are looking for a detail-oriented, eager-to-grow
Junior QA Analyst who can turn well-scoped test tickets into real, trustworthy
verification and help build toward handling harder, higher-stakes testing over time.

The role

We're looking for a Junior QA Analyst — someone early in their testing career who
wants to work on a real, shipping product where a missed bug has real consequences for
real patients, not a sandbox.

You won't be handed a stack of checkbox scripts and left alone. Our team routes work by
how well-defined and complex it actually is, not by title — so from your first sprint
you'll be testing real, scoped tickets: clear specs, a defined "done," and a Lead and
senior QA analysts around you who actually read your test plans and help you get
unstuck. Some of what lands in your lane will be verifying work other developers and our
AI tooling ship; some of it will be building test coverage from scratch. Both count, and
both are how you build judgment.

This is an on-ramp, not a holding pattern. The path from here is well-lit: take on real
testing work, build a track record other QA analysts and your Lead can actually see, and
the complexity — and stakes — of what you're trusted with grows accordingly —
evidence-based, not tenure-based.

We're a startup, which means responsibilities don't stay in one lane. You'll shift
between Development, Review, Product Requirements definition, and Testing as the moment
calls for it — that's a feature of how we work, not a scope-creep exception.

What you'll do

• Own real, scoped test tickets. Clearly-specified feature and regression testing, sized to what you're ready for — not busywork, and not thrown at the highest-stakes work either.
• Write and execute test plans, not just click through a checklist — learning to think about what could actually break, not just confirm what already works.
• File bugs that are actually useful. Clear repro steps, expected vs. actual behavior, enough context that a developer doesn't have to reconstruct your session to understand it.
• Ask for help early and often. Your Lead and the senior QA analysts around you are a resource, not a last resort — using them well is itself a skill we're looking for.
• Build a track record. As you handle real assignments well, that becomes the actual evidence for taking on harder, higher-stakes testing work next — not a review cycle, a resume line, or a guess.

What you need

• A solid grasp of how to think like someone trying to break something, and the discipline to document what you find clearly — demonstrated however you got there: formal QA experience, a CS or related degree, serious personal-project testing, an internship, or self-taught work you can talk through in depth. This is the one non-negotiable requirement for this role. Everything else below is something we expect you to grow into, not something you need to already have done.

Nice to have — things you'll grow into, not gate you out

• Exposure to a real, shared codebase or product (school group projects and internships both count).
• Comfort taking feedback on a test plan or bug report without treating it as a verdict on you.
• Some experience with test tooling, manual or automated, or a demonstrated ability to pick up new tools fast.
• Curiosity about why something breaks, not just confirming that it does.

How we work

• Hours: 8:00 AM – 5:00 PM EST.
• Weekends: Not the norm, and we mean that as a design goal, not a hope. If a weekend gets worked, we treat that as a personal and managerial failure first — something to fix upstream, not shrug off — and every effort is made to avoid it. That said, we're a startup: the team is expected to pivot to meet real opportunities, sometimes on short notice, and that occasionally means weekend work.

Why this role

If you're early-career and tired of interviewing for QA roles that turn out to be
running the same script every day, this is built to actually be that. You'll test real
software from week one, get direct feedback from people who'll actually read your work,
and have a clear, honest path to bigger responsibility that isn't political — it's just
what you've actually done.

Location: Remote

Compensation: We're a startup with real product already in the market, and we offer
competitive salaries. We're also in the process of setting up an Employee Stock Option
Plan (ESOP), with vesting backdated to begin on your employment start date.