A complete application in a minute
Tailored resume and cover letter, ready to send.
Anthill in Copenhagen is hiring a software engineer in test (SDET) at mid level to own the automated evidence that a release is safe on the Aprimo and Veeva Vault connectors. You will build and maintain the Playwright + TypeScript framework used across teams.
The role offers a Danish permanent contract with a hybrid on-site presence: five days in the Copenhagen office and two work-from-home days per month. English is the daily language, enabling collaboration across engineers, product and QA to
Copenhagen, on site. Permanent, full time. Mid level. Reporting to the Engineering Manager, Platform & Quality.
Pharma communication is slow for a good reason. Every claim needs a reference, every asset needs approval, and every market has its own rules. We think the software that wins in this industry treats those rules as part of the product rather than something to work around, and that is what we build.
Anthill builds the software pharmaceutical companies use to create, approve and run their digital communication. At some of the world's largest pharma companies, commercial and medical teams rely on our products to produce and distribute regulated content. We're around 70 people, headquartered in Copenhagen, with four products: Activator, Arcane, Amplify and Anthill Cloud. Our products are already delivering GenAI-powered capabilities to Enterprise customers around the world.
We're growing fast, and it's a good time to join. In our Copenhagen office, engineers, designers, product people and strategists all sit in the same room. We're 15+ nationalities, so English is the official and everyday language in the office and in the codebase.
We are hiring a software engineer in test (SDET) into our Platform & Quality team, at mid level.
Our users are medical and marketing teams inside large pharmaceutical companies, working under regulatory constraints. You own the automated evidence that a release is safe on both of our DAM connectors, Aprimo and Veeva Vault: the framework, the suites that run on it and the signal they give. A red test should always mean something, and a green run should be enough to trust.
You build and maintain the test automation framework in Playwright, with TypeScript. Scenarios are written in Gherkin, plain Given, When and Then text, and you turn them into tests that run: step definitions, fixtures, test data and the environment setup behind them, on both connectors.
You work with coding agents every day. You use them to write and maintain tests, give them the context and conventions they need, and read what they produce with the same suspicion you bring to any test that passes too easily.
In your first year you will:
We work in two-week iterations, and testing runs inside them rather than as a phase at the end. We follow the test pyramid, unit then API then end to end then manual, and automate only what matters to the business.
Releases move through four environments: DEV, QA, STG and PROD, each with its own quality bar. The release decision rests on QA's sign-off, and that sign-off needs your suite to have run on both connectors with every failure traced to a cause: a product defect, a broken test or an environment problem.
You treat test code as production code, and you would rather delete a test than keep one nobody trusts.
What we expect:
A plus if you have already done it, not required:
Useful, not required:
Alex Berliner leads Platform & Quality and would be your manager. Questions about the role can go to him on LinkedIn.