Software engineer, BEng in Software Technology from VIA University College. I live both in Horsens, Denmark and Budapest, Hungary.
I work closest to the machine: embedded firmware, backends, data pipelines, and the infrastructure that holds them together. I've built the web and mobile front ends for most of my projects too, and app development is something I'd happily do more of.
ghanode_ze_si917 — Wi-Fi sensor-node
firmware in C for the Silicon Labs SiWx917, on Zephyr, and the thing I'd point at first.
A sensor thread samples every 20 s; a network thread publishes JSON over MQTT with TLS at
QoS 1. Every reading carries its UTC time from SNTP, so readings queue through outages
of up to ten minutes and still arrive with the right time. A recovery ladder restarts
Wi-Fi and, as a last resort, resets the MCU; I tested it on the board by hanging the
broker and switching the access point off. 33 unit tests on native_sim run in CI. The
earlier FreeRTOS version, ghanode_si917, has a
README that walks through the reconnect bugs found the same way.
GHA — my bachelor project. Sensor nodes published readings over MQTT; Logstash validated and normalised them into OpenSearch, routing anything malformed to a separate error index instead of dropping it; a React frontend showed each user their greenhouses with embedded Grafana panels, behind Keycloak SSO and an nginx reverse proxy. Ten containers under Docker Compose on a private server, since shut down. Two CI workflows gated it, one of which built the whole stack and ran integration tests against the live pipeline. Built with one teammate, where I was tech lead.
SEP4IOT — telemetry firmware in C on an Arduino Mega 2560. It reads temperature, humidity and light, encrypts the telemetry with AES-128, validates it with CRC16, and exchanges it with a cloud backend over WiFi and HTTP, with a cooperative RTOS scheduling the tasks and timers. Unit tested with Unity. I was tech lead and product owner of a seven-person team on this project and wrote the firmware myself. It was also a greenhouse system — I ended up solving the same problem again eighteen months later for my bachelor with a completely different architecture, which taught me more than either project did alone.
avr-thermostat-cpp — a bare-metal thermostat in C++ for the ATmega328P, written directly against the registers with no Arduino framework and no heap. Every driver sits behind an interface with a hardware implementation and a mock, so the same control logic runs on the target and in 87 host tests. It drives a pump through a relay, keeps its setpoints in EEPROM, and fails safe when the sensor lead breaks. It rebuilds a C assignment from my hardware-oriented programming course (HWP1) with interfaces, mocks and CI.
DeliriumApp — an internship at VIA University College building an offline-capable reference app for nurses caring for delirium patients, with a real client. I was tech lead. I built the WordPress content platform and the JavaScript behind the CAM and B-CAM screening tools, and set up the initial React Native structure before handing the mobile work to a teammate. The client presented the prototype at the International Council of Nurses 2025 conference.
ViaEventAssociation — a solo C# event-handling system for organising events on campus, built with domain-driven design on an onion architecture, using the builder, REPR and unit-of-work patterns, with a unit test suite behind it.
ChatRMI — a JavaFX chat application where the client reaches the server through a single interface with two implementations: Java RMI and raw TCP sockets. The server runs both at once and pushes new messages to every client over UDP multicast, so it never needs to know which transport a given client arrived on.
Assignment4-Kingdom — a
multithreaded Java simulation of a treasury: producer–consumer between the miner and
the transporters over a monitor, and readers–writers on the treasure room with a
ReentrantReadWriteLock.
Languages — C (embedded), C++, C#/.NET, Java, Python, JavaScript, TypeScript
Embedded — Zephyr, FreeRTOS (CMSIS-RTOS2 API), RTOS scheduling, PlatformIO, interrupt-driven I/O, ADC, hardware PWM, UART, I2C, Wi-Fi modules, EEPROM, CRC and AES validation, fixed-point arithmetic, host-and-target testing
Infrastructure — Docker and Docker Compose, nginx, GitHub Actions, Azure, Keycloak
Data — MQTT (Mosquitto), Logstash, OpenSearch, Grafana, PostgreSQL, SQLite, PocketBase
Testing — unit, integration and on-board; Zephyr ztest and Twister, Unity, Jest, pytest, JUnit
Ways of working — Scrum, Kanban, UP, TDD, DDD
I use coding agents daily and have specific opinions about where they help and where they don't. The short version: they're fast, they're confidently wrong about anything they can't see — your database schema, your runtime, a niche query language — and the job is knowing which kind of failure you're looking at. I'm happy to go into detail in an interview.
- Email: hockdanield@gmail.com
- LinkedIn: hock-daniel
- Languages: Hungarian (native), English (professional working proficiency), Danish (basic)
