What does an embedded engineer do? Living the Gyro Gearloose dream – Tony Kuitunen’s career story

In my daily work, I develop embedded systems, brainstorm new solutions, code close to the hardware, and even file patents. Kind of like Gyro but in real life. These solutions aren’t developed alone. My work requires constant problem-solving, learning, and collaboration across the organization.

The journey to becoming an embedded software engineer

My path wasn’t straightforward. I started studying information and communication technology at 25 with zero coding experience. At school, they said embedded development was the rockiest path, but I chose it anyway. Almost half of those who started dropped out.

After graduation, I faced the familiar problem: everyone wanted seniors, nobody wanted to train juniors. I ended up doing production testing, then project management, and finally became a partner in a startup. But nowhere did I actually get to code. Eventually, I decided to transition into coding.

That’s how I ended up in my current project as a consultant for a big device manufacturer, hired on my second attempt. My supervisor said they took a “big risk” – they’d never hired anyone so young, under 40, or at junior level before. Now I’ve been on the same project for five years, so the risk apparently paid off.

Why every line counts in embedded systems development

Many people don’t know how different embedded systems coding is compared to web development. You have to look at code completely differently when you’re so close to hardware. Resources are limited, and complex systems are extremely sensitive to faults, and often you can’t update the code afterward. Once a device reaches the customer, it needs to work for the next 20 years without restarts.

Problem-solving is at the heart of embedded development. Professional skill means being able to say: “I can replace that component with this piece of code.” Even if one component costs just 3 cents, the savings across hundreds of thousands of units is enormous.

Embedded specialists stay on projects for a long time because productivity only starts growing after 1–2 years. When you know the device and environment deeply, development becomes fast and smooth. I often start by reading processor datasheets and manufacturer example code that can be 30 years old. I spend a lot of time researching so it’s easier to approach the actual coding phase. First the big picture, then the doing.

Communication skills: The hidden superpower of embedded engineers

Professional competence doesn’t mean knowing everything. It means knowing where your limits are – and who you can ask for help.

Multidisciplinary expertise is at the core of the embedded world. We have physicists, automation engineers, and electronics-background developers on our team. Traditionally, it’s been easier to find a specialist in a certain field and teach them coding than to teach a coder electrical engineering or physics.

For me, this has gone the opposite way. I’ve learned tons on the job by asking, experimenting, reading forums and datasheets. For example, now I’m deepening my knowledge of motor control so I can discuss with experts as equals.

In the embedded developer role, communication skills are crucial. I definitely don’t code alone in a dark corner – I gather information and collaborate in many directions so we can find the best solutions together.

Embedded engineering as a consultant brings freedom and flexibility

Working as a consultant comes with prejudices about limited responsibility or being an outsider. My experience has been completely the opposite.

In my current client organization, I’ve gotten the same opportunities as permanent employees. Responsibility has grown, and now I’m leading a project again, but I also get to code.

In the consultant role, I feel free. I feel like I can choose every time whether to stay at work. Softability’s flexible culture and flat hierarchy suit me. When the client had trouble arranging necessary equipment for the workstation, I got it through the consulting company the next day. Support and security have always been available. That makes work meaningful and smooth.

What does the future of embedded software development look like?

I sometimes even feel guilty about how much fun I have at work. So my future continues in embedded development.

In the bigger picture, one interesting question is whether this multidisciplinary approach will survive. Will the next embedded developers still come from different backgrounds – or will we specialize more tightly in electrical or software engineering? I believe the field needs both. We need deep specialists, but also broad-thinking problem solvers.

And hopefully, there will always be room for a few new Gyro Gearlooses in the field.

Interested in working with us?

Are you also Gyro Gearloose of your own life and willing to push the boundaries in problems solving and coding? Check our career site and open job opportunities!