Elixir in the Enterprise: Lessons from Maersk By Erik Mejer Hansen

September 23, 2025

Erik Mejer Hansen, Senior Engineering Manager at Maersk, shared the story of how Elixir became a core part of Maersk’s Energy Transition Platform — an ambitious initiative supporting the company’s goal of reaching net-zero greenhouse gas emissions by 2040.

What followed was a deep dive into the technical, organizational, and cultural lessons learned while introducing a niche functional language into one of the world’s largest enterprises.

Elixir in the Enterprise: Lessons from Maersk: A comprehensive overview

Why Elixir?

When Erik first encountered Elixir in 2015, it was a game-changer for building APIs and concurrent systems. At Maersk, the platform needed to:

  • Process large volumes of event-driven data.
  • Support fast development cycles without compromising reliability.
  • Enable full-stack capabilities without splitting front-end and back-end teams.

 

Elixir, together with Phoenix LiveView, offered:

  • High developer productivity with built-in tools and clear conventions.
  • Resilience via Erlang/OTP’s proven reliability model.
  • Concurrency designed for real-time, event-driven systems.
  • Fast feedback loops enabling sustainable Extreme Programming (XP) practices.

 

Building the Team: Skills, Culture, and Hiring

One of the biggest challenges wasn’t technology — it was people. Elixir’s talent pool is small, so Maersk designed a two-cohort hiring strategy:

  1. XP Coaches – experts in pair programming, TDD, and iterative delivery.
  2. Elixir Experts – developers with strong language and OTP knowledge.

 

The team was deliberately remote-first, hiring across Europe, India, and especially Portugal, where the Elixir community is thriving. This setup allowed Maersk to scale despite the niche talent market while ensuring developer happiness and retention stayed high.

 

Security and Tooling: Moving Fast Without Breaking Trust

Introducing a non-standard stack into a 100,000-person enterprise required early collaboration with:

  • Cybersecurity teams – integrating custom pipelines for vulnerability scanning, security training, and compliance.
  • Enterprise architects – ensuring alignment on performance, reliability, and integration with existing systems.

 

Maersk adopted a security-by-design mindset:

  • Automated scanning for dependencies and OWASP vulnerabilities.
  • Custom training based on Erlang Ecosystem Foundation guidelines.
  • Integration with existing observability and CI/CD pipelines.

 

Lessons Learned: Technology, Culture, and Pragmatism

Not every tool needs to be Elixir-based. For example, despite early plans to use Broadway for data pipelines, Maersk adopted an existing Python solution already in production.

This reinforced a key principle:

Choose the right tool for the job, not the one that keeps your stack “pure.”

 

Other takeaways:

  • Engage early with security, architecture, and tooling teams.
  • Own your choices when adopting non-standard technologies—build training, processes, and tooling yourselves if needed.
  • Balance speed with trust—move fast, but bring stakeholders along so innovation doesn’t outpace enterprise readiness.

 

Key Principles for Enterprises Adopting Elixir

  1. Hire for complementary strengths—don’t rely on unicorn candidates.
  2. Plan for security from day one—make it part of the culture, not an afterthought.
  3. Be pragmatic—use Elixir where it shines, but integrate with existing systems when it makes sense.
  4. Create feedback loops—in development, hiring, and organizational alignment.

 

Erik closed with a simple yet powerful reminder:

Innovation in the enterprise isn’t just about moving fast—it’s about moving fast without breaking trust.

 

Additional resources

Check out more from the MeetUp Func Prog Sweden. Func Prog Sweden is the community for anyone interested in functional programming. At the MeetUps the community explore different functional languages like Erlang, Elixir, Haskell, Scala, Clojure, OCaml, F# and more.