QA Engineer

• Own the test process: test plans, test cases, release checklists, and the call on whether something is ready to ship.
• Build and maintain automated end-to-end and API tests, and run them in CI.
• Do exploratory testing on real workflows: ordering, cashiering, inventory, bookings.
• Test in both markets: German compliance and data-dense screens, Arabic right-to-left and mobile layouts.
• Test AI features with the AI engineer: conversation scenarios, edge cases, and regression sets for voice and text agents.
• Report bugs clearly, with steps, evidence and severity, and verify the fixes.
• Track quality over time, so the team knows if it is getting better or worse.

• Two or more years of QA on web applications, with both manual and automated testing.
• Hands-on test automation with a modern tool (for example Playwright or Cypress), and API testing.
• You can read code well enough to understand what changed and what might break.
• Experience testing in a CI pipeline.
• Precise bug reports that a developer can act on without asking.
• Clear written and spoken English, and the confidence to block a release when it is not ready.

• POS, ERP, hospitality or retail software.
• Testing AI or chatbot features.
• Arabic right-to-left testing, or German.
• Performance or accessibility testing.

• The first QA seat, with the test process yours to design.
• Real authority over releases, not a checkbox at the end.
• Products used by paying customers in Germany and MENA.
• Time and tools to automate properly, not just click through.

You would report to the CTO and co-founder and work closely with the AI engineer and the product designer. You are the last check before a customer sees the work, and the team treats that seriously.

Four steps, usually inside three weeks. An informal call about the worst bug you found and how you found it. Then a short paid exercise: test a small feature we give you, write the bug reports, and automate two of the tests. A decision within a week of the last conversation.