Selected work across software, automation, delivery, and systems thinking

Context

Stiftung KORA works with wildlife-related data and reporting in a context where official outputs and practical usability matter. The work sat at the intersection of data handling, reporting, stakeholder needs, and operational clarity.

Challenge

The environment required reporting and data workflows that were not just technically functional, but aligned with official requirements and real usage. The work also included map-related functionality tied to how users interact with geographic areas.

My Role

I worked in a developer / requirements-coordination context, contributing to implementation support, requirements clarification, documentation, and delivery structure.

What I Did

• Helped support FOEN-compliant official PDF reporting
• Supported integration with map.geo.admin.ch / Swisstopo for polygon drawing related to hunting-area workflows
• Ran internal stakeholder sessions for requirements gathering and demos
• Prepared delivery-ready documentation and Jira artifacts for a key data import function
• Helped make requirements, acceptance criteria, and follow-up work clearer and more actionable

Outcome

The result was not just code delivery, but improved clarity around what needed to be built, how it should behave, and how future work could be structured.

What It Shows

I work well where technical implementation, documentation, stakeholder alignment, and practical outcomes overlap.

Context

At Stiftung BASE, I worked around the Coldtivate app and related digitalisation efforts in an environment involving internal needs, external developers, and users in different regions.

Challenge

The challenge was broader than coding. The work involved preparing an open-source product to be more usable, understandable, and release-ready while coordinating across different people and priorities.

My Role

I worked as a Digitalisation Specialist with responsibilities touching product readiness, process improvement, coordination, documentation, and QA prioritization.

What I Did

• Coordinated with external developers and stakeholders across different contexts
• Supported open-source release readiness for the Coldtivate app
• Audited documentation and supported demo setup
• Improved setup-script and QA priorities
• Designed and rolled out a custom Agile workflow in Asana
• Standardized work-item structure and introduced recurring sprint metrics such as bug volume and reopen rate

Outcome

The work helped make the product and its supporting process more structured, easier to manage, and better prepared for broader use and collaboration.

What It Shows

I add value not only through implementation, but through structure, coordination, clarity, and improving how work moves through a team.

Context

At SBB, I worked in a Kafka platform environment shaped by integrations, operational needs, customer support, and platform reliability inside a SAFe setup.

Challenge

The environment required balancing technical depth with operational usefulness. Requests had to be handled in a way that supported platform users while keeping reliability and maintainability in view.

My Role

I worked as a BizDevOps Engineer, contributing to platform support, integration-related improvements, and reliability-focused work.

What I Did

• Supported platform users and project integration requests
• Contributed to Kafka topic replication across development, integration, and production environments
• Worked on a Java Spring + Angular self-service portal related to replication features
• Improved monitoring and platform hygiene
• Contributed during investigation of a major incident

Outcome

The work strengthened replication support, improved operational structure, and contributed to a more usable platform environment for internal consumers.

What It Shows

I can operate in technically complex systems while still focusing on usability, supportability, and practical delivery.

Context

At Küffer Elektro-Technik AG, I worked in an industrial engineering environment where software interacted directly with machines, HMIs, and operational reality.

Challenge

Unlike purely digital products, this environment required solutions that had to work under physical, engineering, and customer-facing constraints. Reliability and clarity mattered because the systems were tied to real machinery and use cases.

My Role

I worked as a Software Developer in PLC / automation, building and supporting automation-related software and interfaces.

What I Did

• Developed solutions in Beckhoff TwinCAT 3
• Worked on HMI interfaces and monitoring / visualization tooling
• Integrated PLC systems with APIs, MQTT, Raspberry Pi, and monitoring components
• Ran remote customer consultation and debugging sessions

Outcome

The work strengthened my practical systems thinking and taught me to value solutions that are usable, testable, and grounded in operational reality.

What It Shows

I'm comfortable with technical environments where complexity is real, constraints are physical, and problems have to be solved in practice rather than talked around.

Context

At Slimpeak AG, I worked in a remote product environment with distributed contributors and a need for more structure around delivery and collaboration.

Challenge

The team needed stronger delivery rhythm, better coordination, and clearer ways of working across different roles and people.

My Role

I worked in a Project Delivery Coordinator context, supporting structure, coordination, and team setup.

What I Did

• Helped establish agile / operations structure with boards, time logging, and PR checks
• Supported improvement of product and delivery setup
• Helped hire and coordinate a distributed freelancer team across backend, mobile, QA, marketing, and UX/UI
• Worked directly with leadership on improving execution and team organization

Outcome

The work helped create more visible structure and stronger coordination in a distributed environment where clarity and follow-through mattered.

What It Shows

I'm effective where work needs ownership, coordination, and practical structure more than heroics.

Context

As an independent experiment, I built and tested parts of a signal-to-execution trading flow using alerts, validation steps, automation logic, and exchange-side interaction.

Challenge

The challenge was not just technical connectivity, but designing a flow that could handle alerts, normalize inputs, avoid duplicates, and execute in a controlled way.

My Role

This was an independent technical experiment where I designed, connected, tested, and debugged the flow myself.

What I Did

• Worked with TradingView-style alerts and webhook handling
• Built a Cloudflare Worker / local executor style flow for receiving and validating signals
• Normalized symbols, handled deduplication logic, and tested execution behavior
• Connected the flow to exchange-side order actions in a controlled environment
• Used the experiment to think through automation, observability, and failure points

Outcome

The project gave me a deeper understanding of event-driven automation, practical system design, and the difference between a working script and a usable process.

What It Shows

I like building systems that connect moving parts, expose weaknesses quickly, and force clarity through real feedback.