From Interior Architecture to Front-End at evon GmbH: Sahra‑Marie Kreidl on late starts, fundamentals, and the creative core of coding

Why this devstory matters

Listening to “Sahra-Marie Kreidl, Front End Developer bei evon,” what stood out immediately was her combination of humility and precision about learning. She started university at 21, finished a vocational track in a completely different field before that, and then—nudged by her brother and a circle of friends—chose software development on purpose. The central message: a late start is no drawback if you respect the fundamentals, stay curious, and treat development as a creative craft.

She calls herself a “late bloomer,” describes Go as her first programming language, and notes that she quickly moved on to Python, JavaScript, and C#. Today she works in the MES team—described as a side product of “Gesamtkontroll”—primarily on the front end, with occasional backend tasks like building endpoints. The throughline is creativity: mockups, UI/UX thinking, and designing interfaces so end users aren’t overwhelmed by data.

In this DevJobs.at recap, we focus on the milestones and actionable insight she shared—practical guidance for newcomers and experienced engineers alike, distilled strictly from what she said in the session.

Switching fields at 21: from spatial design to interface design

The starting point is unconventional and instructive. Sahra-Marie first trained in interior architecture and completed that path. That already tells you something about her approach: finish what you start, build a foundation, then evolve. Parallel to that, her environment kept the tech door open: a brother who started programming early and friends involved in technical areas.

The trigger was simple and powerful—the desire to understand what others were talking about, and to be able to do it herself. That curiosity led her to study Business Informatics. Beginning at 21, she might look like a late starter on paper. In practice, it’s a sweet spot: old enough to make a deliberate decision, young enough to attack a steep learning curve with energy.

A polyglot beginning: Go first, then Python, JavaScript, and C#

Her first programming language was Go, which she used to learn the basics. Soon after came Python, JavaScript, and some C#. The result was breadth from the outset—a comparison space that helps decouple principles from syntax. When you’ve seen similar ideas expressed across languages, you understand faster what truly matters and what is stylistic preference.

That early cross-language exposure later becomes her core theme: focus on fundamentals and mental models that carry across stacks.

Team and role: front-end focus in an MES context

Sahra-Marie works in the MES team—described as a side product of “Gesamtkontroll.” Her primary responsibility is front-end development, while she also dips into backend work when needed, mentioning endpoints as an example. This T-shaped profile—deep in one layer, literate in adjacent ones—matches how modern product teams operate. It connects mockups, UI, and API design into coherent flows rather than stopping at layer boundaries.

Creativity as a throughline

For Sahra-Marie, software development is a creative process whether you are in the front end or the back end. There are many ways to reach the same goal, and the act of choosing a path is inherently creative. That becomes especially tangible in UI/UX work: drafting mockups, deciding what matters to the end user, and shaping information so the interface doesn’t feel overloaded.

She emphasizes design as responsibility—visual clarity, information architecture, and reduction. In that sense, the transition from interior architecture to front-end design feels like continuity rather than rupture: both disciplines create environments where people can orient themselves.

Fundamentals over recipes: the lever for complexity

Sahra-Marie’s most emphatic point is her insistence on basics. If you don’t understand the fundamentals, you can’t build complex systems. Programming naturally becomes more complex over time; the only viable path is a solid base.

The practical implication is straightforward: master core concepts—control flow, data structures, modularization, boundaries of responsibility—and you’ll be able to grow complexity gradually, test it, and refactor it. Without that base, every new language or framework becomes just noise. With it, technology turns interchangeable, and learning accelerates.

Don’t fear switching languages: concepts transfer

She challenges a common anxiety among beginners: the fear of picking the “wrong” language. Once you grasp the core concepts, switching languages becomes much easier—your knowledge remains and transfers. Her experience moving from Go to Python, JavaScript, and C# illustrates that point. It’s not about clinging to a syntax; it’s about learning the mental tools that outlast tools and trends.

This mindset reduces friction in teams and raises code quality: language fluency becomes a byproduct of concept fluency, and collaboration across stacks gets easier.

Practical learning paths: tutorials, code katas, and step-by-step progress

Beyond fundamentals, Sahra-Marie points to a concrete learning mix: online tutorials and code katas that guide you step by step. Small, self-contained problems build confidence and pattern recognition. The repetition inherent in katas helps you form a mental library of solutions you can later adapt to new situations.

The structure is the point: frequent, manageable exercises with clear feedback loops. That is how you internalize basics and prepare yourself to decompose larger, messier problems in real product work.

Front-end with intention: mockups, data load, and end-user focus

Her description of front-end work packs practical advice. Mockups are not decoration; they are thinking tools. They help you channel the data torrent and detect early where overload looms. Putting the end user at the center transforms information design into a trade-off: show enough to enable decisions without dumping everything at once.

This is particularly valuable in an MES environment, where many data points and states converge. Mockups allow stakeholders to align and react before you commit to code. They make priorities visible and testable.

Interface-to-API fluency: when the front end needs endpoints

Sahra-Marie’s aside about occasionally building backend endpoints is telling. It shows an appreciation for the dependency the front end has on stable, clear interfaces—and a willingness to help shape them. This isn’t about being a “perfect full-stack engineer.” It is about taking responsibility for the full user flow, including the contracts the UI relies on.

Concretely, endpoint literacy helps convert user-facing requirements into predictable data models and behaviors. That’s where fundamentals reappear: clarity in data contracts, consistent behavior, and sensible error paths directly influence the user experience.

Six takeaways engineers can act on

• Start when you’re ready—not when it’s “typical.” A deliberate decision beats arbitrary timing.
• Learn broadly to understand deeply. Comparing Go, Python, JavaScript, and C# sharpens your grasp of concepts over syntax.
• Design with intention. Treat mockups as thinking tools to tame data load and protect users from overload.
• Guard your fundamentals. Complexity is inevitable; basics turn it from a wall into a ladder.
• Switch languages without fear. Conceptual understanding transfers and speeds up new stack onboarding.
• Practice deliberately. Tutorials and code katas offer small, guided steps that build confidence and problem-solving muscles.

A realistic picture of the job: creative, learning-driven, and collaborative

What makes this devstory compelling is its realism. There’s no grandstanding—just a clear-eyed view of what matters day to day: learning, structuring, designing, and aligning. That explains why creativity isn’t presented as decoration but as the operating mode of engineering. It is visible in UI/UX, effective in backend design, and binding in team collaboration.

The bridge from interior architecture to software development feels natural in that light. Both fields create navigable environments for people. Both seek order in complexity. Both require empathy for perspectives and constraints. In this sense, Sahra-Marie’s path is less a break than a transformation: a new medium with a consistent mindset.

What we took from “Sahra-Marie Kreidl, Front End Developer bei evon”

From our DevJobs.at editorial perspective, the session with Sahra-Marie Kreidl (evon GmbH) delivered a cluster of pragmatic insights:

• Curiosity drives motivation—the wish to understand is a powerful engine.
• Language is a means, not an end—concepts are what endure across stacks.
• Design is responsibility—UI/UX determines whether complexity becomes usable.
• Learning is a process—small steps, repetition, and growing autonomy.

That combination builds resilience against changing trends and keeps you adaptable for new frameworks, team roles, or product lines. In an MES setting, where multiple data streams and roles collide, this mindset is not just helpful—it’s essential.

Turning her approach into your routine

Without adding new facts beyond her statements, you can convert Sahra-Marie’s approach into a concrete routine:

• Define your fundamentals. Pick a few core concepts you want to master and stick with them until they feel intuitive.
• Practice regularly. Short, frequent sessions with tutorials and katas compound into durable skill.
• Train transfer. Solve a problem in one language, then mentally map it to another. That’s how you cement concepts.
• Visualize early. Put mockups and flows on a page before writing code—this works for front end and for data/API flows.
• Build interface literacy. Even as a front-end engineer, understand endpoints and data models. It strengthens product thinking.

These five moves mirror the spirit of her talk—no gimmicks, just habits that scale.

Closing thought

“Sahra-Marie Kreidl, Front End Developer bei evon” is the story of an engineer who prioritizes fundamentals, treats creativity as core to software, and sees learning as an ongoing practice. The transition from interior architecture to code thus feels purposeful: from plans to prototypes, from rooms to interfaces, from conversations in a friend group to building things that others can use. For us at DevJobs.at, it’s an encouraging blueprint—useful for late starters and for anyone aiming at their next step in engineering at evon GmbH or beyond.

• 

  

  Scheduling Optimization in Practice

  Michael Missethan von evon teilt in seinem devjobs.at TechTalk ein paar theoretische Grundgedanken zur Logik von Terminplanung und zeigt ein interessantes Beispiel einer Optimierung.

  Watch now

• 

  

  Lorenz Pretterhofer, Application Engineer bei evon

  Lorenz Pretterhofer von evon gibt im Interview Einblicke in die vielfältigen Tätigkeiten als Application Engineer, wie er zu dem Job gekommen ist und was meiner Meinung nach für Neueinsteiger wichtig ist.

  Watch now
• 

  

  Luca Voit, QA Engineer bei evon

  Luca Voit von evon spricht im Interview über seinen Weg zum QA Engineering, wie sein Arbeitsalltag aussieht und was seiner Meinung nach wichtig für den Anfang ist.

  Watch now