Software that works — and keeps working

Oddfríður Petersen

I am Oddfríður Petersen, a senior software consultant based in the Faroe Islands. For over 17 years I have worked on systems where maintainability, delivery, and operational reliability mattered long after launch.

That experience comes from staying close to the full lifecycle: shaping systems early, building them out, getting them into production, and living with the consequences over time. Migrations, new customer needs, deployment friction, and late-night production issues teach clearer lessons than architecture diagrams alone.

I have worked across early-stage products, growing platforms, and large systems under pressure — usually where design decisions and delivery realities need to be thought through together.

My background is strongest in .NET/C#, SQL Server, TypeScript-based frontend work, multi-tenant SaaS architecture, API design, CI/CD, cloud deployment, and production operations.

How I Work

Clarity over cleverness

I try to make systems clearer, not more impressive. That usually means explicit boundaries, simpler flows, and fewer moving parts that teams have to keep loaded.

Built to ship, built to change

Good decisions are not only about code structure. They also need to support how a team ships, tests, deploys, and evolves the system under real conditions.

Think past launch day

I care about what happens after release: how the system runs, how problems surface, and whether the next person can work on it without unnecessary friction.

Where I tend to work

SaaS products, internal platforms, integration-heavy systems, deployment infrastructure, and modernisation work — usually where the technical direction needs to be as solid as the code itself.

Why work with me

Because I combine architecture thinking with hands-on implementation and operational concerns. I care about long-term structure, but also whether a team can actually ship, support, and maintain what gets designed.

I value substance over novelty. The work I care most about is software that stays understandable, changeable, and dependable once the easy early phase is over.

The name "Ese" comes from my children's initials - Esther, Silas, and Elias. It is a reminder to keep the work grounded: build useful things, serve people well, and aim for work that lasts.

Have something you would like to think through together?

Get in touch