About LearnWise AIpbr/ppLearnWise is an AI-first startup helping universities and colleges support students and faculty with smart, knowledge-driven tools. We’re a small team with high ownership and real user impact — a place where the best idea wins, no matter who says it. /ppWe build the “plumbing” that powers AI assistants and student engagement workflows, integrating with major LMS platforms and supporting institutions at scale. You’ll collaborate closely with Engineering, Product, and our AI team. /ppbr/pWhy this role existspbr/ppWe’ve invested in a Playwright-based test automation suite and CI workflows, and now we need someone to bevolve it into a production-grade quality signal /b — broader coverage, less flakiness, faster feedback, and stronger release confidence as we scale. /ppbr/ppWe’re looking for a btest-first / quality-first engineer /b who can help us move toward bAcceptance Test Driven Development (ATDD) /b: /pulliDefining acceptance criteria and tests early (before implementation). /liliBuilding acceptance tests at bAPI level /b and bfrontend level /b. /liliCreating a clear path from product intent → executable tests → high-confidence releases. /li /ulpbr/ppCrucially, this is a software engineering role first — we expect you to bring solid development skills and to own your work with a high degree of independence. You won't be handed a list of test cases; you'll figure them out yourself, take ownership of the automation end-to-end, and drive quality forward proactively. /ppbr/pWhat you’ll dobrBuild and scale test automation (frontend + API)pbr/pulliDesign, implement, and maintain bE2E and API-level acceptance tests /b (Playwright + TypeScript). /liliBuild reusable testing infrastructure: bfixtures, helpers, page objects (POM) /b, test data utilities, and conventions that scale. /liliImprove suite reliability: reduce flakiness, strengthen selectors, improve waits/assertions, and make failures debuggable (traces, screenshots, logs). /liliPartner with engineers to ensure new features ship with clear, testable acceptance criteria and coverage. /lilibIndependently explore features, identify edge cases, and define what needs to be tested /b — without waiting to be told. /li /ulpbr/pEnable Acceptance Test Driven Development (ATDD)pbr/pulliCollaborate with Product/Design/Engineering to translate requirements into btestable acceptance criteria /b and executable test scenarios. /liliEstablish patterns for: /lili“API-first” acceptance tests (service boundaries, auth, error handling, core workflows). /liliFrontend acceptance tests that validate user journeys end-to-end. /liliHelp the org adopt pragmatic “test-first” habits without slowing shipping velocity. /li /ulpbr/pShape how AI changes QApbr/pulliBring a bclear vision for how AI workflows will transform test automation /b — and actively drive that vision within our team. /liliIntegrate AI tooling into the testing process: smarter test generation, intelligent flakiness detection, AI-assisted debugging, and beyond. /liliStay ahead of the curve on emerging tools and approaches for testing AI-powered, non-deterministic systems (LLM outputs, chat interfaces, retrieval pipelines). /li /ulpbr/pMake CI a high-signal quality gatepbr/pulliIntegrate and optimize automated testing in bGitHub Actions /b (parallelization, retries strategy, reports). /liliEstablish a fast feedback loop: “quick suite” vs “deep regression”, PR gating, and predictable runtime. /liliImprove observability of quality signals: flaky rate, failure reasons, time-to-detect, and actionable reporting. /li /ulpbr/pOwn quality as an engineering practice (not a separate silo)pbr/pulliWork closely with backend/frontend/AI engineers to define coverage strategy per feature (risk-based). /liliHelp define acceptance criteria, edge cases, and “what good looks like”. /liliImprove documentation, runbooks, and the “how to test this” developer experience. /li /ulpbr/pNon‑negotiable requirementspbr/pullibStrong hands-on Playwright experience /b (TypeScript/JavaScript) in a real product environment. /lilibSolid software development skills /b — this is an engineering role, not a manual QA role. You write clean, maintainable code and are comfortable working in a codebase alongside product engineers. /liliProven ability to build bmaintainable, stable automated test suites /b (not just writing a few scripts). /lilibHigh independence and ownership /b: you proactively explore the product, identify what needs testing, and drive it to completion without needing hand-holding. /liliDemonstrable btest-first mindset /b: you push for clarity in acceptance criteria and design tests early. /lilibA vision for AI in QA /b — you understand how AI tools are reshaping test automation and have meaningful hands-on experience integrating them into your workflow. /liliSolid understanding of QA methodologies, SDLC, and pragmatic tradeoffs. /liliComfortable with bGit /b, code review, and CI/CD workflows. /liliStrong debugging skills and clear communication in English. /li /ulpbr/pImportant (nice-to-have, but not required)pbr/pulliExperience building/owning bAPI-level test strategies /b (REST/GraphQL) and test data management approaches. /liliExperience with test frameworks beyond Playwright (e.g., Cypress, Jest/Vitest). /liliFamiliarity with cloud environments and common tooling (Docker, AWS/GCP/Azure). /liliAccessibility testing awareness (WCAG) and web performance testing fundamentals. /liliExperience testing AI-powered features or non-deterministic systems (LLM outputs, chat interfaces). /liliStartup/scale-up experience: you can move fast without breaking trust in quality. /li /ulpbr/pHow we workpbr/pullibAsync-first /b and documentation-driven; few meetings, lots of ownership. /liliSmall team, big responsibility: you’ll shape how testing is done across the org. /liliWe optimize for bhigh signal /b over ceremony: pragmatic testing, fast iteration, and continuous improvement. /li /ulpbr/pCompensation benefitspbr/pulliCompetitive salary (based on location and seniority). /liliRemote-friendly within Europe; hubs in Vilnius/Barcelona/Amsterdam. /liliLearning development budget, home-office support, team meetups/offsites. /liliA role with meaningful product impact: you’ll directly improve release confidence for a platform used at scale. /li /ulpbr/pLocation schedulepbr/pullibFull-time role. /b /liliRemote is OK; bEU is a must-have. /b /liliWe’re especially happy if you’re around Amsterdam or open to occasional in-person meet-ups. /liliFlexible schedule and a “no strict 9–5” mentality, with real respect for work–life balance. /li /ulpbr/pCompensation benefitspbr/pullibCompetitive salary. /b /liliFlexible working arrangements, including remote work within Europe. /liliFocus on work–life balance, not clock-watching. /liliOpportunity to build cutting-edge AI technology and make a real impact in EdTech. /liliJoin team meet-ups globally (e.g. our offsites like Costa Brava). /li /ulpbr/pHiring processpbr/pullibIntro chat (15–20 min): /b quick conversation with our CTO or CPO to learn more about you and the role. /lilibTechnical deep dive (30–45 min): /b discussion about test automation strategy, Playwright experience, and how you'd approach QA challenges at LearnWise. /lilibPractical exercise or pairing session (45–60 min): /b focused on building Playwright tests, debugging flaky tests, or designing a test automation architecture. /lilibCulture/leadership chat (30 min): /b meet another founder or leader to ensure mutual fit. /lilibOffer. /b /li /ulpbr/p