Embedded Firmware Engineer for Secure Storage Device (Prototype)

@engrusmanfaiz

I can develop the firmware for your secure storage prototype using an STM32-based architecture with secure element integration and encrypted storage handling. I have 12+ years of experience in embedded firmware, STM32 systems, USB devices, and secure embedded applications. My experience includes AES encryption, secure communication, bootloaders, and low-level hardware integration. I can integrate ATECC608B or SE05x for protected key storage and authentication. The firmware will support encrypted internal/QSPI storage with secure key management. I will implement USB mass storage functionality with controlled secure access logic. The system can include PIN retry limits, anti-bruteforce protection, and secure boot architecture. I am experienced with mbedTLS and embedded crypto APIs for Cortex-M devices. The codebase will be clean, modular, and suitable for future expansion such as ML-KEM or advanced crypto layers. I can also review hardware interfaces early to avoid firmware and security bottlenecks during prototyping. Ready to collaborate through architecture planning, implementation, testing, and prototype validation.

@rashidamjad

As a seasoned Embedded Firmware Engineer with a deep knowledge of the STM32 platform, I am eager to offer my expertise towards developing firmware for your secure storage device prototype. Having successfully designed and implemented similar solutions in the past, I am confident in my ability to exceed your expectations. What sets me apart is my hands-on experience with secure elements like the SE05x and ATECC608B and my proficiency in implementing AES encryption for internal flash or external QSPI. Furthermore, I am comfortable with essential crypto APIs (e.g., mbedTLS, wolfSSL) and firmly understand anti-bruteforce measures. This aligns perfectly with your project requirements ensuring a secure, reliable, and scalable solution. In terms of previous projects, I have worked extensively on embedded systems, IoT devices, and hardware-software interfaces which are heavily relevant to the success of your project. My rates are competitive but as an investment that will ensure a robust product that stands up to any security test you can throw at it. With clear communication being one of my hallmarks and dedenable delvierables throughout the project available to you put me one step ahead of other applicants. I look forward to discussing this opportunity further!

@tshibsamuel477

Hi there, I carefully read your project description and clarifications, and this is the type of embedded security-focused work I’m comfortable with. I have experience with STM32-based systems, secure firmware design, encrypted storage flows, USB interfaces, OLED UIs, and low-level embedded development in C/C++. Your STM32H5 direction makes sense, especially considering the hardware crypto accelerator, TRNG, and PSA certification goals. I can help implement the firmware side cleanly while respecting your existing security architecture and keeping the trusted code base minimal. I’ve also already worked with similar embedded architectures and security-oriented components, including secure elements and encrypted storage handling. I’m Samuel Tshibangu, a mechatronics engineer with several years of hands-on experience in embedded firmware, STM32 development, PCB/system integration, and hardware-software debugging. I’m comfortable working bare-metal or with lightweight RTOS approaches depending on the final security/performance tradeoff. I can contribute not only implementation work, but also practical implementation-level security feedback during development to help avoid issues early. Feel free to message me so we can discuss the architecture and timeline. Best regards, Samuel Tshibangu

@majeed219

With a profound passion for embedded systems and in-depth expertise in STM32, I'm thrilled to express my interest in your Secure Storage Device project. I believe my extensive experience in ARM Cortex-M based firmware development aligns perfectly with your requirements. Throughout my career, I've successfully integrated platforms with secure elements for key storage and have a solid grasp of AES encryption APIs like mbedTLS and wolfSSL. My skillset also extends to devising simple user interfaces on OLED displays, which could prove fruitful for your device's UI requirements. Although I may not possess direct experience with the SE05x or ATECC608B, my ability to read datasheets, unravel complexities, and quickly adapt has always been touted as a strong suit. Moreover, my previous exploration of secure storage devices akin to hardware wallets bolsters my understanding of the challenges at hand. Additionally, beyond firmware development, I can bring value in spotting potential hardware issues early on due to my hardware design sensibilities. My hourly rate is quite competitive without compromising excellence, and you can be assured of consistent progress throughout our collaboration. Let's discuss the budget and availability details so we can hit the ground running on this exciting venture!

@umg536

Hi, This is exactly the kind of embedded security project my team and I work on regularly. We have experience building STM32-based embedded systems involving secure communication, encrypted storage, BLE/USB interfaces, secure boot flows, and hardware-level protection mechanisms for commercial and prototype devices. For your PoC, we can help architect and develop the full firmware stack including secure element integration (ATECC608B / SE05x), encrypted file storage, USB mass storage handling, OLED UI flow, secure authentication logic, and anti-bruteforce protections. We are comfortable working with STM32 HAL, low-level drivers, FreeRTOS if required, and crypto stacks such as mbedTLS and wolfSSL. We also have experience reviewing PCB designs alongside firmware development to catch hardware-security and manufacturability issues early. A strong architecture phase is critical for devices like this because storage encryption, boot integrity, key handling, and recovery logic all need to work together securely from day one. We can assist with secure boot chain design, AES-based encrypted storage, key derivation strategy, firmware update flow, and overall threat-surface reduction for the prototype stage.

@yuliussmayoru

Hey there! Secure storage prototypes like this usually go wrong when key handling, secure element integration, and USB UX are treated as afterthoughts, so I’d approach it by nailing the threat model, key hierarchy, and SE wiring first, then layering storage and UI on top. I’m comfortable working in the STM32 ecosystem, using HAL or low level drivers, wiring up peripherals like QSPI flash and USB MSC, and then building a thin, well structured firmware layer instead of a monolithic blob. The way I’d think about this device is as a small, opinionated secure appliance: secure element as root of trust, AES based file encryption with per device keys derived from SE secrets, secure boot to protect firmware integrity, and a simple OLED plus buttons UI that keeps user flows predictable. I’ve worked with crypto APIs, key derivation patterns, and embedded constraints enough to keep the design practical rather than “crypto fancy but unmaintainable,” and I’m used to reading datasheets and adjusting when reality does not match the first plan. I like projects where there is room to make sensible architecture decisions and build something you can actually demo without having to apologize for security shortcuts.