Inside Kontron Technologies: Cross‑functional teams, pragmatic Scrum, and a broad tech stack with Klaus Ettmayer

Highlights from “Klaus Ettmayer, Bereichsleiter IoT Produkte bei Kontron Technologies”

In the session “Klaus Ettmayer, Bereichsleiter IoT Produkte bei Kontron Technologies,” Klaus Ettmayer of Kontron Technologies GmbH offered a concise, grounded look at how their engineering organization operates: team setup, delivery practices, hiring and onboarding, and the technology choices that shape day‑to‑day work. From our DevJobs.at editorial viewpoint, what stands out is the blend of end‑to‑end team responsibility, pragmatic agility, and a deliberately broad technology repertoire.

Right up front, Ettmayer lays out the structure: across Linz, Hagenberg, and Vienna, Kontron Technologies runs eleven development teams, each with four to eight people. Every team has a spokesperson to coordinate meetings and act as the team’s voice. Teams are assembled to cover the entire stack—from backend through core to frontend—augmented with testing and mobile development capabilities. Operationally, teams work “Scrum‑like” in two‑week sprints with planning, refinement, and daily stand‑ups. Yet process remains adaptable to meet customer requirements and team needs.

This combination of structure and flexibility mirrors the company’s portfolio: custom software development, in‑house products, IoT solutions, and an “extended workbench” model. Technologically, Kontron Technologies is broad by design—C#/.NET, Java, Angular, mobile stacks, multiple databases, and cloud experience across Azure and AWS. In parallel, long‑standing products are being modernized from monoliths to service‑oriented architectures—work that is both technically and organizationally significant.

Team topology: eleven cross‑functional squads across three locations

Kontron Technologies’ core units are small, capable, and autonomous:

• Locations: Linz, Hagenberg, Vienna
• Team count: eleven
• Team size: four to eight members
• Roles and skills: a team spokesperson for coordination and representation; developers covering backend, core, and frontend; mobile expertise as needed; a dedicated tester embedded in each team

This arrangement keeps end‑to‑end delivery front and center. The spokesperson role links the team to the broader organization, while the skills mix minimizes external dependencies and keeps ownership inside the team.

From an engineering leadership perspective, this is a clear bet on autonomy: teams that own the full value stream make faster decisions, work more closely with stakeholders, and translate feedback into software more quickly.

Ways of working: Scrum discipline with deliberate flexibility

The method is clear but not dogmatic: two‑week sprints, planning and refinement sessions, and daily stand‑ups—paired with enough flexibility to fit customer contexts and human rhythms. If a team prefers a later start, the daily is set to 10:30. If a team starts early, the daily might be at 8:00 or 8:30.

The attitude is consistent: processes serve delivery. They provide guidance without getting in the way of tailored decisions. In practice, that means standardized rituals for quality and predictability, with flexibility where it matters most—timings, day‑to‑day flow, and customer‑specific constraints.

Service teams: infrastructure and process as enablers

Alongside the development teams, Kontron Technologies runs dedicated service teams for targeted support:

• An IT team covers infrastructure topics.
• A process team improves company processes.

The aim is to keep engineers focused on what’s essential and remove distractions that can be handled elsewhere.

For engineers, that’s a strong signal: development time is treated as high‑leverage time.

Portfolio: custom development, in‑house products, IoT, and an “extended workbench”

Kontron Technologies’ offering spans four streams, each with distinct demands on teams and processes:

1. Custom software development
2. In‑house products
3. IoT solutions
4. An “extended workbench” setup

This diversity explains why the organization standardizes around a Scrum cadence yet keeps process knobs adjustable. For candidates, it means the chance to work across different modes—from product evolution to customer‑specific solutions and IoT scenarios.

Hiring philosophy: needs emerge from teams, and soft skills matter most

One of Ettmayer’s key points is how hiring needs arise. Technology needs originate in the development teams and are first addressed internally. If a gap remains, the recruiting team steps in to find candidates.

Interviews involve the business unit and the development leadership team, with an explicit focus on soft skills alongside technical competence. Team fit, engagement, and motivation carry particular weight.

For engineers who value collaborative environments and constructive communication, that’s a clear indicator of cultural intent.

Onboarding and culture: day‑one integration and open doors

Once candidates join, integration starts immediately within the development team:

• Day‑one onboarding with the team
• Gradual introduction to responsibilities
• The team as the first line for questions

Despite being about 150 people strong, Kontron Technologies maintains a “family‑like” atmosphere and an open‑door policy to management—for professional and private conversations alike.

This fosters psychological safety and accessibility—especially critical when engineering teams are modernizing complex systems while delivering customer value.

Tech stack and architecture: breadth by design, modernization in progress

Ettmayer outlines a wide‑ranging technology landscape shaped by company history and deliberate choices:

• Core technologies: C#/.NET, Java, Angular
• IoT solutions as part of the repertoire
• Mobile: Xamarin, Android, iOS
• Databases: Oracle, Microsoft SQL Server, PostgreSQL, MongoDB
• Cloud: Azure and AWS

In parallel, long‑running products are kept up‑to‑date while being modernized from monolithic structures to service‑oriented architectures—work that requires careful engineering and steady iteration.

Crucially, technological breadth is a means to better decisions. It enables the company to choose the “best fit” per project rather than being locked into one or two stacks.

For engineers, this translates into two advantages:

• Exposure and growth: the chance to work across stacks and architectural patterns.
• Pragmatism over dogma: technology choices follow the problem, not the other way around.

Why Kontron Technologies is compelling for tech talent

From this session, several reasons emerge for software and IoT professionals to take a closer look at Kontron Technologies GmbH:

• Cross‑functional teams with real end‑to‑end ownership: backend, core, frontend, mobile, and testing within the same unit.
• Scrum cadence without dogma: two‑week sprints, planning, refinement, and dailies—adapted to customer and team needs.
• Broad technology foundation: .NET and Java, Angular, mobile stacks, SQL and NoSQL databases, Azure and AWS.
• Product and project under one roof: custom development, in‑house products, IoT solutions, and the “extended workbench.”
• Active modernization: hands‑on experience evolving monoliths toward service‑oriented architectures.
• Culture of accessibility: about 150 employees, a family‑like climate, and open doors to management for professional and private conversations.
• Thoughtful hiring: needs originate in teams; soft skills, team fit, engagement, and motivation are central.
• Onboarding that builds momentum: day‑one integration and clear team support.

The picture is of a place where you can go deep on product quality and wide across modern technologies—with the autonomy that makes engineering work satisfying.

Collaboration patterns: standardize where it helps, adapt where it matters

Kontron Technologies balances ritual reliability with autonomy. Dailies happen when the team is ready. Sprint length is consistent; how teams shape their work reflects customer realities. This pattern gives the organization a common cadence while allowing local optimization.

Practically, that means:

• A shared language: planning, refinement, and daily stand‑ups as common touchpoints across teams.
• Local tailoring: start times, meeting cadence, and micro‑processes tuned to people and projects.
• Service support: IT and process teams remove friction so engineering can focus on delivery.

The outcome is a culture that standardizes where consistency adds value and varies where variation drives outcomes.

Engineering challenges with substance

The shift from monolithic systems to service‑oriented architectures is substantive work—requiring clean interfaces, careful decomposition, and steady migration. In parallel, established products must remain up‑to‑date—navigating version changes and related challenges, as Ettmayer notes with Java as an example.

For engineers who want to practice the craft—untangling legacy, shaping services, stabilizing data interfaces, and operationalizing deployments—this is a compelling space.

Benefiting from breadth: knowledge exchange and better decisions

A broad stack naturally fuels knowledge exchange. Teams versed in .NET, Java, Angular, mobile platforms, and multiple database paradigms bring diverse perspectives, improving decision quality. This is consistent with Ettmayer’s point about not being restricted to one or two technologies—less “one size fits all,” more fit‑for‑purpose architecture and stack selection.

From a candidate’s perspective, the environment suits those who:

• enjoy comparing tools and solutions across ecosystems,
• like solving concrete customer problems with the right technology,
• and want to stay current without being confined to a single niche.

People first: soft skills, team fit, and accessible leadership

Ettmayer repeatedly emphasizes soft skills. Technical expertise is necessary, but without team fit, engagement, and motivation it’s not enough. Combined with a management culture that keeps doors open—even for private conversations—the result is an environment where people are visible and heard.

In cross‑functional work, this emphasis is foundational. Quality emerges at the seams—between backend and frontend, development and testing, product and project. Soft skills keep those seams healthy.

Conclusion: structure with purpose, technology with breadth, culture with accessibility

“Klaus Ettmayer, Bereichsleiter IoT Produkte bei Kontron Technologies” outlines a coherent model: eleven cross‑functional teams, Scrum‑like two‑week sprints, process flexibility to fit customers and people, service teams that free engineers to focus, a broad technology base including cloud and mobile, active modernization of long‑running products, and a culture that takes soft skills, team fit, and open communication seriously.

For tech talent, that means the opportunity to have impact across products and projects, to treat technology as a toolbox rather than a constraint, and to work in teams that own the full flow of value. Kontron Technologies GmbH presents itself as a strong environment for engineers who want to pair substantive technical challenges with autonomy and an approachable leadership culture.