solvistas GmbH

Digital Agency

Show all Videos

Vanessa Fediuk, Software Developerin bei solvistas

Vanessa Fediuk von solvistas spricht im Interview darüber, wie sie zum Programmieren gekommen ist, was ihr im Unternehmen gefällt und gibt Tipps für Anfänger.

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

Video Summary

In “Vanessa Fediuk, Software Developerin bei solvistas,” Speaker: Vanessa Fediuk outlines her journey from high school and a pivotal Women-in-Tech day at JKU, through internships and part‑time work, to a master’s degree and joining solvistas, where she has worked for about two and a half years. She modernizes legacy systems in two client projects using Spring Boot and Angular, improves usability and functionality, and supports and organizes the company’s first‑month technical onboarding for new colleagues. She highlights solvistas’ flexibility, flat hierarchies, and direct customer contact, advising newcomers—especially those without an HTL background—to invest time, treat mistakes as learning opportunities, and seek support from teammates.

From curiosity to code: “Vanessa Fediuk, Software Developerin bei solvistas” on modernizing legacy systems, thoughtful onboarding, and learning by doing (solvistas GmbH)

Introduction: A devstory grounded in real work

In our DevJobs.at devstory series, the session “Vanessa Fediuk, Software Developerin bei solvistas” with Speaker: Vanessa Fediuk (Company: solvistas GmbH) stood out for its clarity. In a composed, grounded way, Vanessa maps a journey many engineers will recognize: a strong interest in science and technology at high school, a decisive moment that opened the door to computer science, a study path reinforced by internships and part‑time work, and a professional role that blends legacy modernization with mentoring new colleagues through onboarding.

What resonated most is how specific her touchpoints are: upgrading old software to modern stacks like Spring Boot and Angular; explicitly improving usability, user experience, and functionality; and structuring a first‑month, topic‑focused onboarding where newcomers have someone they can ask “anytime.” Layered on top is a workplace context she appreciates—flexibility, freedom, flat hierarchy, and direct communication with customers. Taken together, these points sketch a practical compass for early‑career developers and seasoned teams alike.

Choosing computer science: Interest becomes a decision

Vanessa starts with a familiar tension: she was already interested in “naturwissenschaftlichen, technischen” topics during high school but “hadn’t had much to do with informatics” yet. That gap—technical curiosity without hands‑on computer science—describes many potential entrants to the field.

A single event became her catalyst: a “Frauen in die Technik” day at JKU. That experience steered her “onto the informatics field,” and after graduating from high school she decided to start her studies. It’s a crisp reminder that orientation often comes from exposure. One encounter can flip a switch from broad curiosity to a concrete direction.

Takeaways

Exposure matters: Opt‑in moments like a women‑in‑tech day can turn interest into intent.
You can start without prior CS background: Vanessa underscores that it’s fine not to have deep informatics experience before choosing the field.
Decide through trying: Making the call “after graduation” shows it’s legitimate to decide once you’ve seen enough to be genuinely intrigued.

The practice bridge: Internships and part‑time work during studies

Vanessa’s path through university is anchored in practice: “I did a few Ferialpraktika and worked part‑time a bit.” These are more than résumé lines. They are bridges—building contacts, observing how technology is applied in real contexts, understanding rhythms and team processes that don’t show up in lectures.

After her master’s degree, she looked for a full‑time role and “luckily found” her way to solvistas “relatively quickly.” She has now been there for “about two and a half years.” Condensed as it sounds, this sequence spotlights the value of combining formal study with practical exposure: it tends to accelerate clarity and confidence when you enter the job market.

Takeaways

Internships and part‑time work shorten transitions: They help you make informed choices and build momentum.
Practice supports conviction: Real project experience gives you a more grounded sense of fit.
Speed comes from preparation: Early exposure stacks the deck toward a smoother landing after graduation.

What she builds: Modernizing old software with Spring Boot and Angular

Vanessa is refreshingly direct about her work: “I’m involved in two customer projects where we are renewing old software.” She lays out the approach succinctly—“use new technologies, now Spring Boot and Angular,” “switch to that,” and “improve usability and user experience a little,” “improve functionality a little.”

These phrases bundle three pillars that consistently define modernization work:

Update the technology stack (Spring Boot, Angular)
Improve usability and user experience
Sharpen and enhance functionality

Why this trio matters

Technology upgrades clarify structure: Moving to frameworks like Spring Boot and Angular signals an orientation toward maintainability and a more modern development workflow.
UX improvements center people: “Usability and user experience” are not afterthoughts—Vanessa calls them out alongside the tech stack.
Functional refinement aligns value: Modernization isn’t a 1:1 rebuild. Even “a little” functional improvement signals intent to make the product better, not just newer.

Two projects, one theme

Working across “two customer projects” suggests an environment of prioritization and dialogue. Later, Vanessa highlights flat hierarchy and direct customer conversations—context that dovetails with modernization’s realities: aligning expectations, validating UX improvements, and making technology choices legible to stakeholders.

Onboarding as a developer responsibility: Making the first month count

Vanessa also “does the onboardings” at her company. She explains what that looks like: in “the first month,” newcomers have “a bit of subject‑matter onboarding.” She “accompanies them a bit,” ensuring they “have support,” “always have someone they can ask,” and that she “organizes them a bit so they can get into projects more easily.”

Her description reveals three qualities of effective onboarding:

A defined, subject‑matter arc for the first month
Constant availability for questions—“anytime”
Light organizational scaffolding so newcomers join projects more easily

Why this works

A known arc reduces anxiety: A first‑month plan lets learners pace themselves.
Social anchoring removes friction: Availability turns questions into routine, not a last resort.
Guided entry accelerates contribution: Mild structure makes project contexts legible faster.

Taken together, Vanessa shows onboarding as a team practice: developers don’t just write code—they help others join the craft. That ethos aligns with her guidance on mistakes and support, making learning a norm rather than an exception.

Culture that enables: Flexibility, freedom, flat hierarchy, direct customer contact

Asked what she likes about her workplace, Vanessa is clear: “It’s so flexible. You have a lot of freedom … We have a flat hierarchy … you can talk a lot directly with customers.”

This paints a cultural foundation for her work:

Flexibility and freedom: Autonomy in tasks and approach
Flat hierarchy: Short paths, direct exchange, fewer barriers
Direct customer communication: Strong coupling between engineering and use cases

Why this matters to engineers

Autonomy breeds ownership: Freedom supports responsibility and quality.
Flat structures accelerate learning: Decisions are more transparent; feedback comes sooner.
Customer proximity sharpens priorities: Direct dialogue reduces misunderstandings and strengthens the user‑centric focus Vanessa highlights with her UX improvements.

Entering without HTL: Accept the curve, allow mistakes, seek support

Vanessa’s advice to those entering software without an HTL background is candid: “At the beginning it’s often a bit difficult to get in, especially if you don’t come directly from HTL. You have to put in a bit of time and a bit of energy.” Then comes a principle we found especially resonant: “The most important thing is to know that you can make mistakes. Everyone makes mistakes. I believe even the most experienced programmers make only mistakes. And the important thing is to learn from them and get support from colleagues.”

Her points translate into three core attitudes:

Embrace the learning curve: Invest time and energy
Normalize mistakes: Treat them as learning opportunities
Actively seek support: Colleagues are a resource

Practical steps for early‑career developers

Budget for learning: New stacks, processes, and team routines take time. That’s normal.
Ask questions early and often: Vanessa’s onboarding approach—“someone you can ask anytime”—applies broadly. Questions are tools.
Track your learning: Notes and small write‑ups reinforce growth and make you better at helping others later.
Prefer short feedback loops: Frequent check‑ins reduce uncertainty and surface misunderstandings fast.
Tie tech to UX and functionality: Vanessa’s emphasis on usability is a reminder—technology lives to serve users.

Themes that bind her story together

Looking at the throughlines in “Vanessa Fediuk, Software Developerin bei solvistas,” several themes stand out directly from what she said:

From interest to decision via exposure: A “Frauen in die Technik” day at JKU nudged her toward informatics and led to starting her studies after graduation.
Practice alongside study: Internships and part‑time work built a bridge to full‑time employment.
Modernization as a holistic effort: Update the stack (Spring Boot, Angular), improve UX, refine functionality.
Onboarding as shared responsibility: First‑month focus, constant availability, and light organization lower the barrier to contributing.
Culture matters: Flexibility, freedom, flat hierarchy, and direct customer contact empower engineers.
Mistakes are part of the craft: Even “the most experienced programmers” aren’t mistake‑free—learning and seeking support are what count.

From the DevJobs.at editorial desk: Actionable advice for developers

Drawing directly from Vanessa’s remarks, here are practical pointers you can apply:

Seek catalytic exposure.

Attend events or sessions that let you sample fields before committing.

Blend academia with application.

Internships and part‑time roles can sharpen judgment and confidence.

Cultivate a modernization mindset.

Consider stack upgrades and UX improvements in tandem.

Practice customer proximity.

Direct conversations clarify needs and align priorities.

Treat onboarding as a craft.

Offer to guide newcomers. You’ll consolidate your own knowledge and strengthen team culture.

Professionalize your mistake‑handling.

Share learnings, request feedback, and document decisions.

Pace yourself through the ramp‑up.

Especially without an HTL background, time and energy are your allies.

Guidance for teams and organizations

Vanessa’s points are not just an individual playbook—they outline what strong teams make visible:

First‑month, subject‑focused onboarding: Defined, encouraging, with a go‑to person for questions.
Flat hierarchies in practice: Shorten information paths and make decisions legible.
Enable direct customer contact: Bring engineers into conversations to align on needs early.
Nurture a learning‑positive culture: Reward questions, surface learnings, and offer support proactively.
Treat modernization as multi‑dimensional: Stack, UX, and functionality should move together.

Lines that linger: Quotes and key statements

A few of Vanessa’s formulations stuck with us:

“I’m involved in two customer projects where we are renewing old software … now Spring Boot and Angular … improve usability and user experience.”

“As a new employee we have a bit of subject‑matter onboarding in the first month … I accompany them so they have support, that they always have someone they can ask … organize them a bit so they can get into projects more easily.”

“It’s so flexible … We have a flat hierarchy … you can talk a lot directly with customers.”

“At the beginning it’s often a bit difficult … especially if you don’t come directly from HTL … The most important thing is to know that you can make mistakes … and get support from colleagues.”

Together, these lines sketch a stance where technology, people, and process reinforce each other.

Conclusion: A clear, encouraging compass for everyday engineering

“Vanessa Fediuk, Software Developerin bei solvistas” (solvistas GmbH) is a devstory laid out with crisp milestones: scientific‑technical curiosity in high school, a decisive exposure moment that led to informatics studies, early practice through internships and part‑time roles, and, ultimately, a position that combines modernization work with onboarding responsibility. The environment she values—flexible, autonomy‑rich, flatly organized, and customer‑connected—acts as an accelerant for good engineering.

For anyone seeking their footing in software, two lines from Vanessa’s story feel enduring: invest “time and energy” for the ramp‑up, and treat mistakes as normal, productive stepping‑stones. Combine that mindset with a modernization practice that pairs stack upgrades with UX and functional refinement, and you’ll not only renew software—you’ll continually sharpen your own professional edge.

More Dev Stories