Two hours as the senior QA engineer on a clinic booking app before a release: your own live copy with real bugs in it, a PRD, a payment provider's docs and a developer's notes that don't all agree. Plan by risk, write test cases, report bugs a developer can fix from your report alone, test flows out of order and the integration against its docs, automate tests in a private GitHub repo that we run against broken builds, triage a release, and sign off (or not) a hotfix under pressure.
What to test first, on which devices and data, and what you will not test today, from what changed and what patients report.
Cases with real boundaries and data. Bugs reported so a developer can fix them from the report alone, with screenshots or requests as evidence.
The PRD sets an order and the payment provider has its own rules. Test what must hold whatever order things happen in, and map the PRD, the provider's docs and the developer's notes against what the app does.
Tests in your own private GitHub repository, in any framework. We run them against the correct app and against broken builds, one bug at a time.
Answer developers, product and support as messages arrive, triage the release, and decide on a hotfix that needs sign-off fast.
Walk us through a test suite or QA work of yours, backed with evidence.
Everyone applying for this role is scored against these same criteria. Where possible, automated checks test whether your work really holds up; people review your reasoning.
You test what could hurt patients, money and data first, from what changed and what people report.
You test against the PRD and the provider's docs, out of order as well as in order, and you notice when documents disagree.
Exact steps and data, expected against the spec, actual with evidence, and severity that matches impact.
A suite that passes on a correct app, fails on broken ones, and does not flake.
You settle open questions with the right people or decide and record them, instead of waiting on someone.
You decide on evidence, not on pressure, and you tell the people who need to know.
Code, CI runs and bug reports you filed count more than titles. "Not yet" is a fine, honest answer.
Use the personal link in your email from careers@automaark.com. No account or password needed.
Add your own accounts, accounts you've worked on and your portfolio, with a screenshot of each. Not timed.
120 minutes in your browser, in one sitting. Everything saves as you type.
Or let the clock run out. We review what you saved.
Yes. Before you start, you connect your GitHub account and we create a private repository for your automated tests. It opens to you when you press Start and closes when your time ends. We only learn your username; we cannot see your other repositories.
Any: Playwright, Cypress, Selenium, WebdriverIO, Pytest, Postman/Newman, k6, or a mix. The repository has two scripts you fill in (setup.sh and run-tests.sh); we run those.
We run your suite against the correct app (it should pass, every time) and against broken versions of it, one bug at a time (it should fail). Tests that fail on the correct app count against you, so reliable beats long.
No. Like real work, some facts live with people and in documents that don't all agree. You can question the product owner, the lead developer and patient support with a small budget of questions, and open a limited number of views in a data room. We read every question.
Yes, and we expect you to. A bug report you did not reproduce, or a test that does not run, scores low.
Yes. Labs runs on automaark.com, our own domain, and invitations come from careers@automaark.com. We will never ask for a password, payment or ID documents. If in doubt, email careers@automaark.com.
Yes, and we expect you to. You own everything you submit, so check what AI gives you, and tell us where it helped and where it was wrong. No help from another person. The full rules are on our AI-use page (labs.automaark.com/ai-use).
Only when you press Start. The deadline in your email is the last moment you can start. Pick any time before then that suits you; once you start, you finish in one sitting.
If our platform fails during your attempt, it's on us. Reply to your invite email and we'll give you a fresh attempt.
Your work is scored against the same written criteria as everyone else applying for that role. Shortlisted candidates are invited to a 30-minute call about what they did.
We store your name, email, the links and screenshots you give us and your assessment work, only for this hiring process. Your work stays private, is never published, and is deleted within 12 months.
