Full‑Stack, Cloud‑First, and Delivery Speed: Inside durchblicker.at with Andreas Deuschl

Context and highlights from “Andreas Deuschl, CTO von Durchblicker”

In the session “Andreas Deuschl, CTO von Durchblicker” (Speaker: Andreas Deuschl, Company: durchblicker.at), the CTO outlines how a compact engineering team in Vienna builds and scales a purpose‑driven comparison platform. Ten engineers, organized full‑stack, cloud‑first, and guided by pragmatic processes—always with the aim of delivering tangible value: helping users save money.

From the DevJobs.at editorial perspective, several themes stand out: a cohesive team structure without silos; a recruiting and onboarding journey that is both structured and human; and an engineering roadmap that elevates quality work—test automation, security, and architectural clarity—as enablers of speed rather than afterthoughts.

Team structure: Ten engineers, one product mission, real end‑to‑end ownership

The engineering team works from a downtown Vienna office. Today, it is ten engineers split into subteams. A small subteam handles internal infrastructure; the remaining engineers work with the Product Owner on the technical platform for the comparison portal.

The key design choice: genuine end‑to‑end ownership. As Andreas Deuschl puts it, “We are organized as full‑stack—within each team we cover frontend, backend, security, testing, and infrastructure.” Every engineer brings strengths, yet is encouraged to contribute across other disciplines and grow beyond a single specialization. Features are not handed over across silos; they are carried through from interface to UI, from provisioning to securing.

What full‑stack means here

• End‑to‑end thinking across frontend, backend, integrations (interfaces), infrastructure, and security.
• No rigid roles: strengths are recognized, while cross‑disciplinary contributions and development are expected and supported.
• Product proximity: working closely with the Product Owner keeps engineering focused on user value.

For talent seeking broad scope and ownership across the stack, this setup is particularly compelling.

Ways of working: Scrum with Scrumban elements and continuous improvement

The team uses Scrum—“adapted to our needs”—and also borrows from Scrumban. Retrospectives are used deliberately: “We look continuously at what we can improve, what fits us better, how we can work even better.”

This is less about subscribing to a framework and more about a learning posture. Agility here is situational and empirical. It fits an organization that wants to ship quickly while investing in sustainable quality.

Why this matters to engineers

• Process is a tool, not a dogma. The team keeps what helps and discards what slows.
• Retrospectives are mechanisms for real change, not calendar fillers.
• Scrumban elements support flow and flexible prioritization.

Company stage: Not a startup, not a corporation—maximizing engineer impact

“durchblicker.at is not a startup anymore, and not an established large company either.” That middle ground matters: there is structure without bureaucracy. For engineers, that translates into visible impact:

Couple that with a clear purpose—helping users save money—and you get a workplace that marries meaning with craftsmanship. It’s not an anonymous feature factory; it’s a platform where outcomes are real and used.

Hiring: A clear, human process focused on mutual fit

The hiring journey is straightforward and substantive, designed to let both sides assess expectations and collaboration.

1. A short introductory phone call with a recruiter.
2. A meeting with one or two engineers plus Andreas Deuschl, with ample time to get to know each other—personally and technically—and to check if “it’s a good match on both sides.”
3. A meeting with the two managing directors and founders of durchblicker.at.
4. A “meet‑the‑team” session—informal coffee or virtual coffee—to get to know the whole team.
5. When both sides decide to proceed, contracts are finalized.

The sequence creates realistic insight into the environment and culture. The informal “meet‑the‑team” step signals confidence and transparency: culture is best understood in conversation with the people you’ll work with.

What the hiring process reveals about the culture

• Transparency: you meet engineering peers and the founders.
• Time for real evaluation: mutual fit is prioritized over merely checking skills.
• Team involvement: the entire team can be met in an open, informal format.

Onboarding: Structure, mentoring, and a buddy as your anchor

Day one starts with a “welcome breakfast.” Your devices are prepared; you get time to set up and familiarize yourself with the development and work environment. A structured onboarding program follows, with a plan that “covers the different areas that are new” to someone joining.

A buddy is assigned—your mentor and trusted person—who guides you through the onboarding journey. Cross‑team formats such as “Meet the Teams” provide early exposure to not only engineering/IT but also to all company areas and the people behind them.

Why this onboarding works

• Clarity over chance: a plan to systematically explore the relevant areas.
• Mentoring with responsibility: the buddy is a dedicated point of contact.
• Early cross‑functional integration: meeting adjacent teams from the start accelerates collaboration.

Tech stack: JavaScript/TypeScript end‑to‑end and cloud‑first on Google Cloud

The primary stack is JavaScript and TypeScript, with JavaScript in the backend as well. The frontend is built with React and Next.js; the backend runs on Node.js. Core services run “as serverless containers in the Google Cloud Platform.” The rationale is clear: “We like to use cloud technology to keep our own effort as low as possible and to leverage the innovative possibilities of cloud technologies.”

What this stack offers

• A unified language ecosystem (JS/TS) across frontend and backend.
• Modern frontend foundations with React and Next.js.
• Scalable services with Node.js and serverless containers on GCP.
• Product focus by minimizing infrastructure overhead in the cloud.

For engineers who thrive in JS/TS and want to deepen their impact across the stack, durchblicker.at provides a coherent environment. The cloud orientation opens avenues into containerization and serverless patterns—while staying anchored to product outcomes.

Architectural work: Growth, boundaries, and sustained speed

With team growth, the organization wants to “cut the architecture well.” The aims are to manage technical debt alongside new feature development and to “remain fast in delivery even as we grow.”

That balance—tidying the inside while shipping to the outside—is the hallmark of healthy engineering. durchblicker.at calls it out explicitly and treats architectural clarity as a speed lever.

Guiding ideas we heard

• Architecture is a productivity multiplier: good boundaries enable independent work and faster delivery.
• Technical debt is not a taboo—it is managed consciously.
• Growth calls for scalable structures that preserve end‑to‑end ownership.

Delivery speed: Reducing lead time for change—with test automation as a lever

“We want to reduce the lead time for change—the average time from a commit, from source code, until it runs successfully in production.” This is a crisp statement: throughput time matters and is being actively improved.

A key aspect is test automation. “We can take the next steps and further increase the level of test automation.” More automation enables faster, more reliable delivery and underpins safer, more frequent releases.

Opportunities for engineers

• Build and strengthen automated tests across the stack.
• Improve throughput by raising confidence and shortening feedback loops.
• Contribute to delivery workflows that make speed and quality compatible.

Security: Continuous, adequate, and never an afterthought

Deuschl emphasizes: “We don’t want to neglect the security aspect and will stay on it continuously with adequate measures.” Security is part of the team’s full‑stack responsibility and is handled continuously rather than episodically.

What this likely means day to day

• Security considerations are integrated early and revisited regularly.
• Measures evolve as part of ongoing engineering work—similar to tests and architecture.

Without speculating beyond what was shared, one thing is clear: security is on the agenda and organizationally owned.

Product collaboration and interface work

Beyond frontend and backend, “interface topics” are a notable domain—integrations that are vital for a comparison platform. Close collaboration with the Product Owner ensures priorities are clear and technical execution remains aligned to product outcomes.

Engineers thus work not only on UI/UX and service logic, but also on data flows and integrations as part of their end‑to‑end responsibility. For people who enjoy systemic thinking and interface quality, this environment is a fit.

Why durchblicker.at is attractive to tech talent

Several strong reasons emerge directly from the session:

• Holistic ownership: full‑stack teams jointly own frontend, backend, infrastructure, security, and testing.
• Purposeful product: helping users save money is clear and measurable.
• Pragmatic agility: Scrum, Scrumban elements, and retrospectives that drive change.
• Transparent hiring: time for mutual fit, meetings with engineering and the founders, and an informal meet‑the‑team touchpoint.
• Strong onboarding: welcome culture, structured plan, buddy system, and early cross‑team exposure.
• Modern stack: JavaScript/TypeScript, React, Next.js, Node.js; serverless containers on Google Cloud Platform.
• Speed with quality: reducing lead time for change, expanding test automation, and sustained attention to security.
• Effective scale: neither corporate bureaucracy nor early‑stage chaos—structures that enable speed and real impact.

Who will thrive here?

• Engineers who think end‑to‑end and enjoy owning the stack.
• JavaScript/TypeScript developers interested in React/Next.js/Node.js.
• Practitioners who see test automation and delivery improvements as core engineering.
• Teammates who value security as a quality attribute.
• People who appreciate a human hiring process and cross‑functional collaboration.

Location and day‑to‑day: Vienna city center—proximity that powers flow

The team works “in our very nice office in Vienna’s city center.” Proximity accelerates decisions and knowledge sharing—especially in full‑stack setups where both code and human interfaces must be aligned quickly.

Day to day, product collaboration with the Product Owner, retrospective learning cycles, and a culture that embraces development—both personal and organizational—define the rhythm.

Memorable quotes

Closing thoughts: Purpose, process, and learning as the backbone of engineering

“Andreas Deuschl, CTO von Durchblicker” reveals an engineering organization built on clarity and impact: full‑stack teams with real end‑to‑end responsibility; processes that serve delivery; cloud technologies that free up focus; and a roadmap that treats quality—tests, security, architecture—as the foundation of speed.

For talent who want to shape rather than merely maintain, who enjoy JavaScript/TypeScript, who think end‑to‑end and take satisfaction in helping users save money, durchblicker.at offers substance—and a growth path designed to keep delivery fast as the team scales.

• 

  

  Raising Infrastructure Configuration to the next Level

  Johannes Brottrager von Durchblicker teilt in seinem devjobs.at TechTalk ein paar Tricks und Learnings, welche das Devteam gemacht hat, wie sie ihre IT Infrastruktur mit Terraform erstellt haben.

  Watch now
• 

  

  Out of the Dark, Into the Light

  Michael Karner von Durchblicker erzählt in seinem devjobs.at TechTalk über den Weg, wie das Team die gesamte Infrastruktur auf die Google Cloud Platform gewechselt hat – und welche Überraschungen es dabei gegeben hat.

  Watch now