There's a moment Ossi Galkin still remembers clearly. He was deep inside a BizTalk integration that had been running at a Finnish food manufacturing company for years. Nobody, not the customer, not the original developers, could fully explain why it had been built the way it had. It was a tangle of logic that had grown organically, patch by patch, over time.

When Ossi and the team finished migrating it to Frends and showed the customer what it looked like on the other side — clean, observable, understandable — the customer was delighted.

"That moment stuck with me," Ossi says. "Not because we did something technically brilliant. But because we made something complicated simple. And that turned out to be the thing I'd spend the next decade doing, in different ways, in different roles."

Starting with the craft

Ossi joined the company in January 2016 as an Integration Consultant, fresh from Aalto University, in Espoo, Finland. His first years were hands-on and varied: migrating Raisio Group's enterprise integration landscape from BizTalk to Frends, building integrations for manufacturers, retailers and facility management companies, and learning what it actually means to keep business-critical systems talking to each other.

What he learned in those years went beyond the platform. He saw how enterprise systems talk to each other, and learned why they so often don't.

Every system has its own data model, its own idea of what a customer or an order or an event looks like, and those models contradict each other in ways nobody documented. Data has to move from where it lives to where it's needed, transformed into a shape the receiving system can use. That means understanding databases, message queues, event streams, and APIs, and knowing when to use which.

It means designing for traceability, so that when something goes wrong at 2am you can find exactly where and why. And it means doing all of this in a way that holds up under SLA pressure, on an enterprise scale, without becoming the next unmaintainable tangle someone will spend years trying to understand.

"The domain is genuinely deep," Ossi says. "Most people don't realize that until they're in it."

Ossi wasn't just delivering projects. He was contributing to Frends Tasks, building reusable components, improving file handling, writing documentation. He even built a browser extension to give the Frends process editor a dark theme.

"I care about the details," he says. "If something was slightly wrong or harder to use than it needed to be, I wanted to fix it. Even if nobody asked me to."

Closing the gap between capability and understanding

In 2018, partners building on Frends needed a technical person they could call when things got complicated; someone who could handle architecture questions, support presales cases and solve the kind of problems that don't fit neatly into a support ticket. That was Ossi.

He moved into a Partner Development Manager role. There, he also rebuilt how Frends handled customer support, by replacing slow email threads with a live documentation and chat system, and helped grow the Frends Community Tasks, an open library where integration developers share reusable components, so nobody has to solve the same problem twice.

Internally, he was part of building a dedicated Operations team from scratch: a new function designed to take ownership of customer environments so the rest of the organization could focus on building.

"I realized that the gap between what the platform could do and what people actually understood it could do was enormous. And that gap was costing everyone’s time. Closing it felt like important work."

Building the academy and rethinking learning with AI

By 2022, Frends was growing fast with new customers, new markets, new geographies. But there was a clear problem: no formal way to train any of them at scale.

Ossi was asked to fix that. There was no playbook, no existing infrastructure, no course content. Just a clear need and an open brief.

He built the Frends Academy from the ground up: learning management system, course catalogue, automated certification, billing and live instructor-led training sessions delivered to customers across Europe.

"The hardest part isn't the technical content," Ossi says. "The hardest part is figuring out what someone needs to know first. What's the one concept that, if they don't understand it, nothing else makes sense? Getting that sequencing right is genuinely difficult."

The Academy changed how Ossi thought about his own work. Designing learning forces, you to understand a platform at a level that years of hands-on delivery never quite requires. You can build something without fully understanding it. You cannot teach it without fully understanding it.

The same instinct that made him a good teacher, like figuring out what someone actually needs before they know how to ask for it, turned out to be exactly what AI systems require. While running the Academy, Ossi took on improving Frends' AI-powered support chatbot. The challenge here was understanding the real conversations customers were having: where they got stuck, what kind of answer would unblock them. He restructured the chatbot's context, reworked how it handled edge cases and redesigned the conversation flows from the ground up. You can read more about how that work came together and what it made possible.

"People assume AI automation is about the technology," Ossi says. "That is not exactly true. AI automation is about understanding the person at the other end of the conversation. That's exactly what teaching taught me. Whether you're designing a course or a chatbot, you're always asking the same question: what does this person actually need right now?"

When the integration platform is the infrastructure

Caruna is Finland's largest electricity grid operator, and unlike most companies talking about infrastructure, they mean it literally.

As Business Analyst and architect on this account, Ossi returned to hands-on delivery and worked through multiple platform migrations and modernizations, the kind of projects where something unexpected always happens and the platform keeps running regardless.

His role sits now at the intersection of architecture and analysis: translating between what the business needs operationally and what the integration platform can deliver, across the full stack of stakeholders from developers and ICT architects and business leadership.

"The environment is large enough that something unexpected always happens," Ossi says. "The job is to have thought through enough scenarios in advance that when it does, you know what to do."

What a decade without standing still

What keeps someone in the same place for a decade? Not inertia, but finding that the work keeps changing before you run out of things to learn from it.

Integration is a domain deep enough to spend a decade in and still find new things to understand. The platform changes. The problems not so much. And the skills that matter — understanding what a system needs, what a person needs, what a business needs, and how to translate between all three — turn out to be just as useful whether you're writing code, designing a curriculum or sitting across the table from a client.

"I still enjoy the code," he says. "I just also enjoy the architecture, and the training, and the analysis, and the AI work. I don't think you have to choose only one."