Hire the Best Embedded Linux Specialists
in Egypt

Your prototype works on the bench. The first time a real customer plugs it in, it falls over — Wi-Fi setup fails, the firmware locks up after a week, the battery dies in three days instead of three months. That's the gap I close. I'm an embedded systems and IoT engineer. I take connected devices from "it works for me" to "it ships to customers and survives in the field." Most of my work falls into three areas: Embedded firmware on ESP32, STM32, nRF52, RP2040, AVR, and Raspberry Pi. C/C++ and Python. FreeRTOS and bare-metal. Low-power design when battery life matters — pushing sleep currents into single-digit µA, debugging the wake-up paths, tracking down the rogue peripheral that's keeping your device awake. Connectivity across BLE, Wi-Fi, MQTT, LoRa, LTE-M, NB-IoT, CAN, RS-485. Consumer IoT and headless devices. Captive-portal Wi-Fi onboarding so a non-technical customer can set up the device from their phone. Systemd watchdog services that recover from network drops automatically. OTA update infrastructure for fleet deployment. SD card write minimization on Linux-based devices, because the field failure mode no one warns you about is filesystem corruption six months in. PCB design when the project needs it. 2 to 8 layer boards in KiCad and Eagle, IPC-2221/7351 compliant. DFM and DFT review baked in from the schematic stage. Signal integrity, RF layout, and the kind of board-level decisions that affect yield, cost, and certification much more than firmware ever will. A few things worth knowing about how I work: I'm honest about scope. If your project doesn't need a custom PCB, cloud infrastructure, or edge ML, I'll tell you. I'd rather build the right thing for your actual budget than oversell. I think about the device's whole life, not just the demo. SD card longevity, Wi-Fi recovery, what happens when your customer's router changes, what happens when the firmware bug shows up in month six. The failure modes that matter are rarely the ones that show up on day one. I document for the human who comes after me. The setup guides and handoff docs I write are aimed at a non-technical reader — your future self, your in-house team, or whoever takes ownership when the contract closes. If you're building a connected device and the path from working prototype to shipping product isn't obvious yet, send me a message with what you're working on. I'll tell you honestly whether I can help.

𝗠𝗟 𝗘𝗻𝗴𝗶𝗻𝗲𝗲𝗿 with 3+ 𝘆𝗲𝗮𝗿𝘀 𝗼𝗳 𝗲𝘅𝗽𝗲𝗿𝗶𝗲𝗻𝗰𝗲 transforming raw data into powerful AI solutions. I specialize in building 𝗰𝘂𝘀𝘁𝗼𝗺 𝗠𝗟/𝗗𝗟 𝗺𝗼𝗱𝗲𝗹𝘀 for 𝗖𝗼𝗺𝗽𝘂𝘁𝗲𝗿 𝗩𝗶𝘀𝗶𝗼𝗻 & 𝗡𝗟𝗣, tailored to real-world startup and production needs As a 𝗠𝗲𝗰𝗵𝗮𝘁𝗿𝗼𝗻𝗶𝗰𝘀 𝗚𝗿𝗮𝗱𝘂𝗮𝘁𝗲, I focus on (𝗧𝗶𝗻𝘆𝗠𝗟) 𝗯𝘂𝗶𝗹𝗱𝗶𝗻𝗴 and 𝗱𝗲𝗽𝗹𝗼𝘆𝗶𝗻𝗴 𝗔𝗜 𝗺𝗼𝗱𝗲𝗹𝘀 𝗼𝗻 𝗲𝗺𝗯𝗲𝗱𝗱𝗲𝗱 𝘀𝘆𝘀𝘁𝗲𝗺𝘀, from data preprocessing and model training to deployment, including 𝗿𝗲𝗮𝗹-𝘁𝗶𝗺𝗲 𝗥𝗧𝗦𝗣 𝗰𝗮𝗺𝗲𝗿𝗮 𝘀𝘁𝗿𝗲𝗮𝗺𝘀, delivering intelligent, scalable solutions with real-world impact

Top-Rated Embedded Engineer, 40+ projects shipped. I build STM32/ESP32 firmware, PCB designs, and custom PySide6/Qt desktop tools that turn hardware concepts into products. Most hardware projects stall in the gap between the silicon and the software that has to drive it. That's exactly where I work, I take a project from schematic and PCB layout, through low-level firmware, all the way to the desktop application your team uses to configure, test, and visualize the system. What I build: • Firmware & embedded C/C++ - STM32 and ESP32 development, from bare-metal drivers to production firmware, with hardware bring-up and debugging. • Hardware & PCB - DFM-ready schematic capture and PCB layout in Altium and KiCAD, designed alongside the firmware so the two actually fit. • Desktop tools & GUIs - Native PySide6 / PyQt / C++ applications purpose-built for hardware interfacing, instrument control, data visualization, and automated test. • Automation & reliability - Self-hosted n8n pipelines with custom Python/JavaScript, plus CI/CD, Git, and automated unit testing across C and Python codebases. Because I own both sides - the hardware and the software that controls it, you don't have to coordinate two contractors who blame each other when something doesn't talk. You get one engineer accountable for a working, production-ready system. If you've got an embedded product, a test rig, or a hardware-control tool that needs building, send me the details and I'll tell you straight whether it's a fit and how I'd approach it.

Embedded Systems | Embedded Linux & Android Systems Engineer | Linux · Yocto · Qt/QML · AOSP · Android Automotive · Android Development · ADB Automation · C/C++ · Python · Java · Kotlin If you're building a product that runs Linux or Android under the hood - from an embedded device to an infotainment system - and you need someone who understands every layer from the hardware up, I can help you ship it. I specialize in the space most engineers avoid: the gap between hardware and the software stack. That means I can trace a boot failure to a kernel driver, customize an AOSP build from scratch, fix a VHAL service that drops vehicle signals, or write Python tooling that replaces hours of manual ADB work across a fleet of devices. What I work on: - Embedded Linux - Yocto, BSP bring-up, driver development, cross-compilation - AOSP builds and system-level customization (permissions, overlays, HALs, system services) - Android Automotive OS - VHAL, AIDL interfaces, CarService integration - Python ADB automation - multi-device control, test frameworks, CI scripting - Android app development in Kotlin/Java when the project needs it - Boot, performance, and crash debugging across hardware and software layers - Docker environments for reproducible builds and clean dev workflows Why this matters for your project: Most engineers are strong at one layer - app, firmware, or Linux. I work across all of them. That means I catch integration bugs that fall between teams, and I can translate clearly between hardware and software sides so nothing gets lost. Recent work includes Android Automotive infotainment systems, AOSP-based product customization, and Python automation tools for multi-device QA workflows. If you're dealing with a system-level issue, need an embedded Linux or Android build customized, or want automation that actually works at scale - let's talk.

Sr. Principal Embedded Software Engineer with 12+ years of experience, Extensive record of Architect, Developing, testing and Leading Embedded Systems Activities. Main experience includes Embedded C, Building Firmware, Device Drivers, low-level programming, Xilinx SoC Architecture, participate in ADAS ECU development. Reading datasheets, Hardware schematic analysis, and debugging with HW design team. Experience in handling large teams, and I can work independently as well. Relevant experience (Development): - Programming Skills: C/C++, Embedded C, Assembly, Python. - HW Platforms : Renesas RH850, Zynq ultrascale+, FPGA, ARM Cortex M3/4, Atmel, PIC, STM32, TI MSP430, ESP32 - Protocols/Peripherals : SPI, I2C, CAN, LIN, Ethernet Lightweight TCP/IP, UART, PWM, ADC, DAC. - Tools/IDEs : WinIDEA, Eclipse IDE, Xilinx ISE/SDK, MPLAB X, STM32CubeIDE, Code Composer Studio, VS Code, CANoe. - Hardware Packages : iSystem Debugger, CAN Case, Logic Analyzer, SPI Tracer, Oscilloscope. - Configuration & Requirement Mgt. : Core ALM, Gerrit, Git, Tortoise SVN, Serena Dimensions, DOORs, Bugzilla Proven experience as a QA Engineer, Systems analyst/tester and I have in-depth knowledge in various domains. Relevant experience (Testing): * ISTQB® Foundation Level Certified Tester * Develop test plans, Preparing and executing test cases, Bug reporting, User experience, Perform result analysis * Perform different kind of testing (functional, localization, exploratory smoke, sanity, regression, user-interface, end-to-end, .. etc) for Web, Desktop, and Mobile applications * Browser logs (Desktop/Mobile) - Mobile devices logs (Android/IOS) * Web debugging proxy for desktop and mobile (Charles proxy & Fiddler) * API testing * Tools: (Jira / Trello)

✅ Responds within 10 to 15 minutes ✅ Among the Top 3% of Upwork Freelancers with consistent 5-star ratings ✅ 30+ production systems shipped using ESP32, STM32, nRF52, Yocto, Zephyr RTOS, Linux Kernel, including ISO 26262 safety-critical projects 8+ years building production-grade C/C++ firmware for several Embedded Systems, IoT devices, and industrial systems. from first prototype through certification and manufacturing. ── WHO I WORK WITH ── Whether you're a startup bringing a hardware product to market, an OEM needing automotive-grade embedded software, or an IoT company scaling a connected device. I deliver clean, testable firmware that passes certification and works in the field. ── WHAT I DELIVER ── ✅ Rapid prototyping: from concept to working proof-of-concept in weeks, not months ✅ Production firmware for automotive systems: AUTOSAR (Classic & Adaptive), CAN/J1939, LIN, ISO 26262 functional safety ✅ IoT device firmware: ESP32, BLE, WiFi, MQTT, OTA updates, sensor integration, low-power design ✅ HMI/display development: Qt/QML touchscreen interfaces on embedded Linux platforms ✅ RTOS-based systems: Zephyr, FreeRTOS, bare-metal, real-time performance on ARM Cortex-M and embedded Linux ✅ Documentation & standards: SRS, SAD, ICD, MISRA-C, traceability for safety-critical projects ── CORE TECHNICAL STACK ── Languages: C, Embedded C, C++17, Python MCU/Platforms: ESP32, STM32, ARM Cortex-M, Raspberry Pi, Infineon AURIX, Nordic nRF RTOS & OS: Zephyr, FreeRTOS, Embedded Linux, QNX Protocols: CAN, J1939, LIN, UART, SPI, I2C, BLE, WiFi, MQTT Standards: AUTOSAR Classic & Adaptive, ISO 26262, MISRA-C Tools: Git, CMake, STM32CubeIDE, ESP-IDF, PlatformIO, MATLAB/Simulink, Qt/QML ── HOW I WORK ── You'll get regular progress updates, clear documentation, and no surprises. I scope honestly, flag risks early, and deliver tested, production-ready code. I'm available for overlap with US, EU, and MENA teams. ── LET'S TALK ── Send me a message with your project brief and timeline. I'll respond within a few hours with an honest assessment of whether I'm the right fit and if I'm not, I'll tell you that too.