Skip to content
Search jobs inside your AI agent. Claude, ChatGPT, Claude Code, Codex, Gemini, Cursor and Grok
Connect

Anthill

NewBe an early applicant

Software Engineer, Test Automation (Playwright)

Posted Updated

Summary

Mid-level software engineer in test (SDET) on Anthill's Platform & Quality team, on-site in Copenhagen. They own the Playwright/TypeScript test automation framework with Gherkin scenarios, API tests, CI regression runs, and Allure/Jira-Xray reporting for a pharma content platform, using coding agents daily across two DAM connectors (Aprimo, Veeva Vault).

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.


Why the role exists

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.


What you will actually work on

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 decide with the QA engineers and developers which layer a check belongs in. Where the browser adds nothing, the check moves down to the API. The end to end suite stays small and fast enough that people run it rather than wait for it. Results land in Allure, and test cases live in Jira with Xray.


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:

  • Own the Playwright framework end to end: structure, fixtures, test data, reporting and the conventions others follow when they add tests.
  • Set up how coding agents work on the test suite: the instructions, conventions and review steps that keep agent-written tests trustworthy.
  • Turn ranked scenarios into automated tests on both connectors, and retire tests that no longer earn their run time.
  • Build API tests wherever a check does not need the browser.
  • Run the regression suite in CI against every release candidate and keep it trusted: every failure traced to a cause, flaky tests fixed or removed rather than retried.
  • Review test code written by developers, and help them put each test at the layer that fits.
  • Agree with the QA engineers what is automated and what stays manual.


How we test and release

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.


What we are looking for

You treat test code as production code, and you would rather delete a test than keep one nobody trusts.


What we expect:

  • End to end tests you have written and kept running in CI for a product that shipped to customers, in any framework. Recorded scripts do not count.
  • TypeScript or JavaScript written to the same standard as product code: reviewed, readable and in Git.
  • An agentic way of working: you use coding agents such as Claude Code or Copilot daily to write and maintain tests, and you catch the agent-written test that runs green but checks nothing.
  • Comfort binding scenarios to step definitions.
  • API testing: you can test an endpoint directly and know when that beats a browser test.
  • Judgement on which layer a check belongs in, and the willingness to say when an end to end test is the wrong tool.
  • Test data and environment handling across more than one environment.
  • The habit of finding out why a test failed rather than running it again.
  • The ability to hold a position with a developer, and to change it when the argument against you is better.
  • Working English. Danish is not required.


A plus if you have already done it, not required:

  • You have designed a test framework that other engineers contribute to, and set the conventions they follow.
  • You have shaped how agents work on a test codebase, with instructions and conventions that other engineers and their agents follow.
  • You have decided what is not worth automating, and defended it to the people who asked for it.
  • You have raised the testing standard of the developers around you through review and pairing, not by writing their tests for them.


Useful, not required:

  • Manual and exploratory testing. Knowing what a script misses makes you better at writing one.
  • CI configuration in Bitbucket Pipelines or AWS CodePipeline.
  • Experience with regulated customers.


What we offer

  • A permanent Danish employment contract, pension and health insurance.
  • A salary set from our salary bands, the same way for everyone at the same level. Where you land in the range depends on your experience and skills, and on pay equity with colleagues at that level.
  • Five days a week in our Copenhagen office, with two work from home days a month as the default. We are on site because most of what engineers learn from each other happens in conversation at someone's desk.
  • Colleagues who have shipped software into pharma and know how demanding that audience is.
  • Clients whose problems are specific and constrained, which is more interesting than it sounds.
  • Occasional office dogs, who expect to be petted.


Alex Berliner leads Platform & Quality and would be your manager. Questions about the role can go to him on LinkedIn.


Applying

If you can recognise yourself in just some of these requirements or skills and simply want to learn the rest, we would love to receive your application. We offer an open environment with freedom under responsibility, where you have the opportunity to grow professionally.


Apply through LinkedIn, or get in touch directly if you would rather have a conversation before a formal application. We read everything ourselves.


Your CV does not need a photo, your age or anything else that is not about your work.


If there is a repository, a component library, a test plan, a bug report you are proud of, a design document or a postmortem that tells us more than a cover letter would, send that too.


We review applications as they arrive. Where the role has a closing date, it is stated at the top of the ad. Otherwise the role stays open until we find the right person.


We only work with recruitment and search firms under a written agreement, and we do not pay fees for candidates we did not ask for. Please do not send CVs to the hiring manager.

Skills

Apply

See also

QA jobs by country — openings, pay and top skills →