Testing
Testing every release before it reaches a client.
You are the last check before work reaches a client, and the job is to be systematic about it: the states nobody tried, the devices nobody owns, the second press on the same button. Most of the work happens before there is anything to test, in deciding what a release has to be checked against. You write bugs so that they can be fixed — steps, expected, actual — rather than reports somebody has to investigate before they can start. Part of the role is holding a release when something is wrong, which is easier to do when the reasoning is already written down.
What the week contains
- A test plan per release
Written from what actually changed, so it covers the new risk instead of repeating the last release’s checks.
- Coverage across real devices and browsers
On the phones, tablets and browsers clients genuinely use, including the older ones that are still in the numbers.
- Regression suites
Automated checks for the things that have broken before, so the same fault does not ship a second time.
- Bugs written so they can be fixed
Steps, expected result, actual result and the environment. A report that has to be investigated before it can be read costs the fix twice.
How applying goes
- 01Send your workA repository, a portfolio, or whatever you consider your best work. No cover letter, and no form that asks you to retype a CV you have already attached. If the best thing you have made is not public, describe what it did and what your part in it was.
- 02A reply from a personEither way, and from somebody who actually opened what you sent. Not an automated acknowledgement, and not silence — an application that goes no further still gets an answer.
- 03A conversation with your discipline leadWith whoever leads the discipline you applied to, not with a recruiter relaying answers. It is a conversation about work you have done rather than a quiz, and you are expected to ask as much as you answer.
The other disciplines
Get in touch
Every one of these reaches us directly, and is answered by a person.
A new project, a quote, or a question about one that is running.
- Reaches us at
- +355 69 752 2209
- Carries
- Messages