From Developer to Head of Node.js Practice: a Growth Story at 01.tech

How long does it take to grow from a developer into a Head?

Short answer: it’s not about time.

In fast-growing companies, career progression rarely follows a "fixed schedule". It usually unfolds differently: the product scales, new challenges, teams, and roles emerge—and with them, your scope of responsibility expands. At some point, you simply find yourself working far beyond what your original role implied.

Nikita, now Head of Node.js Practice at 01.tech, joined the company as a regular developer. Today, he oversees backend development across the entire organization.

In this article, we’ll walk through his journey, what his role looks like now, and what makes 01.tech an environment where developers can continuously grow and evolve.

— A friend of mine spoke very highly of the company and suggested I apply for a React Native developer position. At the time, I was looking for a new job, and it was important for me not just to “fit in”, but to actually have an impact on the product. I wanted a place where I could bring my own ideas to life, not just execute predefined tasks.

Once I joined, I realized all the good things I’d heard were absolutely true.

— When I started, my team had only three people. In my previous job, there were about twenty developers, so at first it felt like things would be much calmer here. But that changed quickly.

The company began scaling rapidly: we moved from a single data center to multiple ones, then to the cloud, introduced Kubernetes, grew our microservices to over a hundred, and significantly expanded our backend teams. We also entered new markets and started working with different currencies and payment systems.

During that time, I worked extensively with ClickHouse, built a custom Node.js library for it, contributed to a meta-framework based on NestJS, implemented OpenTelemetry for microservices monitoring, and developed a metrics system using Prometheus.

— As the company grew, new roles emerged to manage the expanding organization, along with a new matrix management structure. Alongside the traditional hierarchy, a separate vector appeared — the Head of Node.js Practice. In this role, you don’t directly manage developers or their day-to-day tasks. Instead, you focus on hiring, development, and growth. You shape the engineering culture and influence development through technical guidelines, financial levers, and talent calibration.

Right now, I indirectly oversee around 150 people, many of whom I’ve never even met. I study the tech stacks across teams, listen to feedback, discuss and make decisions with different stakeholders. The hardest part is keeping a much broader picture in mind than just a single team or its microservices.

We’ve managed to establish a unified hiring process across teams, align skill levels, build a shared tech radar with over 400 Node.js libraries, and start discussions on standardizing them. A big part of my job is explaining things, negotiating across teams, and learning to do it without friction.

It’s a fascinating experience — somewhat like being an expat in a completely new cultural environment, learning to navigate its diversity. The company also develops JVM, Go, Python, and Kotlin stacks. At times, it feels like the Tower of Babel but that’s exactly what makes it inspiring.

— Two things stand out. First, the comfort and the quiet office, even with lots of people around. Second, the company’s signature lack of toxicity. Even when dealing with tough decisions or problems, the atmosphere stays professional and focused. Emotions take a back seat. It helps you stay effective and it’s incredibly motivating.

— First, salary is above market, and you can clearly see that your work is valued. Second, flexibility: you can work remotely or from the office, without rigid constraints. Third, there are growth opportunities. Internal meetups, tech talks, and real communication beyond your immediate scope. It’s always faster to learn from people than from documentation or video courses.

And, of course, the team. We have a genuinely great culture, with creative team-building activities and corporate events that help people connect. Recently, for example, we had a large group cooking event where we all made wok dishes together. Moments like these are what build a real community.

Nikita’s journey reflects how things work here: you take on challenges, propose ideas, bring them to life and grow alongside the company. The key is not to wait for the “perfect moment.” It won’t come on its own but the challenges, the team, and the environment where you truly want to grow will.

Ready for your next level? Apply on our website and we’ll see you on the team.