Quality Assurance Intern

About CloudAnzen

CloudAnzen builds continuous compliance and trust operations software for AI-native teams. Our customers use us to get audit-ready against frameworks like ISO 27001, SOC 2 and ISO 42001, to automate evidence collection, and to answer buyer security reviews without weeks of manual work.

That means our product's job is to be correct about correctness . When our platform says a control passed, an auditor relies on it. When it stores a piece of evidence, that record has to survive and stay attributable. When one customer's data sits beside another's, the boundary has to hold every time. A bug in most SaaS products is an annoyance; a bug here can put a customer's certification at risk.

QA is not a box-ticking function at CloudAnzen. It is how we earn the trust we sell.

The role

We are hiring a QA Intern to help us test the platform the way an auditor would read it: carefully, sceptically, and with evidence for every claim. You will write and run test cases against real product areas — evidence integrity, audit workflows, roles and permissions, multi-tenant isolation — and report what you find clearly enough that an engineer can fix it without asking you a follow-up question.

This is a hands-on role on a small team. You will not be handed a script to click through. You will be given a product area, the risks that matter in it, and the support to figure out how to break it.

What you'll do

• Write test cases from requirements. Take a feature or a user story and turn it into a set of cases with clear preconditions, steps, test data and expected results — including the negative cases most people forget.
• Test authorization and tenant boundaries. Confirm that a viewer cannot delete, that a contributor cannot approve their own work, and that one customer's data never appears in another customer's response. These are our highest-severity risks.
• Do exploratory testing. Spend focused sessions trying to break a new feature in ways nobody specified, then write up what you found.
• Report defects well. A good report from you has reproduction steps that work on the first try, the actual versus expected result, the environment, and evidence — a screenshot, a response body, a log line.
• Verify fixes and watch for regressions. Re-test what engineering closes, and flag when a fix in one place breaks something else.
• Help grow automated coverage. Work with engineers on API and end-to-end tests (our stack uses Playwright for browser flows and Jest for the backend), starting with reading and extending existing tests before writing new ones.
• Test API behaviour directly. Call endpoints yourself with a tool like Postman or curl, rather than only testing through the UI — a lot of the interesting bugs are not visible on screen.
• Sanity-check the obvious things too. Our marketing site, onboarding and academy flows need working links, correct copy and sensible behaviour on a phone.

What we're looking for

We care more about how you think than what you have already used.

• Currently studying or recently graduated in computer science, information systems, or a related field — or able to show equivalent self-taught ability.
• Precise written English. Most of your output is text other people act on. If your bug report is ambiguous, it costs an engineer an hour.
• A sceptical streak. You are the person who asks "but what happens if I submit this twice?"
• Comfortable reading a requirement and spotting what it fails to specify.
• Basic understanding of how web applications work: client, API, database, authentication, HTTP status codes.
• Willing to get hands-on in a terminal — running the app locally, reading a log, calling an endpoint.
• Organised enough to keep a test catalog tidy and honest about what has and has not been verified.

You do not need prior QA job experience, a compliance background, or knowledge of ISO 27001. We will teach the domain.

Nice to have

Any one of these will stand out. None is required.

• Some JavaScript or TypeScript — enough to read a test file and change it.
• Exposure to Playwright, Cypress, Selenium, Jest, Vitest or pytest.
• Experience with Postman, Insomnia or curl against a real API.
• SQL basics, enough to check that what the UI claims actually landed in the database.
• Git and GitHub: branches, pull requests, reading a diff.
• A personal project, CTF, bug bounty report or open-source issue you can point to.
• Curiosity about security or compliance — you have read about SOC 2, ISO 27001 or the EU AI Act for fun.

How to apply :

How To Apply :

Please fill this form and send your CV to [email protected]

https://forms.gle/LmLHnzyccpgFW5FN8