Hardware, firmware, FPGA design, diagnostics and test automation — as a fixed-price contract with firm delivery commitment, or as an hourly budget for ongoing projects.
Embedded projects often demand several disciplines at once: a circuit must be designed, a microcontroller programmed, an FPGA verified and a test setup built. Instead of orchestrating a supplier chain, you can bring these tasks together in a single hand. That saves interfaces, coordination effort and diffusion of responsibility.
Below are the six service areas in which I work. They are not intended as a catalogue — most projects combine several of them.
Design and development of electronic assemblies and devices — from analogue circuits to FPGA design. Microcontroller- and FPGA-based systems from one source, including schematic, PCB layout, firmware and hardware-near driver development. On request, all the way to series production via established partners.
Systematic development from the mathematical model to the implementation in hardware. Algorithms are first modelled in pseudocode or Matlab, then implemented in C/C++ for microcontrollers or in Verilog/SystemVerilog for FPGAs — depending on the target platform and real-time requirements.
Development and testing of diagnostic concepts and communication interfaces for vehicle ECUs. Experience with the bus systems established in the automotive environment (CAN, CAN FD, MOST) and with UDS diagnostics per ISO 14229.
Systematic verification of embedded systems — from test specification to series release. Test setups are built so that the client team can operate and extend them independently after the project ends.
Companion software for embedded systems: configuration interfaces, dashboards, data visualisation and mobile apps. This layer is often underestimated — yet it determines how an embedded system is perceived by the end user.
When an ongoing embedded project needs additional substance — at bottlenecks, with inherited code bases, or with tricky detail questions — I support in a focused and time-flexible way. This form of cooperation is particularly useful when it is clear what is needed but not how much of it.
Embedded projects rarely fail on individual technical tasks. They fail because of unclear requirements, incomplete documentation, missing evidence against standards, and status reports that obscure more than they clarify. On request, I take on not only the development itself, but also the methodical steering of the project — from the first conversation to acceptance.
On the blog: Project Management for Embedded Projects — Why the Hardest Work Lies Before the First Schematic
I offer project management only in conjunction with technical responsibility — as part of an end-to-end development, or to accompany a team led by the client. Pure coordination without technical depth is not part of my offering.
Two contract models, depending on the project type:
No personnel leasing. Details on the Engagement page.