The part the CV doesn't tell you
Most “about” pages are a victory lap. This one names the work, the projects worth doing over again and what they cost to ship. Same curiosity, harder problems.
Hey, my name is Victor. I'm based in Krakow, Poland, and I build IT products people actually use, while leading the engineering teams that ship them.
My story started in the early 2000s. I was four when I got my first “square” computer with a floppy-disk reader. I was playing StarCraft, Warcraft III, Need for Speed and clicking on every other icon on the screen to see what would happen. That is how I discovered Microsoft Paint, Word, PowerPoint, Excel: the whole suite, by accident.
Primary school added Pascal ABC and a bit of HTML. I kept learning English, kept clicking, simply enjoyed life with computers.
Middle school: small games and projects for fun. High school: real contests in game development and educational tech, a few of them won. A local technical magazine even published a page about me, which felt enormous at the time.
Then came university, where I mastered creative approaches to passing exams. By my second year I was already working part-time at an IT company.
The first three years professionally were about volume and range. Twenty-plus playable ads and mini-games in native JavaScript, four mobile apps, eight websites from blank canvas to production. Different clients, different stacks, the same loop: figure out what they actually need, build it, ship it, fix what is wrong.
In 2020 I joined Elinext as a Node.js developer. The role grew with the work: a few years and a lot of shipping later, solutions architect and tech lead. Bigger systems, backend architecture, database design, infrastructure, distributed teams of up to ten people across Poland, Ukraine, Georgia, Canada and the USA. Five industries so far: HR, EdTech, finance, field service and, more recently, blockchain.
The 2022 industry crisis is the part I am proudest of. The team kept shipping, the client gave us five stars on Glassdoor and not a single core engineer left. Leading people through a year you cannot predict is a different muscle than leading them through a year you can.
Lately the work has gotten more architectural and more public. A Bitcoin settlement backend in three languages, showcased as lead engineer at Bitcoin 2025 in Las Vegas (80 conversations in 3 days, my voice was not the same on the flight home). A pre-sales architecture for a UAE wealth platform that won a 6-figure contract and is now in build. An AI-integrated field service platform from blank repo to MVP in 8 weeks.
The five projects I am proudest of from the last five years live on the Top cases page. Each one in the same shape: the problem it started with, the architectural choices behind it, what actually shipped.
That's the story so far. Same curiosity, harder problems, a lot more at stake. The roadmaps I'm hired for tend to have something in common. You'll know if yours does.
