QA Team Lead

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 meticulous, trusted QA Team Lead
who can catch what routine testing misses and help build a testing discipline the whole
team can rely on as we grow.

The role

We're looking for a QA Team Lead — someone who's already the person other testers and
engineers trust to catch what a routine pass would miss, and who's ready to start shaping
how the team around them tests, without giving up hands-on QA work.

This isn't a "step away from testing and into meetings" role. You'll keep doing real,
hard QA work — that's most of what makes you right for this role in the first place.
What's new is a second layer of responsibility: making sure testing quality holds up as
the team grows, and helping the QA analysts around you build toward handling harder,
higher-stakes work themselves.

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.

If you're a mid-level or senior QA analyst who's already the one people quietly hand the
trickiest, highest-risk tickets to — even if you've never had "Lead" in your title — this
role is built for exactly that moment in a career.

What you'll do

• Keep testing the hard stuff. You'll continue owning and executing the most complex, highest-stakes testing work — this doesn't go away when you take this role, it's central to it.
• Keep a clear, honest read on the QA team. A simple, current picture of who on the QA team is ready to take on more complex, higher-stakes work right now, and who's still building toward it.
• Be a consistent, trusted evaluator. When someone — in QA or engineering — seems ready for more responsibility, you'll help confirm that by giving a calibrated, consistent read on how they actually handled a real, challenging piece of work, not a one-off gut call.
• Watch the health of the testing pipeline. Notice when work is piling up in QA before it turns into a real delay, and step in — reprioritizing, unblocking, or pitching in directly — before it becomes a problem the whole team feels.
• Mentor. Be a resource for QA analysts earlier in their growth than you, especially around the judgment calls — what actually needs deep scrutiny versus what doesn't — that are hard to teach from a checklist alone.

What you need

• A real track record of successfully testing and validating the hardest, most ambiguous, highest-stakes work on a team — catching the problems a routine test pass would miss. 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

• Experience mentoring or informally guiding less experienced QA team members.
• Comfort keeping an honest, current read on where a QA team's skills and capacity actually sit.
• Interest in helping decide when a teammate — in QA or engineering — is ready for more complex responsibility, grounded in real observed work rather than guesswork.
• An eye for catching workflow bottlenecks and pile-ups early, and comfort stepping in to fix them rather than just flagging them.

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've been doing strong senior-level testing work but have never formally led anyone,
this is usually the next real step — not a lateral move into pure management, and not a
step away from hands-on QA. You keep doing the work you're good at. You just start doing
it with a little more say in how the team around you tests, and how it grows.

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.