Two hours on a real partner portal used in four currencies and time zones: fix the bugs partners reported (and the one they did not), build a money flow from an incomplete design, make a slow page fast with evidence, and plan what comes next. Reviewed like a pull request at a top product team.
Four support tickets about wrong data, wrong money and an inaccessible filter. Find the real causes, prove them with tests.
A payout request flow from a design that is incomplete on purpose. The rules live with our designer, who you can question in Labs.
A partner says a page is slow. Measure, fix the real causes without hiding data, and show the numbers.
A one-page architecture for the mobile app and white-label portal coming next quarter, specific to this codebase.
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 find why a bug happens, fix it there, and prove it with a test.
Money in every currency, every partner's own time zone, every state the design forgot, keyboard and mobile included.
You ask the right person the right question, flag what does not add up, and never guess with partners' money.
You measure before and after, and your numbers would survive a reviewer re-running them.
Your plan fits this codebase and the next year of the product, not a blog post.
You steer AI, notice when it is generic or wrong, and own every line.
Use the personal link in your email from careers@automaark.com.
We create a private repository for you. We only see that repository.
Make sure your setup works. The clock hasn't started.
120 minutes for the tasks.
Or let the clock run out. We grade the last commit you pushed.
React 19, TypeScript and Vite, with React Router. Strong engineers from Vue, Angular or Svelte do well: we score judgement, not trivia.
Probably not in two hours, and that is deliberate. Prioritise, ship working parts, and say in your pull request what you would do next.
No. Like real work, some answers live with a person. You can question our product designer in Labs, with a small budget of questions, and we read every one.
We build your pull request and test it in a real browser against our own copy of the API, then senior reviewers read your code and notes. There is a short call after.
To create a private repository for you to work in and open a pull request on. We only see your public profile and that one repository.
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, GitHub username and your assessment work, only for this hiring process. Your work stays private, is never published, and is deleted within 12 months.
