From Computer License to Mobile Developer in IoT: The DevStory of Matthias Schmutzer (Doka GmbH)

Why this session matters: Reflections on “Matthias Schmutzer, Mobile Developer bei Doka”

Many developer careers begin with curiosity rather than spectacle—by poking at a new tool, trying a small project, and feeling something click. That is how Matthias Schmutzer describes it in the session “Matthias Schmutzer, Mobile Developer bei Doka.” His path starts in secondary school with a voluntary computer course: the “computer license.” Office basics, ten-finger typing, and, crucially, a first, very simple HTML page. That was enough to turn curiosity into direction. He chose the IT-focused HTL in Ips, graduated with a specialization in media technology, discovered a love for web development, entered professional life, completed civil service, and ultimately found his footing as a software developer in an industrial setting—today focusing on mobile applications, IoT and sensor services, and coordination at key interfaces.

His journey resonates with questions we hear from aspiring engineers all the time: finding early footholds, choosing an educational path, moving from web into mobile product work, and, above all, realizing that soft skills, teamwork, and mentorship often determine the pace and quality of growth.

In this recap, we trace Matthias’ steps and focus areas, and translate his advice into concrete actions for developers navigating their own careers.

First milestones: Computer license, ten-finger typing, and a basic HTML page

Matthias’ entry point is specific and down-to-earth: a school elective that made technology tangible. Microsoft Word, PowerPoint, and ten-finger typing may not sound glamorous, but they represent foundational skills in operating tools and communicating clearly. At the end of secondary school, he also built a “very basic” HTML page—an experiment that made him want more. That small hands-on success was the moment curiosity became a plan.

What stands out for us:

• Fundamentals matter. Clear writing, presentable slides, and structured thinking make later project work easier.
• Small projects spark momentum. A simple HTML page can be the pivot from “maybe I’ll try this” to “this is what I want to do.”
• Early practice, later payoff. Ten-finger typing sounds mundane, but it is real-world efficiency—freeing focus for more demanding tasks.

Choosing the technical path: HTL in Ips and a focus on media technology

After secondary school, Matthias made a deliberate choice: the IT-HTL in Ips, graduating after five years with a specialization in media technology. In that phase, as he puts it, he discovered a love for web development. The path was set: software, initially with a web focus—and on top of a solid educational foundation.

Two takeaways for aspiring developers:

• Structure helps. An HTL or a degree program can provide learning paths and practical scenarios that would be difficult to construct on your own.
• Specialization often follows practice. “Media technology” can mean many things—here, it became a bridge into web development because building and testing tangible things was rewarding.

From web to industry: First job, civil service, and arriving at Doka GmbH

After graduation, Matthias quickly went hands-on: he started as a web developer. He then completed civil service—“classically,” as he says—for “one or two years.” After that, he joined Doka GmbH as a software developer.

We note a few characteristics of that trajectory:

• Early professional exposure creates momentum. What you learned at school becomes anchored through real projects.
• Transitions are part of the journey. Whether civil service, the first job, or a new role—transitions are opportunities to reflect, consolidate, and prepare for the next step.
• Changing domains broadens perspective. Moving from web into an industrial product-and-services environment introduces new demands around reliability, interfaces, and cross-functional collaboration.

Today’s role: Mobile apps, IoT and sensor services in a Digital Services team

Matthias describes his current work succinctly: he is part of a Digital Services team developing digital services for customers on construction sites, where clients use IoT and sensor services. His own focus is mobile applications. Beyond that, he coordinates with external developers, looks after hardware interfaces, and mentions that industrial protocols like Modbus can come into play.

What this implies:

• Mobile is integrative. Apps are the user-facing touchpoint, connecting digital services, sensor data, and on-site use cases.
• Interface competence matters. Building mobile in the context of IoT and sensors requires handling physical and digital interfaces—and coordinating with teams outside your organization.
• Industrial context sharpens requirements. Terms like “industrial protocols” signal that it’s not only about UI polish but about robust, reproducible, standards-aligned integrations.

“There are many ways in”: Learning pathways in software development

Matthias emphasizes that there are many valid ways to enter development. Online tutorials enable you to “start all by yourself.” HTLs or degree programs are helpful routes, but not the only ones. Importantly, he highlights career changers: in his view, they can bring knowledge on par with graduates from technical schools or universities.

This perspective is inclusive and practical. What counts is the ability to build, learn, and collaborate—not a particular label on your resume. For teams, it translates into hiring and growth practices that prioritize capability, learning curve, and team fit over credentials.

The other half of the craft: Communication, teamwork, and mentoring

Matthias puts considerable weight on soft skills. Development is “always a team effort,” and communication is “very important.” He further recommends finding a mentor—someone “to take you by the hand,” helping you go deeper and discover opportunities.

We see three concrete action areas in his advice:

1. Treat communication as a real skill. It’s more than showing up to meetings: write clearly, listen carefully, set expectations, give and request feedback. If you build mobile apps that integrate with IoT services and coordinate external teams, you need explicit agreements and clarity between intent and outcome.
2. Embrace team reality. In integrated product settings (mobile, sensors, industrial protocols), solo work is the exception. Success depends on alignment among product, hardware, external partners, and users.
3. Use mentoring as an accelerator. A mentor reduces the “black box phase” of learning, especially when combining new domains (e.g., hardware interfaces) with existing strengths (e.g., mobile).

From foundation to depth: How skills compound

Matthias sketches a familiar progression: start with tutorials, build the basics, then use structured education or projects to go deeper. After that baseline, soft skills and mentoring grow in importance, and you begin to specialize.

In the context he describes, that typically involves:

• Mobile development tied to real-world use cases (construction site, direct customer value, service-oriented apps)
• Understanding and coordinating interfaces—technically, organizationally, and cross-functionally
• Handling requirements shaped by industrial use—reliability, clear specifications, reproducible flows

You can make this transition deliberate:

• Anchor in practice: Translate ideas into small, testable pieces quickly.
• Document as you go: Maintain understandable specs and interface descriptions.
• Create feedback loops: Check direction early with your team and stakeholders.
• Find mentorship: Schedule regular sparring with experienced colleagues.

Mobile with IoT and sensors: What this asks of developers

Even without deep technical detail, Matthias’ description paints a realistic picture: mobile work here isn’t just front-end—it's embedded in a system of digital services and sensors. That calls for:

• Awareness of data flows: What data is produced, how it’s processed, and where users experience value.
• Careful integration: With hardware interfaces in the loop, timing, formats, and error handling are critical—in the app and across the service chain.
• External coordination: Working with external developers adds communication and quality boundaries. Ownership, versioning, and testing paths become pivotal.

The power of simple starts: Why “basic HTML” is a great beginning

“Building a very basic HTML page” may sound modest, but it’s one of the most potent motifs in Matthias’ story. Here’s why:

• Visible outcomes: A simple page yields immediate feedback—what you write is what you see.
• Autonomy: Small projects grant autonomy. You can experiment, break things, fix them—and learn.
• Transferability: Understanding HTML and simple logic enables a stepwise move into more complex ecosystems—web, mobile, or backend.

For newcomers: your first build doesn’t need to be perfect. It needs to be tangible—and make you want to keep going.

Living with transitions: Education, work, civil service, new context

Matthias’ path reminds us that nonlinearity is normal. Education, early jobs, civil service—these are not interruptions but phases that consolidate skills and foster maturity. Especially when entering an industrial environment afterward, such stations become reference points: what can I do now, what’s missing, where do I want to go?

Practical suggestions:

• Archive wins: Maintain a small portfolio and notes on projects—what you learned, improved, or discarded.
• Keep a rhythm: Even during transitions, maintain contact with the craft (reading, small exercises, side projects) so re-entry is smoother.
• Stay open: Treat new contexts (e.g., moving from web to mobile + interface work) as opportunities to broaden your skill set.

Communication as an engineering factor: Making team effort work

“Being a developer is always a team effort”—we take this as a design principle. In environments where mobile apps, IoT services, and sensor data converge, collaboration becomes an architectural concern:

• Share goals: Align on what “done” means to prevent interfaces that technically work but miss the actual needs.
• Clarify language: Establish shared vocabulary—from the app’s error types to events at the sensor layer.
• Make changes visible: Surface assumptions, dependencies, and modifications for internal and external partners.

For Matthias, communication isn’t “soft” in the sense of optional friendliness—it’s a primary work tool. In such projects, well-run conversations are as essential as code reviews.

Mentoring: Creating focus and seeing options

“Get yourself a mentor … someone to take you by the hand and say, this is where you can dive deeper, and here are other things that exist.” This is practical, not ceremonial. Mentoring brings early feedback, faster course corrections, and a better map of options.

For mentees, that means:

• Be proactive: Prioritize your questions, bring results, test hypotheses.
• Define learning paths: With your mentor, identify areas that fit your role (e.g., interfaces, quality assurance, architectural concerns).
• Own the work: Mentoring doesn’t replace effort—it amplifies it.

For teams, mentoring is a multiplier: a way to spread knowledge and help new colleagues gain traction faster.

“Start on the internet”: Making self-learning work

Matthias’ nod to online tutorials is more than a casual “just Google it.” It’s an invitation to be systematic about self-directed learning:

• Curate over consume: Choose a few solid sources, work them thoroughly, build the exercises.
• Bias to practice: Measure progress in small, realistic artifacts—mini apps that display sensor events or present a dataset clearly.
• Make it regular: Block time, track progress, and name blockers—as if you were running a sprint.

This turns self-learning into a plan you can align with team and product goals.

Welcoming career changers: Competence over biography

Matthias is unequivocal about the equivalence of different routes: career changers can have knowledge on par with HTL or university graduates. This stance opens doors—especially for teams that value diverse backgrounds.

For recruiters and leads, that translates into:

• Task-focused evaluation: Work samples, reasoning, and learning reflexes often matter more than titles.
• Pair to complement: Mix backgrounds in pairings—an HTL graduate and a career changer can form a formidable tandem.
• Nurture potential: A culture of coaching and feedback turns diversity into performance.

Looking ahead: Specialize without narrowing down too early

Matthias’ path—early foundations, web development, mobile focus, interface work—is a template for specialization that doesn’t box you in. The blend of app orientation with system thinking (IoT, sensors, interfaces, external partners) keeps the work close to both the user and the technology.

If you’re aiming for similar roles, consider questions like:

• Which user interactions are central—and which data flows support them?
• Which interfaces must I understand to integrate reliably?
• Where are my bottlenecks—communication, specification, testing? Which soft skills do I need to strengthen?
• Who could mentor me—and where can I mentor others?

A practical checklist from the session

To close, we synthesize what we heard in “Matthias Schmutzer, Mobile Developer bei Doka” into actionable steps:

1. Start early, start small: A “very basic” HTML page can be the spark. Build something tangible.
2. Learn with structure: An HTL or degree helps—but isn’t mandatory. Consistent learning with practice is what counts.
3. Use tutorials deliberately: Pick a few good resources and turn them into working artifacts.
4. Train soft skills: Communication is part of engineering—write clearly, ask precisely, and give feedback.
5. Live the team reality: Mobile + IoT + sensors only works when all parties are in sync. Surface dependencies and expectations.
6. Seek mentoring: A mentor accelerates your learning curve and reveals options. Be proactive and bring results.
7. Understand interfaces: With hardware, external partners, and industrial protocols in play, clear coordination is essential.
8. Respect career changers: Credentials are secondary. Competence and the capacity to learn are primary.

Conclusion: A grounded developer story with strong real-world anchors

Matthias Schmutzer’s DevStory shows how early interest becomes a robust developer career: practical beginnings, solid education, a decisive first job, and the willingness to step into a demanding, integrated environment. Mobile development that connects customers on construction sites with IoT and sensor services demands technical ability as much as coordination, communication, and team spirit. Matthias’ guidance lines up accordingly: build your foundation, invest in soft skills, find mentorship—and recognize that there are many viable paths into software.

In sum, the session “Matthias Schmutzer, Mobile Developer bei Doka” lands a clear message: take the first step, go deeper, work with people—and lean into systems where mobile apps, digital services, and real-world contexts converge. That’s where impact happens.

• 

  

  Ronni Bjelosevic, DevOps Team Lead bei Doka

  DevOps Team Lead bei Doka Ronni Bjelosevic gibt im Interview einen Überblick über den Aufbau der Teams im Unternehmen, was dort neue Mitarbeiter erwartet und mit welchen Technologien gearbeitet wird.

  Watch now
• 

  

  Benjamin Schauer, Group Leader Digital Operation Tools bei Doka

  Group Leader bei Doka Benjamin Schauer umreißt im Interview die Organisation des Teams für Digital Operation Tools, was dort technologisch spannend ist und wie das Recruiting und Onboarding gestaltet ist.

  Watch now

• 

  

  Katja Hammer, Software Developer bei Doka

  Katja Hammer von Doka erzählt im Interview über ihren Werdegang als Software Developer bis hin zu ihrer aktuellen Arbeit und gibt Tipps für Neueinsteiger.

  Watch now
• 

  

  Michael Hahn, Corporate Software Architect bei Doka

  Michael Hahn von Doka spricht im Interview über seine analogen Anfänge im Programmieren, was die Aufgaben seines aktuellen Berufes umfassen und gibt Tipps für Neueinsteiger.

  Watch now