Embedded Firmware Engineer

The role As an Embedded Firmware Engineer, you will play a key role in developing and improving the firmware running our chargers. Our system consists of two independent embedded systems that must work seamlessly together. One handles safety and power control. The other handles communication and backend connectivity. This is not typical embedded work. It is system design, timing, and precision in practice. What you will work on You will work across the stack. Typical responsibilities include: ☑ Developing firmware across both safety-critical and communication-focused components ☑ Designing and improving communication between two MCUs ☑ Working with real-time logic, state machines, and fault handling ☑ Writing and maintaining hardware drivers (UART, SPI, I2C, GPIO) ☑ Ensuring reliable backend communication via OCPP ☑ Working on OTA updates and system robustness in the field ☑ Debugging at a low level using proper tools, not just logs Technology and architecture The system is split into two parts: • Safety / Power controller (nRF5340, Zephyr) • Communication / App controller (i.MX RT1061, ThreadX) They communicate through a custom protocol focused on determinism and consistency. Backend communication is handled via OCPP over WebSocket. Company momentum Amina Charging is in a strong phase of development and growth: → Employee-led acquisition of the company, with continued support from existing owners → New contract signings driving further expansion → Technology collaboration with a world-leading player in power metering Who we are looking for You do not need to check every box, but this gives a good indication: ☑ Experience with C or C++ in embedded environments ☑ Familiarity with an RTOS (Zephyr, FreeRTOS, ThreadX or similar) ☑ Understanding of real-time systems, timing, and resource constraints ☑ Experience with hardware-level protocols (UART, SPI, I2C, CAN) ☑ Ability to read datasheets and work close to hardware ☑ Hands-on debugging experience in embedded systems Nice to have Not required, but a plus: • Experience with Nordic or NXP platforms • Familiarity with OCPP • Experience with OTA updates on constrained devices • Interest in distributed systems or consistency challenges • Python or scripting for tooling Why this role is interesting This is not a role where you just implement tickets. You will work with: → A fully in-house architecture → Real technical trade-offs → Systems that must work in real-world conditions The team is small, and decisions are made close to the problem. What you build moves quickly from code to physical hardware in the field. EV charging is growing fast. The quality of systems varies. This is a chance to build something that actually holds a high standard.