In conversation with our Full-stack Developer
Discover the journey, collaboration, and ideas shaping software development at Pluxbox.

Behind every platform is a layer of code that makes everything work. In this edition of our employee spotlight series, we sit down with George Pitsounis, our Full-stack Developer from the Core team to explore his journey into software development, and his role in building and maintaining the technology behind our platform.
Can you tell us about your journey into software development and what ultimately led you to join Pluxbox?
“ I've been fascinated by computers for as long as I can remember. As a child I was always tinkering with software and trying to understand how machines worked under the hood, so studying computer science felt like a natural step. What really hooked me was web design and development: you can build something from nothing and see it working minutes later. I started out as a software engineer and gradually moved across the whole web development stack, because I wanted to understand how everything fits together, from the interface down to the servers it runs on.
Pluxbox appealed to me because the product is a technical challenge in itself. It's a no-code platform, so we aren't building one application. We're building the tools other people use to build theirs. That means a visual editor, real-time collaboration, workflows, integrations, and the infrastructure that runs all of it. But it's the team that made me stay. From day one it felt like home, and many of my colleagues have become friends. That's a big part of why I've been here for the past few years. "
As a Full-stack Developer in the Core Team, how would you describe your role, and what does it take to develop and maintain the core technology behind our platform?
“ My work covers the whole platform. One day I'm improving the flow editor so blocks are easier to arrange and connect. The next I'm in a backend service working out why something runs out of memory, or tuning our build pipelines so the team gets feedback faster. Being full-stack in the Core Team means following a problem wherever it leads, even when that crosses several layers.
It takes a few things. The first is understanding the system as a whole, because a small change in one place can affect environments, permissions or deployments somewhere else. The second is care: our customers build their own products on top of ours, so stability matters as much as new features. We also maintain two major versions side by side, which forces you to think about every change carefully. And when something breaks, you have to dig for the real root cause instead of settling for the first explanation that fits. “
At Pluxbox, we work together towards a shared vision. How has collaborating with your colleagues shaped your approach to software development, and what do you think makes teamwork essential to building great solutions?
" Working here has taught me that writing the code is usually the easy part. Understanding the problem correctly is harder, and that almost always comes from talking to people. A conversation with someone from product or support often changes how I'd approach a feature completely, because they see how customers actually use the platform.
Code review has shaped me a lot too. Colleagues regularly push back on my first solution, often by suggesting something simpler or narrower, and the result is nearly always better. I've learned to share my thinking early instead of showing up with a finished solution.
A platform like ours is too big for one person to hold in their head. Good teamwork means knowledge is spread across the team, decisions get challenged before they ship, and everyone can rely on each other when something urgent comes up.”
As software engineering continues to evolve, which skills and qualities do you believe will become increasingly important for developers in the years ahead?
" AI tools are changing how we write code very quickly. I use them daily, and they let me move much faster through the mechanical parts of the job. Because of that, I think the most valuable skills are shifting away from typing code and towards judgement.
The developers who stand out will be the ones who can define a problem clearly, understand the whole system, and judge whether a solution is actually right rather than just plausible. That means knowing how to verify things properly, keeping changes small and focused, and staying curious about root causes.
Communication matters more than ever as well. Explaining a trade-off to a colleague or a customer, or writing a clear ticket, is something no tool replaces. Finally, there's adaptability: the tools will keep changing, so being willing to keep learning is probably the most future-proof quality of all. "
Share this article