We're hiring a senior engineer to join a small team that owns the finance and agreement domain of a production software platform built for a Norwegian organization with distinctive operational needs.

You'll be the third developer on the team, working alongside two experienced engineers with support from Fabillio's founder and architect. You'll interact directly with the customer's product team and coordinate with a second developer team working on other parts of the same platform. The systems are live, they matter to the business, and they're evolving.

**The Domain**

The finance and agreement area covers billing and payment, operational workflows, and contract logic — places where correctness, traceability, and clear state management are not optional. The problems here are rarely simple CRUD. Much of the work involves modeling complex business rules, making changes explicit, and building systems that remain understandable as they grow.

Typical work includes:

·     Designing and building backend services in C# / .NET

·     Working with event-driven architecture and event sourcing

·     Using event modeling to model domain behavior before writing code

·     Supporting systems across their full lifecycle — from design through production

·     Improving system clarity and maintainability as the product evolves

**How We Work**

We primarily work in C# / .NET, but we're open to strong backend engineers from other ecosystems. Our platform runs on modern .NET with RavenDB, hosted on Azure. The frontend uses Angular with TypeScript, shipping to web and mobile through Ionic and Capacitor. What matters more than a specific tech stack is how you think about systems: we care about modeling behavior clearly, making complexity manageable, and building software that stays honest about what it does.

We work in close collaboration with customers and domain stakeholders. At Fabillio, engineering teams don't just build to spec — they help shape understanding of the problem alongside the people who live with it.

**About Fabillio**

Fabillio is a small company of around 10 developers. Many of us have worked together for years, and we build long-term relationships with both our team and our customers.

We focus on domains where the logic actually matters, workflows, decisions, and data that need to be correct and maintainable over time. Our systems are not short-term projects, and neither is the way we build teams.

**What We're Looking For**

You likely have around 5–10 years of experience building backend systems in production, though what matters more is the depth of that experience and how you approach your work.

You're someone who:

·     Has strong experience building backend systems in production

·     Is comfortable working with complex domain logic

·     Thinks carefully about system behavior, data flow, and long-term maintainability

·     Enjoys solving problems that require understanding both technical and business constraints

·     Is curious about the domain you're working in, not just the code

·     Communicates clearly and works well with both engineers and non-technical stakeholders

Experience with event sourcing, event modeling, domain-driven design, or event-driven systems is valuable. So is an interest in using AI tooling effectively as part of how you work. We're actively pushing in both directions, and we're looking for people who want to push with us.

**What You'll Get**

·     Real ownership in a small, senior team

·     Direct influence on architecture and product decisions

·     Work on systems where correctness and design actually matter

·     Close collaboration with engineers and domain experts who've been working together for years

·     Flexible working setup — remote or hybrid depending on location

·     Competitive compensation aligned with experience, responsibility, and impact

**Interested?**

Send a short note and your resume to hello@fabillio.com. We're looking to fill this role as soon as possible and will be reviewing applications as they come in.

We'll typically start with a short intro call, followed by a technical conversation focused on how you approach real problems and system design.