Why Communication Is Just as Important as Code – Ronell on His Role as a Software Development Engineer
For Ronell, communication isn’t just a “soft skill”—it’s a central part of good software development. As a software development engineer at Vector, he develops and modernizes software solutions that allow customers to configure and use Vector hardware—and sees firsthand every day how crucial communication, teamwork, and clear coordination are for achieving good results. In this People Story, he talks about his job, his team, and why code alone isn’t enough.
Please introduce yourself briefly and give us an insight into your responsibilities at Vector.
Hi, I’m Ronell and I work at Vector as a software development engineer on the Firmware and Software Development team within the Measurement & Calibration (PMC) product line. My job revolves around the development and enhancement of our VXtools. These are software solutions that allow our customers to easily configure and use their Vector ECU interface.
What excites you about your work?
I love that I can analyze complex problems and develop solutions from them. To me, it feels like a puzzle. And when everything works in the end, it’s just a great feeling!
What did you study? How did you end up at Vector, and what convinced you to join the company back then?
I earned my bachelor’s degree in Medical and Technical Informatics and my master’s degree in Human-Centered Computing at Reutlingen University.
I first encountered Vector at a job fair. I was immediately impressed by the open nature of the employees and how they talked about their projects. You could tell that teamwork and innovation are truly lived here. I started with an internship during my third semester as part of my practical semester. Even then, it was clear that it was a good fit. Exciting tasks, a supportive team, and the chance to take on responsibility. That’s why I stayed as a working student after my internship, throughout my bachelor’s and master’s programs. And today, I’m a permanent member of the team.
What are you currently working on?
My day revolves around the development and enhancement of our VXtools. These are software solutions that make our hardware products intuitive for customers to use. I typically start with a quick team check-in to align priorities. Then I get to work on programming. I develop new features, improve existing functions, and test to ensure everything runs smoothly.
Lately, I’ve been focusing intensively on the new CMP device product family. CMP stands for Capture Module Protocol. This hardware is used in vehicle development to network control units and exchange data. My task was to integrate this new hardware into our tools. A highlight for me was connecting new communication protocols to the VXconfig interface. This allows our customers to conveniently configure various vehicle networks. The concept works really well and is now successfully in use. Currently, I’m working with my team on modernizing our VXtools. We’re expanding the user interfaces to make them clearer and more intuitive, while simultaneously building a platform-independent backend.
What do I particularly like? The teamwork. We brainstorm, test ideas, and work together to take our products to the next level.
How would you describe teamwork or the atmosphere at Vector?
The atmosphere in our team is really relaxed and open. And if you ever get stuck, help is always there. We share knowledge, brainstorm together, and have a lot of fun doing it. You don’t feel alone, but rather part of something bigger. That makes the work not only productive but also really enjoyable.
We often discuss the development of new features while tossing a football around. Moments like these show just how relaxed yet focused our teamwork is.
What do you particularly appreciate about the way of working and the working conditions at Vector?
What I really appreciate at Vector is the flexibility. If I want to, I can work in a hybrid model. For example, I start the day at home to avoid rush hour on the highway and drive into the office later. The same goes for the evenings, of course.
Another thing I love: ideas matter here. When I suggest trying out a different technology, it’s taken seriously. I can test things and take on responsibility – even as a new graduate. And this trust makes you feel truly valued.
What would you have liked to know about your profession while you were still in school?
I would have liked to have known back in school how important communication is. Not just writing code, but also preparing for meetings and explaining decisions. In the beginning, I was often so fixated on solving a problem on my own that I wasted a lot of time. I could have simply asked a colleague and gotten things done much faster.
My tip: Talk to each other. Especially in the beginning, you lack experience. By exchanging ideas, you reach your goal much faster. We’re a team, and that makes all the difference. If you want to practice this while you’re still in school, actively participate in group projects. Don’t just talk about the code – explain your decisions and ask for feedback. This helps develop exactly the skills that will be crucial later in your career.
(The video is in German, please select English subtitles in the settings.)