I used to lead projects bringing an electronic product from concept to the production line. I used to design hardware and software where safety and reliability were an absolute must. I used to guide small groups of people to get it done.Then I started a new journey: the Strategic Sourcing and Cost Improvement for Electronic products. In dedicated team, I was responsible to monitor and keep on track the cost improvement projects, both when it meant to change the product as well as when it means to act on sourcing or localization.And now? Now I integrate. As a system engineer my role is to let it work: external suppliers with internal projects timelines, electronics with mechanics, our product with the customer's needs... Only together things (and people) can reach the excellence!I am an engineer, and like engineers, I enjoy in problem-solving. I like to try always the next step and I am enthusiast when I can learn new skills, or develop new solutions, especially when done together with people around me.And here is a story I sometimes like to share:Once upon a time.. it was a Thursday; I was very proud of something I did in my firmware. I don't remember what was the topic, but I remember what happened after.I was happy for my success and so, "as usual", I was walking in the office yellowing around: "I am the best! I made it!"... Well... After not more than 90 seconds, I was clumsily able to spill a glass of water on the main supply of my board under test, causing a "short-circuit-resulting-in-a-building-black-out".Nobody was ever able to replicate such devastating failure mode... yet. Nobody has it yet actually explained: usually only the test bench protections are triggered in such cases.Anyway... since then, still now (and some years are passed), when I share some success in the office... well my colleagues immediately save their work before proceed with anything else...