Domain Architect

What we do at Qliro

At Qliro we deliver safe and simple payments. We are a dedicated partner to our merchants who serve their customers every day. We believe that if our merchants grow, we grow. We are a company of dedicated, friendly and highly competent people that together have redefined what Qliro and payments can be. We are now on a journey of scaling our business both here in Sweden and the Nordics.

What you'll do

We are looking for a Domain Architect to shape the technological landscape of our domain - the glue between teams, infrastructure and products. You own the architecture end to end, keeping it robust, cost-efficient, scalable and aligned with Qliro's long-term vision.
Working with our Tech Leads and Product Managers, you set technical direction across team boundaries and make sure architectural strategy is written down, communicated and executed. You facilitate and coach rather than implement - teams keep ownership of their systems, and you stay clear of day-to-day product work. Our Tech Leads are looking for someone they can learn from: someone senior to think through solutions and ADRs with, who guides them to the best answer and shares their experience. This is a 100% architecture role with no managerial responsibility - you'll be part of Qliro's Tech management team, reporting to the CTO.

What you'll focus on first

• Building a clear, shared view of Qliro's architecture - all services, systems and external dependencies - published centrally and maintained by teams to a common standard

• Establishing a target architecture and decision framework that supports market expansion and volume growth without revisiting fundamental decisions each time

• Defining domain boundaries and ownership together with Product - bounded contexts aligned to business capabilities, an accountable owner for every system, and a clear cross-team decision process (when an ADR is needed, and who approves it)

• Using that shared picture to spot duplication, weak boundaries and problematic dependencies - then prioritizing and driving the most important cross-domain improvements

• Driving the system design phase of larger cross-team initiatives - framing the problem, bringing the right teams together early in feature discovery rather than late, and keeping ownership clear

• Setting shared standards with the Tech Leads: API guidelines, development principles and documentation practices, so teams build in a uniform way

What we are looking for

• You have designed and run distributed systems in production - components, data flows, interfaces, deployment topology

• You have owned non-functional requirements and made the trade-offs behind them visible

• You communicate architecture clearly in English - in writing, diagrams and in the room

• You know how domains intersect - you can tell early in discovery which teams a feature will touch, where blockers live and who should be involved

• You guide and coach teams to sound architecture without taking decision-making or ownership away from them

• You balance product speed against platform scalability - and can explain the trade-off to both sides

It is beneficial if you have experience from:

• Working in a regulated, high-availability environment - payments/FinTech is a plus, not required

• Domain-driven design in practice - mapping bounded contexts with business stakeholders

• Modernizing legacy workflows and consolidating duplicated capabilities

Qliro is an equal opportunity employer. All qualified applicants will be considered for employment without regard to gender, gender identity or expression, national origin, religion or other beliefs, disability, sexual orientation or age.