Deep technical expertise at the intersection of hardware and software. I bring embedded systems mastery, IoT architecture experience, and regulatory compliance knowledge; combined with a methodical approach honed through teaching and project leadership.
Technical Domains
Embedded Systems
From firmware to application layers, I build mechatronic and embedded systems that ship. Deep expertise in C/C++, embedded Linux, and low-level system architecture; not surface-level familiarity.
Core capabilities:
- Embedded Linux mastery
- Yocto, Buildroot, OSTree for custom system images tailored to your hardware and requirements
- Firmware development
- Low-power MCU programming (STM8, STM32), sensor integration, real-time constraints
- Cross-platform development
- From bare metal to embedded Linux, understanding the tradeoffs at each layer
- Hardware-software integration
- PCB design experience means I understand what happens at the electrical level, not just the code level
- Production-ready code
- Not just prototypes; code that ships in medical devices, industrial systems, and consumer products
How I approach it:
Embedded systems demand thinking across layers. A hardware decision ripples into driver architecture. A firmware choice affects testability. I build systems that stay maintainable long after initial development, because I've seen what happens when nobody thinks about that upfront.
IoT & Connectivity
Connectivity done right is architecture, not an afterthought. I design IoT systems that work in production (not just in demos) by building security in from day one.
Core capabilities:
- Secure connectivity architectures
- WireGuard-based VPN solutions for remote device management that scale
- Industrial IoT experience
- Energy monitoring systems, building automation, sensor networks in production environments
- Sensor integration & data pipelines
- From Modbus and M-Bus to cloud analytics, I understand the full data path
- Edge computing
- Processing where it makes sense, cloud where it adds value, clear rationale for architecture decisions
- Connected device security
- Security designed in from the start, not bolted on afterward
The approach:
IoT projects fail when connectivity gets treated as a checkbox feature. I start with the data: what you need, when you need it, where it needs to go. Then I design from there.
Case Study: Industrial Energy Monitoring
Challenge: Deploy energy monitoring across 500+ building installations with secure remote management.
Solution: Custom embedded Linux images with WireGuard VPN, enabling centralized monitoring and configuration updates across the entire fleet.
Outcome: 6-month deployment cycle, remote management capability reducing on-site visits by 80%, centralized data collection for analytics.
Regulatory Compliance
Done right, compliance is engineering discipline that makes products better, not just paperwork. I've shipped products under ISO 13485, IEC 62304, and functional safety standards. I know how to make it practical.
Core capabilities:
- Medical device expertise
- ISO 13485 quality systems, IEC 62304 software lifecycle, IEC 60601-1 electrical safety
- Functional safety
- IEC 61508, EN 50657 (rail), experience with safety-critical system design and analysis
- EU Cyber Resilience Act
- Understanding the emerging requirements for connected products and how to prepare
- Audit-ready documentation
- Good process produces good documentation naturally, not retroactive paperwork
- Risk-based thinking
- Focusing effort where it matters, not treating all risks equally
How I work:
Compliance works best when it's invisible: when good engineering practices naturally produce compliant outcomes. I help teams cut through what people think the standards require and focus on what they actually require.
Case Study: Safety-Critical Medical Device
Challenge: Develop electronics and firmware for an insulin pump, a life-critical medical device.
Solution: Implemented functional safety analysis, designed power control electronics to IEC 60601-1 standards, developed low-power firmware with formal verification requirements.
Outcome: Regulatory pathway established, safety case documented, architecture designed for audit and certification.
Approach & Methods
End-to-End Delivery
I don't just write code and hand it over. I've shipped products from initial concept through factory floor, and I understand what happens at each stage.
What you get:
- Ideation to production
- Concept development, prototyping, detailed design, testing, production support; I've done the full chain
- No knowledge silos
- When one person understands the full system, there's no "the guy who wrote that left" problem
- Realistic estimates
- I know what it takes to go from prototype to production because I've done it
- Production awareness
- Code that works on the bench isn't enough; I understand manufacturability, testability, and field service
- Handoff that works
- Documentation, training, and knowledge transfer built into the process, not bolted on at the end
The reality:
Most consultants specialize in one phase. The firmware person doesn't understand the hardware. The hardware person doesn't understand the software. The integration problems appear late and expensively. Working at the intersection across industries, the problems that kill projects are the ones I've learned to anticipate.
Knowledge Transfer
I teach industrial and mobile robotics at Fachhochschule Graubünden. This isn't a side gig; it's core to how I work.
What this looks like:
- Current knowledge
- Teaching forces me to stay current with technology and industry trends
- Clear communication
- Explaining complex systems to students means I can explain them to your stakeholders
- Structured thinking
- Pedagogical training translates to well-organized projects and documentation
- Built-in mentorship
- Your team learns while I deliver, not after I leave
- Documentation that teaches
- Not just specs; documents that help future readers understand the "why"
The philosophy:
The best consultants make themselves unnecessary. I structure engagements so your team gains capability, not just deliverables. The goal is that six months later, you're better positioned than when we started, whether we continue working together or not.
Technical Leadership
I've led projects with budgets up to 250k€, coordinated shared laboratories, trained apprentices, and served as the technical reference point for engineering organizations.
What I provide:
- Project management that works
- Planning, milestone tracking, risk management; practical approaches, not bureaucratic process
- Technical authority
- I've been the person everyone comes to with hard questions; I know how to provide clarity, not just answers
- Team development
- Experience training apprentices and junior engineers means I can grow your team's capabilities
- Cross-functional coordination
- Working between hardware, software, and business stakeholders to keep projects aligned
- Risk identification
- Pattern recognition from projects across industries means I see problems coming before they arrive
The value:
Technical leadership isn't having all the answers. It's spotting what matters, communicating it clearly, and keeping teams focused on the right problems. That's what I've learned from leading projects across industries.
Case Study: Industrial Robotics Innovation
Challenge: Develop a production machine for generator stator winding, a complex mechanical system requiring precise software control.
Solution: Led development of CAD-to-tooling software that automated the programming process, enabling rapid configuration for different winding patterns.
Outcome: 2nd place in Alstom Innovation Awards 2014 (Innovative Processes category). Technology deployed to production environment.