Logo Elektrobit

Elektrobit

Established Company
Show all Videos

Aleksandra Konopacka, Software Engineer bei Elektrobit

Description

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.

By playing the video, you agree to data transfer to YouTube and acknowledge the privacy policy.

Video Summary

In “Aleksandra Konopacka, Software Engineer bei Elektrobit,” Aleksandra Konopacka explains how a love of math and logic—and inspiration from Iron Man—led her into tech, studying Automation and Robotics as well as Telecommunications, learning C++, and embracing problem solving. At Elektrobit she works on the Adaptive Autosar communication module that enables in‑car services to exchange data, delivering new features, maintaining the software, and supporting customers, and she values the creative, non‑monotonous work and supportive team. Her advice: start programming at university, learn together, practice hands‑on to see code effects, and keep skills current, aided by knowledge‑sharing sessions and Vienna “Technologiedocs.”

From Iron Man to Adaptive AUTOSAR: How Aleksandra Konopacka at Elektrobit builds automotive software with C++, teamwork, and a learning mindset

A DevJobs.at devstory recap

Listening to “Aleksandra Konopacka, Software Engineer bei Elektrobit,” we traced a path powered by curiosity, comfort with logical structure, and a moment of pop-culture inspiration. Aleksandra didn’t come from a school background packed with programming; instead, she loved mathematics and logic puzzles—and then came that first viewing of Iron Man.

“I remember the first time I saw Iron Man… Especially the scene where he makes the first suit from scratch. I thought it must be so great that people can make something out of nothing.”

That spark set the direction: technology. At university, programming was part of the curriculum, and the first language on the menu was C++. It was challenging, but it also opened doors. Aleksandra leaned in, kept pace with the material, and discovered that programming was her way to solve problems—and to change how she thinks. Later, she focused on telecommunications—networks, protocols, and aspects of cybersecurity. Today, she builds automotive software at Elektrobit, contributing to a communications module for Adaptive AUTOSAR, enabling in-vehicle services to talk to one another and exchange data.

This long-form recap captures the milestones, motivations, and practical advice that surfaced in her devstory—and what we, as the DevJobs.at editorial team, took away from the session.

The spark: math, logic, and a formative movie moment

The starting point is a love for structure: mathematics and logical puzzles. Programming didn’t play a big role in school. The decision came later—at university—nudged forward by a cultural moment that became a metaphor. Watching Tony Stark build the first suit “from scratch” resonated with a simple but powerful idea: creating something out of nothing.

  • Motivation: the thrill of building from zero.
  • Baseline: little programming in school, strong interest in logic and structure.
  • Decision: pursue a tech education that includes programming.

From there, the road is clear in intent but not without difficulty. The first hurdle: C++.

The tough first step: learning C++—hard, but formative

“Programming was one of the compulsory courses. We started with C++. That’s not the easiest language to learn. But there are many possibilities…”

As an entry point, C++ is demanding. Aleksandra underscores the challenge and, at the same time, its breadth of possibilities. The key was how she worked through it—focused, determined to keep pace, and intent on understanding the material.

“At the beginning it was quite challenging. But I focused on the course… I liked programming—how you can solve problems, and how it changes the way you think.”

What we distilled from this:

  • A hard starting language is not a handicap when problem-solving is front and center.
  • Programming reshapes your thinking—hypotheses, structures, testability.
  • Persistence turns a hurdle into a foundation for later specialization.

Academic foundations: automation/robotics—and a shift toward networks and security

Aleksandra grounded her technical base in automation and robotics. That foundation fosters a systems mindset—how software and hardware interact, how components fit together. She then focused on telecommunications: networks, protocols, and cybersecurity.

“I wanted to learn more about networks and network protocols. And also about cybersecurity.”

This brings two perspectives together: system-level thinking from automation/robotics, and the connective tissue of communications. For automotive software, that intersection is essential—vehicles today are networked systems where services need to interact reliably and securely.

Where she builds today: Elektrobit and the communications module for Adaptive AUTOSAR

“I work for Elektrobit, a software company. My team is part of the communications module for Adaptive Autosar. Thanks to this module, different services in the car can communicate with each other and exchange data. We implement new features and provide maintenance for our software. Additionally, we provide support for customers.”

In concise terms, Aleksandra describes the core of her work: building a communications module within the Adaptive AUTOSAR ecosystem—a foundation for structuring software in modern vehicles.

  • Purpose of the module: enable in-vehicle services to discover, talk, and exchange data.
  • Team responsibilities: develop new features, maintain existing code, and support customers.
  • Skills in play: C++, distributed thinking, attention to robustness and maintainability.

We want to highlight the mix of responsibilities. Feature work and maintenance are not an either–or; they’re two halves of a healthy product lifecycle. Support completes the triad: shipping modules also means shipping answers—about integration, stability, and expectations in real environments.

Why the work is fulfilling: creativity, variety, growth

“A regular person spends a third of their time working. It’s very important for me to like what I do. I love that I can use my creativity to solve different problems. I also like that it’s not monotonous, and I can develop my skills and knowledge.”

Three elements stand out:

  • Satisfaction and meaning: liking what you do matters when it takes a third of your life.
  • Creativity: problem-solving as a creative act—choosing among competing options to design workable solutions.
  • Continuous development: technology evolves, and so do competencies.

This explains why Aleksandra experiences daily work as varied. It’s not just about writing code; it’s about designing communication relationships that work reliably inside a vehicle.

Team culture: working together, learning together—and foosball breaks

“A great part of my work is my team, because people in my team are really smart and helpful. After work we also sometimes hang out and spend time together. My favorite activity during the break is table soccer.”

Teamwork here is tangible. Helpful colleagues, time together after work, and a favorite break activity—foosball—paint a picture of rapport and trust.

From our perspective, this culture accelerates quality. When knowledge is shared freely and relationships are strong, teams can build complex communications modules for Adaptive AUTOSAR with more resilience and better error tolerance.

Learning as a principle: university, learning by doing, and knowledge sharing

Aleksandra returns often to the topic of learning—both structure and practice.

“Programming started for me at university. I can recommend it because it gives an overview of different topics that can be useful for the future job. Also, students are very helpful. It’s great to learn together and share interests.”

University brings overview and a peer-learning environment. Just as important is the hands-on aspect:

“It’s important to learn by doing, because it’s the best way to learn and to check how changes in the code influence how the program works.”

This is the purest form of learning loops: change code, observe behavior, understand cause and effect. And it comes with a commitment to currency:

“To be good at your job, you must constantly develop your knowledge and skills and also stay up to date.”

How is that sustained in practice? Aleksandra mentions two formats worth spotlighting:

  • Knowledge-sharing sessions at Elektrobit where teams present experience and insights across topics.
  • “Technologiedocs” in Vienna, where people talk about automotive topics and learn more about them.

These routines embed learning into the schedule—not as an exception, but as a habit.

What we take away: guidelines for developers

From Aleksandra’s narrative, we extract actionable guidelines that resonate across career stages—from students to seasoned engineers.

1) Let curiosity lead, even if practice comes later

Little programming in school isn’t a blocker. Interest in structure and logic, coupled with the desire to build, becomes capability when anchored in the right learning environment.

2) Accept the hard start—C++ can be your training ground

Beginning with a demanding language can feel daunting. Aleksandra’s experience shows that with focus, the challenge becomes a toolbox. It changes how you think and how you break down problems.

3) Bridge disciplines

Automation/robotics and later telecommunications (networks, protocols, cybersecurity) complement each other in automotive contexts. Vehicle software is both connected and safety-aware—thinking across these dimensions leads to more resilient solutions.

4) Think in product lifecycles: feature, maintenance, support

Her team ships features, maintains software, and supports customers. That three-part model ensures solutions are not only built but kept robust and integrated into real environments.

5) Nurture team culture

Smart, helpful, connected—these aren’t optional soft traits; they’re productivity drivers. From pairing to knowledge sessions to foosball breaks, exchange builds trust, and trust accelerates decisions.

6) Learn in cycles: university, practice, sharing

  • University: overview, structure, and safe spaces for trying things out with peers.
  • Practice: change the code and observe behavior—learning by doing.
  • Sharing: sessions and “Technologiedocs” keep teams up to date by design.

A look at the day-to-day: communication as a system concern

Putting the pieces together, we see software work here through three lenses: communication, robustness, responsibility.

  • Communication: The Adaptive AUTOSAR communications module enables services in the car to find each other, talk, and exchange data. Without this, each function remains isolated.
  • Robustness: Feature development and maintenance interlock. Every addition must fit the existing system, respect service boundaries, and remain testable.
  • Responsibility: Customer support means guiding real integration scenarios—clarifying context and shaping software that works amid heterogeneity.

These three aspects are not add-ons; they are central to making automotive software reliable in practice.

Why “liking what you do” is more than a motto

Aleksandra states it plainly: a third of your life is spent working—liking the work matters. In her case, the satisfaction draws from creativity, variety, and growth. That combination fuels long-term motivation:

  • Creativity: productive freedom inside clear system boundaries.
  • Variety: feature work, debugging, customer questions—never only one mode.
  • Growth: new topics, shared knowledge, constant updates.

For us at DevJobs.at, this feels like a pragmatic career compass: choose roles where you solve real problems; environments where learning is built-in; teams where collaboration is real.

Quotes that stick

From “Aleksandra Konopacka, Software Engineer bei Elektrobit,” a few lines land with lasting relevance:

“I liked programming—how you can solve problems, and how it changes the way you think.”

“Thanks to this module, different services in the car can communicate with each other and exchange data.”

“To be good at your job, you must constantly develop your knowledge and skills and also stay up to date.”

They map to three anchors: love of method, product purpose, and a learning stance.

Practical nudges for your next step

Staying within the boundaries of what Aleksandra shared, here are concrete nudges:

  • Start where structure attracts you: math, logic, puzzles are valid on-ramps to software.
  • Choose learning settings that stretch you: a compulsory C++ course can be a catalyst.
  • Blend breadth with focus: from automation/robotics into networks and security.
  • Seek roles that cover the full product cycle: features, maintenance, and support.
  • Prefer teams that share knowledge—formally (sessions) and informally (breaks, games, conversations).
  • Learn at the code level: change, observe, understand cause-and-effect.

Vienna, “Technologiedocs,” and a learning ecosystem

Aleksandra explicitly mentions Vienna as a place where “Technologiedocs” take place—events where people discuss automotive topics and learn more. These formats anchor learning in the local ecosystem: teams and companies share perspectives, surface experience, and bridge theory with practice.

In sum, we see a loop: university as foundation, day-to-day work as a training ground, community formats as a catalyst.

Closing thoughts: a blueprint for builders who learn

Aleksandra Konopacka’s devstory shows how a developer’s path can form—out of curiosity and discipline, with challenging tools like C++, and with a domain that makes a difference: enabling services in vehicles to communicate.

In “Aleksandra Konopacka, Software Engineer bei Elektrobit,” three elements keep the compass steady:

  • the desire to break down problems and build solutions,
  • the commitment to continuous learning,
  • and the strength of a team that shares knowledge and grows together.

Cultivating these constants, builders can find work in automotive software that is both challenging and fulfilling—and shape technology that proves itself on the road.

More Tech Talks

More Tech Lead Stories

More Dev Stories