Senior Software Engineer

Hub; København; Hybrid; DKK 900,000 - 1,200,000; Full time

Job summary

Dully is building an operating system for hospitality with a platform that scales across Denmark and beyond. You will own end-to-end architectural decisions, spanning .NET backend, Azure infrastructure, and frontends, taking problems from understanding to production-ready solutions.

You will join a small, equally responsible team where decisions land on you. We value ownership, speed, and pragmatic governance in a startup environment, with a preference for strong English and a collaborative

Qualifications

• Deep .NET expertise required.
• TypeScript and Node.js are strong plus.
• Senior level with long-term design experience.
• AI experience preferred and valued.

Responsibilities

• Own end-to-end architectural decisions across the platform.
• Collaborate with product and engineering to shape the road map.
• Drive delivery with a bias for customer impact and quality.
• Maintain production readiness and long-term system health.

Skills

Deep .NET

TypeScript

Node.js

Senior judgement

AI experience

Drive

Startup mindset

Strong English

Danish (nice to have)

Job description

ABOUT US

Dully is the operating system for restaurants and food service. Our customers run their business on us: staff planning, payroll, purchasing and inventory, POS data, insights, and the entire guest ordering stack, from web storefront to delivery aggregators.

Running a restaurant is a hard business. Margins are thin, people and food costs move every day, and most operators steer them with a dozen disconnected tools and a spreadsheet at midnight. Dully brings all of it into one system. When the pieces connect, the owner gets their evening back, and a few points of margin they did not have before.

We have run restaurants ourselves. We build for the people who still do.

WHAT THAT MEANS TECHNICALLY

Several hundred locations run their day on Dully, and we are expanding beyond Denmark. Millions of transactions have gone through the platform, but volume is only half of it: what we run is operational infrastructure. If it stops, shifts do not get planned, stock does not get counted, and food does not get sold. That shapes how we build.

We are also merchant of record for our customers' digital payments, so real money moves through the platform every week. And we sit between systems we do not control: POS, delivery aggregators, payment providers, each with their own idea of what an order looks like. Keeping that coherent is most of the interesting work.

Product, engineering and commercial sit in one office in Copenhagen, plus a few remote developers. It is a small team for a platform this size. Nobody hides behind a process layer, and what you build is in production within days.

THE ROLE

You will work across the whole platform, not a slice of it: .NET backend, Azure infrastructure, our frontends. And you will get a domain of your own to own end to end, from understanding the problem to making the architectural calls to what runs in production.

Two people make the architectural calls here, and you would be one of them. That means the trade-offs land on your desk: what we build, what we buy, and what we leave alone.

You will not be handed a narrow lane. You get a problem area, customers who need it solved, a product team you work closely with every day, and the room to decide how.

WHERE WE ARE GOING

The agent layer inside Dully watches a restaurant as it runs, works out what matters, and acts on it. Not a chatbot bolted onto a dashboard. The system itself, making decisions in the business it runs.

We are underway. The first pieces are running and the direction is set. What we need now is someone to push it further and faster.

If those are the problems you want to spend your time on, this is a good place to do it.

WHAT WE ARE LOOKING FOR

• Deep .NET. That is where our core lives, and it is the one hard requirement

• TypeScript and Node.js are a strong plus. Much of what surrounds the core is built on them

• Senior judgement: you have designed systems, lived with the consequences, and know what keeps a codebase alive over years

• AI is already a normal part of how you build. Not something you are curious about, something you have opinions about

• Drive. You take ownership and see things through

• Comfortable in a startup: things move, and not everything is figured out yet

• Strong English is required. Danish is a plus

Beyond .NET, two of those matter more than the rest.

On AI: We use AI as an integrated part of how we develop, and we expect that you already do too. We are not looking for someone willing to try it. We want someone who brings their own experience and preferences, so we can combine them with ours. What matters is judgement: knowing what to trust, what to check, and how to keep quality up at pace.

On drive: We weigh this above almost everything else. People who take responsibility, follow through, and care whether the thing actually works for the customer. Who ask when something is unclear and decide when nobody else will.

HOW WE WORK

Anyone can raise an idea here, and we would rather you did. We have a roadmap and we hold ourselves to it, but it is a plan, not a contract: when an idea makes a real difference for our customers, we make room for it, sometimes the same day it is raised.

We work hybrid, but we are looking for someone who wants to be in the office. That is where most of the conversations that move things happen.