Intro
Who are you? What is your background? How long have you been with Scalefocus, and what has your journey been like?
I’m Dani, and I’ve been with Scalefocus for about a decade now. Fun fact, this is actually my first job. I’ve been into competitive programming since I was a kid, so getting into tech felt pretty natural.
I started as an intern right after finishing school, and things moved quickly from there: Junior, then Mid, then Senior. At some point, I stepped into a Team Lead role. Interestingly, the hardest part of that transition wasn’t the programming, it was the people side of things. Leading a team is a very different challenge, but also one I find genuinely interesting.
Tech & Career
What first sparked your interest in your field?
It all goes back to competitive programming. I’ve always enjoyed solving problems and pushing myself to think differently. That mindset carried naturally into my career.
You’re currently leading a team on an aviation project. What’s the core goal, and what does a typical day look like?
I’m part of a six-person team spread across Europe – four colleagues from Germany, one from Spain, and me from Bulgaria. We’re working on a predictive maintenance project in aviation.
In simple terms, the goal is to prevent major aircraft issues before they happen. We do this by analyzing flight data and identifying patterns, like recurring errors that could signal bigger problems down the line.
Day to day, that means working across multiple smaller projects, digging into data, and collaborating closely with the team to turn insights into practical solutions.
Why is this one of your favorite projects?
Collaboration is one of the best parts. The level of professionalism and mutual respect from the client side is something I really appreciate it makes a huge difference in day-to-day work.
Another thing I enjoy is how tangible the work feels. In previous industries I’ve worked in, Finance and Oil & Gas, the impact was important, but somewhat distant from everyday life. Now, it’s different. I can take a flight and know that I might be working with data from that exact aircraft. That connection to the real world is fascinating.
Also, the variety keeps things fresh. Our team handles around 30 smaller projects at any given time. Switching between them can be challenging, but it keeps you sharp.
What are the biggest technical challenges in aviation systems compared to other industries?
The sheer volume of data. Even when the data isn’t critical, the expectation is often to process and visualize it within the same day. That requires efficient systems and a consistently fast pace.
You’re not tied to a single tech stack. How did you become a multi-skilled engineer?
Over the years, I’ve worked with a wide range of technologies, starting with .NET, then Front-End, adding a little Java in the mix, and trying some niche technologies like Python. There you have it.
At this point, I focus on using the right tool for the job. Being multi-skilled is both a strength and a challenge. It gives you flexibility, but it also means you’re not deeply specialized in just one area.
What does being “multi-skilled” mean to you today?
To me, it’s about adaptability. At their core, most technologies are just different ways to solve problems. The more you work with them, the more similarities you start to see.
When it comes to AI, I see two camps. One believes the tools will do everything for us, so the specifics don’t matter. The other (where I stand) believes we still need to guide, validate, and optimize what AI produces. It’s evolving fast, and we’re all figuring out what that means in practice.
How do you build trust in a team with diverse technical backgrounds?
It comes down to honesty. It’s always better to admit when you don’t know something than to pretend you do. No one expects someone to know everything. True “unicorns” are extremely rare. Being transparent creates a much stronger foundation for teamwork.
What’s one emerging trend you’re experimenting with?
No surprises here – AI. It’s already reshaping how we work, and we need to learn to collaborate with it. I’m definitely keeping an open mind, because you can hear a lot ot different theories about it, but in its core it’s just a tool.
Culture & Growth
What keeps you motivated in such a fast-evolving industry?
It might sound cliché, but I still genuinely enjoy coding. That original spark hasn’t gone away. It doesn’t feel like a chore, it’s something I naturally gravitate toward. Because of that, motivation isn’t something I have to force. It’s just there.
If you had to describe your work style in three words, what would they be?
Curious, adaptable, pragmatic.
Beyond the Code
Favorite way to recharge?
Coding for myself. I know how that sounds, but I really do enjoy it. I also love traveling without a strict plan. Recently, I explored parts of Bulgaria partly on foot and partly by train. There were moments when I didn’t even know where I’d sleep. I just improvised along the way. That kind of freedom is refreshing.
One fun or unexpected fact your colleagues might be surprised to learn?
I’m a hobby chef, I collect watches, and I try to avoid loanwords when speaking my native language. Оh and the latest news – I officialy ride my own motorbike.
