From Dropout to Platform Pro: Insights from “Markus Duft, Senior Software Developer bei SSI Schäfer IT Solutions”

An unconventional path into software

Few career stories are as candid and consistently anchored in curiosity as the session “Markus Duft, Senior Software Developer bei SSI Schäfer IT Solutions.” Markus Duft (SSI Schäfer IT Solutions GmbH) takes us through a start without a high-school diploma, an apprenticeship in media design, a serendipitous deepening of software work during Austrian military service—and how he taught himself the craft in the months that followed. No traditional degree, no elaborate fallback. Instead: self-directed learning and the drive to build things.

From our DevJobs.at vantage point, this is a reminder of how far intrinsic motivation can carry a developer. Markus describes how he dug in—first on the side, then full-time through self-study—and, after his service, applied to what was then Salomon Automation. By his own account, his submission was “nothing super special,” yet it showed something that matters most: tangible results he had programmed in that time.

Today, some twenty years later, Markus is a Senior Software Developer at SSI Schäfer IT Solutions. The throughline is clear: a maker’s mindset, persistence in learning, and the willingness to shoulder foundational responsibilities.

What a senior developer in a platform team actually does

Markus frames his role succinctly: he’s a “classic Senior Software Developer.” In practice, that means hands on the keyboard, writing code. Not at the periphery, but deep in the platform layer other teams rely on.

In his account, this spans the full set of cross-cutting concerns that free product teams to focus on business logic:

• Enabling communication between software components
• Standardizing and simplifying database access
• Tackling networking topics and abstractions
• Ensuring the software can be installed, operated, and monitored

Put differently: platform work builds common, dependable building blocks so feature teams can move faster with fewer distractions. To our ears, this is platform engineering at its most practical—no buzzwords, just results.

Team culture: depth of expertise and a calm cadence

Two cultural themes stand out in Markus’s story: unusually high density of expertise, and the particular tone of a family-owned business.

That density creates a productive resonance: if you’re stuck, you find sparring; if you want to go deep, you meet people who think deeply. Less ego, more outcomes.

The second theme concerns the company structure:

Markus heads off a common misreading of “family-like” environments: it does not mean blurred boundaries or implicit overtime.

We see this as more than a footnote. Healthy, enduring engineering cultures emerge where commitment coexists with sustainable pace. Markus’s description suggests that this is not just policy—it’s practiced mutual care: “watching out for each other.”

Tech stack in motion: from rich client and OSGi to web frontends and Quarkus

Technically, Markus sketches an evolutionary architecture: deliberate change while respecting what works. His overview is unusually broad—reflecting a diverse system landscape:

• Languages he has used over two decades include Assembler, Perl, Python, shell scripts, C, C++, Java, Kotlin, JavaScript, TypeScript—“you name it, we have it.”
• Frontend: Angular on the website, riding a strong wave of web frontend work—“a lot is happening.”
• Backend: “very Java-heavy,” with no major change on the horizon—“we’re very satisfied.”

Frameworks and architectures over time:

• Historically “very strong on Eclipse and Equinox,” i.e., OSGi-based apps with rich desktop clients.
• Today: much more web, a shift away from rich-client paradigms.
• Backend moving forward on Java with Quarkus rather than Eclipse.

Databases:

• Oracle and Microsoft SQL Server in production; H2 and Postgres for development.
• Choice varies “strongly by application part”: which DB and to what extent differs across the board.

Scale:

This detail is telling. Platform work lives at the intersection of breadth (many technologies, many use cases) and depth (large, long-lived systems). The migration Markus describes is pragmatic: stepwise modernization without jeopardizing stability.

Platform as a force multiplier: what we heard between the lines

In Markus’s depiction of the platform department we see several principles that generally make the difference in engineering organizations:

• Abstraction over proliferation: solve a problem once, leverage it many times. Database access, networking, inter-process communication—centralize what everyone needs.
• Operability by design: “installation, operation, monitoring”—the leap from “works on my laptop” to production realities.
• Enabler posture, not gatekeeping: platform teams create capabilities and reduce toil; Markus’s tone and examples align with that ethos.

It’s quiet craftsmanship: no grandstanding, just sturdy foundations other teams can rely on.

Learning without perfectionism: motivation beats completeness

Markus turns directly to learning mindset—and it lands with clarity:

His reasoning: there are “so many tutorials, so much documentation, so many online sources” to organize knowledge as needed. He explicitly mentions “AI assistants” as helpful when you’re stuck. His advice is deceptively simple: sit down and start.

For developers at any level, that translates to a practical posture:

• Prioritize making over memorizing: small steps, tangible artifacts, quick feedback.
• Build research skills: find, assess, and apply information on demand.
• Tend your curiosity: keep going when the first approach fails.

The early spark: QuickBasic, a calculator, and a memory

A brief vignette grounds Markus’s learning arc. At age twelve, he tinkered in QuickBasic and built a calculator—well before he was truly “programming,” yet close enough to ignite fascination.

He later moved away from it, then returned. The lesson we draw: sometimes a tiny prototype at the right time plants a seed. Even set aside, it can reignite years later.

From application to impact: why tangible output matters

The way Markus recalls his entry is matter-of-fact. His work wasn’t “super special,” but it was concrete. In developer hiring, especially without a formal degree, working artifacts often carry the day.

We extract three mechanisms from his account:

1. Visible initiative: self-built projects demonstrate motivation without buzzwords.
2. Evidence of learning range: varied small builds signal capacity to pick up new topics.
3. Honest self-assessment: no overselling—just dependable substance.

His path underscores a simple truth: if you can deliver, doors open—and you get the chance to grow further.

Technologies at a glance: breadth as ballast

The technological spread Markus mentions reads like a tour of pragmatic choices rather than dogma. No single-tool romanticism; instead, “what fits this context.” A few takeaways:

• Language breadth: from Assembler to TypeScript, C/C++ to Kotlin.
• Measured modernization: away from rich client and OSGi toward web frontends with Angular; backend steady on Java, increasingly with Quarkus.
• Database diversity: Oracle, Microsoft SQL Server, Postgres, H2—chosen per application part.

The scale of the largest application (“around 750 tables”) makes it plain why this can’t be a big-bang rewrite. It’s a migration path: decouple, re-slice services, evolve UIs to the web—while keeping the backend stable. Markus describes exactly that balance: change with a firm footing.

Culture as an operating system: deep talks, healthy limits

Two recurring motifs surface as we listen to Markus: deep technical discourse as the norm, and clear boundaries against overload. Both feel grounded in daily practice:

• “Have deeply technical conversations with anyone”: that implies trust, some tolerance for missteps, and a shared bias for solutions.
• “Watch out for each other”: a proactive form of team health that shows up before things catch fire.

For tech talent, that’s a strong signal: sustainability is born where expertise is shared—not hoarded—and where time is a tool, not a contest.

What developers can take away from this session

Markus’s path and phrasing distill into concrete, portable lessons. From our DevJobs.at editorial view, these seven matter most:

1. Start from where you are: a formal degree helps, but it’s not the only way in. Show what you’ve built.
2. Build tangible artifacts: small tools, scripts, demos—working results outshine slide decks.
3. Learn on demand: lean on documentation, tutorials, and online sources—perfectionism slows you down.
4. Keep the joy alive: enthusiasm is renewable and carries you through dry spells and shifts.
5. Seek depth through dialogue: technical conversations will move you further, faster, than lone struggles.
6. Think about operations and observability: installation, operation, monitoring—build for real conditions.
7. Treat change as default: rich client to web, Eclipse to Quarkus, DB variety—modernization is a journey, not a leap.

Quotes that stick

Some lines neatly capture the essence. From “Markus Duft, Senior Software Developer bei SSI Schäfer IT Solutions,” we carry these with us:

Conclusion: craft, posture, leverage

Markus Duft shows how an unconventional start can lead to a durable senior role—anchored in joy of building, persistence in learning, and a willingness to work where foundations are laid: the platform. His account of the tech stack and its migration—from OSGi/rich client to web/Angular and a Java backend moving to Quarkus—is clear-eyed and steady. So is his read on culture: depth of expertise, respectful collaboration, healthy limits.

From our DevJobs.at perspective, this session is a case for pairing motivation with substance. Start, deliver, learn—doors will open, even without the typical academic arc. And if you take platform work seriously, you don’t just ship software; you build the preconditions for many others to work productively and sustainably.

In that vein, Markus’s story isn’t an exception. It’s an invitation: begin. build. share. stay curious.

• 

  

  Manuela Jobstmann, Requirements Engineer bei SSI Schäfer IT Solutions

  Manuela Jobstmann von SSI Schäfer IT Solutions erzählt im Interview über ihren Werdegang in der IT bis hin zur aktuellen Rolle im Requirements Engineering und gibt Tipps für Neueinsteiger.

  Watch now