Full-stack technical depth
From embedded systems and device communication to backend services, mobile apps, and web interfaces.
Systems engineering • technical consulting
I build and fix complex technical systems
I help turn difficult technical ideas into working systems across hardware, embedded software, backend services, and user interfaces. I also support teams when systems become slow, unreliable, or hard to maintain.
Real-world problem solving
Support for systems that are stuck between prototype and production, or already failing under practical constraints.
Calm, direct collaboration
Clear technical thinking, honest assessment, and focused execution without unnecessary complexity.
How I can help
I work best on technically demanding problems where broad system understanding matters more than narrow specialization.
- System architecture
Clarifying technical direction, interfaces, and responsibilities across the stack. - Prototype to production
Stabilizing and restructuring systems so they become usable in real environments. - Performance and reliability
Investigating bottlenecks, latency, instability, and integration issues. - Technical development support
Hands-on implementation where deep engineering work is needed.
Typical situations
A system has grown too messy. A prototype works only under ideal conditions. Performance is no longer acceptable. Hardware and software do not fit together cleanly. The team needs an experienced technical lead who can understand the whole system and move it forward.
Experience
My background combines research, product development, and technical leadership. I have led and built systems spanning hardware, embedded software, communication interfaces, backend infrastructure, mobile apps, and web tools.
Chapter 01
The moment engineering became real
During my third year at Kyiv Polytechnic Institute, I built my first microcontroller board from scratch. I designed it, soldered it, programmed it with a custom-made programmer, and watched it come alive. That was the moment engineering stopped being abstract and became something deeply personal.
What stayed with me
- Hands-on creation
A lasting fascination with turning raw components into working systems. - Embedded curiosity
Early confidence in electronics, low-level behavior, and practical problem solving. - System mindset
The habit of seeing hardware and software as one connected whole.
The engineer in me truly came alive during my third year at Kyiv Polytechnic Institute. As part of my master's studies, I worked on a microcontroller board with simple but essential elements such as switches and indicators. I designed the board, soldered it together, programmed it, and even used a custom-made programmer to bring it to life.
Seeing that small piece of electronics respond for the first time was a defining moment. It felt like I had breathed life into plastic, copper, and code. Since then, I have been deeply drawn to building complete systems from the ground up.
Chapter 02
Building autonomous distributed systems in Dresden
After moving to Dresden, I joined a smart grid project at TU Dresden focused on autonomous distributed systems for communication-network testing. Over five years, that work grew into an internationally deployed platform of Debian-based mini PCs running for weeks with minimal intervention.
What I built there
- Linux and high-load resilience
Learning how to tune hardware and software for stable autonomous performance. - Multithreaded C++ systems
Developing the core software behind long-running distributed test setups. - Operational tooling
Creating interfaces for setup, remote monitoring, and automated PDF reporting with large measurement datasets.
After graduating in Kyiv and moving to Dresden, I entered a new stage of my engineering career at TU Dresden. I worked on a smart grid research project focused on building an autonomous distributed system for testing communication-network performance. This was where I learned to work deeply with Linux, resilient hardware setups, high-load operation, and multithreaded C++ development.
Over five years, the project evolved into a fully autonomous platform deployed in Vietnam, Austria, and Germany. It included dozens of Debian-based mini PCs running for weeks with minimal intervention and delivering valuable results for both my research and communication-equipment vendors. I also created a graphical interface for setup, remote monitoring, and automated processing of measurement results into large PDF reports with visualizations and explanations.
Chapter 03
Deep work in network simulation with ns-3
In parallel with the smart grid projects, I became deeply involved in discrete-time communication-network simulation using ns-3. For my PhD, I developed a simulator for the G.hn powerline communication standard, covering both the physical and data link layers.
Why it mattered
- Protocol-level understanding
A detailed view of how communication systems behave below the application layer. - Disciplined C++ development
Strong habits in design, coding style, and software structure shaped by the ns-3 ecosystem. - Simulation as engineering tool
Using rigorous models to validate ideas before they reach deployment.
In parallel with the smart grid work, I became deeply involved in discrete-time simulation of communication networks using ns-3. For my PhD, I developed a simulator for the G.hn powerline communication standard, covering both the physical layer and the data link layer of the OSI model.
That work gave me not only deeper knowledge of communication systems, but also a strong foundation in disciplined C++ development. The design style and conventions of the ns-3 ecosystem shaped how I think about software structure, clarity, and maintainability to this day.
Chapter 04
PhD research in routing, coding, and patience
My PhD taught me how to structure long-term work, plan carefully, and stay patient while solving complex problems. Over several years, I developed deep expertise in network coding, routing, and powerline communications, eventually bringing the work together in one manuscript.
Core outcomes
- Research structuring
Learning how to move from scattered ideas to a coherent long-form result. - Algorithm development
Creating a routing algorithm based on network coding. - Practical validation
Demonstrating performance through the G.hn simulator I built in ns-3.
My PhD was not only a technical journey, but also a strong lesson in structuring work, planning carefully, and staying patient over the long term. Multiple years of focused effort eventually came together in a single manuscript, and that process taught me how to move complex work forward methodically.
During that time, I developed deep expertise in network coding, routing, and powerline communications. A central part of the work was creating a routing algorithm based on network coding and demonstrating its performance using the G.hn simulator I had built in ns-3.
Chapter 05
Leading robotics work after the PhD
After my PhD, I became the lead of a robotics group. This was a new step into project management, technical leadership, and collaborative robotics, including hands-on work with the Franka Emika Panda and KUKA iiwa platforms.
What this chapter added
- Leadership growth
Learning how to position myself as a technical leader among colleagues. - Human-robot collaboration
Discovering a new engineering domain centered on robots designed to work alongside people. - Project execution
Leading, and often directly developing, research and demonstration systems.
A significantly different chapter began after my PhD, when I became the lead of a robotics group. I learned the basics of project management, grew into a leadership role among colleagues, and entered the world of robotics as a practical engineering discipline.
I worked with collaborative robot platforms such as the Franka Emika Panda and the KUKA iiwa. That exposure opened a new and exciting area for me in human-robot collaboration. I led, and often also contributed as the main developer in, multiple research and demonstration projects, which made this period especially rewarding for both technical and professional growth.
Chapter 06
Building a product company with Mimetik
Joining Mimetik as a co-founder opened the most complete engineering chapter of my career. We built a unique intelligent-glove product, and I contributed across hardware, firmware, communication interfaces, backend C++, databases, Android, and Linux and Windows desktop applications.
Why it stands out
- Full-stack product development
Taking part in nearly every layer needed to bring a complex system to life. - System integration
Bringing many technical components together into one functioning product. - Beyond engineering
Contributing to production methods, UI/UX, and business development to make the product real for customers.
A surprising phone call during a spring walk in Dresden led to one of the most intense chapters of my professional life: founding Mimetik. As one of the founders, I stepped into many roles across the company, but I was especially energized by the engineering side of building something truly new for real people.
We created a unique product based on intelligent gloves, and I contributed across nearly every layer of development: hardware design, firmware, communication interfaces, backend C++ systems, databases, Android applications, and desktop software for Linux and Windows. Beyond the core technology, I also helped shape production methods, UI/UX, and business development so that the system became not just technically impressive, but a real product.
Common questions
A quick way to understand whether I can help and how I usually work.
What kinds of technical problems do you usually help with?
I usually help when a system is complex, slow, unstable, difficult to integrate, or stuck between prototype and production. That can include hardware-software interfaces, embedded devices, backend services, data flows, tooling, or cross-stack architecture.
Can you work on an existing system instead of starting from scratch?
Yes. A large part of my work is understanding an existing system, finding the real bottlenecks, clarifying responsibilities between components, and improving reliability or maintainability without unnecessary rewrites.
Do you only advise, or do you also implement?
Both. I can help with technical direction and architecture, but I also do hands-on engineering when needed, especially for difficult integration, debugging, system restructuring, and focused development work.
What is the best way to start working together?
Usually with a short introductory call. From there, I can review the situation, identify the main technical risks or opportunities, and suggest a practical next step.
Let’s have a first conversation
If you want to discuss a technical challenge, a system that needs improvement, or a possible collaboration, you can book a free 15-minute introductory call.