Meet The Team: Anton Pletikos

Hi Anton! Can you tell us a bit about who you are and your professional background?

Hi! I’m a software engineer, and I’ve spent most of my career building technical solutions for the book industry. I started out by writing my master’s thesis at the Swedish audiobook streaming service Storytel, and then stayed on for another six years. During that time, I helped build their consumption tracking system and royalty calculation pipeline.

After Storytel, I wanted to broaden my experience and spent some time consulting in the medical industry. But I eventually found myself drawn back to publishing, which led me to Edda. The combination of working with books again and being part of an early-stage product with real impact was hard to resist.

What’s your role at Edda, and what does a typical day look like for you right now?

As one of two software developers at Edda, my role is quite broad. If it’s software-related, it’s probably on my table. Everything from cloud infrastructure and database design to front-end components and even customer surveys.

A big part of my focus so far has been modernising our codebase. The team had already moved incredibly fast before I joined, which meant some parts were built under significant time pressure. I’ve been working on improving structure, readability, and long-term maintainability, and I’m proud of the foundation we’ve built together. It feels like we’re now in a really good position to keep moving fast without things becoming fragile.

“I enjoy solving real problems for real people. Knowing that what we’re building actually makes everyday work easier for publishers and authors is genuinely meaningful to me.”

What has surprised you most about working on Edda so far?

This is my first time working at a startup, and it’s been a very exciting experience. There’s a lot about building a business that I hadn’t really thought about before. In previous roles, I was usually given well-defined tasks that fit neatly into an established business model.

At Edda, it’s often up to the developers to help figure out what we should build and why. A feature request might start as “a user wants to do this,” and then it’s up to the team to decide how it fits into the product, when it should be built, and what the right solution actually is. That level of ownership has been both challenging and very rewarding.

What part of Edda’s mission or product feels most meaningful to you personally?

I’m an engineer at heart. I enjoy solving real problems for real people. Knowing that the product we’re building makes everyday work easier for publishers and authors is genuinely meaningful to me. That sense of usefulness goes a long way.

It also helps that the problems we’re tackling are interesting and the work itself is fun. Building something practical, with a clear purpose, alongside a small and motivated team is a combination I really enjoy.

Outside of work, what tends to inspire the way you think or build?

I’m the father of a seven-month-old baby boy, so a lot of my life right now revolves around routines and structure. That has definitely influenced how I think about my work as well. I try to bring the same sense of structure into my workday, making sure the time I spend creates as much value as possible, both for me and for Edda.

At a startup, there are always a hundred different things you could work on. Being disciplined about focus and priorities is essential, and that mindset has become increasingly important to me.

Join Edda

At its core, Edda is about changing the game for authors and publishers. We are here to introduce a solution that directly addresses the financial challenges authors and publishers face, reshaping the publishing landscape for the better.

Sign up to learn more, get exclusive sneak peaks and early access.