When you think of a CTO, you might picture someone with a perfect resume, a textbook career path, and a fancy MBA. Ivan Roslov’s story is not that straight foreward, and that’s exactly what makes it so real.
Ivan didn’t study computer science. He didn’t even plan on working in tech. But somewhere between hacking together websites in a dorm room and building full-on web applications, he found his way. Today, he’s the new Chief Technology Officer at Apliteni. And in this interview, he shares how he got here, what he’s learned, and why staying curious matters more than knowing all the answers.
So, Ivan, how did you even end up in development?
Honestly, by accident. I was studying oil and gas engineering. Very far from IT. My thesis was about ultrasonic gas sensors using the Doppler effect. But during uni, I needed to make some money. There was no gig economy back then, so a few friends and I started figuring out how to earn online. We picked up some basic HTML, started building websites, and found a few local businesses willing to pay us. I still remember the first one: a guy selling construction materials.
From there, it just took off. We realized we could actually earn doing this, and I got hooked. I finished my engineering degree but never went into the industry. I kept coding instead.
Were you self-taught the whole way?
Pretty much, yeah. I didn’t study programming formally. But I started early. Back when websites were static and the internet was just getting going. I’ve kind of grown alongside the web. At first, it was simple websites. Then came more complex apps, and eventually full-blown platforms. The lines between front-end and back-end were blurred back then, and I had to keep up with both.
How did your role evolve once you joined Apliteni?
I came in as a full-stack developer about 6 years ago. Over time, as our product got more complex, the team split into more specialized roles — front-end, back-end — then came product teams etc. I ended up focusing mostly on the back-end for the past few years, but I’ve always kept a foot in both worlds. I still try out new tech, and stay curious. That’s just how I learn.
What made you stay at Apliteni for over six years? That’s rare in tech.
Honestly? The culture. Before Apliteni, I worked remotely for a company where the remote folks were kind of second-class citizens. Meetings happened in the office, and they’d just plop a laptop on a table so we could listen in — barely included.
Then I saw Apliteni’s remote-first handbook. It laid out exactly how the team works, how they communicate, how they treat people, and it just clicked. It felt like someone had written down everything I wanted from a company. I joined, and it turned out to be exactly what was promised. No drama, no toxicity — just good people doing good work.
How did you end up becoming the CTO?
There wasn’t a big formal process. Our CEO, Arthur, realized the company needed a dedicated tech lead — someone to support the product side with technical direction. He wrote up what the role should look like and started talking to people. He asked around — even asked me who I thought would be a good fit.
At some point, I started getting messages from teammates saying they thought I should do it. People I didn’t even expect were backing me. That meant a lot. I probably would’ve overthought it, maybe even said no, but that support pushed me to say yes to the role.
What’s been the hardest part of stepping into the role?
Two things. First — the one-on-one meetings. I had to talk to everyone, across all levels and teams, and that took a lot more time and energy than I expected. One conversation even lasted over two hours. The prep, the scheduling, the note-taking — it was a lot.
Second — the emotional shift. As a developer, you get validation from what you produce. Tasks completed, code written — it’s measurable. But now? My success is tied to how well the whole team is doing. I can’t just stay up late and code my way out of a problem. I have to enable others to move fast and do great work. That’s been a big mindset shift.
If you could give your younger self some advice, what would it be?
I’d go back 20 years and say: start learning now. Don’t waste time. Read more, study more, dig into the tech. I didn’t really get serious about deep learning until I hit 30. Now I see younger devs come in already super sharp, and I think — yeah, I could’ve started sooner.
What advice would you give to someone who wants to eventually become a CTO?
Aside from loving what you do and learning all the time — I’d say: work on your communication. A lot of devs (myself included) are introverts, and that’s fine. But being able to express your thoughts clearly, give feedback, listen — that’s huge. Also, find a company that fits you. Culture and values matter way more than we think.
- Love what you do
If coding lights you up, follow that feeling. It’s your fuel. - Never stop learning
Tech changes fast. Stay humble, stay curious, stay in motion. - Work on your communication
It’s not just about knowing the answer — it’s about sharing it clearly and kindly. - Find a team that fits you
The right environment will help you grow faster — and feel better doing it. - Be open, not perfect
It’s okay not to know something. What matters is your willingness to learn it.
