Electronic Products, Machines & Test Systems
I help companies develop, integrate and evolve electronic products, machines and test systems until they work reliably and can be verified.
Where system risk begins
The hardest problems rarely belong to a single discipline. They often emerge during integration, at interfaces, or when the product meets the real system.
Electronics, firmware and software appear correct in isolation, but integration exposes incompatibilities or unexpected behaviour.
Everyone sees their own piece, while the root cause ends up outside everyone’s scope.
Wiring, loads, interference and operating conditions expose problems that the development setup never revealed.
Architecture, interfaces and responsibilities across hardware, firmware and software need to be clarified before changing them becomes expensive.
The system appears to work, but testing, diagnostics and acceptance criteria are not yet strong enough to prove it.
Existing interfaces and poorly documented knowledge make it risky to integrate new functionality within existing constraints and dependencies.
The problem can span electronics, firmware, communications, software and testing. My job is to follow it through the relevant layers until the different parts come together in a working system that can be verified.
What I do
I can address a specific problem, take responsibility for part of the system or support your team on an ongoing basis, through integration and verification on the real system.
When
How I help
Outcome
When
When architecture, technical choices or requirements are still unclear, or you need to decide how to proceed before investing more time in development.
How I help
I analyse the system, constraints, interfaces and alternatives. Where needed, I work directly with schematics, firmware, signals, protocols and existing setups to build an assessment grounded in evidence.
Outcome
When
When the system does not behave as expected, the cause is unclear, or hardware, firmware, software and devices work separately but not together.
How I help
I reproduce the problem, measure what is happening and trace the cause across the layers involved, making changes where needed to electronics, firmware, communications, software or the test setup.
Outcome
When
When the product needs to evolve and part of it must be designed, adapted or extended without compromising the rest of the system.
How I help
I start from requirements and interfaces with the rest of the system, then work directly on the parts needed: electronics, firmware, embedded software, protocols, diagnostics and supporting tools.
Outcome
When
When development, troubleshooting or production still relies on manual checks, implicit knowledge or setups that are difficult to reproduce.
How I help
I design diagnostics, fixtures, HIL systems, measurement tools and software automation. As the product moves towards production, I also address testability, manufacturability, programming, production testing and technical coordination with suppliers and partners.
Outcome
I’m Bernardo Destito, an electronic engineer working independently.I work with companies developing electronic products, machines and test systems.
I like working close to the real system: schematics, firmware, signals, instruments, software, sensors and actuators. Over the years, this has taken me across industrial systems, building automation, connected products and test systems.
My way of working is practical: understand the problem, observe and measure what is happening, keep the solution as simple as the problem allows, and build the tools needed to verify it.
I usually work directly with R&D teams, founders and engineering companies. I can take responsibility for a defined subsystem, a difficult problem or a broader development path, especially when continuity across different parts of the project matters. When needed, I can also coordinate suppliers or external partners to reach the result.
Tell me what you are building, where the project stands and what result needs to be achieved.
