QA Engineer

Our vision is to elevate online learning by applying the most successful approaches in virtual education to create an accessible and inclusive homeschool curriculum platform where all students can be successful! Our K-8 platforms include Miacademy , Always Icecream , and Clever Dragons , and our 9-12 options include MiaPrep and MiaPrep Online High School . Our student base is rapidly growing, and we’re hiring for multiple positions across several departments! Our expansion stems from our commitment to providing exceptional educational content and our pursuit of new opportunities. 🚀

▶️ You can hear our CEO, Johannes Ziegler, discuss our company’s values and future !

How you’ll make an impact (position summary)

Miaplaza is dedicated to making education engaging and accessible through innovative online learning platforms. We develop personalized learning experiences for students, helping them grow in a supportive and interactive environment. Our vision is to elevate online learning by applying the most successful approaches in virtual education to create an accessible and inclusive education curriculum platform where all students can be successful!

The Role

We're looking for a QA Engineer to join our current QA team. You'll take ownership of how we test, validate, and sign off on quality across our platform. We're actively investing in our QA practice: expanding automated test coverage, improving our release testing process, and moving toward a model where quality is embedded throughout the development lifecycle.

You'll report to a technical Engineering Manager and work alongside engineers who value clear test documentation, reliable automation, and confident code releases.

As a mature company, we have legacy systems and established manual testing workflows, but we are transitioning to modern automated testing practices using Playwright and TypeScript. The split between manual and automated work varies, but you should be comfortable working across both, bringing automation where it adds the most value while pragmatically maintaining manual coverage where it's still the right tool.

A core goal of our QA evolution is to make testing faster, more reliable, and less dependent on last-minute changes before each release: replacing fragile manual regression cycles with stable automated suites, reducing flakiness, and building coverage that the whole team can rely on. Every testing investment is measured by whether it improves quality and reduces the team's burden at release time.

What You'll Do

• Write and maintain automated regression tests; review automation MRs from peers
• Execute manual testing across web UIs (functional, regression, cross-platform, responsive layouts on mobile/tablet)
• Create and maintain test cases, checklists, and test documentation in TestRail
• File clear, actionable bug reports with reproduction steps; collaborate with developers to triage and resolve
• Own the release testing process to ensure only high-quality changes ship
• Partner with PMs and designers on requirements review, edge cases, and acceptance criteria
• Contribute to QA process improvements as we scale (currently a 2-person team growing to 4)

How We Work

We believe you should know what your days look like before you accept an offer.

We don't have much bureaucracy. Small team, direct communication, short decision loops. If you've worked at places where opening a Jira ticket to request a Jira ticket was normal, this isn't that. Here's the reality:

Meetings (yes, we keep them minimal)

• Daily standup with your product team. Show up, share updates and unblock each other..
• Sprint planning and retrospectives with your product team, once per sprint.
• 1:1 with your Engineering Manager - Regular cadence, your agenda.
• Monthly Engineering all-hands.
• That's it. The rest of your time is yours to work.

Deployments

• Bi-monthly release cadence with a schedule published in advance. As a QA Engineer, you own the release testing window. Coordinating with developers, running regression suites, and signing off on quality before the release.
• Infrequent ad-hoc hotfixes

Communication

• Async-friendly. Documentation-first.
• Slack/ Jira/ GitLab MRs/ Notion
• Google Workspace for email and documents.
• Zoom for video calls.

Timezone

• We need significant overlap with typical CET (Central European Time) working hours to coordinate and collaborate synchronously. Additionally we have stakeholders and developers in US timezones that we occasionally need to meet.