Inside the integrations — where the complexity of hotel tech lives

Integrations are where hotel tech’s complexity actually lives.

Joonas Hamunen leads the team globally responsible for that complexity at MeetingPackage, the work that translates the platform’s logic into the language of every hotel system it touches.

Ask him who thrives there, and the answer is immediate:

“People with ownership. People who want to solve hard problems instead of just closing tickets.”

Started in business and ended up in tech.

“I wasn’t really an engineer at first. I was just the only one who knew how to build websites.”

The path here

From business school to hospitality tech

Why MeetingPackage

After eight years building his own startup as CTO, then crossing through product leadership, consulting, and software architecture, Joonas had figured something out about himself.

“I get bored in environments where things move too slowly.”

Large organizations and endless bureaucracy weren’t for him. He missed the pressure, the ambiguity, and the feeling of building something meaningful in real time.

MeetingPackage hit the right balance: established enough to work with major hotel chains globally, but still small enough that every engineer could make a visible impact.

"At around 70 people globally, you still feel close to everything happening in the company. You can actually influence things."

Joonas Hamunen, Director of Engineering & Product, Integrations

He also appreciated the honesty during the recruitment process. No illusions that everything was perfectly polished — the team was transparent about the challenges. For Joonas, that openness was a positive sign.

The two domains

Joonas leads a team in two domains. Together, they own how MeetingPackage talks to the rest of the hotel tech stack:

Inbound bookings

Handles incoming requests and the booking flows that move them through the system.

Outbound sync
Syncs booking data to and from various external systems that hotels already use.

Each integration is its own translation problem.

Property management systems track rooms one way. Sales & Catering systems track events another way. CRM systems operate on yet a third model. A booking that looks straightforward inside MeetingPackage’s logic might need to be reshaped, validated, and routed differently for every destination system it touches.

And no two integrations are ever quite the same.

“Every system has its own philosophy. You’re constantly solving the challenge of how to translate MeetingPackage’s logic into another system’s way of thinking.”

For engineers, that means much more than routine backend development — architecture decisions, complex problem solving, integration patterns that scale across many clients and platforms.

It also has to be resilient. Hotel systems go down. APIs change without notice. The integrations have to keep working — or fail gracefully and recover — when any individual external system misbehaves.

The tech stack is pragmatic — Node.js, JavaScript, TypeScript. But that’s not where the excitement is. “The interesting part isn’t the syntax,” Joonas says. “It’s the architecture, the patterns, and the domain-driven thinking behind it.”

A platform mid-rebuild

MeetingPackage is in the middle of a generational shift — moving from a legacy platform to a new one.

For the integration teams, that means the work isn’t maintenance. It’s foundational.

Every integration pattern designed now sets the shape of the platform for years to come. Every architectural decision compounds. Joonas’s teams aren’t just connecting things — they’re choosing how MeetingPackage will be connected for the next decade.

AI is part of how those foundations get built. Engineers are encouraged to experiment, test new tools, and learn quickly — without heavy processes slowing things down. “We want to be at the forefront of it,” Joonas says. “We’re not afraid to be bold and see what actually works.”

It’s the kind of moment that doesn’t come around often in a software career.

Ownership as the key driver

That depth of integration work is only possible because engineers actually own their domain. One engineer typically becomes the internal expert for one or two major hotel integrations — shaping technical direction and architectural decisions without constant approval.

“If every integration decision had to go through the whole team, we’d drown in overhead,” Joonas says. “People need the space to own things.”

“You’re not just getting Linear tickets and calling it a day. You have to think more.”

It requires initiative, communication, and comfort with shifting priorities and delivery of high-quality solutions for customers. For the right person, that’s exactly what makes the work rewarding — “you really see the impact of what you’re building.”

A job that challenges and grows you

Joonas is honest about life at MeetingPackage.

It’s busy. Customers expect excellence. Deadlines are tight. Systems are complex. And there’s legacy technology to navigate.

But the pressure comes with opportunity. “You get to learn constantly,” he says. “You solve difficult problems, and you work on things that actually matter to the business.”

MeetingPackage isn’t for everyone. For people energized by ownership, complexity, and visible impact, it offers something much harder to find: a chance to help modernize an entire industry.

Want to join our engineering team? Check out our careers