From Struggling Student to Embedded Engineer: Insights from “Johannes Balog, Embedded Software Engineer at Elektrobit”

A beginning that doesn’t look like a natural-born coder

Watching the session “Johannes Balog, Embedded Software Engineer at Elektrobit,” one thing struck us immediately: Johannes doesn’t open with a polished origin story. In his first upper school year, computer science wasn’t his strong suit. Ten-finger typing? “Far away,” he recalls. And when the first semester focused on Word and PowerPoint, the grades reflected his lack of interest.

That honesty sets the tone. Instead of the “I’ve always been coding” narrative, Johannes shows how a small shift in perspective can change everything. In his second semester, he decides to fully commit—no matter what. Then chance plays its part: his teacher introduces C—at age 15. That’s the moment programming stops being abstract and starts to spark curiosity.

From our DevJobs.at seat, this is one of the session’s central messages: the first spark doesn’t need to happen in primary school. Sometimes the right entry point and a concrete task are enough to open the field.

HTL with an electrical engineering focus: Little coding, growing motivation

Johannes stays close to hardware through his education, attending an HTL with an electrical engineering focus. Programming is present, but scattered across the years. That’s why, after graduation, the desire to do “something with programming” gains momentum—ideally without losing touch with hardware. He reduces the options to two: pure computer science, or a track that still involves hardware—electronics, maybe mechatronics. He chooses electronics because he genuinely enjoys working with hardware.

This decision shapes his path. It also explains why the next step—a university of applied sciences degree in electronics—becomes so significant. Johannes points out that his initial programming knowledge was quickly exhausted: after two weeks, “everything was new.” That steep learning curve later matters when he explains how deeply he dives into topics and why formal study supported him.

Three years at the university of applied sciences—and the bridge to Elektrobit

The bridge into industry comes through his studies: Johannes gets to Elektrobit via his program. To put it simply, Elektrobit “produce software for the automotive sector or the automotive industry.” The Vienna site specializes in in-car communication technologies—the data flows that move through a vehicle.

For us, this answers his earlier dilemma—pure computer science or with hardware lean-in—almost automatically. Embedded software in the automotive domain, driver development for bus protocols, in-car communication: it’s the blend of software engineering with pronounced hardware sensibilities. The broader perspective he built fits the job.

First assignment: FlexRay driver maintenance as a deep dive

Johannes’ first concrete project is memorable: maintaining a FlexRay driver. FlexRay sits alongside CAN and Ethernet in the space he references—and he calls this his first “real” project. Maintenance often sounds routine. In this session, it comes across as an accelerator. Maintenance means reading, understanding, and reconstructing decisions—absorbing system knowledge that later pays off when you build new things.

From our vantage point, Johannes confirms a learning path many underestimate: maintenance as the school of robustness, readability, and architectural insight. You don’t just use a codebase; you truly comprehend it.

Projects, maintenance, variety: “No day is like the other”

In his role, Johannes and his team move between new projects and maintenance—a rhythm that sets both pace and perspective. He experiences this variety as a strength:

Variety also means onboarding, reading, and continuous ramp-up. He describes it as core to the work to repeatedly learn new things, to be confronted with state-of-the-art topics, and to develop your own problem approaches. This mix of self-study, system understanding, and solution architecture defines day-to-day embedded development at Elektrobit—at least as Johannes lives it.

Two takeaways stand out:

• Learning is not a bonus; it’s the tool. If you like diving in, you’ll thrive here.
• Variety is both reward and demand—curiosity and the satisfaction of concrete outcomes provide the energy.

Working master’s: A one-year project—a win for both sides

A defining chapter in Johannes’ development is his working master’s. Elektrobit provides the framework for him to complete the practical portion of his degree inside the company. Materials, environment, and tasks are there. He gets a one-year project out of it; he gets focus; the company gets results.

We see this as a mini blue-print: when study and work reinforce each other, both benefit. Theory meets practice, and practice gains structured depth. For developers in similar situations, this can be the lever that anchors knowledge while creating value at the same time.

“Go deep” as an attitude: Why formal study made the difference for Johannes

Johannes also addresses the perennial question: study, self-taught, bootcamp—what’s the best way in? His answer is lived and nuanced: there is no silver bullet. For him personally, formal study was the key, because his prior knowledge had limits and his role at Elektrobit requires deep understanding.

At the same time, he references a colleague who learned a lot via YouTube tutorials and books. Self-study can work—especially today with resources everywhere. What matters is the individual and the role. Where deep system knowledge is required, structure helps—this is his experience.

Actionable takeaways for developers

Several clear, practice-ready lessons emerge from Johannes’ story—drawn directly from what he shared:

• Start where you are—and make it concrete: Johannes’ turning point was a firm decision and a tangible goal (learn C, build small examples). Specific exercises beat abstract ambitions.
• Treat maintenance as a fast lane to system mastery: His first project—FlexRay driver maintenance—helped him understand an existing system in depth. That’s where architecture-level insight accumulates.
• Build depth, not just tool familiarity: In his environment, deep knowledge counts. You can get there through a degree—or through disciplined, structured self-study. The measure is depth, not labels.
• Combine software with hardware if that excites you: Johannes’ path into in-car communication and driver work shows how a love for hardware can guide software choices.
• Learn continuously—and plan for it: “Reading in” and “learning” are part of his daily work. Treat these phases seriously to turn variety into a strength.
• Seek environments that support learning: The working master’s with strong company support shows how context can accelerate your learning curve.
• Accept that there’s no universal route: A colleague leaned on YouTube and books; for Johannes, formal study was better. The best path is the one you can sustain.

The path, step by step

To keep Johannes’ journey tangible, here’s the sequence as he sketches it in the session:

1. First upper school year: computer science does not go well; focus is on Office tools. Motivation—and grades—are low.
2. Second semester: a choice to double down—and a lucky break: learning C at 15. He builds small programs at home.
3. HTL in electrical engineering: programming remains occasional and scattered. The desire grows to “do something with programming,” ideally with a hardware angle.
4. After graduation: choosing electronics over pure computer science or mechatronics, because hardware work is enjoyable.
5. Three years at a university of applied sciences: within weeks it’s clear there’s a lot to learn. The path to Elektrobit emerges via the program.
6. Entry at Elektrobit: software for the automotive industry; at the Vienna site, a focus on in-car communication. In his team: development of device drivers for bus protocols like Ethernet or CAN.
7. First project: maintenance of a FlexRay driver—a deep dive into an existing system.
8. Working master’s: completing the practical part inside the company, one-year project, materials provided—benefits for both sides.
9. Today: a steady alternation between projects and maintenance, “no day like the other,” continuous immersion in state-of-the-art topics, developing problem approaches.

Onboarding as a core skill

Johannes stresses onboarding and ramp-up as a mindset. It’s more than reading. It means building context, checking assumptions, and turning insights into actionable problem approaches. In a space defined by in-car communication and bus protocols, that depth of understanding is the foundation for sensible decisions—whether you’re maintaining or building anew.

From our editorial view, that’s the developer stance that makes teams resilient: no fear of new topics, the willingness to enter systems with structure and patience, and the discipline to convert understanding into concrete next steps.

“Pretty cool”: Why variety motivates

Johannes sums up his workday impression in two words: “pretty cool.” It’s a fitting conclusion to the story he tells: variety, learning curves, and tangible results. We recognize a familiar pattern among engineers: a sense of meaning emerges from the mix of challenge and freedom to act; motivation comes from visible progress.

Degree or self-taught? The useful answer: “It depends”

The perennial developer question gets the most honest answer: it depends. Johannes’ path—HTL in electrical engineering, then a university of applied sciences in electronics, then Elektrobit, then a working master’s—shows how well formal structure can work when a role demands deep understanding. His colleague’s self-taught success shows the other side: with the right habits and resources, it’s possible to build the needed depth outside academia.

Rather than pitting options against each other, evaluate the role’s demands and your learning habits: do you benefit from structure, or does intrinsic motivation carry you? In both cases, consistency beats short bursts.

What we’re taking away from “Johannes Balog, Embedded Software Engineer at Elektrobit”

To wrap up, here are the core insights we’re carrying forward—an invitation to design your own path deliberately:

• Create turning points: a semester, a teacher, a language—and committed practice at home. That’s how many engineering journeys begin.
• Depth over surface: whether via a degree or self-study, what counts is how deeply you understand your domain. Johannes’ environment demands it.
• Maintenance as a learning engine: existing systems reveal architecture and quality—and make you robust in new projects.
• Embrace variety: “no day like the other” is demanding—and “pretty cool.”
• Find learning-friendly environments: if you study, look for companies that enable practical projects. If you self-learn, build structures that keep you going.

In a fast-moving field, Johannes Balog offers a calm, constructive message: there is no holy grail. There are decisions, practice, projects—and the willingness to repeatedly ramp up on new topics. That’s where a sustainable career takes shape.

Final thought

Embedded software for the automotive industry, in-car communication, drivers for bus protocols like Ethernet, CAN, or FlexRay—this sounds highly technical. In Johannes’ telling, it’s above all a path shaped by curiosity and follow-through. Perhaps that’s the most important insight from “Johannes Balog, Embedded Software Engineer at Elektrobit”: find your entry point, go deep, and a shaky start can turn into a remarkably steady career.

• 

  

  Introduction and Trends in Automotive Software

  Dr. Georg Gaderer von Elektrobit gibt in seinem devjobs.at TechTalk einen Überblick zum Thema Automotive Software und spricht über zukünftige Trends in diesem Gebiet.

  Watch now

• 

  

  Dr. Michael Ziehensack, Vice President Automotive Networks bei Elektrobit

  Vice President Automotive Networks bei Elektrobit Dr. Michael Ziehensack erzählt im Interview darüber, wie die Devteams im weltweiten Unternehmen die Software entwickeln, was dort Herausforderungen sind und auf was der Fokus beim Recruiting liegt.

  Watch now
• 

  

  Nikolaus Donath, Technology Team Manager bei Elektrobit

  Nikolaus Donath von Elektrobit gibt im Interview Einblicke in die Rolle als Technology Team Manager und spricht über den Aufbau des Teams.

  Watch now

• 

  

  Aleksandra Konopacka, Software Engineer bei Elektrobit

  Aleksandra Konopacka von Elektrobit spricht im Interview über ihren ursprünglichen Zugang zum Programmieren, was ihre aktuelle Arbeit beinhaltet und gibt Hinweise für Anfänger.

  Watch now
• 

  

  Michael Wegner, Senior Software Developer bei Elektrobit

  Michael Wegner von Elektrobit erzählt im Interview über seine Tätigkeit als Developer für Automotive Software, welche Challenges es hier gibt und gibt Tipps für Neueinsteiger.

  Watch now
• 

  

  Kostiantyn Sobakar, Scrum Master bei Elektrobit

  Kostiantyn Sobakar von Elektrobit betrachtet im Interview die interessanten Aufgaben und Herausforderungen in der Rolle als Scrum Master – und warum Humor hier am allerwichtigsten ist.

  Watch now
• 

  

  Miriam Leopoldseder, Software Engineer bei Elektrobit

  Miriam Leopoldseder von Elektrobit erzählt im Interview über ihren Background im Programmieren, gibt Einblicke in das Embedded Hardware Development Team, in dem sie aktuell arbeitet und gibt Tipps für Neueinsteiger.

  Watch now