DE
Maximilian Schluer
  • Software Quality Assurance
  • Test Automation
  • QA Workshops, urgent debugging

Your release needs to ship. Your QA shouldn't stand in the way.

I stabilize your software QA, find critical weak spots and build the foundation for predictable releases — with a QA audit, test strategy and sensible test automation.

Browse services

Software QA without guesswork

  • Your current software QA
  • Your test strategy
  • Potential for E2E, integration and regression tests
  • Opportunities for test automation
  • User Acceptance Tests

Afterwards you know where things are stuck — and what to do next.

From “hope it works” to “this release can ship”

Your path to software without critical bugs

  1. QA Check

    We look at your current QA and find the biggest risks for your next releases.

  2. A clear action plan

    You don't get a 50-page theory deck. You get a clear priority list: What needs to happen now? What can wait? Where is automation worth it?

  3. Implementation

    If you want support, I implement the measures with your team — from test strategy to test automation.

  4. Stable releases

    Fewer bugs in production. Less firefighting. More confidence when you ship.

Senior QA consultant. No detours.

10+ years in software QA

Senior QA consultant with practice from startups to global enterprises.

Software startups

Specialized in speed, release pressure and scarce resources.

For CTOs and tech leads

You work with me directly. No middleman, no handovers.

Ready to start fast

No weeks of onboarding before anything happens.

Sustainable test automation

Automation that lasts — not short-lived cosmetics.

If your release is shaky, you don’t need theory.

You need someone who gets in.

I ramp up quickly in your software, find the risks and help get them out of the way — before your users trip over them.

Senior QA consulting, direct and pragmatic.

No long alignment loops. No overhead. No PowerPoint battle. I know startups: little time, high pressure, fast releases.

I find bugs before your user does.

I have been testing software for over 10 years — from startups to global enterprises.

I know complex processes from finance and automotive as well as the pace of software startups. That’s why I know: not every QA problem needs a huge project.

Sometimes a ticket has to be solved today. Sometimes a team needs support for a few months. And sometimes it is time to build QA so that certain problems never come back.

What do you need right now?

Urgent support

A ticket is on fire? We fix the problem before it becomes a release problem.

Goal: take stress out of the team immediately

Project support

You need extra QA capacity for a defined period? I work directly with your team.

Goal: finish the initiative cleanly and on time

Long-term QA setup

Test strategy, test automation and processes that make your QA lastingly better.

Goal: stop the same problems from coming back

Get in touch. The free QA Check is the first step.

You build. I find bugs.

Track Record

A selection of completed projects:

Assignment

We're switching to the new SAP release. Please make sure test coverage is established.

Procedure

I developed a test concept for the project that defines a clear hierarchy, processes and responsibilities. As a result, I made myself obsolete: everything that landed on my desk was handled through the process.

Result

The release switch – a project with hundreds of people involved – was not only completed on time. No major crises occurred along the way.

Assignment

Please introduce testing to our IT department.

Procedure

Working closely together with the teams, I introduced different procedures on how to integrate tests into their way of working.

Result

As everybody could proceed like how it fits best for them, processes were accepted easily which reduced the bugs in production to almost 0.

Assignment

Help us with our Automation.

Procedure

Together with the customers team, we put the code base to a healthy state. For this, I introduced new standards, refactored plain JavaScript to TypeScript and parallelized the tests.

Result

Not only the tests provided more and more helpful data for all stakeholders. The Build Time was cut in half which sustainably increased acceptance for the tests and the development of new features.

Assignment

Help us with Testing & Compliance

Procedure

Looking at Process & Requirements as whole I found duplicates in documentation and way of working. As well I connected open ends and made the process sleek. Now, every task has to be done only once.

Result

By reducing duplicates, with every quarterly release the client saves a lot of time. Also, bugs are found earlier. The customers Quality Management department is happy as well: Complaints have dropped to almost 0.

Ready for releases without a knot in your stomach?

Additional Topics