How to apply for (Senior) QA Engineer - AI-Driven Testing (m/f/d)

About 1KOMMA5°

1KOMMA5° builds a virtual power plant that controls solar, batteries, heat pumps, and e-mobility as one integrated system connected to the electricity market. The company aims to move 1.5 million households to renewable energy by 2030 and has over 3,000 people across more than 80 locations. Working here means your QA work directly supports real-time, automated energy management.

About the role

You will own the quality strategy for 1KOMMA5°'s Flutter apps within the Mobile App Platform team. The role focuses on reinventing QA with AI-driven testing: autonomous exploration, smarter test orchestration, self-directed QA workflows, and systems that detect product risks before release. You will build on an existing AI test-generation setup and push it much further.

A typical day

You might review AI-generated test results, refine autonomous exploration rules for the Flutter apps, and investigate a product risk flagged by the QA system. You would also coordinate with the Mobile App Platform team on release readiness and improve test orchestration for the virtual power plant's mobile interface.

Who 1KOMMA5° is looking for

• Has hands-on experience testing Flutter mobile apps, including test automation frameworks and CI integration.
• Has applied AI or machine learning to QA workflows, such as test generation, autonomous exploration, or risk detection.
• Can define and own a quality strategy for a mobile app platform, not just execute test cases.
• Is comfortable working remotely and collaborating with a distributed product and tech team.

Tips for this application

• In your CV or cover letter, name specific AI-driven QA techniques you have used, such as autonomous test exploration or self-directed test orchestration.
• Show Flutter testing experience with concrete examples: which frameworks, how you integrated tests into CI, and what results you achieved.
• Explain how you would move beyond AI test generation to autonomous exploration and risk detection, since the job description says the team wants to go much further.
• Mention any experience with energy, IoT, or virtual power plant systems, even if indirect, because the product controls real-time energy assets.
• Apply through the company's Product & Tech team link and tailor your materials to the Mobile App Platform team, not a generic QA role.

What to cover in your cover letter

State your Flutter testing experience and the specific tools you used. Describe an AI-driven QA system you built or improved, including what it detected and how it changed release quality. Explain how you would own a quality strategy for a mobile app platform. Connect your work to 1KOMMA5°'s goal of controlling energy assets in real time through Heartbeat AI.

Research before applying

• Read how 1KOMMA5°'s Heartbeat AI connects solar, batteries, heat pumps, and e-mobility to the electricity market in real time.
• Look up the company's Product & Tech team page to understand how mobile apps fit into the virtual power plant.
• Check 1KOMMA5°'s 2030 goal of 1.5 million households and what that scale means for mobile app quality.
• Find any public information on 1KOMMA5°'s current QA stack or Flutter usage to speak concretely in your application.

Likely interview topics

Based on the job description, expect questions about:

• How you would design an AI-driven QA system that detects product risks before release for a Flutter app.
• Your experience with autonomous exploration and self-directed QA workflows, and how you measured their effectiveness.
• How you integrate AI test generation into CI/CD for mobile apps and handle flaky or non-deterministic tests.
• How you would test a virtual power plant's mobile app that connects to real-time electricity market data.
• How you prioritize QA risks when the product controls solar, batteries, heat pumps, and e-mobility as one system.

Common mistakes to avoid

• Applying with generic QA experience and no Flutter or mobile app testing examples.
• Claiming AI-driven QA experience without naming specific techniques, tools, or outcomes.
• Ignoring the energy domain and treating this as a standard mobile QA role, since the product controls real-time energy assets.