solvistas GmbH

Digital Agency

Show all Videos

Daniel Fasthuber, Front End Developer bei solvistas

Daniel Fasthuber von solvistas redet im Interview darüber, wie er als Quereinsteiger zum Programmieren gekommen ist, wie sein Arbeitsalltag im Front End aussieht und gibt Tipps für Beginner.

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

Video Summary

In "Daniel Fasthuber, Front End Developer bei solvistas," Speaker Daniel Fasthuber shares his career‑change journey: he discovered a passion for programming, studied business informatics at the University of Vienna, began as a full‑stack developer, then moved to front end for more creative work and ultimately joined solvistas. He explains building UI/UX in close collaboration with designers and coordination with the backend, meticulously translating designs, and why solvistas stands out—a young team, flat hierarchy, and supportive colleagues. His advice to newcomers: don’t give up; the start is tough, rely on colleagues, self‑motivate, read widely, and keep at it.

From Career Switch to Front‑End Craft: Daniel Fasthuber (solvistas GmbH) on Practice, UI/UX, and Staying the Course

A DevJobs.at editorial take: Why this devstory resonates

“Daniel Fasthuber, Front End Developer bei solvistas” is a title that already points the way. In his devstory, Daniel shares a clear, down‑to‑earth view of how he transitioned into software, why hands‑on work drew him more than theory, and what makes front‑end work so fulfilling for him: its closeness to UI and UX. For us at DevJobs.at, the story stands out because it crystallizes what many engineers live through: the rough start, the daily push for quality interfaces, the human glue of teamwork—and the realization that persistence and a learning mindset are often your most valuable assets.

In the following, we recap what we heard from Daniel and translate his key points into concrete, everyday takeaways—useful for newcomers and experienced developers alike who want to sharpen their front‑end practice.

A late start with a clear compass: Finding passion, setting a course

Daniel calls himself a career switcher. He didn’t start out with programming as an obvious path; the decision came “in [his] mid‑20s,” sparked by a discovered passion for coding. He then enrolled in Business Informatics at the University of Vienna, only to realize that he’s “more of a practitioner” and moved into a job:

“Ich bin ein Quereinsteiger, habe mir Mitte 20 überlegt, in welche Richtung ich mich entwickeln möchte. Habe die Leidenschaft für das Programmieren entdeckt, habe mich dann auf der Uni Wien für Wirtschaftsinformatik studiert. Habe aber dann entdeckt, dass ich eher der Praktiker bin und mir einen Job gesucht.”

There’s a lot in this short passage for anyone facing similar crossroads:

Passion needs direction: Daniel deliberately thought about where he wanted to grow, rather than simply drifting from one opportunity to the next.
Academic paths can provide orientation—yet they need not be the only or final stop. The key is honestly knowing how you work best: Are you driven by research or by making? By theory or by practice?
Moving into a job is not a break with education; it’s continuing to learn—just in a different mode.

Early practice: From full stack beginnings to a creative front‑end focus

Daniel’s first on‑the‑job experience was as a full‑stack developer. That broad vantage point often attracts career switchers early on: you get to try a lot, see how pieces fit together, and understand how front end, back end, and data flows interact. But Daniel soon realized one part of the work appealed to him most—the creative task of shaping what users actually see and touch.

“Habe dann meine ersten Erfahrungen gesammelt, als Full-Stack-Developer. Habe aber gemerkt, dass ich eher kreativer arbeiten möchte und mir dann einen Job gesucht als Front End Entwickler …”

This move is more than a title change. It marks a shift in perspective:

From breadth to depth: Rather than “a bit of everything,” Daniel specializes in the discipline that intrinsically motivates him—the front end.
From internals to the surface: Not because back end is less important, but because the direct encounter with users (UI/UX) is his strongest driver.
From generalist to shaper: The intent to implement designs “meticulously” demands an eye for detail—and that pursuit is where creativity so often meets engineering rigor.

Finding the right home over several stops

Daniel mentions reaching solvistas GmbH “over several stations.” Many of us know that pattern—and it can be a strength. Different environments, teams, and product contexts sharpen your understanding of where you create the most value and what kind of setup helps you do your best work. For Daniel, that environment is now solvistas.

Front end as a team sport: UI, UX, and the art of alignment

Asked what front‑end work is about, Daniel’s answer is pragmatic and team‑centric:

“Also als Front End Entwickler, wie es schon heißt, kümmern wir uns um das Front End, die UI, die UX. Wir arbeiten eng mit den Designern zusammen, aber auch in Abstimmung mit dem Back End Team natürlich. Wir schauen, dass wir optimale Benutzeroberflächen hinkriegen, die dem entsprechenden Design entsprechen und den Kunden zufrieden stellen.”

Several core facets emerge here:

UI/UX as the compass: Front end isn’t “just implementation,” it’s turning design intent and product goals into the best possible user interface.
Tight loops with design: Design isn’t merely a set of pictures; it frames how front end decides on motion and interaction.
Alignment with back end: Solid UI/UX relies on reliable data, sensible APIs, and performance. Without back‑end sync, even the most polished UI feels empty.
Outcome orientation: “Optimal user interfaces” means meeting the design’s intent and the customer’s expectations. The benchmark is whether it all works—visually, interactively, and in day‑to‑day use.

Design fidelity in practice: “Meticulously implementing the designs”

When Daniel talks about the craft, he emphasizes something many teams know but not all uphold daily: design fidelity—the precise implementation of design artifacts. As he puts it:

“Besonders gefällt mir die enge Zusammenarbeit mit den UI Designern. Wir schauen, dass wir gerade im Front End eben penibelst die Entwürfe umsetzen und da eben auch dieses ganze Grafische und Designtechnische mit einbauen und das umsetzen, wie es auch für den Kunden dann UI, UX mäßig ideal ist.”

That’s a statement of craft discipline. In everyday work, it points to:

Precision as a mindset: Pixel‑level accuracy isn’t vanity; it’s a mark of respect for the design effort and a way to meet user expectations.
Consistency as quality: Typographic rhythm, spacing, and component patterns aren’t “decoration.” They drive clarity and usability.
UI/UX as an integrated task: “Graphical and design‑technical” aspects aren’t afterthoughts. In front end, they are the work.

For teams, this implies investing in shared standards, crisp design hand‑offs, and a culture that values details.

Collaboration as force multiplier: Designers and back end at the same table

Daniel links two collaboration planes: the tight feedback loop with UI designers and the coordination with the back end. The real leverage shows where those planes meet—when interaction design, visual language, and data flow line up. Front end often sits at that seam: close to users, translating intentions from design, and grounded enough in the system to account for back‑end realities.

Practical guidelines that follow from his description:

Sync early: The earlier front end, design, and back end align expectations, the fewer friction points emerge in late sprints.
Translate in both directions: Front end communicates design intent to the back end—and back‑end constraints back to design.
Treat quality as shared responsibility: An “optimal user interface” is not a solo act. It’s crafted in coordinated team play.

Culture as a productivity engine: What Daniel appreciates at solvistas GmbH

Daniel draws a clear picture of his current environment:

“Die Solvistas ist für mich ein spezieller Arbeitgeber im Vergleich zu anderen Arbeitgebern, wo ich schon war. Wir sind ein relativ junges Team, sind in einer flachen Hierarchie aufgestellt, also wir sind alle bei Du. Jeder versteht sich gut miteinander und man hat immer einen Ansprechpartner, ein offenes Ohr für diverse Anliegen, privat oder beruflich hauptsächlich. Das schätze ich sehr.”

Four aspects stand out:

A young team: Energy and a willingness to learn—crucial when continuously refining front‑end practices.
Flat hierarchies: Short paths, direct feedback, fewer hand‑over hurdles.
First‑name basis: An atmosphere of proximity can ease communication—especially when fine‑tuning UI/UX details.
An open ear: When both professional and private concerns can be voiced, trust grows—and trust makes quality feedback possible.

To us, this underscores a simple truth: technical excellence rarely thrives without interpersonal excellence. When culture and structure work, people like Daniel can bring their attention to detail to full effect.

The honest early‑career reality check: Struggle first, then steady progress

Daniel offers candid advice to developers at the beginning of their careers:

“Auf jeden Fall nicht aufgeben. Der Einstieg ist schwer, man struggelt am Anfang, man braucht viel Unterstützung von den Kollegen. Da muss man einfach durch. Es wird besser mit der Zeit. Man muss sich selber auch motivieren, viel einlesen und einfach am Ball bleiben.”

That crisp advice translates into actionable cues:

Expect the learning curve: “The entry is hard.” That’s not a personal failure; it’s the default. Budget time and patience for it.
Seek support proactively: Help from colleagues isn’t charity; it’s part of the craft. Ask early, ask specifically, show gratitude—and pay it forward later.
Build self‑motivation: No one learns for you. Set up reading and practice routines that fit your life.
Stay the course: Consistency beats intensity. Those who learn and ship regularly win over time—just as Daniel says.

Practice prompts: Putting Daniel’s insights to work

Daniel’s compact devstory lends itself to simple, everyday routines. Directly derived from his statements, here are a few prompts you can apply now:

1) Focus your front‑end strength

If UI/UX energy motivates you, start tasks by clarifying the user‑facing goal—not just implementation steps.
Treat design artifacts as your single source of truth and explicitly allocate time for high‑fidelity implementation.

2) Tighten design feedback loops

Schedule consistent check‑ins with UI designers to catch misunderstandings early.
Use visual comparisons (e.g., reviewing implementation against design) to make “meticulous” fidelity tangible—always in service of the intended user experience.

3) Systematically align with the back end

Clarify data needs and interfaces early: what does the front end require to make interactions smooth and comprehensible?
Treat constraints as design input: when something is hard server‑side, surface it and explore alternatives together.

4) Contribute to a healthy team culture

Practice the “open ear” you want to receive: listen well, ask follow‑ups, share uncertainties, and celebrate small wins.
Keep feedback paths short: lean on flat hierarchy and first‑name culture with frequent, lightweight syncs and transparent decisions.

5) Strengthen your learning routine

“Read a lot” suggests a two‑step cadence: absorb, then apply. Make time to study patterns and tie them to immediate tasks.
Track what you’ve learned—and what you haven’t. Over time, this list becomes your personal roadmap.

Mental checkpoints for front‑end quality

Daniel’s emphasis on UI/UX and fidelity invites a few simple self‑checks:

Does my implementation reflect the design’s intent—visually and in the interaction flow?
Can a new user understand what to do without extra explanation? If not, which UI decision contributes to the friction?
Are design and back end engaged early enough that we spot issues while they’re still small?

These questions focus the daily craft. They fit Daniel’s framing of front end as the visible interface to customers—and precision and collaboration as the two levers that make that interface strong.

What this devstory means for career switchers

Daniel shows that a later start is no handicap. What matters is:

An honest view of your motivation (“passion for programming”)
The readiness to leave theory when practice calls (“more of a practitioner”)
The focus on the discipline that pulls you most (from full stack to front end)
The resilience to get through the early phase—with support, self‑motivation, and patience

Together, these elements form a path that need not be linear to be reliable. Internalize them, and you build a foundation for growth—whether in a young, flat team like solvistas GmbH or any environment that values collaboration and meticulous craft.

Quotes that stick with us

“Ich bin ein Quereinsteiger … habe die Leidenschaft für das Programmieren entdeckt …”
“… entdeckt, dass ich eher der Praktiker bin und mir einen Job gesucht.”
“… erste Erfahrungen als Full‑Stack‑Developer … eher kreativer arbeiten … Job als Front End Entwickler …”
“… kümmern wir uns um das Front End, die UI, die UX … enge Zusammenarbeit mit den Designern … Abstimmung mit dem Back End … optimale Benutzeroberflächen …”
“… penibelst die Entwürfe umsetzen … grafische und design‑technical aspects … UI/UX ideal …”
“… relativ junges team … flat hierarchy … first‑name basis … open ear …”
“Auf jeden Fall nicht aufgeben … Einstieg ist schwer … support from colleagues … self‑motivation … read a lot … stay on the ball.”

These lines are compact—precisely why they’re powerful. They describe a professional stance anchored in clarity, care for detail, and teamwork.

Closing: Front end as visible quality—and why perseverance wins

The session “Daniel Fasthuber, Front End Developer bei solvistas” shows how a career switch can become a strength when passion and a love for practice meet. It reminds us that front end is more than visual build‑out: it’s the precise translation of design intent into tangible value—powered by close collaboration with design and back end.

Our key learning at DevJobs.at from Daniel’s path: excellent user interfaces are forged where people stick with it over time, seek and give help, and treat meticulous detail not as nitpicking but as service to customers. Share that compass, and—with patience—you’ll reach what Daniel exemplifies today: a role where creativity and practice interlock, and where your work makes a visible difference every single day.

More Dev Stories