About the Role:
Sit between Engineering and Customer Success. Every release passes through you first, and you lead testing through the lens of the customer.
Continu is the enterprise learning platform enterprises use to train their customers, partners, and internal teams from one place. That means multiple audiences, admin and learner experiences, Eddy (our conversational AI learning agent), and deep integrations that all have to work together.
We build fast and ship often, usually multiple times a week. This is a contract quality assurance role focused on one thing: making sure that work is genuinely ready before it reaches customers. You'll review completed work against specific acceptance criteria, test it thoroughly, and hold the line on release quality.
What sets this role apart is customer fluency. Passing a checklist isn't enough. You need to understand how real customers actually use the product, and build your testing around their specific workflows, configurations, and edge cases. You'll take that understanding and turn it into structured test plans, then apply them rigorously against new functionality before it ships.
You'll also be the clearest voice in the room when something's wrong. Bugs you find need to be documented so precisely that Engineering can reproduce and fix them without a follow-up conversation.
What You'll Do:
Review completed development work against defined acceptance criteria as it lands, typically turning a ticket around within one business day
Build test plans that translate real customer use cases and account configurations into concrete test scenarios
Run functional, regression and edge-case testing ahead of each release, applying known customer workflows to catch issues generic testing would miss
Test Eddy and other AI features for accuracy, relevance and tone, where the output can change from run to run
Identify, document, and report bugs with clear, reproducible steps, expected vs. actual behavior, and severity
Verify fixes with Engineering and confirm issues are fully resolved before sign-off
Flag areas where new functionality risks breaking existing customer workflows
Maintain and evolve test checklists and QA documentation as the product changes
Partner with Customer Success to keep a current picture of key customer configurations and workflows
Give Engineering and Product a clear, honest read on release readiness, including when something isn't ready
Prioritize and triage issues by customer impact and severity
What We're Looking For:
Experience in QA, software testing, or a similar quality-focused role, ideally in SaaS
A track record of thinking like the customer, testing how features get used, not just whether they technically work
Comfortable manually testing web applications thoroughly and methodically; scripting or automated-testing experience is a plus, not a requirement
Excellent written communication. You can write a bug report an engineer can act on without asking a clarifying question
Skilled at reading specs and requirements and spotting the gaps, edge cases, or untested paths nobody thought to write down
Naturally detail-oriented, with the patience to test the same flow several ways before calling it done
Comfortable using bug and issue tracking tools such as Jira, or similar
Able to work independently and manage your own testing timeline against release deadlines
Comfortable with a fast pace, where priorities shift and work arrives continuously rather than in tidy sprints
Background in EdTech, HR Tech, LMS, or adjacent enterprise SaaS is a plus
Experience testing AI or LLM-powered features is a plus
What Success Looks Like:
Zero P1 bugs reach customers, and releases ship free of regressions and known customer-impacting issues
Test coverage reflects how customers actually use the product, not just the happy path
Engineering gets bug reports clear and complete enough to act on immediately
Every ticket gets a QA pass within one business day of being marked ready, so testing never becomes the bottleneck
Known, high-value customer workflows are proactively tested before every release, not just after something breaks
QA documentation and process get sharper over time, making the next release easier to test than the last
Engagement Details Type: Contract
Location: Remote, with at least 4 hours of daily overlap with US Eastern time
Hours: 30 to 40 per week, ongoing
Reports to: VP Engineering, working closely with Product and Customer Success
Rate: Hourly, based on experience
Process: Intro call, then a short paid test on a real Continu build
