About | Arash Sarfehjou

How I got here

“ I didn't set out to become a technical leader. I kept finding myself where engineering, architecture, people and business met.”

Leadership beyond delivery

Leadership isn't limited to the project I'm assigned to. Some of the work I'm most proud of has happened around the projects — creating structures, developing people and making engineering teams stronger.

Pentia · Knowledge Sharing

Building an engineering culture

I created and facilitate a recurring knowledge-sharing forum — inspired by the idea of a community of practice — where engineers step outside project delivery to explore technologies, practices and ideas together. The goal is to create space for organisational learning that otherwise gets lost when teams are focused entirely on delivery.

Pentia · Organisational Initiative

Creating a maintenance capability

I identified an ownership gap between project delivery and long-term operation. Once project teams moved on, responsibility for maintaining completed solutions was fragmented — work flowed back unpredictably into delivery teams, creating drag for both engineers and clients. I helped establish a dedicated 4–5 person team with clear ownership boundaries around post-launch maintenance and support, with its own commercial model and operational remit.

Independent · Consulting & Business

Running my own consultancy

Before Codehouse and Pentia, I ran my own consulting practice. Working directly with clients — owning pricing, delivery and scope — taught me to see technical decisions in a wider context. It's part of why my architectural work today considers budget, delivery and long-term operating cost alongside the technology.

Beyond client work

External Examiner

Danish higher-education institutions

Alongside consulting, I periodically serve as an external examiner at Danish higher-education institutions. On a typical examination day, I assess 10–15 students across different projects — understanding unfamiliar technical solutions, challenging their reasoning, and making independent professional judgments against academic criteria.

The role strengthens something I use constantly in engineering leadership: the ability to quickly understand unfamiliar solutions, ask the right questions and evaluate not only what someone built, but how they think.

Career Highlights

2018 – Present

Pentia A/S

Junior Partner

Co-responsible for company direction, people strategy and long-term growth. Involved in hiring, mentoring and building the engineering culture.

2013 – 2018

Pentia A/S

Senior Frontend Engineer · Architect

Technical leadership across complex client projects — defining architecture, guiding teams and bridging the gap between business needs and engineering decisions.

2010 – 2013

Codehouse

Frontend Developer

Where the foundation was built — design, develop and deploy across a range of client projects.

Pre-2010

Independent

Consultant & Freelance

Ran my own consulting practice — working directly with clients, responsible for delivery, pricing and adapting quickly to new domains and organisations.

How I work is shaped by where I've been.

Read my approach →