Embedded Software & Data Connectivity Engineer – HCMC, Vietnam

We’re Attacan GmbH, an engineering partner that brings electronic products from idea to mass production. We design electronics, mechanics, and embedded software, connecting devices to the cloud and data systems. Our projects range from prototypes for startups to industrial-grade series products.

We’re expanding our software team in Ho Chi Minh City and seeking an Embedded Software & Data Connectivity Engineer who loves working with hardware and real-world devices.

Your Mission: Build the Brains of Our Products!

You’ll be at the heart of our product development, crafting the software that makes our electronics smart and connected.

Here’s what you’ll do:

• Embedded Software Wizardry: Develop and implement firmware for microcontrollers and embedded systems. You’ll create drivers, optimise interfaces (UART, SPI, I²C), and ensure our software is real-time, reliable, and robust.
• IoT & Connectivity Guru: Design communication interfaces for IoT devices (MQTT, HTTP, Modbus) and integrate wireless tech (Bluetooth, Wi-Fi, LoRa). You’ll ensure secure and seamless data flow between devices, cloud platforms, and local servers.
• Observability & Backend Integration Expert: Develop and maintain data-visualization and monitoring pipelines using tools like Grafana and InfluxDB (or similar). You will design efficient data flows from embedded devices into backend systems, build dashboards for real-time sensor monitoring, and support backend scripting for data collection, transformation, and alerting. Experience with REST APIs, lightweight backend services (e.g., Python/Node.js), and system-level metrics is highly valued.
• Data Architect: Design and maintain databases for sensor data and logs, building the bridges between our embedded systems and data storage (MySQL, PostgreSQL, SQLite).
• Quality Champion: Test, debug, and refine software using advanced tools (JTAG, logic analyzers) to ensure flawless performance.
• Collaborative Creator: Work closely with hardware engineers and clients to define requirements and shape our product architectures.
• Web Enthusiast (Bonus!): Help modernise our company website (WordPress/Typo3) if you have the skills or interest.

Who We’re Looking For

Are you passionate about embedded systems and data, with a knack for problem-solving?

You’re a great fit if you have:

• A degree or solid experience in Computer Science, Electrical Engineering, or Embedded Systems.
• Strong skills in C, C#, C++, Python, and SQL.
• Experience with RTOS, embedded Linux, or database systems (MySQL, PostgreSQL, SQLite) is a big plus.
• A love for working close to hardware and understanding the full system.
• A systematic, precise, and reliable approach to engineering.
• Good English skills (spoken and written) for international team collaboration.

Why Join attacan GmbH?

• Work on diverse, impactful projects that bring real products to life.
• Flexible employment (full-time or part-time options).
• Collaborate directly with senior engineers in Germany and Vietnam.
• Shape your role: dive deep into embedded, explore data systems, or even contribute to our web presence.
• Be part of a culture that values engineering quality, curiosity, and responsibility.

Ready to build the future of connected electronics? Apply now!

Job Types: Full-time, Part-time, Contract

Application Question(s):

• Please describe one or two embedded projects where you developed firmware for microcontrollers (including which MCUs you used, interfaces like UART/SPI/I²C, and how you ensured reliability/real-time behaviour). What was the application and your exact role?
• What practical experience do you have connecting embedded devices to cloud or backend systems (e.g. MQTT, HTTP/REST, Modbus, Bluetooth/Wi-Fi/LoRa)? Please give a concrete example, including how data was stored or processed (e.g. MySQL/PostgreSQL/SQLite).
• We develop and produce real electronic products. Can you describe a situation where you debugged a complex issue on an embedded system using tools such as JTAG, logic analyzers or protocol analyzers? What was the problem, how did you approach it, and what was the final fix?