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, Backend (Node.js)

Posted

Summary

Anthill is hiring a mid/senior backend engineer, on site in Copenhagen, to build Anthill Cloud — the shared platform layer behind its pharma communication products. The stack is AWS (Lambda, ECS, DynamoDB, RDS) with Node/TypeScript/NestJS, Terraform, and a heavy emphasis on agent-driven development.

Copenhagen, on site. Permanent, full time. Mid or senior.


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 into our backend chapter.


What you will actually work on


Anthill Cloud is the shared platform layer behind our products. It handles identity, tenancy, content and the services that belong across the suite rather than inside any one product. Most of the interesting backend work at Anthill over the next two years sits on that line: deciding what belongs to a product, what belongs to the platform, and how to move something from one to the other without breaking a client who is mid-campaign.


We run on AWS. Lambda, ECS, API Gateway, EventBridge, DynamoDB, RDS, S3 and CloudWatch, with Terraform as how infrastructure gets changed. The code is Node: TypeScript on NestJS for Anthill Cloud, and JavaScript in parts of the product backends.


Coding agents write a growing share of that code, which moves most of the engineering to the work around it: shaping the solution, running spikes before anyone commits to an approach, building the harness agents work inside, orchestrating the work, and judging what comes back. You still write the code yourself when that is the better way.


In your first year you will:

  • Shape solutions before they are built: service boundaries, contracts and data models, written down as decision records in the repo that people and agents build from.
  • Run spikes that answer a technical question with evidence before a mission commits to an approach, and throw the spike away once it has.
  • Build the harness our agents work inside: the specs, agent instructions, tests and checks that keep generated code inside the architecture, and tighten it when something gets through.
  • Orchestrate agent work on changes that span several services: split it so agents can do it well, and own how the pieces fit together.
  • Build and run services on Anthill Cloud, serverless or containerised depending on what the workload actually needs.
  • Turn product-level capability into shared services the rest of the suite can call, including the unglamorous part where you migrate the original caller.
  • Build integrations into the systems our clients already run, including Veeva, DAM platforms and client identity providers. Pharma clients do not adopt tools that ignore their existing stack.
  • Work on the data models behind content authoring, modular content and referencing. The domain has real structure to it and getting the model wrong is expensive.
  • Run what you build. You will have production access, you will see your own service misbehave, and you will fix it.


The levels


We are hiring at mid or senior level and will fit the role to the person we meet. The kind of work is the same at both. What changes is scope. A mid owns features and the design inside them, and works well inside service boundaries and agent setups that someone else defined. A senior owns decisions that outlast the mission they were made in, and other engineers and agents build on them. Tell us where you think you sit, and we will tell you if we see it differently. You do not need to tick every box below. Some of this is learned here.


What we are looking for

  • Backend development against cloud services, ideally AWS.
  • JavaScript, TypeScript and Node you can write well yourself, without an agent.
  • Hands-on work with databases, both SQL and NoSQL.
  • Infrastructure as code. We use Terraform.
  • CI/CD pipelines, and some appetite for the operational side of what you ship.
  • API design for consumers you do not control, and the discipline that comes with not being able to change them at will.
  • Solution design you have done yourself and lived with: service boundaries, contracts and data models, written clearly enough that an engineer or an agent can build from it, including the decisions you would now make differently.
  • Spikes and prototypes that answered a question rather than became the product, and the discipline to throw them away.
  • Experience with agent-driven development: daily work with coding agents such as Claude Code, building the context, instructions and checks they work inside, splitting work so they can do it well, reviewing what comes back to the standard you would hold a colleague to, and knowing when to stop and write it yourself.
  • Working English. Danish is not required.


Useful, not required:

  • NestJS and TypeORM, or another structured Node framework.
  • Event-driven architecture, and experience with the failure modes rather than the diagrams.
  • Python or another backend language alongside Node.
  • Experience in a regulated industry: GxP, validated systems, ISO 27001, or anything where an auditor eventually reads your change log.
  • Work on AI features in production, including retrieval and evaluation. We run on AWS Bedrock and have a dedicated AI chapter you would work alongside.
  • Agent tooling you have built yourself: MCP servers, agent instructions shared across a team, or evaluations of what agents produce.


How we work


Engineers belong to a chapter and work in missions. The chapter is your professional home and where your craft is developed.


Missions are time boxed, cross functional teams pointed at one outcome. When a round of missions closes, people rotate and a new set forms. The rotation is the point. Over a couple of years you work with most of the engineering team and across most of the product surface, instead of spending three years in one squad on one corner of the codebase.


Product decisions run through HIVE, our gate model. Nothing gets built because someone senior liked the idea. Initiatives pass through evidence, solution framing and a funding decision before engineering starts, and they are not closed until the outcome is validated rather than when the code ships. As an engineer this means you get told why something is being built, and you are expected to argue if the reasoning is thin.


What is agreed gets written down in the repo, as docs and decision records that people and coding agents both work from. A growing share of the engineering is in that writing and in the review, rather than in typing the code.


We work trunk based on Anthill Cloud and review each other's code, including the code our agents write. We expect the person who merges something to be able to explain how it runs, and we hold the line on security and access because our clients audit us and we hold their data.


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.


In the interview you use the tools you use at work, coding agents included. You will also write some code without one, review code an agent wrote and tell us what is wrong with it, and take a design problem from question to plan with us: how you would shape the service, what you would spike first, and how you would set agents up to build it.


Sebastian Søberg leads the backend chapter and would be your manager. He is also our Senior Solution Architect and the person you argue with about architecture, which we consider a feature. Questions about the role can go to him on LinkedIn.


You will help make the architectural decisions at the platform layer, not be handed the result of them.


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

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