QA Engineer — manual and API testing in an AI-native product team (long-term)

Great products need people who ask great questions. We are looking for a QA engineer who does more than find bugs: someone who understands how a business process is supposed to work, notices where it quietly doesn't, and helps the team ship releases it can trust.

alpview it service is a small software company based in Germany, building long-term products for established European companies, mainly in the HR and staffing domain: a modern SaaS platform built on years of proven business logic, with Laravel backends, Angular web portals and Flutter mobile apps. Claude Code is how we build, every day — and that makes good QA more important, not less.

WHAT YOU GET

- A long-term contract that works like employment: paid vacation, paid public holidays, a steady full-time workload and reliable monthly payment. No gig hopping, no "we'll see after the sprint"
- Claude Code as your daily tool, with the licence paid by us — for test ideas, test data, API checks and, if you like, automation. In a team that actually uses it well
- Quality from the start, not at the end: you join a product at an early stage and help decide how quality is approached — you are in the room when requirements are written, not only when builds are handed over
- Your voice counts: you work directly with the developers and the Product Owner. Your questions change requirements, and "I don't think we should release this" is taken seriously
- Meaningful challenges: real business processes, complex workflows, interconnected modules, web and mobile — not clicking through the same login form every day
- Products built to last for years, with continuous development and more work coming
- Full remote, flexible hours, async-friendly, very few meetings
- A fast, respectful hiring process — no unpaid test assignment (details below)

WHAT YOU WILL WORK ON

You are part of a cross-functional team with developers and the Product Owner, working on several connected products: web portals, mobile apps and the APIs behind them.

- Test new features and complex business workflows end to end — across web, mobile and API
- Explore APIs, integrations and data to find the problems a happy-path click-through never shows
- Challenge requirements early: ask questions, find edge cases and contradictions before they become code
- Write practical test documentation that the team actually reads, and clear bug reports a developer can act on without a call
- Help the team deliver reliable releases — and grow automated checks where they pay off

This suits people who like to understand why a system behaves the way it does, are not afraid to ask "What if?", and are comfortable being the one who says something does not work yet.

We keep client specifics out of a public posting. You get the full picture, including a look at the real products, in the first conversation.

HOW QA WORKS WITH CLAUDE CODE HERE

Our developers build with Claude Code, and so will you. It helps you generate test ideas and edge cases, prepare test data, explore an API quickly or write a first automated check. Experience with it is a plus, not a requirement — we will help you get good at it.

One rule above all: you are responsible for your verdict. When you sign off a story, that sign-off is yours, no matter which tool helped you get there. You check what an AI suggests instead of copying it, you know which cases it missed, and you can explain why you believe a feature works — including the failure paths.

THE DEAL, IN BOTH DIRECTIONS

Formally this is a long-term freelance contract, as with all our team members in Ukraine. In practice we work together like a good employment: paid vacation, paid public holidays, a steady workload, and a cooperation meant to last for years. You are a member of the team, not an external resource.

We ask for the same commitment back:

- This is your main engagement, not one of several projects you juggle. If something else starts competing for your time, tell us first
- Transparent working hours: you track your time in a way we can follow, and you say early when you are behind or unavailable. That is what makes paid vacation and flexible hours possible
- Ownership when it counts: occasionally, when a release is in flight, that can mean an evening. It is the exception, and those hours come back to you as time off

WHAT YOU BRING

- 3+ years of hands-on QA experience, ideally with web and mobile applications
- Solid understanding of testing principles, test design and bug tracking — you choose test cases deliberately, not by habit
- Real experience with REST API testing: requests, status codes, payloads, authentication, and checking that the data behind the response is actually right
- Comfort with complex business workflows, roles and permissions, and data that moves between systems
- An analytical mindset and proactive communication: you ask early, write clearly, and follow a bug until it is really fixed
- Careful handling of personal data (GDPR is a real constraint here, not a footnote)
- English B2+

Nice to have: test automation (web, mobile or API) and CI/CD pipelines; practical experience with Claude or other AI tools in QA work; SQL for checking data; German; HR, staffing or ERP domain experience.

REQUIRED SKILLS EXPERIENCE

- QA / Manual testing — 3 years
- REST API testing — 2 years
- Web and mobile application testing — 2 years

Required languages: English — B2 (Upper Intermediate)

HOW TO APPLY

Answer three short questions with your application — a few sentences each is plenty, concrete beats polished. Please also add your earliest possible start date. We read every answer properly and reply to everyone who answers them.

1. Tell us about a bug you are proud of finding — one that no test case or requirement pointed to. How did you find it, and what happened next?

2. How do you use AI tools in your QA work today? Describe one case where you did not trust the result, and what you checked instead. (If you don't use them yet, tell us how you would start.)

3. A short scenario, no single right answer: an employee enters their working hours in a mobile app, a manager approves them in a web portal, and the approved hours are later exported for payroll. A new feature lets the employee correct hours after submitting. List the first test ideas you would check, and say which one you would check first and why.

What happens next: a short call with the people who actually decide, then a practical conversation where we look at a real feature together and talk about how you test. No unpaid test assignment, and a quick decision — we know good people have options.