Backend Engineer

Skatteguiden; København; On-site; DKK 900,000 - 1,300,000; Full time

Job summary

Skatteguiden, based in Copenhagen, seeks a Backend Engineer to build and ship features for a cross-functional product team with a commercial mission. You’ll influence design decisions, work closely with leadership, and contribute to the plan from problem shaping to production.

You’ll excel if you have strong backend production experience in Java/Kotlin/Go, understand distributed systems, and are curious about AI tools like Claude.

Qualifications

• Backend engineer with focus on reliable, high-quality code.
• Experience building and running services used by real users.
• Proficiency in Java, Kotlin, Go or similar; Spring Boot stack preferred.

Responsibilities

• Ship end-to-end features as part of a product team.
• Help redesign multi-broker architecture for tax support.
• Own observability and critical business flows.

Skills

Java

Kotlin

Go

Distributed systems

Product mindset

Reliability

AI tools Claude

Tools

RabbitMQ

MySQL

Kubernetes

Argo

GitHub Actions

Grafana

Loki

Job description

Tech-first. Ego-free. User-obsessed.

Over one million Danes use Skatteguiden to understand and optimise their taxes. We automate tax tracking, surface deductions people didn't know they had, and give users the insights they need to make better financial decisions — all directly connected to the Danish tax authority.

We're an independent company of around 50 people based in Copenhagen, with a 4.7-star App Store rating and a simple mission: make financial insight accessible to everyone, not just those who can afford an accountant.

About The Role

Path to Plus is the engine that converts users into paying members and keeps them there. As a Backend Engineer on this team, you'll be building and shipping features as part of a cross-functional product team with a direct commercial mission — not executing on a spec handed down to you, but helping shape what gets built and why. This is a product engineering role. The team owns the problem, not just the delivery. That means getting involved before requirements are written, connecting your technical work to user and business outcomes, and iterating based on real feedback. You'll work closely with engineering leadership — not as a follower, but as a collaborator who contributes to the plan. If you've worked that way before — or you're actively looking to grow into it — this is the right environment.

What you'll do

• End-to-end features. Ship features as part of the team's product cycle, from problem shaping to production.
• Multi-broker architecture. Stock tax support is live. The next challenge is redesigning the current model to support multiple brokers — a real architectural problem you'll be part of solving.
• Observability. You'll help us own the health of critical business flows and catch issues before users do.
• Azure migration. We're migrating our systems in the coming months. Cloud architecture thinking will be an active part of the role.
• Tech debt on the roadmap. We believe tech debt belongs on the roadmap, not hidden under it. You'll help identify, prioritise, and plan for it alongside the team.

What we're looking for

You're a backend engineer who takes reliability and code quality seriously, and you can move fast without cutting corners. We care more about how you build and think than about which stack you've used.

• Strong backend experience in production. You've built and run services that real users depend on, in Java, Kotlin, Go or a similar language. Our stack is Java and Spring Boot. If you haven't used it, we expect you to be keen to learn it quickly, and we'll help.
• Comfort with distributed systems. You've worked with message queues, relational databases, or both, and you understand the trade-offs.
• A product mindset. You care why something is built, not just how. You're happy to question a requirement, suggest a simpler path, and judge your work by its effect on users and the business.
• Good engineering habits. You can read an unfamiliar codebase, spot its strengths and weak spots, and improve it over time without needing a perfect plan first. You think about reliability and data, and you're realistic about making change in a production environment.
• Practical use of AI tools. Every engineer here uses Claude in daily work. You don't need to be an expert, but you should be curious and willing to make it part of how you work.

Bonus points

• Java, Spring Boot, JUnit, RabbitMQ or MySQL specifically
• Kubernetes, Argo, GitHub Actions, Grafana or Loki
• Running services in Azure or another cloud, including tuning resources and cost
• Experience with fintech, payments, subscriptions or regulated data

Why join us

• Visible impact. You're joining a team with a full pipeline, and your work will show results quickly.
• A company serious about engineering quality. We're actively investing in elevating engineering practices across the organisation. You'll be part of that, not just a passenger.
• Solid company. Independent, profitable, growing. No VC pressure, no bloated roadmap. Just a clear mission and a team that cares.
• Good people. We take the work seriously without taking ourselves too seriously. The culture is professional, informal, and genuinely collaborative.
• Room to grow. The scope of the work and the team's ambitions mean there's real room to step up.

Practical details

Location:

Copenhagen. We're an office-first company, and it's a deliberate choice. We're moving fast, we have big ambitions, and we genuinely believe that being physically together is one of the things that makes that possible. Things move quicker when you can turn your chair and talk to someone.

The office is a five-minute walk from Rådhuspladsen and stocked with everything from fruit to fizzy drinks to afternoon snacks. Lunch is at Claus Meyer's canteen just across the street — proper food, not an afterthought. If you're putting in a long day, dinner is covered too.

Start:

As soon as possible.

Salary:

Competitive and based on your experience.

Reporting to:

Engineering Manager.

Our hiring process

• Screening call with the hiring manager (30 min) — online
• Technical interview: build something together with a Backend Engineer and the Engineering Manager (60 min) — onsite
• Culture conversation with the Engineering Manager and CTO (60 min) — onsite
• Meet the CEO (30 min) — onsite