Hey, I'm Aleksandr.

How I got here

It started with The Elder Scrolls IV: Oblivion. I was twelve, with no internet and no documentation — just the game's built-in scripting engine and an endless supply of curiosity. I'd copy scripts from the game's files, rearrange them, change the numbers, see what happens. NPCs that weren't supposed to fly started flying. Doors that led nowhere started leading somewhere. I had no idea what I was doing, but I was learning my first programming language without realizing it.

The moment it clicked — that I could create worlds that live by my own rules — there was no going back. A couple of years later that curiosity turned into freelance work, and clients started finding me on their own. At eighteen I wanted something more stable, found a company, and built their entire platform solo. We landed clients, I grew into the CTO role, hired the team, and scaled it from there.

Then JetRockets came along and I fell in love with how they work. Six years later, it's "we". Leading teams, shaping architecture, shipping software across industries — from SaaS products to complex enterprise systems where every technical decision carries weight.

What I do at work

My focus is on teams — technical direction, architecture decisions that hold up for years, code reviews, mentoring engineers. I care about building environments where people ship with confidence and grow while doing it.

Full-stack at heart — I still write production code daily. The real leverage is the team, but staying in the editor keeps the technical judgment honest.

AI has become a natural part of how I work every day — whether it's generating code, exploring architecture trade-offs, or crafting prompts that save hours of manual work. It doesn't replace engineering judgment, but in the right hands it's a force multiplier that's hard to ignore.

The hardware side

There's something honest about hardware — no abstraction layers, no framework magic. When something doesn't work, it's physics, not a config file. That contrast with web development is exactly what keeps me coming back to the workbench.

Most of it starts the same way — an ESP32 or STM32, a handful of components, and a question I want to answer. Sometimes it's an Arduino when I just need something quick. HomeKit sensors, LED controllers, custom firmware for whatever board is on the desk. The most ambitious project so far is a web-based logic analyzer — browser-side signal rendering with WebUSB, built as a modern alternative to PulseView.

Firmware in C and Rust, with a bit of assembly when the hardware demands it — like bit-banging protocols for WS2812 LEDs. You pick whatever fits the chip.

Life on the road

In August 2025 I married Julia — the girl who makes every country feel like home. We chose this lifestyle because remote work doesn't care about borders. If the laptop works and the Wi-Fi holds, the country doesn't matter — so why not see as many of them as we can?

A new place every month or two. Some we stay longer — a year and a half in Thailand, because sometimes you just find your spot and there's no reason to leave. Once we drove across Madagascar for two weeks in a rental car — no WiFi, no laptop, just the road and the baobabs. The country list keeps growing, but the suitcase stays the same size.

How I think about work

My setup

Toolset

I believe in choosing the right tool for each problem. No technology is universally superior — every language, framework, and library has its strengths and weaknesses depending on the context. What matters is understanding the trade-offs and knowing when each one shines. Here's what I've worked with over the years: