Career stories
An interesting product is only the starting point.
For developers, it matters just as much to influence decisions, see the results of their work, and keep growing alongside the team.
We chatted with Igor, who has been with Eyes of Wonder (and Multilogin specifically) for years and made the move from support to frontend engineering, to talk about what makes the work here genuinely interesting.
Tell us how you ended up at Eyes of Wonder.
Why us, and what have you noticed over the years?
Back when I was still teaching English to kids, I found myself with enough free time to try my hand at IT. I took online courses and picked up small projects on Upwork, and that's exactly where I met people from Eyes of Wonder. We started talking about working together soon after, and I joined the technical support team.
Why did I choose EoW? A few things drew me in:
an interesting product;
the chance to work on an international team;
an open atmosphere;
colleagues and managers who were ready to help from day one.
I've been here several years now, and in that time I've watched the company grow from a small startup into an international team of more than a hundred people.
What's been especially interesting is seeing how the processes, the communication culture, and the product itself evolved along with that growth.
You're a Frontend Developer now. How did that come about?
After a few years in support, I knew the product inside out from the user's perspective, and I realized I wanted to help build it as a developer. The company's open culture played a big part.
Thanks to regular random online coffee chats with colleagues from different teams, you could simply talk about your career plans. I mentioned that I wanted to move into development - and I was heard.
From there it happened step by step:
I said I wanted to move into development;
I was given a test project in React;
I worked on it for about three months outside my main job;
I passed the assessment and joined the Frontend team.
The whole transition took roughly six months, from the first conversations about changing direction to officially starting in the new role.
What did the learning process look like? And what would today's you tell someone who wants to get into development?
The company helped set up my training. It included:
an online course;
weekly meetings with the team lead;
hands-on practice with the same stack the product uses.
That format made it much easier to adapt once I started working on real tasks.
If today's me were giving advice to someone who wants to get into development, it would be this: start with the fundamentals — HTML, CSS, JavaScript, or another core technology. Build simple projects with your own hands first, and only then bring in AI tools as assistants. That approach gives you a balance between solid foundations and modern capabilities.
You spent a long time in support. Has that shaped how you write code today?
Enormously. Working in support taught me to:
look at the product through the user's eyes;
notice even small UX problems;
understand how much the details matter;
remember that there's a real person behind every bug.
When I got the chance to work on the company's core product in September 2024, that experience helped me see tasks not just as technical problems but as user problems that deserve the best possible solution.
What technologies do you work with day to day? What do you use AI for, and what do you do by hand?
Right now my main stack is Angular and React, with some Go on the side. I use these daily to build and maintain the company's website and product.
As for AI, I use it to generate boilerplate, look for optimal solutions, and speed up routine work. But I think it's important not to trust the output blindly - you have to steer the agents and check the architectural integrity of whatever they suggest.
The critical parts of development, architecture design, UX work, performance optimization, I prefer to do manually. That keeps me in control of the quality and makes sure I understand exactly how the product works. For me, AI is a tool that helps you move faster, but responsibility for the end result always stays with the developer.
Which results of your work are you most proud of?
There have been several projects over the past few years that really stuck with me.
One of the bigger ones was migrating from the Carbon design system to Google's more modern Material. Opinions were split right after release: some users welcomed the update, others asked us to bring back the old version. Thanks to the work of our designers and the development team, we managed to deliver a high-quality replacement and ultimately meet most people's expectations.
And of course, the most significant addition right now is mobile phone emulation. That's not a personal achievement but the result of the whole development team's work, both frontend and backend. Users immediately saw the value, and it became a key step forward for the product.
What do you like most about working at Eyes of Wonder?
A few things make this job genuinely comfortable for me.
An interesting product. You get to work on complex engineering problems that thousands of people actually use.
Room to keep growing. The company supports learning, and new technologies show up in the work all the time.
Freedom and trust. You feel trusted to make technical decisions and take ownership of your work.
All the resources you need. You don't waste time fighting infrastructure — you can focus on building.
Work-life balance. Personal time is respected here, and there's a real effort to keep things healthy.
Clear goals. You always understand why you're doing a given task and what it contributes to the product.
Our developers don't just work through backlog tickets - they take part in shaping the product, weigh in on decisions, and see the results of their work in every release.
If this sounds like your kind of place, take a look at our open roles. Maybe before long we'll be telling your story too! 😎
