From Police Officer to Full‑Stack Builder: How David Kandler at ECO-Soft GmbH Crafts Freight Software and Shapes His Learning Curve

Context: A career switch that sticks

In the session 'David Kandler, Software Developer bei ECO-Soft' with speaker David Kandler (Company: ECO-Soft GmbH), we hear a crisp, memorable developer story: moving from a completely different profession into software engineering—without prior coding experience, but with curiosity, persistence, and a clear love for logic. From our DevJobs.at editorial seat, we watched how David distills core realities of modern engineering work: autonomy, problem-solving, team culture, and a learning posture built on steady, self-imposed challenges.

The opening line sets the baseline: he used to be a police officer. Then came the shift—triggered not by abstract fascination with tech, but by a grounded appreciation for structured thinking. Through his girlfriend’s work-from-home window into programming, he saw how the work flows: logical, focused, self-directed. That fit between personal profile and day-to-day practice runs like a thread through his story.

The spark: logic, focus, and working independently

David describes the moment of clarity with disarming simplicity. After completing his training in law enforcement, he realized it wasn’t a path he wanted to pursue for the long haul. Programming appeared by chance—he watched it up close at home and felt the appeal. What struck him wasn’t hype; it was the sober pleasure of logic and structure.

That emphasis on logic and solo focus is decisive. For David, the draw is not about spotlight or tech for its own sake; it’s about taking ownership of a problem, structuring it, and solving it without constant micromanagement. That’s the lane where he thrives.

A decisive move: applying to ECO-Soft GmbH

Insight became action quickly: he applied to ECO-Soft GmbH. His verdict on the start is telling—right from the beginning, it clicked. He found precisely the kind of environment he had hoped for: a place where his way of thinking is not just allowed but useful. This wasn’t a cosmetic career change; it closed the gap between person and profession.

What stands out to us editorially is how matter-of-fact his courage looks in hindsight. He stepped off a stable, well-defined path onto a steep learning curve with uncertain outcomes. The upside is the day-to-day fit he now describes—role, team, leadership. His initial 'why' gets reaffirmed by the work itself.

The role: full‑stack in a small team

David states it plainly:

He’s part of a relatively small team building an application for an ECO-Soft client—a freight forwarding company. The way he puts it serves as a neat snapshot of full‑stack responsibility in a focused product context: not abstract micro-tasks, but end‑to‑end accountability for a forwarding software.

In practice, that means he works on both design and backend—gaining a scope that reaches beyond execution into shaping the product. This combination affords him two vantage points: direct contact with user and process logic on the design side, and the deep, functional backbone on the backend. It’s no surprise he keeps circling back to self-actualization: carrying both concerns turns problem-solving into creative, responsible craft.

Autonomy as a core motivator

David’s phrasing is unambiguous: what energizes him is the freedom to set things up 'the way you need them,' within clear alignment through discussion. It’s a balance of autonomy and agreement—smart guardrails rather than narrow prescriptions. Not anarchy, but self-directed work with a shared target.

This marks the passage from newcomer to professional: it’s not just about meeting requirements, but about how you get there. Your method becomes part of your value. For many engineers, that’s when the job turns into a creative, accountable craft.

Product context: forwarding software as a full‑contact discipline

Even without a feature list, David hints at breadth—this forwarding software does essentially 'all' one would expect of it. From a learning angle, that breadth matters: freight operations are data- and process-dense. For a full‑stack role, that implies many mental interfaces, consistency checks, and decisions about data flow, validation, and interaction.

When design and backend sit with the same person, the center of gravity shifts from mere building to delivering coherent, robust solutions users can follow. Holding both lenses—presentation and logic—demands a narrative that works for people and machines. David’s account implies exactly that level of expectation.

Team culture: young, low‑friction, with humor—and support tied to delivery

David paints a culture that many would sign up for: young team, no fights, and a healthy dose of fun.

He also points to a leadership style that rewards commitment and results:

We read that as trust in exchange for ownership. Those who deliver get room to operate; those who take responsibility get support. That logic isn’t novel, but living it daily is what changes outcomes. For career switchers, this kind of culture can be a force multiplier: it accelerates learning because it doesn’t smother initiative with suspicion or tight controls.

The learning curve: stay, tolerate doubt, keep looking for solutions

David is candid about the difficulty of the entry phase—especially since he 'couldn’t really program' beforehand. The lever he describes is pure consistency: he kept going, no matter what surfaced. Doubt is normal; the difference is in showing up and solving.

This might be the strongest signal in his story: learning isn’t a sprint. The competence curve is lumpy—plateaus and jumps. Those who push through eventually notice that it 'gets easier.' That inflection point is when confidence turns from wishful thinking into experience.

Practice principle: set yourself challenges

David’s method becomes tangible when he advises challenging yourself again after a problem is solved: can it be done better? Can you shorten the code? Make it more dynamic?

As a compass for durable learning, this is powerful:

• Review instead of mere box-ticking: Only on the second, deliberate pass does craftsmanship deepen.
• From working to understanding: When you slim a solution down, you learn what’s essential and sharpen your feel for structure and variation.
• Internal quality drive: Not just external reviews, but personal standards move the bar over time.

What resonates with us is how specific yet universally applicable this advice is. It scales—from a first utility function to a complex application flow.

What we extract from David’s story

The session 'David Kandler, Software Developer bei ECO-Soft' compresses a clear message. From our perspective, four principles stand out for career changers and early-career developers alike:

1. Take your profile seriously

If logic, focus, and self-responsibility bring you joy, software offers a natural arena. David found his fit not in theory but in the cadence of the workday.

1. Learning curves don’t advertise themselves

Doubts are part of the package. The difference lies in continuity. Those who endure the dry spells experience the 'it gets easier' phase.

1. Use autonomy productively

Freedom is a privilege and a duty. David shows how alignment and independence complement each other: clarity on goals makes freedom in implementation valuable.

1. Quality is what you make of it

Self-imposed mini-challenges—shorten code, make it more dynamic—shape the craft. It’s the small, deliberate training that compounds into stability, readability, and elegance.

For career switchers: operationalizing David’s approach

Because David’s tips are pragmatic, they translate well into recurring routines:

• After each solved issue: a mini‑retro
• What’s the core of the solution? Which decision unlocked it?
• Which two lines could be removed without losing substance?
• Where can a parameter, condition, or structure be generalized to make the code more dynamic?
• Treat doubt as a signal
• When a task feels 'heavy,' deliberately reduce its scope: pick a sub‑step, create visible progress, repeat.
• Log learning gains, even tersely: What got 'easier'? What is obvious today that was new yesterday?
• Secure your autonomy
• Propose your own approach, but anchor it in clear alignment: name the goal, assumptions, and likely risks.
• Seek feedback actively: don’t wait for problems to grow—mirror your direction early.

These are technical habits and a mindset at once: stay agile, stay focused, and keep the courage to simplify.

The role of environment: support that compounds

David describes how team and leadership fuel his growth: young, low‑friction, humorous—and a leader who rewards delivery and provides support. That scaffolding isn’t a luxury; it’s a catalyst. It reduces the friction that inevitably comes with learning and channels energy into the essentials: understanding problems, developing solutions, and owning outcomes.

For organizations, there’s a lesson: if you want career changers to thrive, build rooms where initiative is rewarded and learning is treated as investment rather than interruption. David’s experience at ECO-Soft GmbH illustrates this dynamic.

Programming as personal fit: logic meets agency

David returns again and again to his core driver: he’s a 'very logical' person and wants work where that matters. Programming gives him exactly that—and pairs it with agency. Seeking and implementing your own solutions that create product value is both outcome and motivation.

That fit isn’t accidental. It emerges when demands, tasks, and environment align. In David’s case, we see three pieces:

• Task: frame, structure, and solve problems clearly.
• Role: carry both design and backend, think end‑to‑end.
• Environment: freedom plus support, commitment plus humor.

Find that triad, and learning accelerates—and sticking with it becomes easier.

Why forwarding software is a rich learning space

Without detail, David suggests the application covers essentially 'everything' one expects of such a system. From a learning perspective, that matters because complexity forces variety: different processes, states, and dependencies. For a full‑stack role, that naturally becomes a training ground where technical craft and domain understanding interlock.

Notably, David doesn’t cloak this breadth in abstractions. He anchors his work in what suits him: logical structure, clear alignment, self‑devised solutions. The takeaway for listeners: even in high‑density problem spaces, orientation holds if core principles are sound.

The contrast with his former job: self‑actualization through design and ownership

David makes a clear contrast: he felt little room for self‑actualization earlier. In his current role, he can 'set things up as needed,' with explicit agreement—building something that fits and functions. The change is more than technology. It is a move from a rigid role to responsible design.

For many career changers, that’s the essence of switching: finding work where professional quality and personal style don’t collide but complement each other. David’s experience shows what then becomes possible.

Simple lines, strong impact: why his quotes stick

A distinctive trait of David’s account is its simplicity. There’s no grand rhetoric—just short, direct statements. That’s what makes them compelling. The listener senses a person who tried, stayed, and now reports what holds water. The punchlines are unpretentious and credible:

• Programming is 'something logical.'
• He is 'in the end, a full‑stack developer now.'
• The software 'includes everything' the program should do.
• He kept going 'no matter what came up.'
• He sets challenges: 'shorten code,' 'make it more dynamic.'

These are not slogans; they are building blocks of a workday that improves with every cycle.

Our takeaways at DevJobs.at

From 'David Kandler, Software Developer bei ECO-Soft' with David Kandler (ECO-Soft GmbH), we extract concise, practical lessons:

• Career changing works when inner drivers align—logic, problem focus, and self‑direction.
• Culture and leadership multiply outcomes—young team, low friction, support that follows delivery.
• Full‑stack in a small team yields reality contact—design and backend sit together, accountability is tangible.
• Learning hygiene beats hustle—mini‑challenges after each solution build craftsmanship and routine.

In combination, these explain why David’s switch didn’t just happen—it stuck.

Putting it into practice: a lightweight daily framework

If you want to mirror David’s approach, translate his principles into a compact personal framework:

1. Clarify your why

• Name what energizes you: logic, focus, autonomy. Make it concrete.

1. Choose an environment that matches

• Look for teams that pair freedom with support.

1. Add a mini‑challenge to every solved task

• Shorten, simplify, generalize—one deliberate improvement.

1. Cultivate endurance

• Accept doubt, keep going, watch how it gets 'easier.'

1. Align, then own

• Set clear goals together, then chart your path—alignment as amplifier, not brake.

This scaffold is intentionally small—like David’s own tips. The constant cadence matters more than the size of any single step.

Closing: a story that encourages—and sets a bar

David’s path from police work to full‑stack engineering at ECO-Soft GmbH isn’t just inspiring; it’s instructive. It shows how much becomes possible when personal fit, meaningful autonomy, and a supportive team converge. His learning stance stands out in particular: keep at it, look for solutions, challenge yourself—and improve a bit every day.

If you’re considering a switch into software or are at the beginning of your developer journey, this session offers clear anchors. And if you’re building teams that enable such transitions, you’ll see which culture makes a difference: trust, delivery, support, humor. The result is tangible: a full‑stack engineer contributing to a forwarding software that does what it needs to do—and someone who spends his days doing what he always wanted to do: solve problems logically, with focus, and on his own steam.

• 

  

  Hans Burgstaller, Full Stack Developer bei ECO-Soft

  Hans Burgstaller von ECO-Soft gibt im Interview Einblicke in die Entstehung des Unternehmens, das heutige Development Team, die Technologien die dort zum Einsatz kommen und wie das Recruiting im Unternehmen gestaltet ist.

  Watch now
• 

  

  Florian Knoll, Full Stack Developer bei ECO-Soft

  Florian Knoll von ECO-Soft beschreibt im Interview das Team des Unternehmens, den Ablauf des Bewerbungsprozesses und gibt Einblicke in die technologischen Challenges.

  Watch now

• 

  

  Tobias Hafner-Fuchs, Full Stack Developer bei ECO-Soft

  Tobias Hafner-Fuchs von ECO-Soft spricht im Interview über seine Anfänge im Programmieren, was seine Aufgaben als Full Stack Developer im Team umfassen und gibt Empfehlungen für Einsteiger.

  Watch now
• 

  

  Bastian Schmidt, Software Developer bei ECO-Soft

  Bastian Schmidt von ECO-Soft redet in seinem Interview von seinem Werdegang als Developer – von den frühen Anfängen, bis hin zur aktuellen Arbeit als Developer – und welche Tipps er für Anfänger hat.

  Watch now
• 

  

  Ricardo Reindl, Software Developer bei ECO-Soft

  Ricardo Reindl von ECO-Soft erzählt in seinem Interview von den spielerischen Anfängen während der Schulzeit und über seinen weiteren Werdegang bis zum Software Development – und was das Wichtigste für Neueinsteiger ist.

  Watch now