Quality Assurance Engineer, Papernest

• The context doesn't require heavy mobile automation infrastructure today. What it requires is someone who understands mobile deeply, can design the right test approach for a product being built from scratch, and is ready to scale into automation as the apps mature. You'll work within Agile delivery with short release cycles (bi-weekly sprints)
• Minimum 2 years of hands-on mobile testing experience on both iOS and Android (automation + real devices + emulators/simulators)
• Proficiency with at least one mobile automation framework (Detox, Maestro, XCUITest, Espresso, or similar). Experience with Flutter/Dart testing is a strong bonus
• Good scripting skills in Python + TypeScript or JavaScript
• REST API testing experience (Postman or similar)
• Solid grasp of test types (functional, regression, smoke, exploratory, performance) and test case design techniques
• Experience integrating tests into CI/CD pipelines (GitHub Actions preferred)
• Work style: You take ownership of outcomes, not just tasks. You communicate directly, prefer building to blocking, and move forward with pragmatism rather than waiting for perfect information. You're comfortable working in a distributed team with async communication and written documentation
• Languages: Good level of English, spoken and written. French and/or Spanish is a bonus
• You understand that automation is a tool, not the goal — and you know when exploratory testing will find what scripted tests won't
• Ladies, we strongly encourage you to apply! Even if you feel that you do not meet all the criteria mentioned in this offer, please note that they are only indicative. Your application will be considered with great interest. Parity and diversity are an asset for our teams!

Desirable

• You'll be joining the QA team as our first dedicated mobile tester, at a pivotal moment: Papernest is building new mobile apps from scratch — currently using Flutter/Dart, though the stack may evolve
• The apps will bring Papernest's contract management platform to mobile, helping millions of users switch energy providers, manage telecom contracts, and handle insurance from their phone
• You'll own mobile quality from the ground up — designing the test strategy for a product that doesn't exist yet, and growing into mobile automation as the apps mature. You'll work in a continuous deployment culture where teams ship autonomously (2,000+ releases/year), and quality gates are a core part of that engine
• You won't work in isolation. You'll join a QA team of 8 engineers distributed across Paris and Barcelona. We work in pairs that combine automation depth with testing strategy, and you'll have a dedicated pair partner from day one
• Together, you'll challenge acceptance criteria, shape what gets tested and how, and help developers take ownership of quality. Our approach to AI is pragmatic: AI-augmented engineers, not AI-replaced engineers — and we want you to bring that mindset to testing
• The context doesn't require heavy mobile automation infrastructure today. What it requires is someone who understands mobile deeply, can design the right test approach for a product being built from scratch, and is ready to scale into automation as the apps mature. You'll work within Agile delivery with short release cycles (bi-weekly sprints)
• Design and own the mobile test strategy for your squad, covering the full spectrum of mobile-specific risks — from network conditions and device fragmentation to gestures, deep links, and app lifecycle edge cases (iOS and Android, real devices + emulators/simulators)
• Integrate multi-language and accessibility constraints (RGAA) into your testing approach
• Validate mobile-to-backend communication through REST API testing — ensuring the contract between app and services holds under edge cases
• Collaborate with your QA partner to design coverage strategies that balance manual testing, exploratory testing, automation, and deliberate risk acceptance
• Own quality outcomes for your squad — from challenging acceptance criteria in refinement to deciding what risk the team can accept and defending that decision
• Contribute to web e2e tests using Playwright (with Currents for test orchestration) across your squad's critical user journeys
• Explore and adopt AI-assisted testing approaches — test generation, intelligent test selection, coverage analysis — as part of the team's quality toolbox
• Build deep product domain knowledge for your squad(s) and document it so another engineer could pick up your coverage within a week
• What success looks like in the first semester:
• By month 1: A complete exploratory coverage map for the Flutter app's critical mobile flows is delivered, with a documented test strategy distinguishing what to test manually, what to automate, and what risk to accept
• By month 3: You independently own mobile quality for one product squad — attending refinement, reviewing ACs, producing clear bug reports, and co-owning sprint goals with your pair partner
• By month 6: A first automated mobile test suite is running in CI for at least one critical user journey, integrated into the team's GitHub Actions pipelines. The mobile testing practice is documented and transferable — another QA engineer could pick up your coverage within a week using your documentation, automation, and coverage maps
• Technical environment:
• Mobile: Flutter / Dart (new apps, built from scratch), but this can evolve
• Web automation: Playwright + Currents for test orchestration
• CI/CD: GitHub Actions (continuous deployment, 2,000+ releases/year)
• API testing: REST (Postman or similar)
• Observability: Sentry (errors), OpenSearch (logs), AWS
• Environments: Ephemeral per-branch environments for isolated testing
• Project / knowledge management: Jira, Notion
• Languages: Python, TypeScript

• Video interview with Wolfgang from the Talent team (30 min)
• Interview with Claudio, QA Manager and your future direct manager (45 min)
• Live technical test (45 min) — with the use of AI tools encouraged
• Final conversation with Raphaël, CTO (45 min) — focused on culture, ownership mindset, and long-term ambition (this is not a second technical round)