Senior Domain Architect

Some systems you don’t just replace. As a Senior Domain Architect you set the direction from complex legacy toward a modern architecture that also works in reality.

Apply for the position As a Senior Domain Architect you will have cross-cutting architectural responsibility in Securities, Custody & Inbound Data. You work closely with development teams, the area’s leadership team and Enterprise Architecture and have great influence on the technological choices that will shape the area in the coming years.

Your work isn’t about architecture from a distance. You must understand the complexity, gather different perspectives and translate long-term goals into choices and transition steps that teams can actually implement. The role has no people management responsibility, so your influence comes from your professional credibility and your ability to build following.

Set the direction in a complex modernization

Securities, Custody & Inbound Data supports the value chain from securities trading and settlement to custody, corporate actions and market and reference data. It places high demands on stable operations and on being able to modernize with respect for the business-critical nature of the existing systems.

As a Senior Domain Architect you create coherence between the long-term architecture and the decisions made close to the solutions.

You make complex technical problems understandable and highlight the consequences and trade-offs, so teams and leaders can make well-founded decisions about, among other things, risk, quality, costs and technical debt.

It will not always be the architecturally purest solution that is right right now. Your task is also to be able to see the difference.

You challenge existing solutions constructively and with respect for the domain and system knowledge that already exists. When the target architecture meets reality, you help identify transition steps that both move the architecture in the desired direction and take into account stable operations and realistic implementation.

You use, among other things, domain modeling and principles from BIAN to create clearer domain boundaries. At the same time you qualify decisions about integration, APIs, data sharing, third-party solutions, resilience, disaster recovery and other non-functional requirements.

And you don’t let go of the architecture when the decision is made. You gather the relevant perspectives, facilitate design reviews and help teams from decision to implementation without taking over their solution responsibility.

After 6-12 months we can see your imprint

You have succeeded in the role when a common architectural starting point has been created that both managers and teams can act on.

After 6-12 months we expect, among other things, that

• there is a consolidated overview of the system landscape, critical data flows, dependencies, risks and significant technical debt
• a pragmatic target and transition architecture is anchored with clear principles, priorities and deliberate inclusions and exclusions
• an initial BIAN-inspired domain model has made relevant domain boundaries and candidates for gradual separation clearer
• 2-3 concrete modernization tracks are prioritized, so the architecture is translated into visible progress
• architecture decisions are made closer to the teams through design reviews and lightweight, documented decision processes
• you have built the professional credibility that makes teams and leaders use you as an advisor, even when difficult technology choices must be made.

A domain with deep domain knowledge

You work across product and development teams in Securities, Custody & Inbound Data and closely with the area’s leadership team, Enterprise Architecture and central technology functions.

There is already substantial knowledge about both the systems and the domains: trading, settlement, custody, corporate actions as well as market and referencedata.

You won’t come in as the architect with all the answers. Instead we expect you to ask some of the questions that may be hard to ask when you’ve worked with a system for many years.

You must be able to bring together specialists’ knowledge, challenge routines and assumptions constructively and create a direction in which different disciplines can see themselves.

The workplace is Fredericia with the possibility of flexible work and an expectation of physical presence when close collaboration, workshops and important decisions require it.

You have been in the complexity before

We imagine you have a solid technical background and experience such as Domain- or Solution Architect or Tech Lead/Senior Developer.

The most important is that you have previously worked with complex, business-critical legacy systems and modernization or migration.

Mainframe is not a requirement. The important thing is that you have dealt with legacy before and know that modernization rarely starts with a blank sheet of paper.

Perhaps your experience comes from finance. Perhaps from insurance, pensions, aviation, medical or another environment where the systems are complex, the integrations numerous, and the consequences of mistakes real.

We are more interested in what you have tried to move, and how you did it, than whether your tech stack matches ours one-to-one.

Technically we would like experience in several of the following areas

• modern, modular or service-based application architecture
• integration architecture, APIs, messaging and event-driven patterns
• Domain-Driven Design and bounded contexts
• container-based platforms such as OpenShift or Kubernetes
• modern data and analytics platforms and their interplay with operational systems.

As a person you can create followership without formal mandate. You go deep technically when required, but also know when to step back and let teams own the solution.

You communicate clearly to both managers and technical profiles, challenge constructively and keep focus on the direction, even when interests and considerations pull in different directions.

Want to help set the direction?

Send your CV and tell us which complex system landscapes or modernization programs you have previously worked with.

Welcome to Bankdata

Bankdata builds software for the financial sector. We are almost 1000 colleagues on the team, and we develop digital products, platforms and infrastructure that are used every day by about one in three Danes, 200,000 companies and thousands of bank employees.

We believe in structured personal development, a solid collegial community and that ambitious employees with flexible and sustainable work lives perform better. Learn more about working life at Bankdata here .

At Bankdata we actively promote diversity and inclusion among our employees, and we therefore encourage everyone regardless of gender identity, age and cultural background to apply for jobs with us.

Business unit Capital Market, Finance & Risk Role Architecture Location Fredericia Employment type Full-time About Bankdata

Bankdata is one of Denmark’s most important technology companies. We go to work to find technological answers to the financial sector’s business problems. To develop and build the bank of the future.

Founded in 1966 Colleagues 1050 Revenue 1,802.7 million DKK