Careers Denmark
Browse opportunities

Digital & Data

Solution Architect

Nilfisk Nordhavn/Copenhagen Posted 21 Sept 2026 Employer's career siteHybridFull timeSenior specialistEnglish
This job is no longer confirmed open. We have not seen it at the employer in the last 24 hours. Check the employer's own posting before you apply. View the employer's posting

Summary

The Solution Architect will set the target architecture, shared standards and building blocks for Nilfisk’s Digital Product portfolio. The role also evaluates proposed work, reviews designs and helps teams build architectural judgement.

The fields are read by AI from the ad. If the employer filled in a field themselves, we use theirs.

Opportunity summary

Employment type: Full time. Remote: Hybrid. Requisition: R017587. Country: Hungary.

Additional locations: Nordhavn/Copenhagen.

Nilfisk's Digital Product department builds the software around the machines: customer portals, connected-machine and fleet services, mobile apps, service and field tooling, internal applications for our own colleagues. Today that is cross-functional product teams working on different products, and it is growing.

We are hiring our first Solution Architect to make those products add up to one landscape rather than separate ones. You will define the target architecture, and the shared building blocks our teams design within. You will also be the person the organisation comes to when a new idea, product or roadmap needs an architectural answer, and the person who says, clearly and early, what it will take.

How we will work, and where you fit

Our product teams are cross-functional and durable. A Product Owner, UX and engineers own a problem area end to end, from discovery through to running it in production. They make their own technical decisions inside their boundary, and we intend to keep it that way.

That shapes this role in a specific way. You are not an approval gate, and you do not design other teams' services for them. You own the decisions that cross team boundaries, and for everything else you make the good path the easy path: clear patterns, reusable building blocks, sensible defaults, and documentation developers actually read.

A team should build within your architecture because it is the fastest route to something that lasts, not because someone mandated it.

What you will own

  • The target architecture for the Digital Product portfolio, and a realistic roadmap to get there from where we are
  • The principles, reference architectures and design standards teams work within, and the boundaries between products and teams

This is an extract. Read the whole advert at Employer's career site